What a good consultant does, and what they don’t
ISO 27001 is a management system standard. The certificate says your organisation runs a working ISMS: it understands its risks, has chosen controls for good reasons, operates them and checks they work. A consultant’s job is to get that system built and running in a way that fits your business, then step back so you can run it.
In practice, a good consultant:
- Sets the scope with you. They tie it to what your customer or tender actually requires, so you certify what matters rather than the whole business by default.
- Runs the risk assessment properly. They bring a method, facilitate the conversations and make sure the results reflect your business, not a generic register. See ISO 27001 risk assessment.
- Writes documents that match how you work. Policies your people can follow, and a Statement of Applicability with a reason for every decision.
- Tells you exactly what evidence is needed, then checks it before an auditor sees it.
- Prepares you for Stage 1 and Stage 2 and supports you through any findings. See what happens at Stage 1 and Stage 2.
A good consultant doesn’t certify you, run your systems or make your risk decisions for you. Clause 5 puts leadership commitment on top management, and the risk owners must accept residual risk themselves. A consultant who quietly makes those calls leaves you with a system nobody inside understands, which shows up quickly at the certification audit when the auditor interviews your people.
Consultant, platform and certification body: who does what
Three kinds of outside party can be involved, and they are often confused. Getting the roles straight is the first filter for any proposal.
| Consultant | Compliance platform | Certification body | |
|---|---|---|---|
| What it is | An advisor who helps you build and run the ISMS | Software that connects to your systems, tracks controls and collects evidence | An accredited, independent organisation that audits you against the standard |
| Main job | Scope, risk, documents, control design, internal audit, audit preparation | Automated evidence, monitoring, policy templates, auditor access | Stage 1 and Stage 2 audits, the certification decision, surveillance audits |
| Can it certify you? | No | No | Yes, and only an accredited one counts |
| Who engages it | You | You | You, directly |
| Must be independent of the others? | From the certification body, yes | No | Yes. It can’t consult on the system it certifies |
Whether you need a platform, a consultant or both is a separate decision, covered in consultant, platform or both? and choosing a compliance platform.
The questions to ask
1. Have you taken organisations like ours through certification?
Ask for experience that matches your size, industry and setup: a cloud-first SaaS company, a professional services firm with an MSP, a business with its own developers. Ask how many of their implementations reached certification, and what the certification audits found. A consultant who has seen the full journey many times knows where projects stall. If they can’t talk specifically about past audits without breaching confidentiality, that is fine; if they can’t talk about them at all, it isn’t.
2. Who will actually do the work?
The person who runs the sales meeting is not always the person who writes your risk assessment. Ask who leads the engagement, who drafts the documents and who you will speak to each week. Ask for that person by name and what happens if they leave. Continuity matters: the consultant who scoped your ISMS should be the one who prepares you for the audit.
3. What are your auditing credentials?
An ISO/IEC 27001 Lead Auditor qualification from a recognised training scheme shows the person understands how certification audits are run and what auditors look for. It’s a sensible baseline, not a guarantee of quality. Ask whether they have actually audited, either for a certification body in the past or as an internal auditor, and whether they keep up with the 2022 edition and Amendment 1:2024, which added climate change considerations to clauses 4.1 and 4.2.
4. How will you set our scope and run the risk assessment?
These two decisions drive everything else: the effort, the audit days and how useful the certificate is to your customers. A good answer explains how they will connect scope to your sales trigger, which interfaces and suppliers sit at the boundary, and what risk method they use and why. A weak answer is “we’ll use our standard register” or “we usually scope the whole company”.
5. What will we own at the end?
You should own every document produced for your ISMS, in editable formats, with no licence that expires when the engagement ends. If a platform is used, the account should be in your organisation’s name. Ask too what your team will be able to do on their own afterwards: run a management review, update the risk register, handle a new supplier. The aim is a system you can run, not a dependency.
6. Have you worked with our compliance platform?
If you already use Vanta, Drata, Secureframe or similar, your consultant should know how to work inside it: which tests matter for ISO 27001, which templates need rewriting and what the platform can’t evidence on its own. If you don’t have a platform, ask whether they think you need one and why. An honest answer can go either way.
7. How do you stay independent of the certification body?
ISO/IEC 17021-1 forbids certification bodies from offering management system consultancy, and an auditor who has consulted for you can’t audit you for at least two years. Ask whether the consultant has any commercial arrangement with the certification body they recommend, such as referral fees or a shared ownership. Ask who the certification body’s contract is with. It should be with you directly, and its fees should not be bundled into the consultant’s quote.
8. How is the internal audit handled?
Clause 9.2 requires internal audits to be objective and impartial. If the consultant offers the internal audit, ask who performs it. It should be someone who didn’t build the parts they are auditing, ideally with Lead Auditor experience, so it tests your system the way the certification body will. See the ISO 27001 audit cycle for when internal audits fall each year.
Red flags
- Promising certification or a “guaranteed pass”. Nobody but the certification body decides. Some firms use “guarantee” to mean they will keep supporting you until you are certified. That is a reasonable commitment; promising the outcome is not.
- Template-only document packs. Templates are a starting point. A pack of generic policies with your logo on them doesn’t reflect your risks, and auditors spot policies nobody follows. See which documents ISO 27001 actually requires.
- A consultant who is also your certification auditor. The same organisation, or a closely linked one, cannot build your ISMS and certify it. A certificate obtained that way is worth little to the customers who asked for it, and an accredited certification body is not allowed to work that way.
- Certification through an unaccredited body. Some “certificates” come from organisations with no recognised accreditation. Check the certification body on the JAS-ANZ register or with another member of the International Accreditation Forum, and confirm it is accredited for ISO 27001 specifically.
- Senior people in the pitch, juniors on the job. If the experienced person disappears after signing, the hardest decisions get made by whoever is left.
- Vague scope. A proposal that doesn’t say what is in scope, what is delivered and by when will grow. Open-ended time-and-materials with no deliverables is the most common way a project drifts.
- No mention of your team’s time. Every implementation needs input from leadership, system owners and HR. A proposal that doesn’t say how much is either unrealistic or hasn’t thought about it.
- Everything is urgent and everything is in scope. A good consultant pushes back when your scope is bigger than your customer needs.
How to compare proposals
Comparing headline figures tells you little unless the proposals cover the same work. Line them up on substance first. These are the factors that drive effort, and every proposal should address them:
| Factor | What the proposal should say |
|---|---|
| Scope | What’s in and out: products, locations, people, systems. Whether they will help you narrow it |
| Starting point | Whether they have assessed what you already have, or assumed you start from nothing |
| Deliverables | Risk assessment, risk treatment plan, Statement of Applicability, policies, internal audit, management review support, audit preparation |
| Who does it | Named people, their roles and qualifications |
| Your team’s time | Roughly how many hours a week, from whom, at which stages |
| Timeline | An audit-ready date tied to your deadline, with the certification body booked early enough |
| Exclusions | Certification body fees, platform licences, penetration testing, remediation by your IT providers |
| Findings | What happens if Stage 1 or Stage 2 raises nonconformities, and whether support is included |
| After certification | Support for surveillance audits, annual internal audits and recertification |
Once the proposals cover the same ground, you can compare them fairly. Our guide to what drives the cost of ISO 27001 explains each part of the budget, and how long ISO 27001 takes helps you test whether a timeline is realistic.
Two more checks are worth making. Ask each consultant to walk you through how they would handle your scope in a short call; how they think about your business tells you more than any brochure. And weigh the whole three-year certificate cycle, not just the first audit. A cheap build that your team can’t maintain costs more at the first surveillance audit.
What good looks like
As one example of the model: at Cyber Veda, one certified security expert runs each engagement from the first call to the certificate, a typical SME is audit-ready in about eight weeks with about two hours a week of the client’s time, and the internal audit is done by a Lead Auditor who didn’t build what they are auditing. We are not a certification body and never certify anyone. Whoever you choose, hold them to the same tests: named senior people, a defined scope, documents you own and clear independence from the auditor.
You choose the certification body separately. Our guide to ISO 27001 certification bodies in Australia explains accreditation, how to check a certificate and how to choose a certifier.
Next step
If you are doing ISO 27001 yourselves, plan the internal audit early. The standard requires it to be objective and impartial, so staff can do it only where they aren’t auditing their own work, and in a small team that often means bringing in an outside auditor. Our independent internal audit is run by a Lead Auditor the way a certification body will audit you. If you’d rather have it built with you, see our ISO 27001 service or book a free 30-minute consultation and ask us the questions above.
