A schedule basis memo, also called a basis of schedule document, records the assumptions, calendars, logic and methods used to build a baseline programme. It explains why durations were chosen, which calendars apply, what sequence drives the critical path and which constraints were applied, so that anyone reading the P6 file later can understand the intent behind it.
In a dispute, the basis of schedule is often one of the first documents an opposing expert asks for. A clear, contemporaneous memo supports the baseline as realistic; a missing or vague one leaves it open to the argument that the plan was arbitrary. This guide covers what to include, the omissions that undermine credibility, how a basis memo differs from a schedule narrative, and a checklist you can reuse as a basis of schedule template.
What is a schedule basis memo?
A schedule basis memo is the companion document to the baseline schedule. It sits alongside the P6 file and explains the thinking the file cannot show: where durations came from, what the calendars mean, why the work is sequenced the way it is, what is excluded and what risks shaped the plan. AACE International publishes a recommended practice on documenting the schedule basis, and many contract specifications ask for a basis of schedule with the baseline submission.
It is best written as the programme is built, issued with the baseline and revised whenever the baseline is formally revised. How the basis memo relates to the saved baseline itself is covered in Primavera P6 baselines explained.
What should a basis of schedule include?
1. Scope, WBS and activity coding
State the scope the programme covers and what it excludes. Describe the work breakdown structure and the activity coding scheme, for example codes for area, discipline, phase or contractor, and how they are used to filter and report the programme.
2. Calendars and working time
List every calendar used, such as a five-day, six-day or seven-day calendar. For each, state the working days and hours, shifts, public holidays, shutdowns and any weather allowance, and which activities it applies to. Example: "Concrete calendar: six-day week, Sunday non-working, public holidays as listed in Appendix A."
3. Durations and logic
Explain how durations were estimated: productivity rates and quantities, historical data, subcontractor or supplier input, or planning judgement. State the default relationship type (normally Finish-to-Start), and justify every lead, lag and non-FS relationship, for example a lag representing concrete curing time.
4. Constraints and external dependencies
List every constraint with its reason, such as a contractual milestone or a permit date. Identify third-party dependencies, such as utility connections, authority approvals or client-supplied information, and say how each is modelled, whether as a separate activity, a milestone or a constraint.
5. Sequencing and critical path
Describe the overall sequencing strategy, for example "floor by floor, with MEP first fix following structure by two floors". State how the critical path is defined, either as the longest path or as activities with total float at or below a stated threshold, and describe the critical and near-critical paths at baseline.
6. Risk and contingency
Record any schedule contingency, where it sits and who controls it. Contingency is easier to defend when shown as visible, named activities than when hidden inside activity durations. Note the risks that influenced logic or durations, and if a schedule risk analysis was run, record the confidence level of the baseline completion date.
7. Quality checks and approval
Record the result of the schedule quality check run on the baseline, such as the DCMA 14-point assessment, and explain any metric outside its threshold, for example lags above 5% because of curing and drying times. Close with the data date, the baseline name in P6, the revision history and the approvals.
What omissions undermine a basis memo?
- Undefined calendars: "five-day calendar" without stating which days, hours and holidays apply is ambiguous.
- Unjustified constraints: a Finish On or Before or a mandatory constraint with no stated reason is an immediate red flag.
- Vague logic descriptions: "activities are linked in sequence" says nothing. Be specific: "footing pour starts two days after excavation finishes, to allow inspection".
- Ignored external dependencies: if a utility connection depends on a third party, say so and say how it is modelled.
- Unexplained quality check results: a high count of leads, lags or hard constraints with no explanation invites the conclusion that the programme is unreliable.
- No version control: a memo that does not identify the baseline it describes cannot be relied on.
What is the difference between a schedule basis memo and a schedule narrative?
The terms are often used loosely, but they do different jobs. The basis memo explains how the baseline was built and is revised only when the baseline is revised. A schedule narrative usually accompanies each update and explains what has changed in the period: progress achieved, movement in the forecast completion date, changes to the critical path, delays, logic changes and recovery actions. Some specifications call the baseline document a "baseline narrative", so check what the contract asks for. Together, the basis memo and the update narratives form a contemporaneous record that is valuable in any later delay analysis.
How do you check the programme before writing the memo?
Run the baseline through a schedule quality check before drafting the memo: missing logic and open ends, leads and lags, relationship types, hard constraints, high float, high durations and the critical path test. Fix what should be fixed, and document why anything that remains outside the thresholds is intentional. The memo should explain the programme as issued, not the programme as it was before review.
Basis of schedule template: checklist
Use this checklist to confirm the memo is complete, or as the outline of a basis of schedule template.
| # | Item | What to record |
|---|---|---|
| 1 | Project identification | Project name and number, baseline name in P6, data date and revision |
| 2 | Scope and exclusions | What the programme covers and what it does not |
| 3 | Calendars | Every calendar with working days, hours, shifts, holidays and weather allowance |
| 4 | WBS and coding | WBS structure and activity coding scheme |
| 5 | Duration estimating | Method and source: productivity rates, historical data, supplier or subcontractor input |
| 6 | Relationships | Default relationship type, and justification for every lead, lag and non-FS link |
| 7 | Constraints | Every constraint with its reason, including contractual milestones |
| 8 | Sequencing narrative | Overall strategy, for example structure ahead of MEP by two floors |
| 9 | Critical path definition | Longest path or total float threshold, and the critical and near-critical paths at baseline |
| 10 | Contingency | Amount, location in the programme and who controls it |
| 11 | External dependencies | Third-party, authority and client-supplied milestones and how they are modelled |
| 12 | Risks | Risk events that shaped logic or durations, and any risk analysis result |
| 13 | Quality check results | Schedule quality metrics, for example DCMA 14-point, with explanations |
| 14 | Revision history and approval | Version, date, changes made, and approval signatures |
How do you make the memo defensible?
- Write it while you build the schedule. Assumptions reconstructed later are weaker than assumptions recorded at the time.
- Keep it in step with the baseline. When an approved change alters a key assumption and the baseline is revised, revise the memo and record the version.
- Be honest about judgement. If a duration is a planning estimate rather than a calculation, say so.
- Use plain language. The memo will be read by project managers, commercial teams and lawyers as well as planners.
A schedule basis memo is not paperwork for its own sake. It is the explanation that makes the baseline usable and defensible. Preparing the baseline and its basis of schedule together is part of Project Assure's project planning work.
