Procurement tender process
Editable procurement tender process swimlane from “Approve scope and tender route” through “Submissions received by deadline and compliant?” to a documented outcome. Includes named roles, exception paths and evidence.
What the procurement tender process process is
The workflow starts at “Approve scope and tender route”. The next two steps, “Publish or invite under tender rules” and “Manage bidder questions and addenda”, 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 “Submissions received by deadline and compliant?” and “Evaluation and approvals complete?”. The first branch leads to reject late or noncompliant bid under published rules; the second can require resolve conflicts, clarification or scoring gaps. If that cannot be resolved, the case can end at “Cancel tender and notify bidders”. Adapt publication, opening and standstill steps to the rules that apply to your organization.
What this flowchart covers
In this template
- Approve scope and tender route followed by publish or invite under tender rules.
- Submissions received by deadline and compliant? with a route for reject late or noncompliant bid under published rules.
- Close tender and record submissions and evaluate technical bids and commercial bids as separate supplier and internal handoffs.
- Evaluation and approvals complete? with resolve conflicts, clarification or scoring gaps when the decision fails. A separate decision can end at “Cancel tender and notify bidders”.
- Consolidate scores and conflict declarations, approve award recommendation and notify bidders and retain tender record as the controlled closeout.
When to use this template
- Use it to agree who owns “Approve scope and tender route” and what information the next role needs.
- Use it when the answer to “Submissions received by deadline and compliant?” is unclear or decisions are made outside the record.
- Use it to make “Notify bidders and retain tender record” visible in an audit or operational review.
How it works
Assign decision owners
Replace the Business owner, Procurement, Supplier, Evaluation committee, Approver lanes with your actual functions. Keep the owner of “Submissions received by deadline and compliant?” separate from the requester where your authority rules require it.
Configure the gates
Adapt publication, opening and standstill steps to the rules that apply to your organization. Define what evidence is sufficient for “Evaluation and approvals complete?” and who may authorize an exception.
Connect downstream records
Link notify bidders and retain tender record 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 procurement tender process template include?
It covers approve scope and tender route, manage bidder questions and addenda, evaluate technical bids and commercial bids, and notify bidders and retain tender record, with three labelled decisions and rework paths.
Can the decision rules be changed?
Yes. Adapt publication, opening and standstill steps to the rules that apply to your organization. Edit the gate labels, swimlanes and return paths before using the chart in your organization.
What evidence should be retained?
Keep the input to “Submissions received by deadline and compliant?”, the evidence behind “Evaluation and approvals complete?”, approvals or exception decisions, and the closeout record: “Notify bidders and retain tender record”.
Where this process fits
In most operations this process follows Strategic sourcing process and hands off to Bid evaluation process.
Comes before
- Strategic sourcing process — Editable strategic sourcing process swimlane from “Identify spend or upcoming need” through “Sourcing route and competition justified?” to a documented outcome. Includes named roles, exception paths and evidence.
Comes after
- Bid evaluation process — Editable bid evaluation process swimlane from “Lock evaluation criteria and conflict declarations” through “Bid technically compliant?” to a documented outcome. Includes named roles, exception paths and evidence.