Resources · Implementation guide
Audit stage gates guide: 7 steps to controlled audit stages
How do you design audit stage gates?
Seven steps, from naming the stages to reviewing how they work.
- Name the stages
Use a small number that everyone understands. ISO 19011 describes initiating, preparing, conducting, reporting, completing and follow-up.
Stages - Set the conditions for each move
State what must be true before an audit leaves a stage, in terms that can be checked.
Exit conditions - Name the approver and a backup
A different person from the one who did the work, with an alternative for absence.
Approval - Set time targets
Decide how long each approval should take, by importance.
Targets - Define escalation
Say who is told, and what they must do, when a target is missed.
Escalation - Record every transition
Keep who moved the audit, when, the approval and any comment. Record reversals the same way.
Audit trail - Review the gates
Look at where audits wait longest and adjust the conditions or approvers.
Improvement
Go deeper: workflow state transition · approval log · escalation path.
What do stage gates look like?
Example gates for an internal audit. Adapt the stages and roles.
| Move | Condition | Approver |
|---|---|---|
| Planning to fieldwork | Audit plan agreed with the auditee; evidence requests sent | Audit sponsor |
| Fieldwork to findings | Every planned test has a recorded result with evidence | Lead auditor |
| Findings to reporting | Every finding graded and agreed as fact with the auditee | Lead auditor |
| Reporting to follow-up | Report issued; each nonconformity has a corrective action with an owner and date | Head of audit |
| Follow-up to closed | Every corrective action verified as effective, or the risk formally accepted | Head of audit |
A gate is useful only if the condition can be checked from the record.
Are your stage gates complete?
Tick what is done. Nothing is saved or sent; the list resets when you leave the page.
What goes wrong most often?
Conditions that cannot be checked
'Fieldwork substantially complete' is a matter of opinion.
Instead: use conditions the record can confirm.
Too many gates
Every small step needs an approval, and audits slow down.
Instead: gate the moves that matter.
Gates on paper only
The procedure describes gates the tool does not enforce.
Instead: configure the tool to match.
How does QULDEX support this?
Plan, test, record findings and report in eight phases, with every step recorded against the audit.
Audit stage gates: common questions
What is a stage gate?
A checkpoint between two stages of an audit where set conditions must be met, and usually an approval given, before work continues.
Who should approve a stage move?
Someone with the authority to judge the conditions who did not do the work being approved.
Can an audit move backwards?
Yes, for example from reporting back to fieldwork when more testing is needed. The reversal should be approved and recorded.
Do stage gates slow audits down?
Badly designed ones do. Gates with checkable conditions and time targets usually remove rework later.
Eight audit phases, each with its own gate and record
Controls, evidence, findings and corrective actions together, mapped to each framework.