How to plan supplier onboarding on a Gantt chart
Plan supplier onboarding as a dated schedule: due diligence, risk, contract, systems setup, a first order and a trial period, with the gates that decide when a supplier can really be used.
Supplier onboarding is slow because of what each step waits for, not because the steps are hard. This guide shows how to lay the steps out with their gates so you can say when a supplier will be ready and what would move the date.
The short version
- Find the gates first: approval, signed contract and working system access.
- Start work early where it does not need the gate, such as drafting the contract during risk assessment.
- Plan the first order and the trial period as tasks with a length, not as an afterthought.
- Use milestones for the gates so a change in one task shows up as a change in the date.
- A schedule shows when work is meant to happen; it does not approve or vet a supplier.
Plan the gates, not just the tasks
A typical onboarding checklist lists the documents to collect, the checks to run and the forms to complete. It does not say what blocks what. The consequence shows up late: the bank details are verified but the vendor record cannot be created because the contract is unsigned, or the contract is signed but nobody has asked for system access. Each team did its part and the supplier still cannot receive an order.
The method is to find the gates first. In most organisations there are three: an approval to use the supplier, a signed contract, and working access in the ordering and payment systems. Everything before a gate is preparation, and everything after it waits. Sort the tasks by which gate they sit behind, add the length of each, and then look for work that can start before a gate opens, such as drafting the contract while the risk assessment is still running.
The last part of onboarding is often left out of the plan: proving that the supplier works in practice. A first order, a delivery and an inspection, a first invoice that gets paid, and a trial period that is long enough to see more than one delivery. These take calendar time and nothing speeds them up, so they belong in the schedule as tasks with a length.
A schedule does not do the checks. It does not make a supplier approved, safe or compliant, and policies on due diligence and approval differ by organisation and sector. What it does is show whether the dates you promised the business are possible. The example follows the supplier onboarding template. For the process and decisions, use the vendor onboarding process at /templates/vendor-onboarding-process.
Supplier onboarding, built in stages
Nineteen tasks in four groups. Durations are illustrative; set your own. Open the spreadsheet panel to see the rows behind each stage.
Checks run side by side
"Financial and legal due diligence" (6 working days) and "Quality and compliance questionnaire" (5) both follow "Request onboarding pack from supplier". "Supplier risk assessment" starts 3 days into the due diligence and "Supplier approved" is a milestone after it.
The contract starts before the gate
"Draft supply agreement" (5) starts 2 days after "Supplier risk assessment" starts. "Negotiate terms" (5) waits for the draft and for "Supplier approved", so the signature follows soon after approval and "Contract signed" is the next milestone.
Systems setup waits for two things
"Verify bank details" (2) needs only approval. "Create vendor record in systems" (3) waits for it and for "Contract signed", then "Set up ordering and invoicing access" (4) leads to the "Systems ready" milestone.
First order, payment test and trial
"Place first order" (1) and "Supplier prepares and ships first order" (10) lead to "Goods receipt and inspection" (3). Then "First invoice and payment test" (3) and the 30-day "Trial period" start together, "Review trial results" waits for both and "Supplier fully onboarded" closes the plan.
How it works
Name your gates
Write down what must be true before the supplier can receive an order: approval, a signed contract, a vendor record. Make each a milestone with a length of 0.
List the tasks behind each gate
Under each gate list the work that leads to it, with a length in working days. Put the checks in one group and the contract in another, so the bands show who is waiting for whom.
Fill in Depends on
Use finish-to-start by default. Use start-to-start with a lag where work can begin early, for example 2SS+3, and a task that waits for two gates lists both, separated by a comma.
Add the proof tasks
Add the first order, delivery, inspection, payment test and a trial period. Set the trial from how many deliveries or invoices you need to see, and put the pass criteria in the task notes.
Check the finish date and the critical path
Read the finish date and compare it with the date you need. Switch on the critical path in the View menu to see the chain that decides it, then shorten or overlap those tasks first.
Share it and keep it current
Put owners in People, share the chart with each team involved, update progress as tasks complete, and export a PDF or CSV when the file needs a copy.
Mistakes to avoid
Starting systems setup before the contract is signed
A vendor record created early can be used to place orders before terms are agreed. Keep the dependency on the signature unless your policy deliberately allows otherwise.
Leaving out the trial
If the plan ends at the signature, the date the business hears is the date you are ready to start testing, not the date the supplier is relied on. Include the first order and trial.
Assuming each team is available the day the gate opens
QueryChart does not check workload or leave. If a team is busy, enter the length it will really take, or add a waiting task before theirs.
Treating the schedule as the approval record
A completed task shows work was done on time. The decisions and evidence belong in your own supplier file and systems, referenced in the task notes.
Open the supplier onboarding Gantt chart
Open the supplier onboarding template, enter your own durations and see when the supplier can take an order.
Related guides
Frequently asked questions
Should onboarding be one chart per supplier?
Usually yes. Copy the chart for each supplier so dates and owners stay clear. For a sourcing project that selects and onboards one supplier, see /templates/procurement-project-gantt-chart.
How do I plan for a supplier who responds slowly?
Add a task for the waiting time after you request documents, with the length you expect. The chart then shows what a slow reply does to the later dates.
Can I paste in an existing checklist?
Yes. Copy the rows from a spreadsheet and paste them into the sheet. If the first line names columns such as Task, Duration and Depends on, they are matched by name.
How do I show that a gate failed?
Increase the length of the task that failed, or add a task for the rework, and the later dates move. QueryChart does not keep a baseline, so export a PDF first if you need to keep the earlier plan.
Where do the decisions in onboarding go?
In a flowchart. The supplier qualification process at /templates/supplier-qualification-process shows the approve and reject paths. For the milestone method, see /guides/gantt-chart-milestones.
