How to lay out a Gantt chart for a regulated, stage-gated project
Lay out a stage-gated plan where sign-offs, reviews and approvals are the schedule: gates as milestones, review windows as tasks with a real length, and the response loop after a reviewer replies.
In a regulated project the dates are set less by how long the work takes than by how long it waits: for a sign-off, a review, an answer. This guide shows how to put those waits on a Gantt chart so they move the dates.
The short version
- Make every gate a milestone (length 0) that depends on all it needs and that the next stage depends on.
- Give a review window a real length in working days, so the wait pushes the dates behind it.
- Plan the response loop after the window as its own tasks: draft answers, approve, send.
- Use start-to-start and finish-to-finish links with a lag for work that may overlap inside a stage.
- The chart schedules the work. It does not make anything compliant, validated or approved.
When the waiting is the schedule
A normal project plan treats approvals as a footnote: finish the work, get a signature, move on. In a stage-gated project the signature is the point. Nothing in the next stage may start until the gate is passed, and a reviewer outside your team decides how long that takes. If the plan shows only the work, its dates are optimistic by the length of every wait it leaves out.
The layout that holds up has three parts. A gate is a milestone, a task of length 0, that depends on everything the gate needs and that the next stage depends on in turn. A review window is a task with a real length in working days, so it takes space on the chart and pushes everything behind it. A response loop is a short run of tasks after the window: read the questions, draft the answers, approve and send them. Once those are in as dependencies, the finish date is calculated and you can see which wait sets it.
Some work in a stage does not need to wait for the rest. Drafting can start before the last input has arrived, and a formatting pass can begin while comments are still being addressed. Start-to-start and finish-to-finish links with a lag describe that overlap honestly, and they are where a regulated plan usually gets its time back. If you want the mechanics first, see /guides/gantt-chart-dependencies and /guides/gantt-chart-overlapping-tasks.
A timeline schedules work. It does not make a study, a device file, a submission, a method or a system compliant, validated or approved, and every task being on time proves nothing about the quality of what was done. The evidence stays in your quality records; the chart says what has to happen before what, and by when if nothing slips.
The example is the regulatory submission template at /templates/regulatory-submission-gantt-chart, built in four stages. The same layout applies to the device and clinical templates: /templates/medical-device-development-gantt-chart puts design reviews and verification gates between phases, and /templates/clinical-trial-gantt-chart does the same for protocol approval, site activation and database lock. For quality-system work see also /templates/method-validation-gantt-chart and /templates/computer-system-validation-gantt-chart.
A submission plan with four gates, built in stages
Twenty-two tasks in four phases. Durations are illustrative; set your own. Open the spreadsheet panel to see the rows behind each stage.
The first gate waits for two things
"Define scope and content outline" (3 working days) is followed by "Run gap analysis on available data" (6) and "Confirm authors and reviewers" (2), which run side by side. The milestone "Gap analysis agreed" waits for both, and authoring starts only after it.
Authoring overlaps inside the stage
"Draft clinical summaries" (14 days) starts 4 days after "Close data gaps with missing reports" starts, and "Write overview and cross-module summary" finishes 2 days after it. "Content approved for publishing" waits for "Address review comments" and "Format documents and navigation".
Publishing, checks and the submission gate
"Compile and publish the package" (3 days), "Run technical checks on the package" (2) and "Submit to the authority" (1) follow one another with no overlap, because each needs the last. "Submission sent" is a milestone and the start of the wait.
A review window, then the response loop
"Authority review period" is 30 working days and is time you wait, not effort. Behind it, "Draft answers to questions" (8 days) and "Approve and send responses" (3) lead to the "Responses sent" milestone, so a longer window moves the final date one for one.
How it works
List the gates first
Before any tasks, write down the points where someone must say yes: a scope sign-off, a design review, a protocol approval, a submission. Each becomes a milestone with a length of 0 in the order they will be passed.
Add the work between gates and link it
For each stage list the tasks and give each a length in working days. In Depends on, make every task wait for the gate before it, and make the next gate wait for every task it needs. A gate with only one input is a sign that something is missing.
Turn each outside review into a task with a length
A regulator's or sponsor's review is not a milestone, because it takes time. Add it as a task, set its length to your best realistic number, and note where the number came from. Anything behind it will start after it ends.
Plan the response loop
After the window add the tasks you will have to do when questions come back: draft answers, internal approval, send. Their length is a guess until the questions arrive, so keep them short and visible and adjust them when you know more.
Let work overlap where the stage allows it
Where one task can start before another ends, use a start-to-start link with a lag, for example 8SS+4. Where one must not finish before another does, use finish-to-finish, for example 9FF+2. Keep strict finish-to-start for the handoffs that really are strict.
Check the critical path, then share the chart
Switch on View, Critical path to light the chain that sets the final date. In a gated plan it will usually run through the review window. Group by stage, put owners in People, share the chart, and export a PDF for the project file.
Mistakes to avoid
Treating the review as a milestone
A milestone has no length, so a review drawn as one takes no time and the plan finishes weeks early. Anything that waits on another party needs a length, even if the length is an estimate.
Leaving out the response loop
Plans that end at the submission or the review show a date that holds only if no one has a question. Add the tasks for answering, and keep them in the chart until the file is closed.
Fixing dates that should be calculated
Pinning a Start on every task makes the plan a list of promises and hides what moves when a gate slips. Fix a date only where it is genuinely fixed, such as a meeting or a deadline set by someone else; the chart flags a fixed start that conflicts with a dependency.
Reading the chart as a record of compliance
On-time tasks do not show that a review was adequate or that a document is acceptable. QueryChart also keeps no baseline to compare against, so export a PDF before you change the plan if you need to show what it said.
Open the submission Gantt chart
Open the regulatory submission template, change the review window to yours and see the final date move.
Related guides
Frequently asked questions
Should a sign-off be a milestone or a task?
If it is a decision that happens at a moment, such as a signature in a meeting, use a milestone. If it takes days for someone to read and respond, use a task with a length and put a milestone after it for the decision.
How long should I make a review period?
Use the figure from the authority, the sponsor or your own procedure, and note the source in the task. Working days are Monday to Friday and the chart has no holiday calendar, so add days for any known closures.
Can the work in the next stage start before a gate?
Only if you decide it may. Link the task to an earlier task instead of the gate, or use a start-to-start link with a lag. Write in the notes why it is allowed to start early, since that is the question a reviewer will ask.
What if the questions come back and the answers take longer?
Change the length of the answer tasks and the dates behind them move. If you need to show the earlier plan, export a PDF first, because the chart does not keep the original dates.
Where do I find a starting point for my area?
Start from the submission template at /templates/regulatory-submission-gantt-chart, or from the device or clinical versions at /templates/medical-device-development-gantt-chart and /templates/clinical-trial-gantt-chart. For linking tasks see /guides/gantt-chart-milestones and /guides/gantt-chart-critical-path.