BOE

A Basis of Estimate (BOE) is the written justification for every cost element in a proposal. It names the source of each labor hour, material dollar and travel cost. A government analyst can then trace the number to a defensible method rather than a guess. The estimate is the number. The BOE is the reason the number is credible.

What does a BOE actually contain?

A contractor normally writes one BOE per WBS element. Each BOE states:

• The scope — the work this element covers, tied to the Statement of Work (SOW) paragraph and the requirement that generates it.
• The estimating method — the method that produced the number, and the reason that method fits this work.
• The inputs — hours by labor category, material quantities, travel trips and durations, subcontract amounts.
• The rationale — the historical program, engineering analysis, vendor quote, parametric model or standard that supports the inputs.
• The assumptions — government-furnished equipment, facility access, response times, staffing availability. State them. They also become your change-order basis later.
• The risk and complexity treatment — where this work is genuinely harder than the historical analogue. State the reason the hours reflect that.

Standard estimating methods

• Analogy — this element resembles a prior effort, with an adjustment for known differences. It is fast. It is only as good as the relevance of the analogue.
• Parametric — a driver such as lines of code, drawings, test cases or square footage produces the hours. A rate established from history converts the driver into hours.
• Engineering build-up (bottom-up) — decompose the work to tasks, estimate each task, and sum the result. This method is the most defensible and the most expensive to produce.
• Vendor quote or catalog price — for materials and subcontracted scope.
• Level of effort — a staffing profile held over a period. It suits sustainment and support work. It is a red flag on discrete deliverables.

Where a BOE appears in a bid

The BOE appears in the cost volume, usually as a required attachment or an appendix per WBS element. On larger negotiated procurements the government cost analyst reads it first. The BOE supports the cost realism analysis under FAR 15.404-1. That analysis determines whether your proposed costs are realistic for the work your own technical volume describes.

The mistake that makes this term matter

A cost volume is usually the last thing a proposal team writes, and the BOE is usually the last thing in the cost volume. By the time anyone reaches it, the price has already been settled in a management review, and the job in front of the writer is not to justify the hours. It is to arrive at a number everyone has already agreed to. So the BOE gets written backward from the total.

It reads fine internally. It survives the internal review, because the reviewers were in the meeting where the number was set. What it does not survive is a cost analyst reading it beside the technical volume, because the technical volume describes the work the engineers actually intend to do, and the two documents were built from different starting points. That gap is the thing cost realism analysis exists to find, and discovering it in an evaluation notice is the expensive way to learn it.

What goes wrong with a BOE in practice

It restates the estimate and never justifies it. "The interface needs 480 hours" is not a basis. A basis reads differently: 480 hours, from the 2023 effort on a comparable interface at 420 hours. The extra 60 hours cover the added protocol that the earlier baseline did not contain.

It contradicts the technical volume. The technical approach describes an automated pipeline. The BOE prices manual effort. Cost realism analysis exists specifically to find this. The finding has two possible consequences: the government may raise your evaluated cost, or it may read the gap as a misunderstanding of the requirement.

Nobody states the assumptions. Every assumption you omit is a cost you silently absorb. Every assumption you record is a documented basis for an equitable adjustment if it proves false.

Round numbers everywhere. A BOE where every element lands on 100, 200 or 500 hours signals that someone decomposed a target price backward. Estimates from real methods rarely land on round numbers.

Nobody prices the data deliverables. CDRL items, program reviews, and the effort to answer government comments on delivered documents are real hours. Recurring deliverables across a multi-year period of performance accumulate quickly.

What to do

1. Write the BOE from the WBS, one element at a time.
2. Draft each BOE before the team agrees the price internally.
3. Name a real source for every input.
4. State every assumption, including the assumptions that feel obvious.
5. Read the technical volume and the BOE side by side.
6. Confirm that both documents describe the same program.
7. Price the data deliverables and the program reviews as real work.

What a BOE is not

A BOE is not a ROM (Rough Order of Magnitude). A ROM is a fast order-of-magnitude figure with a wide, stated uncertainty band. Contractors use a ROM for planning and market research. A BOE is the auditable justification behind a proposed price.

A BOE is also not the cost model. The spreadsheet computes. The BOE explains.

Silas™ generates per-WBS basis-of-estimate structure from the shredded SOW, with the requirement trace and cost breakdown attached to each element.