Back-schedule the bid: start from the submission date and the planned contract start date, apply the statutory minimum periods, then set internal hard stops that give your team real working time. The Procurement Act 2023 guidance sets tendering minima and a mandatory standstill period before award, and these become the fixed points everything else is built around. An AI workspace can hold those dates, the evidence library and the sign-off checkpoints in one place, so nothing slips.
TL;DR:
- A qualifying planned procurement notice published 40 to 365 days before tender notice can reduce the minimum window to 10 days, so check notices weekly.
- Schedule portal testing and final fixes by setting an internal submission target 24 to 48 hours before the actual deadline.
- Reserve three to five days for independent review, and freeze evidence at least three working days beforehand so reviewers assess stable materials.
- After award notice, allow at least eight working days before signing; weekends and bank holidays do not count, and mobilization planning should begin earlier.
- Writing and evidence gathering take 40% to 60% of the schedule; book subject matter experts in fixed windows rather than leaving contributions open ended.
Table of Contents
- Why a disciplined timeline matters for compliance and winning bids
- Legal minima and mandatory dates to plan around
- Stage-by-stage tender timeline: milestones, roles and typical durations
- How to build and back-schedule a tender timeline
- Tools, templates and how BidBlock can operationalise your tender timeline
- Common timing pitfalls and a compact checklist to add to your bid schedule
- Post-award timeline considerations including contract signing and mobilization
- Integration of resource allocation and team responsibilities within the tender timeline
- Risk assessment and contingency planning for delays during the tender process
- Communication plan and stakeholder coordination checkpoints
- Author perspective: changing timeline culture in bid teams
- Try BidBlock: organise deadlines, evidence and internal sign-offs
- FAQ
- Sources
Why a disciplined timeline matters for compliance and winning bids
A tight timeline is not just an administrative habit. It protects compliance, because the Procurement Act 2023 requires contracting authorities to give all suppliers equal time and to treat each deadline as fixed once set. For bidders, the same discipline determines whether a response is strong or rushed.
Every schedule should anchor to four fixed external dates: the tender notice, the submission deadline, the contract award notice, and the planned service start. Working back from these gives a realistic internal plan rather than a guess.
Starting early, as soon as a notice appears or a planned procurement notice signals intent, pays off in several ways:
- Earlier sight of teaming or subcontracting needs, so partnerships can be agreed calmly rather than at the last minute.
- More time to close capability or accreditation gaps before they become disqualifying issues.
- Fairer resource scheduling across writers, reviewers and subject matter experts who often support several bids at once.
Legal minima and mandatory dates to plan around
The Procurement Act 2023 sets out the shortest periods a contracting authority may allow for tendering and participation, and these minima set the floor for every schedule you build. According to GOV.UK guidance on time periods, the minimum tendering period generally varies depending on circumstances such as whether the procedure is electronic, the timing of document availability, and if special conditions like a qualifying planned procurement notice or urgency apply; these periods range from shorter durations where such conditions exist to longer durations in less streamlined situations.
A qualifying planned procurement notice, published between 40 and 365 days before the tender notice, can reduce the minimum tendering period to just 10 days. This single mechanism changes how early you need to start watching a pipeline, since authorities that signal early can legally compress the formal window later.
Section 54 of the Procurement Act 2023 also requires authorities to keep time limits equal for all suppliers and to factor in contract complexity when setting them. After award, a mandatory standstill period of at least eight working days must pass before the contract is signed, and working days exclude weekends and bank holidays, so a standstill spanning a holiday period runs longer in calendar terms than it first appears.
Stage-by-stage tender timeline: milestones, roles and typical durations
A tender runs through nine distinct stages, each with its own purpose, rough duration and natural owner. Mapping these against your calendar, rather than treating the whole process as one undifferentiated block, is what prevents the final week from absorbing every unresolved problem.
- Opportunity identification: ongoing, owned by business development; spot notices and planned procurement notices as they appear.
- Bid/no-bid decision: 1 to 3 days, owned by a senior sponsor; a fast, honest call protects capacity for bids you can actually win.
- Document analysis: 2 to 5 days, owned by the bid manager; this is where requirements, scoring weightings and compliance obligations get mapped.
- Bid planning: 2 to 3 days, owned by the bid manager; this sets the schedule itself, assigns owners and books reviewer time.
- Clarification questions: aligned to the buyer's published window, owned by the bid manager; questions should be submitted early enough to use any answer before drafting locks in.
- Writing and evidence gathering: the largest block, often 40% to 60% of total time, owned by writers and subject matter experts together.
- Review and quality assurance (Red Team): 3 to 5 days, owned by an independent reviewer outside the writing team.
- Final submission: 1 day, owned by the bid manager, with the actual upload completed well ahead of the portal deadline.
- Post-submission and standstill actions: variable, owned by the bid manager, covering debrief requests and award notice tracking.
Pro Tip: Protect evidence gathering as its own line in the schedule; teams that fold it into writing time nearly always run short on supporting proof at the review stage.
How to build and back-schedule a tender timeline
Start from the two dates you cannot move: the submission deadline and the desired service commencement date. Every other milestone is placed by counting backwards from these, leaving enough room for the mandatory minima and your own quality checkpoints.
A practical sequence:
- Confirm the submission deadline and the statutory minimum period that applies to this notice.
- Set an internal submission target 24 to 48 hours before the actual portal close, to allow time for a portal test and any last-minute fixes.
- Place an evidence-freeze date before Red Team review, so reviewers work against a stable document rather than a moving target.
- Size buffers to complexity: a straightforward framework response might need a one-day buffer at each gate, while a complex multi-lot bid often needs three to five days.
- Rebuild the schedule immediately whenever the buyer reissues documents or amends the deadline, and push the revised dates to every owner the same day.
A simplified illustrative example for a bid with a submission deadline of March 20 and a service start of June 1:
Tools, templates and how BidBlock can operationalise your tender timeline
Four templates belong in every bid team's toolkit:
- A master bid schedule, showing every external deadline and internal hard stop in one view.
- A clarification tracker, logging questions asked, answers received and any resulting changes to scope or dates.
- An evidence index, mapping case studies and proof points to the questions they answer.
- A Red Team checklist, covering compliance, scoring alignment and plain-English clarity.
An AI workspace holds these elements together rather than scattered across spreadsheets and email threads. It organises an evidence library drawn from past submissions, sets reminders against internal hard stops like evidence freeze and Red Team dates, and flags accreditation gaps before they become last-minute blockers.
Pro Tip: Build your master bid schedule from a clarification-question template first; most schedule slippage traces back to clarification answers arriving after drafting has already locked in.
Common timing pitfalls and a compact checklist to add to your bid schedule
A handful of timing errors recur across bid teams. Quality assurance started too late, so Red Team comments arrive after the document is effectively finished. Planned procurement notices go unnoticed, so a shortened 10-day window catches the team unprepared. Clarification time gets underestimated, so questions submitted late miss the buyer's answer window entirely.
A short checklist closes most of these gaps:
- Evidence freeze: set it at least three working days before Red Team; fixes drafting against a moving evidence base.
- Red Team buffer: book reviewer time the day the bid is confirmed, not the week before submission.
- Portal test window: schedule 24 to 48 hours before close; catches upload or format failures with time to resolve them.
- Planned procurement notice check: review live notices weekly; prevents a surprise 10-day window.
Post-award timeline considerations including contract signing and mobilization
Winning the bid does not end the timeline discipline. Once the contract award notice is published, the mandatory standstill period of at least eight working days must run before the contract can be signed, and that clock pauses in effect over weekends and bank holidays, so it is worth marking the likely signing window in calendar days as well as working days.
During standstill, unsuccessful bidders may request a debrief, and it is good practice to prepare responses in advance rather than drafting them under pressure once requests arrive. Once standstill closes and the contract is signed, mobilisation begins, and this phase deserves its own schedule rather than being treated as an afterthought to winning.
Mobilisation typically covers staff onboarding or TUPE transfer where relevant, system and access setup, compliance checks such as insurance and accreditation confirmation, and a formal handover from the bid team to the delivery team. Building a short mobilisation plan alongside the bid itself, rather than starting it only after signature, shortens the gap between award and service start. It also reduces the risk that promises made in the winning bid, particularly around social value commitments or named personnel, get lost in the handover.
Commencement timing also has downstream effects worth flagging early: invoicing and payment terms need to be ready from day one, and smaller suppliers in particular benefit from confirming invoicing compliance obligations before service start rather than scrambling once delivery is underway.
Integration of resource allocation and team responsibilities within the tender timeline
A timeline is only as reliable as the people assigned to hold it. Resource allocation should happen at the bid planning stage, not be improvised once writing is already behind schedule. Each stage in the nine-stage model benefits from a named owner, and that owner should be confirmed in writing before the clock starts rather than assumed.
Subject matter experts are usually the scarcest resource, since they are often supporting operational delivery alongside bid input. Booking their time in fixed windows, rather than leaving contributions open-ended, protects both the bid and their day job. A bid manager who maps named contributors against each milestone in the master bid schedule can see conflicts early, when there is still time to resolve them by bringing in additional support or adjusting the plan.
Reviewers deserve the same treatment. Red Team reviewers should be confirmed and calendar-blocked at the start of the bid, not chased in the final week, because independent review loses most of its value when it happens under time pressure. Where a bid spans multiple lots or a consortium, resource allocation also needs to account for partner organisations, whose own internal sign-off processes may run on a different rhythm and need to be built into the shared schedule rather than assumed to match.
Risk assessment and contingency planning for delays during the tender process
Delays in tender timelines tend to come from a small number of recurring sources: late or incomplete answers to clarification questions, reissued documents that reset parts of the schedule, illness or unavailability among key contributors, and portal or IT issues close to submission. Naming these risks at the planning stage, rather than discovering them mid-process, is what makes contingency planning possible.
A practical approach is to build buffer time into the schedule proportional to complexity, as covered earlier, and to identify a backup owner for each critical role before the bid starts. If the bid manager, lead writer or key subject matter expert becomes unavailable, having a named second person who already understands the bid reduces the time lost to handover.
Reissued or amended tender documents deserve a specific response: as soon as an amendment is published, the schedule should be revised immediately and the new dates communicated to every owner the same day, rather than left to surface informally. Authorities are required to consider whether time limits need revising when documents change, so a reissue is not unusual, and treating it as a routine schedule event rather than a crisis keeps the team calmer.
Finally, build in a small amount of slack before the internal submission target itself, separate from the portal test buffer, so that one unexpected delay does not cascade into a missed deadline.
Communication plan and stakeholder coordination checkpoints
A tender timeline only works if everyone involved knows where it stands at any given point, which means communication needs its own structure rather than happening informally. A short daily or twice-weekly check-in during the writing and review stages, with a fixed agenda covering progress against the schedule and any emerging risks, catches slippage while there is still time to correct it.
Stakeholder coordination checkpoints should be built into the master bid schedule itself, not left as separate meetings nobody remembers to book. Useful fixed points include a kickoff session once bid/no-bid is confirmed, a mid-point review at the end of document analysis, a pre-Red-Team briefing, and a final go/no-go check before submission. Each checkpoint should have a clear decision attached to it, rather than existing purely as a status update.
Where a bid involves external partners or subcontractors, communication needs an agreed cadence from the outset, including who owns updates to the shared schedule and how quickly a partner is expected to flag a problem. Clarification questions submitted to the buyer should also be logged and shared internally the moment an answer arrives, since a change buried in one person's inbox can silently invalidate work already underway elsewhere in the bid.
Author perspective: changing timeline culture in bid teams
Most late bids are not caused by one big failure. They come from small slippages, each individually forgivable, that stack up because no one owned the schedule itself. We think the fix is cultural as much as procedural: treat internal hard stops as fixed, run a short post-standstill review on every bid, win or lose, and timelines start protecting quality instead of just tracking dates.
— Syed
Try BidBlock: organise deadlines, evidence and internal sign-offs
Keeping a tender timeline on track usually comes down to having one place where deadlines, evidence and sign-offs live together, rather than spread across spreadsheets, inboxes and someone's memory. We provide a workspace built around public sector submissions, where past responses and social value evidence sit ready to reuse rather than rewritten from scratch each time.
With plans running from Free through to Standard, Pro and Max, we offer a starting point for teams of any size to see the BidBlock workspace and try it against a live opportunity.
- Hold your master schedule, evidence library and accreditation records in one workspace.
- Set automated reminders against internal hard stops like evidence freeze and Red Team dates.
- Draft responses grounded in your own past submissions rather than generic text.
Start on the Free plan and see how a structured workspace changes the shape of your next bid.
FAQ
What are the seven stages of the tendering process?
Common models describe between five and nine stages, with the seven-stage version typically covering opportunity identification, bid or no-bid decision, document analysis, bid planning, writing, review, and submission. Post-submission activity and standstill are sometimes folded into a final "evaluation and award" stage rather than listed separately.
How long should a tender process take overall?
There is no single fixed duration, since it depends on contract complexity and which statutory minimum tendering period applies, ranging from 10 days where a qualifying planned procurement notice exists up to 35 days for non-electronic processes with delayed documents. Internal preparation before the formal notice, and the mandatory standstill period after award, typically add further time beyond the tendering window itself.
What are the five stages of the tendering process?
A commonly used five-stage model groups the process into planning, document preparation, submission, evaluation, and award, each of which can be broken down further into the nine-stage model used by many bid teams. The exact grouping varies between guidance sources, so the number of stages matters less than making sure each task has a named owner and a date.
What is the standstill period and how long does it last?
The standstill period is a mandatory pause of at least eight working days after the contract award notice is published, during which the contract cannot be signed. Working days exclude weekends and bank holidays, so a standstill period that crosses a holiday runs longer in calendar days than the eight-day minimum suggests.