Estimate Basis Memorandum: What It Is and Why It Matters on Capital Projects
Every cost estimate for a capital project tells you what the project is expected to cost. Only the estimate basis memorandum tells you why. It documents the assumptions, data sources, pricing basis, methodology, and risks that underpin the estimate — the entire reasoning chain that produced those numbers. Without it, an estimate is a set of figures without provenance: defensible only by the person who built it, opaque to everyone who inherits it, and nearly useless as a starting point when scope or conditions change.
Cost engineers who treat the EBM as afterthought paperwork are optimising for the wrong thing. The estimate is used once, to secure approval. The basis document is used repeatedly — in contractor audits, reforecast cycles, benchmarking exercises, claim defences, and the next round of project estimates that draws on this one as historical data. This article covers what the EBM captures, how to structure its core sections, how it is used beyond estimate approval, and the common gaps that undermine its value in practice.
What the EBM Captures — and What It Is Not
An estimate basis memorandum is a written record of the estimating process. It documents what was included in the estimate, what was explicitly excluded, what assumptions were made in the absence of definitive information, what data sources and pricing references were used, and what risks and uncertainties remain unresolved at the time the estimate was produced. It is typically prepared in parallel with the estimate itself, while the decisions made during preparation are still accessible to the people who made them.
The EBM is not an estimate review. It does not evaluate whether the numbers are right; it records how they were arrived at. It is also not a risk register, though it references one. The risk register quantifies and tracks identified risks; the EBM describes what risk allowances appear in the estimate and whether they are carried through contingency or through individual line-item provisions. The distinction matters because the two documents serve different audiences at different points in the project lifecycle. Reviewers consult the risk register to understand exposure; they consult the EBM to understand what the estimator already assumed about that exposure.
What makes the distinction operational: when the project’s forecast diverges from the estimate six months into execution, the first question from the project director is whether the conditions assumed in the estimate still hold. An EBM provides a structured answer. A project without one can only answer from memory, and institutional memory has a short half-life in capital project environments where team composition shifts throughout execution.
The Six Core Sections
A well-structured EBM contains six sections, each serving a distinct purpose for a distinct downstream audience.
- Scope description. A narrative statement of what is in the estimate and what is explicitly excluded. This is the section most likely to be read by people unfamiliar with the estimating process — executives, auditors, subsequent project teams. It should be written in plain language and be specific: not “civil works included” but “all earthworks inside the project fence line included; site access road from the highway to the gate excluded.”
- Estimating methodology. Which estimating method was applied to which portions of scope: parametric models for early-stage process units, vendor quotes for long-lead equipment, bottom-up priced bills of quantities for civil and structural packages. Where methods were blended, the EBM should explain the rationale — typically a function of available design definition and data confidence at the estimate class level being produced.
- Pricing basis. The reference date for all prices, the labour market assumed, the productivity factors applied, and the source of each. This section must be specific enough that a reviewer can reproduce the labour cost for a given discipline given the quantities in the estimate. Currency and exchange rate assumptions belong here, as does the cutoff date for vendor quotes.
- Key assumptions and exclusions. Every assumption that, if wrong, would change the estimate by more than one percent of total project cost should be documented individually: ground conditions assumed, regulatory requirements assumed not to change, contractor procurement strategy assumed, owner-furnished equipment assumed to be within a separately held budget.
- Risk treatment. How contingency was determined — probabilistic analysis, percentage allowance, or informed judgment — and what risks it covers. Whether specific known risks are carried as individual line-item provisions within the base estimate, or whether they sit entirely within the contingency envelope. This section cross-references the risk register.
- Escalation basis. The index or rate assumed for price escalation on long-duration projects, the base date from which escalation is calculated, and how it was applied across trade packages — uniform rate, trade-specific rates, or time-phased against the project schedule.
How the EBM Is Used Beyond Estimate Approval
The immediate use of an estimate basis memorandum is to support estimate review at the project gate. Reviewers can assess whether the assumptions are reasonable, whether scope is correctly bounded, and whether the contingency allowance matches the risks documented. Without the EBM, independent estimate review becomes a reconstruction exercise — auditors trying to reverse-engineer what the estimator assumed rather than evaluating whether those assumptions are defensible.
The more consequential uses emerge later. When execution variances need explaining, the EBM is the baseline of assumed conditions against which actual conditions are compared. A labour productivity assumption that held at estimate time but failed in execution is identifiable and quantifiable because it was written down. A ground condition assumption that proved incorrect generates a defensible change claim precisely because the EBM documents what was assumed at sanction. In contractor disputes and insurance claims, the basis document is frequently the most important evidence establishing what the project thought it was procuring.
The EBM also carries institutional knowledge from one estimate cycle to the next. A parametric model calibrated against this project’s actual unit rates is only transferable if the conditions of the estimate — market, location, technology, contracting approach, site constraints — are recorded well enough that future estimators can judge when the model applies and when its assumptions diverge from their own project context.
Common Gaps That Undermine Estimate Basis Documents
Four failure patterns appear consistently in EBMs that fall short of their purpose.
The first is assumption vagueness. “Market conditions assumed normal” is a placeholder, not a documented assumption. A well-documented labour market assumption names the specific region, the industrial relations conditions assumed, the union agreement in effect, and the productivity norm applied. The test is whether a reviewer who has never visited the project site can form a concrete picture of the assumed conditions from the document alone. If not, the assumption is not documented — it is merely noted.
The second is incomplete exclusions. Estimators tend to document inclusions and omit a systematic review of exclusions. On a capital project, excluded scope — owner-furnished interfaces, offsite infrastructure, regulatory fees, commissioning consumables, owner’s project management costs — is as important as included scope, because exclusions define the boundary of the project’s cost responsibility. Gaps in exclusion lists are among the most common sources of scope boundary disputes during execution.
The third is missing contingency rationale. A contingency of 15% of the base estimate is not a documented basis; it is a result. The EBM must record how the contingency was derived and what risks it is intended to cover. This matters when contingency is drawn down during execution: a team that cannot connect a specific draw to a specific risk cannot tell whether the draw is appropriate or whether it is masking a cost overrun.
The fourth is retrospective preparation. An EBM produced months after the estimate, with pricing details recalled from memory, is not a basis document — it is a reconstruction. The pricing basis section must be contemporaneous: written when the vendor quotes are fresh, the rate sheets are open, and the productivity assumptions are still grounded in current site intelligence rather than compressed recollection.
Key Takeaways
- The estimate basis memorandum records the reasoning behind an estimate — scope boundaries, methodology, pricing basis, assumptions, risk treatment, and escalation — not the numbers themselves.
- Its value compounds over time: it is consulted in estimate reviews, reforecast cycles, contractor audits, claim defences, and future estimate calibration — not just at gate approval.
- Document assumptions specifically enough that a reviewer who has never visited the project site can evaluate whether they were reasonable and whether they still hold.
- Exclusions deserve as much attention as inclusions; incomplete exclusion lists are a primary source of scope boundary disputes during execution.
- Write the EBM contemporaneously with the estimate; a basis document reconstructed from memory months later cannot be relied upon in disputes or audits.