For most organizations, ISO certification takes about six to seven months from kickoff to the certificate. Simpler quality standards at a single, well-run site can move faster; heavily regulated sectors, multiple locations, or a system built from scratch can take longer. The honest answer is that timeline is driven less by the standard and more by how ready you are and how consistently you can give the work attention.

Here is what actually happens across those months, so you can plan around real milestones instead of a vague hope.

The phases behind the timeline

Every certification, whatever the standard, moves through the same arc. We have refined it into a ten-step method, but the shape is universal:

  • Kickoff and awareness (weeks 1–2). Leadership and the quality team align on what the standard requires, what the registrar will look for, and who owns what.
  • Documentation (weeks 2–7). The manual, procedures and forms are drafted with your process owners. We keep this to a single level and under 200 pages — written for the people who use it, not for show.
  • Implementation (weeks 6–14). The system goes into daily practice and starts generating real records. This is usually the longest stretch, because it depends on your people actually working the new way.
  • Internal audit and management review (weeks 12–18). A full internal audit cycle plus a genuine leadership review — the dress rehearsal for the real thing.
  • Stage 1 audit (around month 4–5). The registrar reviews your documented system.
  • Stage 2 audit (a few weeks later). The registrar walks your floor and confirms you run the system you wrote down. Pass, and the certificate follows.

What makes it faster

  • Existing habits. If you already keep records and run in a disciplined way, documentation and implementation compress dramatically.
  • A single site and one standard. Scope drives effort more than anything else.
  • Consistent attention. A few focused hours every week beats a frantic sprint at the end.
  • Simplified documentation. A lean, single-level system is faster to write, faster to train, and far less likely to trip you up at audit.

What slows it down

  • Multiple sites or standards pursued at once.
  • Regulated sectors such as medical devices or food, where evidence requirements are heavier.
  • A stalled or failed previous attempt that has to be unpicked before it can be rebuilt.
  • Bloated documentation inherited from a previous consultant — a 400-page binder nobody follows is slower to fix than to start fresh.

What about cost?

Certification cost is driven by the same factors as timeline: scope, number of sites, the standard, and how much of the system already exists. There is also the registrar's separate audit fee, which is paid directly to them. Rather than quote a number that would be wrong for your situation, we scope every engagement to what you actually need — and price it against the value of passing the first time, with a system you can run yourself afterward. A rough timeline and a clear scope come out of the first conversation, at no cost.

The number that matters more than months

Timeline is worth planning around, but the figure we care about most is the first-time pass rate. Across 900-plus certifications, ours is 100% — because the months above are spent closing the gap between what your documents say and what your team does, not decorating a binder. Get that right, and the audit is a formality.

Want a realistic timeline for your standard and sites? See how the 10-Step Approach works, or tell us your standard and deadline and we will map it out.