Production ramp-up Gantt chart template with yield and rate gates
An editable production ramp-up Gantt chart: line readiness, first articles, a yield gate, a staged rate ramp with staffing and supplier volume, a rate gate and handover to operations, with dependencies.
What the production ramp-up gantt chart template with yield and rate gates process is
A ramp-up is not a long production run that starts slowly. It is a series of steps up, and each step is allowed only when the one below it is holding: first articles pass inspection, the pilot run reaches the yield you need, the line runs at half rate, then at full rate. Plans for ramp-ups often go wrong because they are drawn as one straight line from the first article to full output. The real schedule has gates in it, and the work around the gates, staffing a second shift and getting suppliers to deliver at volume, has lead times of its own that do not shrink when the line is ready.
This template has four phases: Line readiness, First articles, Ramp to rate and Steady state, with 19 tasks and three gates. "Freeze line layout and process flow" is the only starting task. After it, "Qualify critical suppliers" (8 working days), "Install and debug the line" (10) and "Recruit line operators" (8) run side by side. "Train operators on the line" follows the recruiting, but starts no earlier than 5 working days after the install starts, because operators need a line to train on.
The first articles phase is where quality holds enter the plan. "First article build" needs the installed line and the qualified suppliers. "First article inspection" is finish-to-finish with the build plus one working day, so inspection runs alongside the build and ends the day after it. "Review quality holds and fix causes" (5 working days) then sets the date of the "First article approved" milestone. Everything after that milestone waits for it.
In the ramp phase the pilot run is followed by the "Yield gate met" milestone. "Staff the second shift" and "Confirm supplier volume for full rate" start 2 and 1 working days after the pilot starts, so they run during it and not after it. "Ramp to half rate" waits for the yield gate; "Ramp to full rate" waits for half rate, the second shift and the supplier volume. The "Rate gate met" milestone follows, then "Run at rated output" (10 working days), with "Close open quality holds" finishing with it before "Hand over to operations". All durations are illustrative. Set your own, and set the gate criteria, such as the yield and rate you need, in the task notes before the ramp starts.
A timeline schedules the ramp. It does not make a gate pass, and a milestone marked complete is not evidence that the yield was reached. Keep the measured yield, rate and inspection records in your quality system and refer to them in the notes. For the process logic around the ramp, see the new product introduction process at /templates/new-product-introduction-process, the first article inspection process at /templates/first-article-inspection-process and the engineering to production handoff at /templates/engineering-to-production-handoff-process. For the wider product timeline, see /templates/new-product-introduction-gantt.
What this flowchart covers
In this template
- Four phases, Line readiness, First articles, Ramp to rate and Steady state, with 19 tasks and three gate milestones: "First article approved", "Yield gate met" and "Rate gate met".
- Readiness work in parallel: "Qualify critical suppliers", "Install and debug the line" and "Recruit line operators" all follow "Freeze line layout and process flow", and "Train operators on the line" starts 5 working days into the install.
- A finish-to-finish overlap in the first articles: "First article inspection" finishes one working day after "First article build" finishes, and "Review quality holds and fix causes" follows it.
- Supply and staffing planned during the pilot, not after it: "Staff the second shift" and "Confirm supplier volume for full rate" both start a working day or two into "Pilot run at low rate" and must be done before "Ramp to full rate".
- Steady state with a tail: "Run at rated output" for 10 working days, "Close open quality holds" finishing with it, then "Hand over to operations".
When to use this template
- You are launching a new line, a new plant or a transferred product and need dates for the steps between the first article and rated output.
- You want yield and rate targets to appear in the plan as gates, with the staffing and supplier work that has to be ready for each step.
- A customer, a plant manager or a programme board asks when full rate is expected and what could move it.
- You want to see how a quality hold or a slow supplier ramp moves the date of the rate gate.
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 | Freeze line layout and process flow | Line readiness | 5 | |
| 2 | Qualify critical suppliers | Line readiness | 8 | 1 |
| 3 | Install and debug the line | Line readiness | 10 | 1 |
| 4 | Recruit line operators | Line readiness | 8 | 1 |
| 5 | Train operators on the line | Line readiness | 4 | 3SS+5, 4 |
| 6 | First article build | First articles | 3 | 2, 3 |
| 7 | First article inspection | First articles | 3 | 6FF+1 |
| 8 | Review quality holds and fix causes | First articles | 5 | 7 |
| 9 | First article approved | First articles | Milestone | 8 |
| 10 | Pilot run at low rate | Ramp to rate | 5 | 5, 9 |
| 11 | Yield gate met | Ramp to rate | Milestone | 10 |
| 12 | Staff the second shift | Ramp to rate | 6 | 10SS+2 |
| 13 | Confirm supplier volume for full rate | Ramp to rate | 6 | 10SS+1 |
| 14 | Ramp to half rate | Ramp to rate | 8 | 11 |
| 15 | Ramp to full rate | Ramp to rate | 10 | 12, 13, 14 |
| 16 | Rate gate met | Ramp to rate | Milestone | 15 |
| 17 | Run at rated output | Steady state | 10 | 16 |
| 18 | Close open quality holds | Steady state | 5 | 17FF |
| 19 | Hand over to operations | Steady state | 3 | 17, 18 |
How it works
Run readiness work in parallel
Keep "Qualify critical suppliers", "Install and debug the line" and "Recruit line operators" as separate tasks after the layout freeze. Change their lengths to yours and see which one sets the date of "First article build".
Write the gate criteria before the ramp
Treat "First article approved", "Yield gate met" and "Rate gate met" as decisions, not dates. Write the yield and rate you need in the notes of each milestone, and keep the measured results in your quality system.
Give quality holds their own time
Set the length of "Review quality holds and fix causes" from how long root cause and rework take at your plant. If you expect holds in the later steps too, add a task before the next gate.
Start staffing and supply during the pilot
Keep "Staff the second shift" and "Confirm supplier volume for full rate" as start-to-start links from the pilot run, and put the people and suppliers involved in People and the notes.
Add more steps if you ramp in more stages
Duplicate "Ramp to half rate" for a quarter-rate or three-quarter-rate step, and link each step to a gate milestone before it.
Switch on the critical path and share
Turn on the critical path in the View menu to light the chain that sets the handover date. Share the chart, update progress as the ramp goes, and export a PDF for a review.
Frequently asked questions
Does the chart check yield or rate?
No. A milestone is a point in the plan, not a measurement. The yield and rate results belong in your production and quality records. The chart shows when each gate is meant to be reached and what has to be in place for it.
What if a gate is not met?
Add the rework, retest or fix as tasks before the gate and link the gate to them, or lengthen the existing task. The dates move and the new handover date shows. QueryChart does not keep a baseline, so export a PDF first if you want to keep the earlier plan.
Can I model a ramp with several lines or sites?
Yes. Duplicate the phases for each line, or group the tasks by line, and link the later lines to the gate of the first. Keep the number of tasks manageable, and use the process templates for the detail inside a line.
Are the durations realistic for my product?
They are illustrative. A ramp for a simple assembly and one for a process with long validation cycles are very different. Replace the lengths with your own and keep the dependencies that match how your line works.
