General

How long does ISO 37001 certification take? A realistic timeline

11/10/2026

How long does ISO 37001 certification take? A realistic timeline

You’re weighing up ISO 37001 and you need a straight answer on timeframes. Not a glossy promise, just what it actually takes from first gap analysis to certificate. Here’s how the timeline really plays out, based on audits I’ve led and the improvements I’ve seen stick.

What really drives the timescale

The standard is the same for everyone, but the clock isn’t. Your starting point matters as much as the scope you set. Before you block out weeks in the diary, look at the factors that will set your pace.

  • Baseline maturity: If you run ISO 9001 or ISO 27001 already, controls, risk processes and internal audits shorten the journey.
  • Risk profile: Higher-risk markets, intermediaries or public sector contracting require deeper due diligence and testing.
  • Scope and sites: A single UK office moves faster than multiple countries with different laws and languages.
  • Decision-making speed: Policies, gifts registers and due diligence changes stall if sign-off loops are slow.
  • People and training: Real adoption takes time, especially for teams in sales, procurement and third-party management.
  • Evidence readiness: If records are scattered, pulling proof for audits will drag on.

Be honest with yourself on these points and you’ll set a timeline you can actually hit.

A realistic end-to-end timeline

Most SMEs with a decent management system already in place complete certification in 4–6 months. Mid-sized organisations or those with higher bribery exposure typically land in the 6–9 month range. Large, multi-site or high-risk operations should plan for 9–12+ months.

To make that concrete, this is the usual path from day one to certificate.

  1. Initial gap assessment (2–4 weeks): Review your current controls, interview key people and map gaps against ISO 37001.
  2. Action plan and design (2–3 weeks): Prioritise risks, agree scope and draft the policy, objectives and core procedures.
  3. Implementation and training (6–12 weeks): Roll out due diligence checks, gifts and hospitality controls, and a confidential reporting channel.
  4. Operate and gather evidence (4–8 weeks): Run the controls in real life and collect records that show they work.
  5. Internal audit and management review (2–4 weeks): Test what you’ve built and make decisions on corrective actions and resources.
  6. Stage 1 audit scheduling and delivery (3–6 weeks lead time): Book dates, share documentation and complete the readiness review.
  7. Stage 2 audit scheduling and delivery (4–8 weeks after Stage 1): Host the on-site audit across relevant functions and sites.
  8. Close nonconformities and certification decision (2–6 weeks): Submit evidence of fixes and await the decision and certificate issue.

The third‑party ISO 37001 certification audit typically happens in two stages, with enough space between them to address any Stage 1 findings and to finalise your deployment.

What this looks like in practice

A 70-person UK engineering firm, already running ISO 9001, completed a gap analysis in two weeks, set up proportionate third-party due diligence for two overseas agents, trained sales and procurement, and reached Stage 2 in month five. A services company operating in multiple African jurisdictions, with heavy agent use, took eleven months because mapping intermediaries and screening contracts was a substantive piece of work. Both outcomes were right for the risk.

How the audits are scheduled and what to expect

Stage 1 focuses on readiness: scope, policy, risk assessment, high-level procedures, and whether the system is mature enough to proceed. It is often remote, lasts one to two days depending on scope, and results in a clear list of things to tighten before Stage 2.

Stage 2 tests implementation: how you assessed bribery risks, the operation of due diligence, controls over gifts and hospitality, charitable donations and sponsorship, training effectiveness, speak‑up channels and investigation handling. We sample records, talk to people and look for consistent behaviour across sites and functions.

Lead times depend on diaries on both sides. As a rule of thumb, allow 3–6 weeks to book Stage 1 and a further 4–8 weeks to book Stage 2, especially if site travel is involved. If you want a specific month, get provisional holds in early.

Common delays and how to avoid them

  • Vague scope: Define which entities, sites and processes are in, and document why, so nothing surprises you at Stage 1.
  • Risk assessment drift: Set a deadline, use a simple scoring method and lock it in for management review.
  • Third-party mapping: Build an up-to-date list of intermediaries, agents and partners and prioritise due diligence by risk.
  • Policy paralysis: Keep the policy clear and concise and agree a single owner with authority to finalise it.
  • Training gaps: Identify mandatory audiences early and track completions with reminders and manager escalation.
  • Weak speak-up arrangements: Define channels, test anonymity options and publish them where staff and third parties will actually see them.
  • Slow corrective actions: Assign owners, due dates and evidence requirements for each internal audit finding and review progress weekly.

Practical ways to accelerate without cutting corners

  • Use what you have: Reuse risk, competence and document control processes from other ISO systems to avoid reinventing the wheel.
  • Start with high-risk areas: Pilot due diligence and control testing with your riskiest countries, intermediaries or contract types first.
  • Create simple artefacts: Use a one‑page risk register, a clear gifts register template and short guidance notes staff will actually follow.
  • Make procurement your ally: Embed anti‑bribery clauses and screening in supplier onboarding rather than bolt‑ons later.
  • Schedule audits early: Pencil in Stage 1 and Stage 2 windows at the start so the diary drives momentum.
  • Evidence as you go: Save samples of due diligence checks, approvals and training records weekly to avoid a scramble pre‑audit.

How nonconformities affect timing

It’s common to see a few nonconformities raised during Stage 2, often around incomplete third‑party due diligence or patchy training records. These are fixable, but they do affect your finish line. You’ll need to correct the issue, address root cause and submit evidence within an agreed timeframe.

Minor nonconformities are typically closed with documentary evidence, which can be reviewed quickly once submitted. If something is more systemic, we might need to sample additional records or revisit a site, which adds time. Plan for 2–6 weeks between your Stage 2 closing meeting and certification decision, depending on how swiftly you can demonstrate effective fixes.

Typical timelines by organisation type

Small to mid-sized, single-country (4–6 months)

  • Gap and plan in month one, implementation in months two to three, audits in months four to five and decision shortly after.
  • Biggest effort sits in training, gifts and hospitality controls and putting due diligence into procurement.

Mid-sized, selected high-risk exposure (6–9 months)

  • More time needed for third‑party assessments, contract updates and testing the speak‑up and investigation process.
  • Internal audit and management review often require two cycles to settle the system.

Large or multi-site, multi-jurisdiction (9–12+ months)

  • Phased rollout by region or business unit helps, but scheduling and evidence collection extend the calendar.
  • Expect deeper sampling by auditors across sites and intermediaries, with more findings to close out.

What happens after certification

Once the certification decision is made, your certificate is issued and you move into the surveillance cycle. We’ll agree annual surveillance audits to confirm the system is maintained and improved. In practice, you’ll keep refining due diligence criteria, tightening approvals around higher‑risk spending and using investigation outcomes to update training.

The important thing is not to treat certification day as the end. ISO 37001 works when it becomes routine: proportionate checks, active registers, clear consequences and managers who can explain the why, not just the how.

If you want a timeline you can plan a board paper around, let’s talk through your scope, risk profile and audit windows. UKCTL’s team are happy to give a straight view on what’s realistic for your organisation and how to keep the programme moving.