Analytical method validation Gantt chart with overlapping runs
An editable Gantt chart for laboratory method validation: protocol, reference standards lead time, overlapping validation runs, out-of-spec investigation, report and approval, with four milestones.
What the analytical method validation gantt chart with overlapping runs process is
Validating an analytical method looks like a list of experiments, but the calendar is decided elsewhere. The protocol has to be approved before any validation run counts. Reference standards and reagents have a lead time that nobody on the bench controls. Instrument and analyst time is shared, so runs that could overlap in theory are staggered in practice. And when a result falls outside its acceptance criterion, an investigation has to finish before the affected runs are repeated. A timeline makes those waits visible before the first vial is prepared.
This template has four groups: Protocol and materials, Validation experiments, Results and investigation, and Report and approval. It has 22 tasks, four of them milestones. "Define scope and acceptance criteria" is the only starting task. It leads to "Draft validation protocol" and, on a parallel track, to "Order reference standards and reagents". The milestone "Protocol approved" follows "Review and approve protocol", and "Materials ready" follows "Wait for delivery of materials" (12 working days) and "Qualify standards and prepare solutions". "Run system suitability checks" waits for both milestones, so the long delivery wait is usually the date to watch, not the protocol.
The experiment group is where the plan differs from a generic project. "Run specificity and forced degradation" (5 working days) comes first. "Run linearity and range" starts 1 day after it starts, "Run accuracy recovery" starts 2 days after linearity starts, and both "Run repeatability and intermediate precision" (starting 2 days after accuracy starts) and "Run robustness variations" (starting 3 days after) follow. Runs overlap because different samples and different analysts can share a window, but each one starts only after the earlier run has begun, so you can still change course on what you learn.
"Process data and calculate statistics" starts 3 days after accuracy starts, so early results are reviewed while later runs finish, and it finishes 2 days after the repeatability and robustness runs finish. Then "Investigate out-of-spec results" (6 working days) and "Repeat affected runs" (4) sit on the path to the "Experiments complete" milestone. Many validations will not need them. Keep the tasks as a contingency slot, shorten them or delete them, and read the effect on the finish date. "Draft validation report" starts 2 days into data processing and finishes 1 day after "Experiments complete". Then "Quality review of report", "Approve report and method" and the milestone "Method validated and approved" close the plan. All durations are illustrative.
A timeline schedules the work. It does not make a method validated, a result acceptable or a report approved. Acceptance criteria, deviations and approvals follow your own procedures and are recorded in your own systems. For the process behind the plan, see the analytical method validation process at /templates/analytical-method-validation-process, the out-of-specification workflow at /templates/oos-investigation-process and the lab-to-lab handoff at /templates/method-transfer-process. The same gate-and-sign-off logic runs through four neighbouring plans: /templates/clinical-trial-gantt-chart (a clinical study), /templates/medical-device-development-gantt-chart (device development), /templates/regulatory-submission-gantt-chart (a regulatory submission) and /templates/computer-system-validation-gantt-chart (computerised system validation).
What this flowchart covers
In this template
- Four groups, Protocol and materials, Validation experiments, Results and investigation and Report and approval, with 22 tasks and four milestones: "Protocol approved", "Materials ready", "Experiments complete" and "Method validated and approved".
- A materials track beside the protocol: "Order reference standards and reagents" leads to "Wait for delivery of materials" (12 working days) and "Qualify standards and prepare solutions", independent of "Draft validation protocol" until "Run system suitability checks".
- Overlapping validation runs: "Run linearity and range" starts 1 day after "Run specificity and forced degradation" starts, and "Run accuracy recovery" starts 2 days after linearity starts.
- A contingency slot for "Investigate out-of-spec results" and "Repeat affected runs" between "Process data and calculate statistics" and "Experiments complete".
- A report that starts early: "Draft validation report" starts 2 days after "Process data and calculate statistics" starts and finishes 1 day after "Experiments complete", before "Quality review of report".
When to use this template
- You are planning the validation of a new or changed analytical method and need dates that analysts, quality and the instrument owner can agree.
- A reference standard or reagent has a long lead time and you want to see whether it, rather than the protocol, decides the finish date.
- You want to show how much overlap between runs the instrument and analysts allow, and what a repeated run does to the plan.
- You want a repeatable skeleton that each method or product can adapt before the protocol is written.
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 | Define scope and acceptance criteria | Protocol and materials | 3 | |
| 2 | Draft validation protocol | Protocol and materials | 4 | 1 |
| 3 | Review and approve protocol | Protocol and materials | 3 | 2 |
| 4 | Protocol approved | Protocol and materials | Milestone | 3 |
| 5 | Order reference standards and reagents | Protocol and materials | 2 | 1 |
| 6 | Wait for delivery of materials | Protocol and materials | 12 | 5 |
| 7 | Qualify standards and prepare solutions | Protocol and materials | 3 | 6 |
| 8 | Materials ready | Protocol and materials | Milestone | 7 |
| 9 | Run system suitability checks | Validation experiments | 2 | 4, 8 |
| 10 | Run specificity and forced degradation | Validation experiments | 5 | 9 |
| 11 | Run linearity and range | Validation experiments | 4 | 10SS+1 |
| 12 | Run accuracy recovery | Validation experiments | 5 | 11SS+2 |
| 13 | Run repeatability and intermediate precision | Validation experiments | 6 | 12SS+2 |
| 14 | Run robustness variations | Validation experiments | 4 | 12SS+3 |
| 15 | Process data and calculate statistics | Results and investigation | 4 | 12SS+3, 13FF+2, 14FF+2 |
| 16 | Investigate out-of-spec results | Results and investigation | 6 | 15 |
| 17 | Repeat affected runs | Results and investigation | 4 | 16 |
| 18 | Experiments complete | Results and investigation | Milestone | 17 |
| 19 | Draft validation report | Report and approval | 5 | 15SS+2, 18FF+1 |
| 20 | Quality review of report | Report and approval | 3 | 19 |
| 21 | Approve report and method | Report and approval | 2 | 20 |
| 22 | Method validated and approved | Report and approval | Milestone | 21 |
How it works
Start the protocol and the order together
Keep "Draft validation protocol" and "Order reference standards and reagents" as separate tasks that both follow "Define scope and acceptance criteria". Replace "Wait for delivery of materials" with the lead time your supplier quotes.
Hold the runs behind both gates
"Run system suitability checks" waits for "Protocol approved" and "Materials ready". If part of the work is allowed to start earlier under your own procedures, change that dependency deliberately.
Set the overlap between runs
The linearity, accuracy, repeatability and robustness runs are linked start-to-start with lags of 1 to 3 days. Increase the lags when analysts or the instrument cannot work in parallel, or link the runs one after another.
Decide how to treat the investigation
Keep "Investigate out-of-spec results" and "Repeat affected runs" as a buffer, shorten them if your history shows few failures, or delete them. Compare the finish date with the date you need.
Draft the report while data is processed
"Draft validation report" starts early and is linked finish-to-finish to "Experiments complete" with a lag of 1 day. Remove the overlap if your procedure requires complete data first.
Add owners, share and export
Put the responsible person in People, share the chart with the analysts and the quality reviewer, and export a PDF or CSV when you need a copy for the validation file.
Frequently asked questions
How long does method validation take?
It depends on the method, the number of parameters, instrument availability and how many results need investigation. The durations here are illustrative. Replace them with your own and read the finish date from the chart.
Does the chart make a method validated?
No. It schedules the work. Validation depends on your protocol, your acceptance criteria and your quality system, and results and approvals are recorded in your own systems. The chart shows when each part is meant to happen.
Why are the investigation tasks in the plan?
Because a result outside its acceptance criterion stops the affected runs until the cause is understood. Many validations never need the slot, so treat it as a buffer you can shorten or delete. For the workflow itself, see /templates/oos-investigation-process, and for padding in general, see /guides/gantt-chart-buffer-time.
Can I add or remove validation parameters?
Yes. Add a task for each parameter your protocol requires, such as detection limit or stability of solutions, and link it start-to-start to the run it can share a window with. The guide at /guides/gantt-chart-overlapping-tasks explains the link types.
Can I use this for a method transfer or verification?
With changes. Remove the experiments you do not need and add the receiving lab's runs. For the transfer process, see /templates/method-transfer-process, and for a related quality plan, see /templates/audit-preparation-gantt-chart.