Preview build. ComplianceForge is not yet trading.

Built for the room it will be tested in.

Six stages, in order. Each one exists because of what an auditor will ask. Your named validator runs all six.

From first call to certificate

  1. Qualify: Gap Analysis

    We read what you have, walk the site, and talk to the people doing the work. You get a written list of what an auditor would raise today, and a straight call on whether you need us.

    You supply: existing documents, site access, an hour with each process owner.

  2. Build the system

    We write your management system from how your business actually runs, clause by clause. Procedures name real roles. Records match the forms your people already fill in. Nothing aspirational.

    You supply: answers, sample records, a decision-maker who signs off.

  3. Validate before handover

    Every system goes through our eight-point internal validation checklist before it's yours. Every one, not a sample. If it fails a point, it doesn't ship.

    You supply: nothing. This one is on us.

  4. Rehearse the challenge

    Your validator runs a mock audit with your people. We ask the questions an auditor will ask, in the tone they'll ask them. People who've heard the hard question once answer it better the second time.

    You supply: the people who'll be in the room.

  5. The audit room

    Your named validator sits in the certification audit alongside your management representative. They answer clause challenges, show where the evidence lives, concede what should be conceded and hold what holds.

    You supply: the audit booking with your certification body.

  6. Close and keep it

    We help you respond to any findings, then debrief: what the auditor tested, what held, what to tighten. Surveillance audits come every year. Continuous Improvement keeps the system true between them.

    You supply: the time to act on the debrief.

The five tests every document has to pass

Our Audit Defensibility Framework is how one validator can stand behind many systems. Each test is a question an auditor will ask, answered before they ask it.

  • Clause to reality

    Every clause traces to something that happens in your business, and to a record that proves it.

  • Evidence expectation

    Enough evidence to satisfy the auditor. Not so much that you're audited on paperwork you never needed.

  • Operational plausibility

    Could your crew actually do what the procedure says, on a normal shift? If not, it gets rewritten.

  • Decision trail

    Why you chose this control, this frequency, this owner. Auditors test reasoning, not just results.

  • Human ownership

    A named role owns every process. Somebody in your business can explain it without reading it.

Questions buyers ask

Do you issue the certificate?

No. Certification decisions are made by independent, accredited certification bodies. We prepare and defend your management system. Your certification body audits it and decides.

Who in my business has to be involved?

A senior person who owns the outcome, plus the people who run the processes the standard covers. We interview them, not just the manager. A system written without them is the kind that fails in the room.

How long does it take?

It depends on your size, the standard and how much already exists. Our working target is a system ready for audit within 30 days of getting the access and information we need. Your Gap Analysis gives you a real date.

Do you use AI to write documents?

We use software, including AI drafting tools, to prepare first drafts quickly. Nothing reaches your system until a person has tested it against how your business actually works. We don't sell AI. We sell the person who checks it.

What if the auditor raises a finding?

Findings happen, and some are right. Your named validator helps you respond, writes the corrective action with you and closes it out. Any commitment we make about findings is written into your proposal, bound to a defined scope.

Can our validator also be our certification auditor?

No. Accreditation rules keep consulting and certifying separate, so the person who builds and defends your system cannot also certify it. Your certification body sends its own independent auditor. That separation is what makes the certificate worth having.

Should we build to ISO 9001:2015 or ISO 9001:2026?

Build to 2026. The new edition was published on 16 September 2026, with a transition period of about three years. ISO 14001 has the same choice: its 2026 edition was published in April 2026. Your audit runs against whichever edition your certification body is accredited for on the day. We confirm which, and build so the system holds up under either.

Where do you work?

We're based in Australia and work wherever our clients are, including overseas. Audit room attendance is planned into your proposal.

Certification on the line? Talk to the person who'll be in the room.

Tell us the standard, the contract or tender that needs it, and when the audit is. You'll get a straight answer on whether we're the right fit, including when we're not.