Source-to-contract process
Editable source-to-contract process swimlane from “Define category need and business outcome” through “Competition route and criteria approved?” to a documented outcome. Includes named roles, exception paths and evidence.
What the source-to-contract process process is
The workflow starts at “Define category need and business outcome”. The next two steps, “Assess market and sourcing alternatives” and “Prepare specification and evaluation criteria”, establish the information needed for a defensible decision. The chart assigns each handoff to a role and retains the evidence at closeout.
The main gates are “Competition route and criteria approved?” and “Final terms and supplier risk accepted?”. The first branch leads to revise sourcing strategy or document exception; the second can require renegotiate or escalate unresolved term. Set evaluation criteria before bids arrive and hand signed obligations to the contract owner.
What this flowchart covers
In this template
- Define category need and business outcome followed by assess market and sourcing alternatives.
- Competition route and criteria approved? with a route for revise sourcing strategy or document exception.
- Supplier responds to issued RFI, RFP or tender and evaluate bids and negotiate terms as separate supplier and internal handoffs.
- Final terms and supplier risk accepted? with renegotiate or escalate unresolved term when the decision fails.
- Recommend supplier and legal position, approve and sign contract and store obligations, owner and renewal date as the controlled closeout.
When to use this template
- Use it to agree who owns “Define category need and business outcome” and what information the next role needs.
- Use it when the answer to “Competition route and criteria approved?” is unclear or decisions are made outside the record.
- Use it to make “Store obligations, owner and renewal date” visible in an audit or operational review.
How it works
Assign decision owners
Replace the Business owner, Procurement, Supplier, Evaluation team, Approver lanes with your actual functions. Keep the owner of “Competition route and criteria approved?” separate from the requester where your authority rules require it.
Configure the gates
Set evaluation criteria before bids arrive and hand signed obligations to the contract owner. Define what evidence is sufficient for “Final terms and supplier risk accepted?” and who may authorize an exception.
Connect downstream records
Link store obligations, owner and renewal date to the relevant purchase order, contract, supplier record or operational case. Set retention and review dates under your document policy.
Frequently asked questions
What does the source-to-contract process template include?
It covers define category need and business outcome, prepare specification and evaluation criteria, evaluate bids and negotiate terms, and store obligations, owner and renewal date, with two labelled decisions and rework paths.
Can the decision rules be changed?
Yes. Set evaluation criteria before bids arrive and hand signed obligations to the contract owner. Edit the gate labels, swimlanes and return paths before using the chart in your organization.
What evidence should be retained?
Keep the input to “Competition route and criteria approved?”, the evidence behind “Final terms and supplier risk accepted?”, approvals or exception decisions, and the closeout record: “Store obligations, owner and renewal date”.
Where this process fits
In most operations this process hands off to Procurement contract process.
Comes after
- Procurement contract process — Editable procurement contract process swimlane from “Confirm award, scope and commercial schedule” through “Required specialist reviews complete?” to a documented outcome. Includes named roles, exception paths and evidence.