What Delays a cGMP Certification — and How to Avoid It
Most cGMP certification delays are not caused by failing an audit. They are caused by scope changing mid-process, documentation that describes a different plant from the one the auditor walks into, and corrective actions that get raised quickly and closed slowly.
- Realistic stage-by-stage plan agreed up front
- Written quotation before any work begins
- A named contact through the whole cycle
- Certification under IAS’s UQAS accreditation
None of the three is difficult to avoid. All three are easier to avoid before the application than after it.
Want a realistic timeline for your site? Send IAS your product categories, site count and current documentation position and you will get a stage-by-stage plan with the quotation — talk to IAS Australia.

At a glance
- The five common cGMP certification delays: unsettled scope, stale documentation, records completed after the fact, slow corrective action, and untrained staff who cannot explain their own work.
- Where time is really lost: between the audit and the certification decision, not during the audit.
- The cheapest fix: a two-hour self-check before you apply.
- What has no effect: perfect documentation. Demonstrable practice matters more.
- What shortens everything: having people inside the business who already audit it.
Delay one: scope that keeps moving
Scope is agreed at application. When it changes afterwards — a product family added, a second site remembered, a contract-packed line discovered — the audit plan changes with it, and so does the quotation.
The fix costs nothing. Before applying, list every product family, every activity and every physical location, including the ones you are not sure count. Send the whole list. It is far quicker to remove something from a draft scope than to add it after an audit has been planned around a narrower one.
Delay two: documentation that describes a different plant
The most common finding in a first audit is not a missing procedure. It is a procedure that exists, is approved, and no longer matches what people actually do.
| What the auditor checks | What causes the delay | The pre-audit fix |
|---|---|---|
| Procedure version at the workstation | The floor copy is two revisions behind | Walk the line and compare against the register |
| Training records against revision dates | People trained on the old version | Check the last three revisions were retrained |
| Batch or production records | Completed at shift end from memory | Watch one being filled in real time |
| Equipment status at time of use | Calibration current, but not linked to batches | Trace one batch back to its equipment records |
| Change records | The change happened; the assessment did not | List every change in the last six months |
An hour spent on that table before you apply prevents more cGMP certification delay than any amount of document tidying.
Delay three: corrective actions that stall
Findings are normal. A first assessment that raises nothing is unusual, and it is not the finding that costs time — it is the gap between raising it and closing it with evidence.
Two things slow closure. The first is a corrective action written as an intention (“staff will be reminded”) rather than a change (“the line clearance form now requires a second signature, effective from the date below”). The second is evidence gathered too early: an action implemented on Monday and evidenced on Tuesday has not yet been shown to work.
Sites that close findings quickly tend to have decided in advance who owns the response and who verifies it. Sites that stall usually have not.
Already been audited and stuck on corrective actions? IAS can review your responses before you resubmit them — contact the team.
Delay four: nobody can explain their own work
Auditors interview the people doing the job. Not to catch anyone out, but because what an operator says reveals whether the system was communicated or merely issued.
An operator who can explain why a step exists demonstrates a functioning quality system more convincingly than any document. One who says “because that’s the form” leaves the auditor with a question to pursue, and pursuing questions takes audit time.
This is the delay that training removes, which is why GMP internal auditor training in Australia tends to be bought before a first assessment rather than after it. Dates for open sessions are published on the IAS Australia training schedule. Background on what a GMP programme involves is set out in the IAS piece on navigating pharma quality with GMP certification.
What does not actually cause cGMP certification delays
Two beliefs are behind a good share of Australian cGMP certification delays.
“Documentation must be perfect before we apply”
It does not. Gaps found during documentation review are carried into the audit plan and addressed through corrective action. Waiting to present a polished but untested system usually takes longer than applying with an honest picture of where you are.
“A small site takes less time by definition”
Size matters less than readiness. A well-run twelve-person operation with contemporaneous records moves faster than a two-hundred-person plant whose procedures were last reviewed three years ago.
GMP audit preparation: a two-hour self-check before you apply
- Pull three recent production records at random and trace each to raw materials, equipment status and personnel sign-off.
- Compare the procedure version at two workstations against the master register.
- Check training records for the last two procedure revisions.
- List every change made in the last six months and find the assessment for each.
- Ask two operators why one step in their job exists.
- Write down every product family, activity and site you might want covered.
Anything that fails those six checks is a finding you would rather raise yourself than have raised for you.

Delay five: evidence that exists but cannot be found
The fifth delay is the quietest, because nothing is actually wrong. The record exists, the control worked, the process was followed — and nobody can produce the document inside the audit.
An auditor asks for the calibration certificate for the balance used on a particular batch. It is in a folder, in an office, in a filing system that made sense to someone who has since left. Twenty minutes pass. The auditor moves on and returns to it later, which means the same ground is covered twice.
Multiply that by six requests across a day and you have lost an afternoon of audit time you are paying for, plus an impression of disorganisation that colours everything else.
The retrieval test
The fix is a retrieval test rather than a filing project. Pick five things at random and time how long each takes to produce. Choose a training record, a calibration certificate and a deviation from eight months ago. Add a supplier approval and a batch record from the far end of your retention period. Anything over five minutes needs attention before an audit, not after one.
What a realistic timeline actually looks like
There is no standard number of weeks, and any provider offering one before seeing your scope is guessing. What is predictable is the shape.
| Stage | What happens | What controls its length |
|---|---|---|
| Application and scoping | Scheme, products and sites are settled in writing | How completely you listed everything first time |
| Documentation review | A desk review of your quality documentation | Whether documents match current practice |
| Readiness stage | Confirmation the system is developed enough to proceed | The gap found at documentation review |
| On-site assessment | The audit itself, scaled to scope | Number of sites, product families, scheme complexity |
| Corrective action | Findings closed with evidence | How the actions are written, and who owns them |
| Certification decision | Independent technical review of the evidence | Completeness of the corrective action pack |
Which stages you actually control
Two of those six rows are inside your control before you ever apply: how completely you scope, and whether your documents match practice. A third — how corrective actions are written — is inside your control during the process. Sites that treat those three deliberately tend to move through the cycle at roughly the pace the plan predicted. Sites that leave them to chance are the ones asking, three months in, why it is taking so long.
The honest summary is that the assessment itself is rarely the slow part. Scoping done casually at the start, and corrective actions written loosely at the end, account for most cGMP certification delays in a first cycle.
Quick definitions
- Application and scoping: the stage where scheme, products and sites are settled.
- Documentation review: the desk stage that precedes the site visit.
- Finding: a documented gap between a requirement and the evidence.
- Corrective action: the change made so the gap does not recur.
- Effectiveness verification: confirming the change worked, using records made afterwards.
- Certification decision: the independent technical review before a certificate is issued.
- Scope extension: the reassessment that brings something new under an existing certificate.
- Contemporaneous record: entered while the task was under way, not caught up on later.
Why Australian manufacturers work with IAS
- A stage-by-stage plan issued with the quotation, so the timeline is visible from the start.
- Scope settled in writing before the audit is planned, which removes the commonest cause of cGMP certification delays.
- One fixed written quotation, with no open-ended billing if the process runs long.
- Certification and internal auditor training from one organisation, so the audit method your team learns matches the criteria they are assessed against.
- Open to every manufacturing sector, not only pharmaceutical and food producers.
One boundary, stated without decoration: IAS assesses and certifies management systems, and it trains people. Operating permission and market authorisation sit entirely with regulatory authorities.
Routine queries are answered in the frequently asked questions, what stands behind an IAS certificate is set out under IAS accreditation, and the wider service is described on the ISO certification in Australia index.
Frequently Asked Questions
How long does GMP certification take?
There is no fixed number of weeks, because readiness, scope breadth, site count and scheme complexity all move it. What IAS commits to is a stage-by-stage plan issued with the quotation, so you can see where the time goes rather than waiting to find out.
Will findings during the audit delay our certificate?
Findings themselves rarely cause the delay. What causes it is the closure — a corrective action written as an intention rather than a change, or evidence gathered before the change has had time to work.
Should we wait until our documentation is complete before applying?
Usually not. Gaps identified during documentation review are carried into the audit plan and addressed through corrective action. Applicants who wait for perfection generally take longer overall than those who apply with an honest picture.
Does a smaller site certify faster?
Not automatically. Readiness matters more than headcount. A small, well-run operation with contemporaneous records moves faster than a large plant whose procedures no longer match practice.
What is the single most common first-audit finding?
A procedure that exists and is approved but no longer describes what people do — usually because a change was made and never traced through to the document, the training and the records.
Can we shorten the process by training our staff first?
It helps considerably. Interviews go faster when operators can explain why a step exists, and a site with internal auditors has usually found and closed its own gaps before the assessor arrives.
What happens between the audit and the certificate?
An independent technical review of the audit evidence, plus closure of any findings. This stage is where most cGMP certification delays arise, and it is the one most within your control.
Do changes made during the process affect the audit?
They can. A change to product lines, sites or processes outside the agreed scope usually calls for a scope extension. Telling IAS as it happens keeps the plan intact; discovering it at the audit does not.
How do we keep the timeline from slipping after certification?
By running internal audits between assessments. Surveillance visits go quickly at sites that have already found their own drift, and slowly at sites discovering it for the first time.
Can we pause the process if production gets busy?
Usually yes, and it is better than pressing on with nobody available to host an audit. Say so early. What causes real difficulty is a pause taken silently, after a plan has been built around dates that then pass without contact.


