Audit preparation Gantt chart template with mock audit
An editable audit preparation Gantt chart: scope, evidence request list, collection, document review, gap closure, a mock audit, audit support days and finding responses, with dependencies and four milestones.
What the audit preparation gantt chart template with mock audit process is
Audit preparation fails in a predictable place: the evidence arrives late, the review finds a gap nobody owned, and the fix lands the day before the auditor does. The work is not hard, but it is serial in a way that is easy to miss. You cannot request evidence until the scope is fixed, you cannot review documents until owners have sent them, and you cannot call yourself ready until the gaps are closed and someone has tested the answers. A timeline makes those waits visible while there is still time to move them.
This template has four groups: Scope and planning, Evidence and documents, Readiness and people, and Audit and response. "Confirm audit scope and criteria" (2 working days) is the only starting task. "Agree audit plan and dates with auditor" (3) and "Build evidence request list" (3) both follow it and run side by side, and the "Scope agreed" milestone waits for both. Nothing in the evidence group starts before that milestone, which stops teams collecting material for a scope that later changes.
The overlap is in the middle. "Assign evidence owners" (1) leads to "Collect evidence from owners" (8). "Review documents for currency and gaps" (5) starts 3 days after collection starts, so the reviewer works on what has arrived instead of waiting for the last item. "Log gaps and raise corrective actions" (3) follows the review, and "Close gaps and update documents" (10) starts 2 days after logging starts, because the first gaps are known long before the list is complete. "Evidence pack ready" is a milestone that waits for the fixes. The longest task on the chart is the one most likely to decide the date.
Readiness runs beside this. "Prepare interviewee briefings" (3) and "Book rooms, access and escorts" (2) follow the audit plan, so they can start while evidence is still being collected. "Run mock audit" (3) waits for "Evidence pack ready" and the briefings, "Fix mock audit findings" (4) follows it, and "Ready for audit" waits for those fixes and for the logistics. After that comes "Hold opening meeting" (1) and "Run audit support days" (5). "Answer evidence follow-up requests" (3) starts 2 days into the support days, then "Hold closing meeting" (1), "Draft finding responses" (5) and the "Responses submitted" milestone. All durations are illustrative.
A timeline schedules preparation and does not guarantee an audit result. It does not make a system compliant, certified or free of findings, and it does not replace your audit programme or the auditor's own plan. For the flow of the audit itself, see the audit process at /templates/audit-process and the checklist workflow at /templates/audit-checklist-workflow. For the corrective actions that gap closure raises, see /templates/capa-gantt-chart.
What this flowchart covers
In this template
- Four groups, Scope and planning, Evidence and documents, Readiness and people and Audit and response, with 21 tasks and four milestones: "Scope agreed", "Evidence pack ready", "Ready for audit" and "Responses submitted".
- A request list built from a fixed scope: "Build evidence request list" and "Agree audit plan and dates with auditor" both follow "Confirm audit scope and criteria" and both feed "Scope agreed".
- Overlapping review and repair: "Review documents for currency and gaps" starts 3 days after "Collect evidence from owners" starts, and "Close gaps and update documents" starts 2 days after "Log gaps and raise corrective actions" starts.
- A mock audit gate: "Run mock audit" waits for "Evidence pack ready" and "Prepare interviewee briefings", and "Ready for audit" waits for "Fix mock audit findings" and "Book rooms, access and escorts".
- The audit itself and what follows: "Run audit support days" (5), "Answer evidence follow-up requests" starting 2 days in, "Hold closing meeting" and "Draft finding responses" ending at "Responses submitted".
When to use this template
- An external, customer, financial or regulatory audit is booked and you need to agree dates with the people who own the evidence.
- You want to see how long preparation takes if every owner delivers as planned, and which task decides the date.
- An audit lead needs the readiness date in front of management and wants to compare the finish date with the date you need.
- You want a repeatable skeleton for the audits you face each cycle that each audit type can adapt.
The plan, task by task
Every task in the chart with its length in working days and what it waits for. A dependency is a step number; SS is start-to-start, FF is finish-to-finish, and +n is a lag in working days.
| # | Task | Group | Working days | Depends on |
|---|---|---|---|---|
| 1 | Confirm audit scope and criteria | Scope and planning | 2 | |
| 2 | Agree audit plan and dates with auditor | Scope and planning | 3 | 1 |
| 3 | Build evidence request list | Scope and planning | 3 | 1 |
| 4 | Scope agreed | Scope and planning | Milestone | 2, 3 |
| 5 | Assign evidence owners | Evidence and documents | 1 | 4 |
| 6 | Collect evidence from owners | Evidence and documents | 8 | 5 |
| 7 | Review documents for currency and gaps | Evidence and documents | 5 | 6SS+3 |
| 8 | Log gaps and raise corrective actions | Evidence and documents | 3 | 7 |
| 9 | Close gaps and update documents | Evidence and documents | 10 | 8SS+2 |
| 10 | Evidence pack ready | Evidence and documents | Milestone | 9 |
| 11 | Prepare interviewee briefings | Readiness and people | 3 | 2 |
| 12 | Book rooms, access and escorts | Readiness and people | 2 | 2 |
| 13 | Run mock audit | Readiness and people | 3 | 10, 11 |
| 14 | Fix mock audit findings | Readiness and people | 4 | 13 |
| 15 | Ready for audit | Readiness and people | Milestone | 12, 14 |
| 16 | Hold opening meeting | Audit and response | 1 | 15 |
| 17 | Run audit support days | Audit and response | 5 | 16 |
| 18 | Answer evidence follow-up requests | Audit and response | 3 | 17SS+2 |
| 19 | Hold closing meeting | Audit and response | 1 | 17, 18 |
| 20 | Draft finding responses | Audit and response | 5 | 19 |
| 21 | Responses submitted | Audit and response | Milestone | 20 |
How it works
Fix the scope before anything else
Keep "Confirm audit scope and criteria" as the first task and let "Scope agreed" wait for both the plan and the request list. Change the durations to how long your audit lead and the auditor really need.
Turn the request list into owners
After "Scope agreed", "Assign evidence owners" gives each item a person. Add one task per large evidence area if collection by one task hides who is late.
Let review run on partial evidence
"Review documents for currency and gaps" is linked start-to-start with a lag of 3 days to "Collect evidence from owners". Change the lag if your reviewer needs more of the evidence before starting.
Start closing gaps early
"Close gaps and update documents" starts 2 days after "Log gaps and raise corrective actions" starts. If a fix needs a change approval, add that task and link it before "Evidence pack ready".
Hold the mock audit as a real gate
Keep "Run mock audit" and "Fix mock audit findings" between "Evidence pack ready" and "Ready for audit". Remove them only if you accept going in untested.
Add owners, share and export
Put the responsible person in People, share the chart with the evidence owners and the auditor liaison, and export a PDF or CSV for the audit file when you need a copy.
Frequently asked questions
How long does audit preparation take?
It depends on the audit type, how current your documents are and how many owners hold evidence. The template adds up to a few weeks of working days with illustrative lengths. Replace them with your own and read the finish date from the chart.
Does the chart make us ready, or guarantee a clean audit?
No. It schedules the work. A timeline schedules preparation and does not guarantee an audit result. Evidence quality, control design and the auditor's judgement stay with you and with them.
Why is a mock audit a task?
Because it takes calendar time and the readiness milestone waits for what it finds. If the findings need fixing, "Fix mock audit findings" shows how much the real audit start is pushed back.
Can I use it for an ISO certification or a customer audit?
Yes, with changes. Rename the criteria in the first task and add the evidence areas your standard or customer asks for. For quality system implementation, see /templates/qms-implementation-gantt.
How do I show tasks that overlap?
Use a start-to-start link with a lag where work genuinely overlaps, as the template does for the review and the gap closure. For the method, see /guides/gantt-chart-overlapping-tasks and /guides/gantt-chart-dependencies.