
Work backwards from the tender deadline
Give your team time to check the bid before it closes. Start with the buyer’s submission instructions, then work backwards through approvals, pricing and the inputs each person needs.
The closing date is in everyone’s calendar. The supplier’s revised quote is still outstanding, the signatory is travelling and the estimator needs one more scope answer. A deadline reminder cannot tell you which of those gaps will hold up the final pack.
A preparation plan can. Give each task an owner, the input it depends on, a finish time and evidence that it is ready for the next person. Then look for the chain of work that leaves the least room to recover.
Download the tender planning worksheet
Capture the buyer’s dates before choosing your own
Read the current invitation, submission instructions and issued amendments. Record the closing date, exact time, stated time zone, submission channel and the source of that instruction. Keep the enquiry cutoff, briefing arrangements and any other fixed events in separate calendar entries.
An example checked on 14 November 2026 shows why this matters: the Department of Justice’s RFQ 03/2026 listing gives 6 November 2026 as the questions cutoff, 11 November for departmental responses and 19 November at 11:00 for closing. It requires responses through the eTender portal and excludes email or hand delivery. Those are instructions for that RFQ, not a general rule for every tender. Recheck the current notice and its erratum before relying on it. Department of Justice tender listing.
For physical submissions, plan the actual delivery as a task. Confirm the required tender box, delivery arrangements and deadline from the buyer’s instructions, including when you use a courier. Ask the delivery owner to retain the confirmation available through the specified process.
If two sources conflict, log the discrepancy and use the stated enquiry route. Give someone responsibility for checking subsequent notices. A changed date should have a source, a recorded check time and a clear update to the team’s plan.
Build the plan from the final handover
Choose an internal target for completing submission that leaves room for the actual channel and foreseeable recovery work. Estimate that allowance from your files, access, delivery arrangements and support options. Do not assume that a particular number of hours is enough for every bid.
- 1. Submission readyApproved files or package, a named submitter and a way to confirm completion.
- 2. Review completeTime to check the response, resolve corrections and obtain the required approvals.
- 3. Inputs availableSupplier answers, pricing, technical information and documents ready before the reviews that use them.
Work backwards from the internal submission target. When must the authorised reviewer approve the pack? When must corrections be finished? When does the first complete review start? What information must be ready for that review to mean anything?
Then check the dates forwards against reality. Confirm people’s availability, weekends, public holidays, supplier working hours and any fixed briefing or enquiry dates. A schedule that reaches back before the work can start is a warning to change the plan or reconsider the bid.
Make dependencies visible
“Finish pricing” is too broad to track on its own. The estimator may need a supplier quotation against the current specification, the applicable quantities and an agreed treatment of an exclusion. Link those inputs to the pricing review so a delay has an obvious consequence.
Use a short record for each handover: task, owner, predecessor, internal finish time, reviewer and completion evidence. A quotation marked “received” may still need its scope and validity checked. Distinguish received, checked, approved and submitted in your record.
Run independent work in parallel where your team has capacity. Company-document checks may begin while pricing is developed. Final pricing approval still depends on the information needed to support it. Allocate an owner and backup for submission, and confirm who is authorised to sign or approve before setting the dates.
A worked schedule for a small bid team
Fictional example. A team has already decided to bid on a maintenance contract. Its illustrative tender permits early electronic submission and closes on Friday at 11:00. After checking availability and the required work, the team chooses Thursday at 14:00 as its internal submission target.
The times below are illustrative choices. They do not promise that a maintenance bid can be prepared in this period or that one day is always an adequate margin.
| Milestone | Example time | Owner and dependency | Evidence to move on |
|---|---|---|---|
| Buyer’s closing deadline | Friday, 11:00 | Coordinator maintains the current source instruction | Current notice and amendments recorded |
| Internal submission target | Thursday, 14:00 | Named submitter needs the approved package and working access | Required completion confirmation retained |
| Release approval | Thursday, 11:00 | Authorised approver needs corrections and required signatures complete | Approved version identified |
| First full review | Wednesday, 15:00 | Reviewer needs pricing and technical content assembled | Issues assigned for correction before release approval |
| Pricing check complete | Wednesday, 11:00 | Estimator needs checked supplier inputs and the current pricing schedule | Totals and scope reconciled |
| Supplier inputs ready | Tuesday, 12:00 | Procurement owner needs responses to the issued specification | Scope, exclusions and validity checked |
The coordinator now works further back from Tuesday: when must requests go out, when will suppliers confirm they can respond, and which unanswered scope questions could prevent a usable quotation? The same process applies to technical documents, supporting records and approvals.
When a task slips, change the plan visibly
In the fictional schedule, a critical supplier quotation moves from Tuesday lunchtime to Wednesday lunchtime. That is after the planned pricing check. The coordinator records the revised arrival time and tells the estimator and reviewer that their original handover is no longer credible.
Identify which downstream tasks actually depend on the missing input. Continue unaffected work, then agree a realistic sequence for the affected checks and approvals. Record any extra capacity or alternate supplier option the team can genuinely use. Do not treat an unconfirmed quote as an agreed price just to keep the schedule looking complete.
Show the tender owner how much margin remains and what is unresolved. If the team cannot produce the required response in the time available, make that decision explicit. An internal reschedule does not extend the buyer’s closing deadline; only rely on a changed external date when it is supported by the buyer’s current instructions.
Review the plan at a frequency appropriate to the remaining work. A useful update answers four questions: what finished, what changed, what is blocked and who will act next. Keep a dated change note rather than silently overwriting a missed checkpoint.
Define what “submitted” means for this channel
Before the final handover, identify the exact approved files or physical pack and the person responsible for submitting them. Check the channel’s actual requirements: access, permitted formats, file sizes and confirmation steps for electronic submission; address, packaging, copies and tender-box arrangements for physical delivery.
Retain the confirmation available through that process and a copy of what was submitted. If an upload or delivery is uncertain, record the facts and follow the stated support or enquiry procedure promptly. Do not mark the bid submitted just because files were prepared or a courier was booked.
The bid-pack assembly guide covers the document checks behind these handovers. Use this planning worksheet to decide when those checks need to happen and who will complete them.
Start with the next real tender
Download the worksheet, enter the buyer’s verified dates and build one complete chain from the longest uncertain input to submission. Assign owners and ask them to confirm the handover times. You will have a plan the team can challenge and update before the last-minute rush.
A shared document or spreadsheet can be enough for a small team if ownership and versions stay clear. When comparing preparation software, test it against these same handovers and your required outputs. The TenderProSA walkthrough is a starting point for that assessment; your team still needs to check the source instructions and approve the response.