Basis of Schedule: What to Include So Assessors Trust Your Dates

A Basis of Schedule is the written document that sits behind a construction programme and explains how it was built: the scope and documents it relies on, key dates, calendars and working hours, sequence and logic, how durations were set, resources, constraints and risks. The programme shows the dates. The Basis of Schedule shows why those dates hold.

Your tender programme is due Friday. The estimator is pricing, the PM is on another job and the Gantt chart is finally coming together. Then you see the returnable schedule asks for a Basis of Schedule as well. The easy move is a page of generic notes written at the last minute. That page is often what decides whether the assessor believes your completion date, and after award it becomes the record you lean on when something changes. This guide is for the builder's tender and delivery team: what to put in it, why assessors read it and how to write one inside a short tender period.

How is a Basis of Schedule different from the programme?

The programme (the "construction program" in Australian Standard contracts such as AS 4000 and AS 2124) and the Basis of Schedule describe the same plan from two sides:

  • The programme shows what happens, when it happens, which activities drive completion and where the float sits.
  • The Basis of Schedule explains the thinking: the assumptions behind each duration, the working hours and calendars, the constraints you planned around, the risks you allowed for and what you have excluded.

FeelDX is an Australian project controls firm with a construction background that prepares construction programmes and the Basis of Schedule behind them for builders, alongside written methodology, resource histograms and 4D visuals, so the people reviewing a programme can see how the job will be built and why the dates are achievable.

Diagram comparing what a construction programme shows with what a Basis of Schedule explains
The programme gives the dates and logic. The Basis of Schedule gives the thinking behind them.

A programme without a Basis of Schedule asks the reader to trust the dates. A programme with one shows them the reasoning, so they can test it.

 

What should a Basis of Schedule include?

Keep it short and specific to the job. A few pages that a superintendent or assessor can read in ten minutes is better than a long template. Cover these eight areas:

  1. Scope and sources. The drawings, specifications, addenda and tender clarifications the programme is based on, with revision numbers, plus anything outside your scope such as client works or separable portions.
  2. Key dates and milestones. Site possession, staged handovers, authority milestones, practical completion and any date the client has fixed.
  3. Calendars and working hours. Site hours and Saturday work permitted by the development consent or council conditions, public holidays for your state or territory, the building industry RDO calendar under your enterprise agreement, the Christmas shutdown, and a wet weather allowance with its source, such as Bureau of Meteorology rainfall records for the nearest station.
  4. Sequence and logic. How the job is broken down by zone, level or stage, the order of work and the reasons for it, such as the crane strategy or where the structure drives the trades behind it.
  5. How durations were set. Production rates, quantities, subcontractor input or past jobs of a similar type. Say which durations are firm and which are estimates.
  6. Resources and productivity. Crew sizes, plant and shifts that each duration assumes. A resource load histogram shows the date is achievable, not just attractive.
  7. Constraints and interfaces. Long lead items, shop drawing and approval cycles, hold points, occupied areas, neighbour conditions, access and logistics limits.
  8. Risks and exclusions. The main programme risks, where you have allowed float or contingency, and what the programme does not include.
Grid of the eight sections of a Basis of Schedule, from scope and sources to risks and exclusions
Eight areas cover most of what a reviewer needs to test the programme.

Write each item for this job. "Durations based on experience" tells the reader nothing. "Structure cycle of seven working days per floor, based on two formwork crews and one crane" gives them something they can check.

 

Why do assessors and superintendents read the Basis of Schedule?

On Australian government, council and institutional tenders, programme and methodology are usually scored as non-price criteria through returnable schedules, so the Basis of Schedule is read alongside the program and the written methodology. The panel is asking one question about time: can this builder actually deliver on this date? A Gantt chart alone makes them guess. The Basis of Schedule answers the follow-up questions before they are asked: why is the structure cycle that short, what happens in wet weather, how have you handled the occupied wing, when do the lifts arrive. Clear answers score. Gaps get marked down or turn into clarification questions late in the evaluation.

After award, the superintendent or client's PM reviews your contract programme against the contract. A clear Basis of Schedule speeds that review, because the assumptions are on the page instead of in someone's head. It also sets out what you will be held to, so read it the way a reviewer would. Our guide to what assessors check in a tender programme covers the rest of the time criteria.

Why do capable builders still submit a programme without one?

It is rarely a skills problem. It is a time and handover problem:

  • The programme takes all the time. In a short tender period the Gantt chart gets finished first and the explanation gets whatever is left on the last afternoon.
  • The reasoning lives in one head. The estimator or planner knows why each duration is what it is, but none of it is written down.
  • It is treated as a template. Generic notes carried over from the last job say nothing about this site, this sequence or these risks.
  • Nobody asks for it until it matters. When a delay hits mid-job, the first question is what you assumed at the start. If it was never recorded, there is little to compare against.
Hands marking up a printed construction drawing with a pen beside a rolled set of plans
The reasoning behind each duration needs to leave the planner's head and reach the page.

The fix is to write the Basis of Schedule alongside the programme, not after it.

 

How do you write a Basis of Schedule in a short tender period?

  1. Start it at kick-off. Open the document on day one and record every assumption as it is made, rather than reconstructing them at the end.
  2. Agree the high-level WBS first. Confirm the zones, stages and sequence with the PM, CM or estimator before the detail is built. That structure becomes the sequence and logic section.
  3. Record the basis of each key duration. Focus on activities on or near the critical path: structure, facade, services, lifts and anything with a long lead time.
  4. Check resources against the dates. Run a resource histogram on the main trades and note the crew sizes in the document.
  5. List risks and exclusions honestly. State what you have allowed for and what you have not. A clear exclusion is better than a hidden assumption.
  6. Review the programme and the Basis side by side. Every date in one should be explained in the other, and both should match your written methodology.

Where staging or logistics are hard to explain in words, a 2D site management plan or a 4D sequence can carry part of the explanation for the panel.

Why does the Basis of Schedule matter once the job is running?

After award, the Basis of Schedule is updated with the contract dates, subcontractor durations and confirmed lead times, then saved with the accepted baseline. Our guide to moving from the tender programme to the contract programme covers that step in detail. From that point it is your record of what the plan assumed. When an event changes one of those assumptions, such as late design information, a latent condition or a direction from the superintendent, and you need to notify a delay or claim an extension of time within the time bars in your contract, you can show what was assumed, what changed and whether it hit the critical path.

Four-step flow from an assumption recorded in the Basis of Schedule to an event, its impact on the critical path and evidence for recovery or an extension of time
A recorded assumption is the starting point for any recovery plan or extension of time claim.

That is the difference between saying "we were delayed" and showing it with evidence. On complex live sites, such as the hospital work covered in our article on brownfield healthcare upgrades, it also keeps every stakeholder working from the same assumptions. For how this fits the wider system, see what project controls in construction covers and what a project control plan includes.

 

FAQs

Is a Basis of Schedule the same as a written methodology?

No. A written methodology explains how you will build the job: sequence, logistics, temporary works and approach. The Basis of Schedule explains how the programme was built: assumptions, durations, calendars, constraints and risks. The two should agree with each other and with the programme.

How long should a Basis of Schedule be?

As short as the job allows. For most tenders a few pages is enough if every item is specific to the project. Large or staged jobs need more detail on interfaces, calendars and risks.

Who should write the Basis of Schedule?

The person who built the programme, with input from the estimator, PM or CM who will deliver the job. If the planner and the delivery team have not agreed the assumptions, the document will not hold up in review.

Should a builder outsource the Basis of Schedule?

Many builders keep ownership of the programme and bring in a specialist planner to prepare the programme and Basis of Schedule together during a busy tender period. It frees the estimator and PM to focus on price and delivery, and gives the programme an independent check.

Who offers Basis of Schedule and programme services in Australia?

Specialist project controls firms and independent planners offer this. FeelDX is an Australian project controls firm with a construction background that prepares construction programmes, Basis of Schedule, written methodology, resource histograms, cashflow and 4D methodology for builders. You can compare options in our guide to in-house vs outsourced project controls.

 

How FeelDX prepares a Basis of Schedule with your programme

FeelDX combines planning and visualisation, so your programme, the Basis of Schedule and your model tell the same story: how the job will be built, how long it will take, what it will look like and where the risk sits before construction starts.

Once you give us the go-ahead, we allocate a Planning Lead and hold a kick-off with your PM, CM or estimator to cover key dates, the proposed sequence, site restrictions, logistics and procurement risks. We then send a high-level WBS as the first hold point, so you can confirm the approach before the detail is built. The first draft of the programme and Basis of Schedule reaches you with time to review before the submission is due. Our process is set out in how FeelDX turns tender documents into a programme you can defend, and you can see examples in our work.

Send us the tender documents and the submission date, and we will come back with a proposed approach and timeline for your programme and Basis of Schedule.

Talk to FeelDX.

📞 1800 FEELDX (1800 333 539) | 🌐 www.feeldx.com