Home › Resources › Guides › Audit stage gates

Resources · Implementation guide

Audit stage gates guide: 7 steps to controlled audit stages

In shortTo control how an audit moves from stage to stage, define the stages, set the conditions that must be met before each move, name who approves it and who stands in for them, give each approval a time target with escalation, and record every transition. The audit then cannot be closed with work unfinished, and the record proves it.

How do you design audit stage gates?

Seven steps, from naming the stages to reviewing how they work.

  1. Name the stages

    Use a small number that everyone understands. ISO 19011 describes initiating, preparing, conducting, reporting, completing and follow-up.

    Stages
  2. 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
  3. Name the approver and a backup

    A different person from the one who did the work, with an alternative for absence.

    Approval
  4. Set time targets

    Decide how long each approval should take, by importance.

    Targets
  5. Define escalation

    Say who is told, and what they must do, when a target is missed.

    Escalation
  6. Record every transition

    Keep who moved the audit, when, the approval and any comment. Record reversals the same way.

    Audit trail
  7. 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.

MoveConditionApprover
Planning to fieldworkAudit plan agreed with the auditee; evidence requests sentAudit sponsor
Fieldwork to findingsEvery planned test has a recorded result with evidenceLead auditor
Findings to reportingEvery finding graded and agreed as fact with the auditeeLead auditor
Reporting to follow-upReport issued; each nonconformity has a corrective action with an owner and dateHead of audit
Follow-up to closedEvery corrective action verified as effective, or the risk formally acceptedHead 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?

01

Conditions that cannot be checked

'Fieldwork substantially complete' is a matter of opinion.

Instead: use conditions the record can confirm.

02

Too many gates

Every small step needs an approval, and audits slow down.

Instead: gate the moves that matter.

03

Gates on paper only

The procedure describes gates the tool does not enforce.

Instead: configure the tool to match.

How does QULDEX support this?

Audit Workspace

Plan, test, record findings and report in eight phases, with every step recorded against the audit.

See the module

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.

Schedule
Book a Demo