How to Build a Tender Programme That Wins

The tender programme wins the job — or it loses it quietly in clarification. Owners and operators have learned to read schedules. A bar chart that is merely shorter than the competition is not a strategy; it is an invitation to be scored down for fantasy. Tender programme work worth paying for is aggressive, buildable, and defensible under scrutiny.

Three programmes, not one pretty picture

Serious bids carry scenario thinking even when only one file is submitted:

• Expected — the plan you would actually run with known design maturity and market lead times
• Accelerated — priced levers (resequence, overtime envelopes, procurement pull-forwards) with cost and risk attached
• Shortest viable — the edge of defensibility; anything tighter is a commercial bet, not a schedule

Without that spread, leadership cannot see what time costs. With it, the bid can choose how much risk to wear instead of discovering the number after award. On hyperscale work we have supported, the winning posture was never "shortest bar at all costs" — it was "shortest bar we can defend in the interview."

Buildability before software

A schedule is only as good as the plan behind it. Before loading Primavera P6 or MS Project, lock the construction and commissioning story: sequence, access, interfaces, live-site constraints, and the long-lead chain (transformers and switchgear in the 18–24 month band are a classic — see transformer and switchgear lead times). If the narrative cannot be told without the Gantt, the Gantt will not survive a sophisticated client.

Operator-standard baselines — Microsoft's among them — punish improvisation after award. The tender file is where that standard should first appear, not the month-three recovery workshop.

What evaluators actually probe

In interviews and clarifications, the questions that decide scores are predictable:

1. What sits on the critical path at award, and why should we believe it?
2. Which packages are OFCI/LLE and who owns the order dates?
3. How does commissioning L1–L5 sit in the logic — or is it a summary bar after PC?
4. What happens if a key factory slips eight weeks — which lever is real?

If your team cannot answer without inventing, the programme is decoration. Pair the file with a short narrative that names assumptions, exclusions, and residual risks. Silence on assumptions is how tender programmes become disputes.

Integrity is part of winning

Open ends, sequestered float, and constraint forests might make a date look achievable on paper. Under programme audit they read as posture. Sophisticated owners now run mechanical and narrative checks at tender. Submit a file you would be willing to defend after award — because you will.

Engagement shapes that work

• Full tender programme from first principles for the bid team
• Peer review of an in-house draft before submission (cheaper than a lost score)
• Owner-side assessment of bidder programmes for realism and hidden risk transfer

The third is underused: awarding on a fantasy schedule transfers the delay into the job. Reading the programme properly at tender is project controls before the contract exists.

The posture that works

Win the work. Deliver on promise. Protect the margin. A tender programme that only achieves the first sentence has already spent the other two. Build the shortest defensible timeline — and put the indefensible ideas in the risk register, not in the critical path.

Nomad SPS develops tender programmes that hold up under operator and head-contractor scrutiny — the same planners behind $2.1B+ of hyperscale bids in Australia. If time is your number one factor, talk to us.