The construction program is one of the most scored — and most poorly executed — components of a civil tender response. Here is how to build one that demonstrates control of the works, justifies your methodology, and scores against the evaluation criteria.
A construction program for tenders is the time-based articulation of how a contractor will deliver the works. In a tender response, it does double duty: it sequences the project on a calendar, and it tells the evaluator a story about whether the contractor genuinely understands the job. Tender evaluators read programs as a window into your operational thinking — not just as a Gantt chart with the right finish date.
For civil construction SMEs in Australia, the quality of the tender program is one of the single biggest swing factors in non-price evaluation. A program that demonstrates control of the works, a defensible critical path, productivity-based durations, and honest weather and contingency provisions will outscore a competitor’s bid even where the price is comparable. A program that simply distributes activities across the contract duration with round-number durations and no logic links will signal an inexperienced submission no matter how good the rest of the response reads.[1]
This guide walks through how to build a tender-grade construction program for civil works — from the work breakdown structure through to critical path logic, productivity-based durations, float and contingency, and the presentation that turns the program into evaluation points. It pairs with our companion guide on writing a construction methodology statement; the methodology and the program are two views of the same delivery plan.
In This Guide
- Why the construction program matters in tender evaluation
- What evaluators actually look for in a tender program
- The relationship between program and methodology
- Choosing the right scheduling tool
- Building the work breakdown structure
- Activity logic and the critical path
- Productivity-based durations
- Float, contingency, and weather allowances
- Linking the program to plant, crews, and resources
- Milestones, hold points, and interface dates
- Eight common programming mistakes that cost tenders
- How to present the program in a tender response
- Worked example — a council road reconstruction program
1. Why the construction program matters in tender evaluation
On a typical Australian government civil tender, the construction program is either a separately scored non-price criterion (5–15% of the total weighted score) or it is the principal evidence that supports the methodology criterion (which is usually weighted 15–25%). Either way, it carries weight.
More importantly, the program is the first place an experienced evaluator looks to test whether the methodology statement is real. A contractor can write polished prose about staged delivery, hold points, and traffic management; the program tells the evaluator whether the contractor has actually thought about how those things relate to one another in time. A two-week earthworks duration in the methodology and a six-week earthworks bar in the program is a credibility-destroying mismatch.
For civil works specifically, the program also drives evaluation of several adjacent criteria: traffic management adequacy (does the program allow enough time for staged traffic switches?), environmental controls (are wet weather provisions reasonable?), resource availability (can the listed key personnel actually be on site when the program says they will be?), and interface management (does the program align with the principal’s own constraints such as utility shutdowns, possession windows, or rail occupations?).
2. What evaluators actually look for in a tender program
Across civil tender evaluations, evaluators consistently look for the same set of attributes. A program that demonstrates each of these attributes will score well; a program that lacks any of them will not.
- Sensible sequencing — activities follow the logical order of civil works: site establishment, services, earthworks, drainage, pavement, surfacing, line marking, demobilisation
- Defensible critical path — the longest chain of dependent activities through the program is identifiable, makes physical sense, and explains the total project duration
- Activity durations that match real productivity rates — not round numbers, not over-optimistic, not padded
- Honest weather and contingency allowance — visible in the program, not buried in unstated optimism
- Float that flows naturally from logic, not added arbitrarily
- Milestone alignment with the principal’s specified milestones, hold points, and interface dates
- Resource consistency — durations and concurrency are achievable with the plant and crew levels nominated in the methodology
- Pre-construction activities included — submittals, ITP approval, traffic management plan approval, environmental management plan approval
- Practical completion and defects liability dates clearly identified
Evaluators discount, sometimes heavily, for the absence of any of these. A program with no critical path indication, or with activities shown as parallel bars without logic links, signals an unsophisticated submission regardless of how the prose reads. Conversely, a program that visibly captures all these elements creates a strong impression of operational maturity that often carries through the whole evaluation.
3. The relationship between program and methodology
The program and the methodology statement are two representations of the same delivery plan. They must be internally consistent — and the easiest way to ensure consistency is to build them together rather than in sequence.
A useful working order is:
- Draft the methodology narrative around the major stages of the works — site establishment, services protection, bulk earthworks, drainage, pavement preparation, surfacing, ancillary works, demobilisation
- Identify the activities that sit within each stage and the logical sequence of those activities
- Identify the plant, crews, and key personnel for each activity
- Build the program structure from the same stages and activities
- Apply productivity-based durations and logic links
- Iterate the methodology and the program against each other until they tell a single, coherent story
The methodology explains how you will do each stage; the program shows when. Every activity named in the methodology should appear in the program; every program activity should be reflected in the methodology. Where the principal asks for staged delivery — say, a road reconstruction broken into three handover stages — both documents should mirror the stages in identical terms.
4. Choosing the right scheduling tool
For Australian civil construction tenders in the $50K–$2M range, four scheduling tools dominate. Each has a sensible role, and the choice should be matched to the size and complexity of the project, the principal’s reporting requirements, and the contractor’s existing capability.[2]
| Tool | Best fit | Considerations |
|---|---|---|
| Microsoft Project | Most civil SME tenders up to ~$5M; widely accepted by councils and state agencies | Reasonable cost, broadly familiar to evaluators, good Gantt presentation, supports basic critical path logic |
| Primavera P6 | Larger contracts where the principal mandates P6 reporting; some state road agency contracts | Industry-standard for major infrastructure; significant licence and skill cost; overkill for small contracts |
| Asta Powerproject | Civil contractors specifically; popular in UK and growing in Australia | Strong civil-specific features; cost between MS Project and P6 |
| Excel-based Gantt | Very small tenders where the principal accepts a simple bar chart | Acceptable for some council and minor works tenders; do not use for any tender where critical path or logic links are expected to be shown |
Tool selection should match contract scale and principal requirements. Always check the request for tender for any mandated software, exchange format, or reporting requirement before selecting a scheduling tool.
One rule of thumb: if the request for tender specifies a particular software or reporting format, comply. If it specifies an exchange format such as XER (Primavera) or XML, you must use a tool that exports to that format. If it specifies nothing, use the most capable tool you can credibly maintain through the project — not just through the tender.
5. Building the work breakdown structure
The work breakdown structure (WBS) is the hierarchical decomposition of the works into manageable activities. For a tender-grade civil program, three levels of WBS are usually enough:
- Level 1 — Project (e.g. Smithfield Road Reconstruction)
- Level 2 — Stage or major work element (e.g. Site Establishment, Stage 1 Earthworks, Stage 1 Drainage, Stage 1 Pavement)
- Level 3 — Activity (e.g. Bulk excavation, Subgrade preparation, Lay 200 mm DGB20)
For most council and state government civil tenders, Level 3 activities should be sized to last between three days and three weeks. Shorter activities create unnecessary noise in the program; longer activities hide the granularity that evaluators are looking for. A pavement construction activity broken into “Subgrade preparation,” “Subbase delivery and placement,” “Base course delivery and placement,” and “Surfacing” tells a much clearer story than a single “Pavement construction” bar spanning eight weeks.
Standard civil WBS template
For most road, drainage, and earthworks contracts, the following Level 2 elements form a reliable WBS template that can be adjusted to the specific scope:
- Pre-construction (insurances, bonds, submittals, ITP and SWMS approval)
- Site establishment (compound, traffic management setup, environmental controls, services location and protection)
- Demolition and clearing
- Bulk earthworks (cut to fill, cut to spoil, import to fill)
- Drainage (pit and pipe, kerb inlets, headwalls, scour protection)
- Subgrade preparation
- Pavement construction (subbase, base, surfacing)
- Ancillary works (kerbs, footpaths, line marking, signage, landscape reinstatement)
- Stage handovers (for staged works)
- Demobilisation and defects rectification
- Practical completion and defects liability period (shown as milestones)
6. Activity logic and the critical path
Logic links between activities are what make a Gantt chart into a program. Without logic, the bars on the chart are essentially decoration. With logic, the program calculates a critical path, identifies float, and responds correctly to changes in activity duration.
The four standard logic relationships are:
- Finish-to-Start (FS) — the second activity starts when the first finishes. The dominant relationship in civil works (you cannot lay base until subbase is placed)
- Start-to-Start (SS) — the second activity starts when the first starts. Useful for staggered concurrent crews (e.g. drainage crew starts 5 days after earthworks crew on a long linear project)
- Finish-to-Finish (FF) — the second activity finishes when the first finishes. Less common in civil works
- Start-to-Finish (SF) — rare in construction; mostly an artefact of poorly built programs
For civil works, the FS relationship handles 80–90% of the logic. Use SS with a lag (typically expressed in days) to model staggered concurrent activities — particularly common in linear projects like road reconstruction where multiple work fronts progress in sequence behind one another.
The critical path
The critical path is the longest sequence of dependent activities through the program. Activities on the critical path have zero float — any delay to a critical path activity delays the project. Tender programs must visibly indicate the critical path, typically by coloured bars (red is conventional) or by a clear note.
The most common civil critical path runs:
Site establishment → bulk earthworks → drainage → subgrade → pavement → surfacing → ancillary works → practical completion
If your program shows a different critical path, the evaluator will look for the reason — typically a long-lead procurement item, a specific principal-imposed milestone, or a staged handover constraint. The reason should be visible from the program logic itself; if it is not, add a note.
7. Productivity-based durations
The single most diagnostic feature of a tender program — for an experienced evaluator — is the duration of individual activities. Round-number durations (5 days, 10 days, 4 weeks) signal an estimator who has guessed. Durations like “7 days,” “12 days,” “23 days” signal an estimator who has actually computed productivity.
The right way to determine an activity duration is to work it back from quantity and productivity:
Duration (days) = Quantity ÷ (Crew productivity rate × Working hours per day)
For example, a 4,000 m³ bulk earthworks activity with a crew comprising one 20-tonne excavator and three 12-tonne articulated dump trucks, operating at a sustained productivity of around 180 m³ per hour over a 9-hour working day, calculates to:
4,000 ÷ (180 × 9) = 2.47 days, rounded up to 3 working days in the program.
The advantage of productivity-based durations is twofold. They are defensible if the evaluator asks (and on larger contracts, the evaluator will ask). And they tie the program directly to the resources nominated in the methodology — meaning a change to either drives a recalculation of the other.
Indicative civil productivity rates
The following rates are starting-point indicative ranges only. Actual productivity varies significantly with material, haul distance, site access, weather, and crew experience.[3] Always benchmark against your own historical project records before committing to a tender duration.
| Activity | Indicative productivity range |
|---|---|
| Bulk excavation, free-digging material, single excavator + trucks | 120–250 m³ per hour |
| Bulk fill placement and compaction, sheepsfoot or smooth drum roller | 150–300 m³ per hour |
| Pipe laying — DN300 to DN600 RCP, normal trenching conditions | 30–80 lineal metres per day |
| Kerb and gutter — extruded | 200–400 lineal metres per day |
| Subbase placement and compaction | 800–1,500 m² per day per crew |
| Asphalt surfacing — paver-laid AC14 | 1,500–3,500 m² per day |
| Line marking — long-line thermoplastic | 3,000–8,000 lineal metres per day |
8. Float, contingency, and weather allowances
Three time provisions need to sit somewhere in a tender program: float, weather, and general contingency. How you expose each of them in the program affects both your evaluation score and your contractual exposure once the contract is awarded.
Float
Float is the difference between an activity’s earliest possible finish and its latest possible finish without delaying the project. It arises naturally from the logic — non-critical paths have float; the critical path has zero float. Float should not be added arbitrarily; it should emerge from the calculated logic. Most modern scheduling tools display float as part of the standard program view.
Weather allowance
Weather allowance should be explicit. For most Australian civil works, a defensible weather allowance is in the range of 5–10% of the total construction duration for projects in NSW, Victoria, and southeast Queensland; up to 15% for projects in tropical Queensland or northern Australia during the wet season; and project-specific provisions for unusual circumstances (e.g. coastal works during a known storm window).
The Bureau of Meteorology publishes long-term climate data that supports project-specific weather allowance — historical rainy day counts by month for each climatological station are freely accessible and provide defensible benchmarks for tender programs.[4]
Two ways to expose weather allowance in a program both work:
- Distributed weather allowance — durations include a small weather contingency loading. The advantage is realism; the disadvantage is that it is invisible to the evaluator.
- Discrete weather allowance bar — a clearly labelled “Weather contingency” activity inserted into the program, typically at the end of major outdoor work elements. The advantage is transparency; the disadvantage is that it makes the total duration look longer.
For tender programs specifically, the discrete weather allowance bar is generally the better approach. Evaluators respect transparency; hidden contingency reads as either naive or evasive.
General contingency
A separate general contingency, distinct from weather, is appropriate for projects with significant unknowns — underground services in old urban areas, unconfirmed material properties, or principal-side dependencies. Where included, it should be modest (typically 5–10% of construction duration) and labelled honestly.
Programmer’s discipline. Never inflate activity durations to create hidden float. Build the program with honest durations and expose contingency as separate bars. When the project actually runs, the discipline pays off — you will know whether you are losing time to weather, to unforeseen conditions, or to crew underperformance, because each is accounted for separately.
9. Linking the program to plant, crews, and resources
A tender program that aligns with the resources nominated in the methodology is dramatically more credible than one that does not. The check is mechanical: for each activity, the program implies a crew working at a particular productivity for a particular duration. Multiply that out across the program and you get an implied total resource demand. That demand must match the plant and crews you have nominated as available to the project.
The clearest way to surface this alignment is to include a simple resource histogram alongside the program — even a basic chart showing crew numbers and major plant items by month. The histogram tells the evaluator that you have thought about resource concurrency. It also reveals problems: a histogram showing four concurrent crews where the methodology nominates two is an obvious contradiction.
Common civil crew compositions for indicative planning:
- Earthworks crew: 1 supervisor, 1–2 excavator operators, 2–4 truck operators, 1–2 dozer/grader operators, 1 roller operator, 1 labourer
- Drainage crew: 1 supervisor, 1 excavator operator, 1 truck operator, 2–3 pipe layers/labourers, 1 plant operator (compaction)
- Pavement crew: 1 supervisor, 1–2 grader operators, 1 roller operator, 2–3 truck operators, 1 paver operator (for asphalt), 2–3 labourers
- Concrete crew: 1 supervisor, 1–2 form carpenters, 1 steel fixer, 2–3 concretors, 1 finisher, 1 plant operator
10. Milestones, hold points, and interface dates
Most civil tenders specify a small number of milestones that the program must reflect. These typically include:
- Commencement of works on site — usually a number of working days after Letter of Acceptance
- Practical completion — the contractual completion date
- Stage handovers — for staged works, each handover is a distinct milestone
- Hold points and witness points — defined in the specification and the ITPs
- Principal-supplied items and information dates — the dates by which the principal must provide drawings, instructions, access, or material supplies
- Defects liability period commencement and conclusion — typically 12 months from practical completion for council works, 12–24 months for state road works
The program must show every specified milestone. Where the principal has imposed an interface constraint — a road or rail occupation, a utility shutdown, a possession of an adjacent site — the program must reflect it. Where the program proposes early completion of a milestone (commonly used as a competitive differentiator), the methodology must explain how the early date is achievable, not just claim it.
11. Eight common programming mistakes that cost tenders
Across the civil tender programs we review, the same mistakes recur. Each costs evaluation points; collectively they can shift a winning submission to second place.
- No logic links. Activities shown as parallel or arbitrarily-sequenced bars with no defined dependencies. The Gantt chart becomes decoration.
- No identified critical path. Evaluators expect to see the critical path called out — either in the program itself (typically by coloured bars) or in a short note.
- Round-number durations everywhere. Every duration is 5, 10, 15, or 20 days. Signals an estimator who has guessed rather than calculated.
- Total duration that does not match the proposed Date for Practical Completion. A simple arithmetic error that creates an instant credibility problem.
- No weather allowance. For any project longer than about four weeks running through any season other than peak dry, weather should be visible in the program.
- No pre-construction activities. Programs that start with “Site establishment” on Day 1 ignore the 2–6 weeks of submittals, ITP approvals, traffic management plan approvals, and procurement that actually need to happen first.
- Activities that cannot be physically delivered with the nominated crews. A pavement activity scheduled to deliver 10,000 m² per day when the methodology nominates a single paver crew — the contradiction is fatal to credibility.
- No connection to the methodology narrative. The methodology describes a four-stage delivery and the program shows two stages, or vice versa. The two documents must be locked together.
12. How to present the program in a tender response
A program presented well scores better than a program presented as an opaque appendix. Five practical presentation rules apply across virtually every civil tender:
1. Include a one-page program summary in the body of the response
A simplified Level 2 program — major stages only, with key milestones — fits on a single landscape A3 page. Include this in the body of the response, with the full Level 3 program as an appendix. The evaluator scans the summary; only an evaluator who has questions reads the full program.
2. Use clear visual conventions
Differentiate critical and non-critical activities visually. Highlight milestones distinctly (diamonds or flagged bars). Use a clear date axis. Avoid clutter — strip out unused columns and float bars unless the evaluator needs to see them.
3. Include a short narrative explaining the program logic
Two or three paragraphs of narrative — sitting next to the program in the response — explaining the staging logic, the critical path, the weather and contingency provisions, and any unusual sequencing decisions. The narrative gives the evaluator the story; the program gives them the evidence.
4. Reference the methodology explicitly
“This program reflects the four-stage delivery sequence described in Section [X] of our methodology statement, with Stage 1 critical path running through bulk earthworks and drainage installation.” Cross-references between program and methodology make the response easier to evaluate and reinforce the impression of an integrated submission.
5. Provide the program in both PDF and the native software format
PDF for the evaluator to view. Native format (MPP, XER, or XML as required) for the principal’s planner to review post-award. Some tenders specifically require both; even where they do not, providing both is professional practice.
13. Worked example — a council road reconstruction program
To make the principles concrete, consider a typical council tender: 1.2 km of urban road reconstruction including kerb and gutter renewal, drainage upgrade (28 new pits, 480 m of new RCP), pavement reconstruction to 280 mm depth, 14,500 m² of asphalt resurfacing, and replacement of all line marking. Contract duration nominated as 18 weeks. Staged delivery in three sections to maintain local access throughout.
Level 2 program structure
| Stage / element | Indicative duration (weeks) | Notes |
|---|---|---|
| Pre-construction (submittals, ITPs, TMP approval, materials procurement) | 3 weeks | Runs prior to physical site start |
| Site establishment and TMP setup | 1 week | Includes site office, environmental controls, sediment fencing |
| Stage 1 (eastern 400 m) — services protection, demolition, drainage, kerb and gutter, pavement, asphalt | 5 weeks | Includes 2 days weather contingency within stage |
| Stage 2 (central 400 m) — same scope | 5 weeks | Stage 1 substantially complete before Stage 2 commences full intensity |
| Stage 3 (western 400 m) — same scope | 5 weeks | Includes 2 days weather contingency within stage |
| Line marking, signage, landscape reinstatement (full length) | 1 week | Following Stage 3 asphalt completion |
| Demobilisation and practical completion inspection | 1 week | |
| Total construction duration | 18 weeks | Matches contract DPC |
Critical path
For this project, the critical path runs: Site establishment → Stage 1 drainage (longest single duration activity at 12 working days) → Stage 1 pavement → Stage 2 drainage → Stage 2 pavement → Stage 3 drainage → Stage 3 pavement → Stage 3 asphalt → Line marking → Practical completion.
Stage staggering using SS logic with lag
Within each stage, drainage commences with a 5-working-day lag after the end of services protection. Kerb and gutter commences with a 3-working-day SS lag from the start of drainage. Pavement commences once drainage is complete on each stage section. This staggered concurrent approach is the key to delivering each 400 m section in 5 weeks while maintaining single-crew resourcing.
Weather and contingency
Within each of the three stages, a 2-day weather contingency is included at the end. A separate 3-day general contingency bar is included before practical completion. Total weather and contingency allowance is approximately 9 days across 18 weeks, or roughly 10% of construction duration — defensible for an autumn-into-winter program in coastal NSW or southeast Queensland.
Resource histogram
The resource histogram shows one earthworks/drainage crew, one kerb crew, one pavement crew, and one asphalt subcontractor working in sequence across the three stages — never more than two concurrent crews on site at any time, consistent with the methodology and consistent with the project’s traffic management constraints.
This is, ultimately, what a tender-grade construction program does: it tells a coherent story about how the works will be delivered, supported by defensible logic, defensible durations, and visible discipline around float and contingency. Done well, it is the most powerful single piece of evidence in your non-price response.
The bottom line for civil contractors
The construction program is not just a Gantt chart — it is the principal piece of evidence the evaluator uses to test whether your methodology is real. A program built from a sensible WBS, with productivity-based durations, defensible logic, an identifiable critical path, and honest weather and contingency provisions does most of the work of selling your bid. A program built from round numbers and arbitrary bars undermines a tender response no matter how good the prose reads.
The investment to develop a tender-grade program is modest — for most civil SMEs, a competent program for a $1M–$5M tender takes one to three days of estimator and program lead time. Against the win-rate uplift that a well-built program delivers across a tender pipeline, the ROI is one of the cleanest in tendering practice.
Footnotes & Sources
- TenderBuilt practice guidance based on review of civil construction tender evaluation reports across NSW, VIC, and QLD councils and state agencies; consistent with published tender evaluation methodologies under the NSW Procurement Policy Framework, Queensland Procurement Policy 2026, and Victorian Government Purchasing Board frameworks. ↩
- Scheduling tool selection guidance based on industry adoption patterns across Australian civil construction. Microsoft Project, Primavera P6, and Asta Powerproject remain the dominant tools; Excel-based Gantt charts persist for smaller council tenders without mandated software requirements. ↩
- Indicative productivity rates synthesised from published Australian civil construction productivity benchmarks including the CCAA Concrete Pavement Manual and Austroads guidance. Actual project productivity should always be benchmarked against contractor-specific historical data. Austroads — austroads.com.au. ↩
- Bureau of Meteorology, Climate Data Online — bom.gov.au/climate/data. Long-term rainfall statistics by station, including rainy day counts by month, are freely accessible and provide defensible benchmarks for weather contingency provisions in tender programs. ↩
Need help building a tender-grade construction program?
TenderBuilt specialises in tender writing and bid management for civil construction SMEs across NSW, Queensland, and Victoria — including construction programs that turn your methodology into evaluation points.Get a Free Quote