Building a Basis of Estimate for a Cost Volume That Survives DCAA Scrutiny

The Problem Starts Before You Price Anything

A source selection board opens your cost volume and goes straight to the basis of estimate. Not the summary spreadsheet. Not the labor categories. The BOE. If the narrative does not explain how you sized the work, why you chose those hours, and what historical or engineering data supports the number, the cost evaluator flags it as unsupported. On a cost-plus or cost-realism solicitation, that flag can collapse your evaluated price upward, or knock you out entirely.

Building a defensible BOE is not a formatting exercise. It is a discipline that starts at kickoff and runs through final review. The sections below walk through each layer.

Understand What the Government Is Actually Asking For

Section L of the solicitation tells you what to submit. Section M tells you how it gets scored. Read both before you write a single line of BOE narrative. Common requirements include a description of the estimating methodology, a mapping of labor categories to the Statement of Work (SOW), a list of assumptions and exclusions, and a traceability table linking hours to deliverables or Contract Data Requirements List (CDRL) items.

Some solicitations, especially those evaluated under FAR 15.404-1(d) cost realism, require you to demonstrate that your proposed costs are realistic for the work, reflect a clear understanding of the requirements, and are consistent with your technical approach. That last phrase matters. If your technical volume says you will use a senior systems engineer to lead integration testing, your BOE must show senior-level hours in that task. A mismatch between the technical and cost volumes is one of the most common findings in post-award debriefs.

Choose and Document Your Estimating Methodology

The BOE must state the method used to develop each estimate. The four primary methods recognized in government cost estimating are:

• Analogous estimating: You reference a prior contract with similar scope, adjust for differences, and document the adjustment rationale. This works when you have relevant historical data and can show the comparison is valid.
• Parametric estimating: You use a cost model or statistical relationship, such as lines of code per labor hour or square footage per inspection hour, to derive the estimate. Document the model, its inputs, and its source.
• Engineering (bottom-up) estimating: You decompose the SOW into discrete tasks, estimate each task independently, and roll up. This is the most defensible method for complex technical work and the one DCAA auditors most often expect on cost-type contracts.
• Expert judgment: A subject matter expert provides the estimate based on experience. This is the weakest method standing alone. Pair it with at least one of the above, or document the expert's qualifications and the basis for their judgment in detail.

Most cost volumes use a combination. A software development task might use parametric sizing for new code and analogous data for integration. Document each method by task, not just once at the top of the volume.

Map Hours to the Work Breakdown Structure

A Work Breakdown Structure (WBS) is not optional on most cost-type efforts. MIL-STD-881 (when invoked) and applicable DFARS provisions define WBS requirements for major programs, but even on smaller efforts, a clear WBS gives the evaluator a logical framework to follow your pricing.

Each WBS element should tie to a specific SOW paragraph or CDRL. Your BOE table might look like this in practice: WBS 1.2.3 (Software Integration and Test) maps to SOW paragraph 5.4 and CDRL A003 (Test Report). The hours in that cell are supported by the parametric model described in Attachment B. That chain of traceability is what separates a defensible BOE from a spreadsheet with numbers in it.

If the solicitation does not specify a WBS, build one that mirrors the SOW structure. Evaluators follow the SOW when they read your cost volume. Make it easy for them to find the corresponding estimate.

Write the Narrative So It Stands Alone

Assume the person reading your BOE narrative has not read your technical volume. The narrative must explain the scope being estimated, the method used, the key assumptions, and the result. Each task section should answer four questions:

1. What work is being performed?
2. Who is performing it (labor category and skill level)?
3. How many hours are required, and how was that determined?
4. What assumptions or constraints bound this estimate?

Assumptions are not weaknesses. They are disclosures. Stating that your estimate assumes government-furnished equipment (GFE) will be available at contract start, or that travel is limited to the locations listed in the SOW, protects you if conditions change. An assumption section also signals to the evaluator that you read the solicitation carefully enough to identify what is and is not included in scope.

Exclusions matter equally. If the SOW is ambiguous about whether a particular deliverable is in scope, state your interpretation and exclude the alternative. This prevents the government from assuming you priced something you did not.

Support the Rates Separately From the Hours

The BOE covers hours and quantities. The rate build is a separate but connected document. Your direct labor rates need to be supported by your accounting system, your Forward Pricing Rate Agreement (FPRA) if you have one, or a rate proposal submitted alongside the cost volume. Indirect rates, fringe, overhead, G&A, and fee or profit are applied on top of direct costs and must be consistent with your disclosed accounting practices.

If you are a small business without an FPRA, you will need to provide a rate build that shows how each rate was calculated. DCAA may audit this. Consistency between your BOE hours, your rate build, and your cost summary spreadsheet is non-negotiable. A single arithmetic error that creates a discrepancy between the narrative and the spreadsheet can trigger a clarification request or, on a competitive acquisition, a finding that your cost volume is unbalanced.

Common BOE Failures and How to Avoid Them

Proposal managers reviewing cost volumes repeatedly see the same problems. Avoid these:

• Hours with no rationale: Stating "480 hours for program management" with no explanation of how that number was derived is not a BOE. Show the calculation: one PM at 20 hours per week for 24 weeks equals 480 hours.
• Labor category mismatches: Using a junior analyst labor category for tasks the SOW clearly requires senior expertise, or vice versa, invites a cost realism adjustment.
• Stale historical data: Analogous data from a contract completed several years ago needs an escalation adjustment and a note explaining why the comparison is still valid.
• Missing subcontractor BOEs: If you have subcontractors, their BOEs must be included or summarized in your cost volume. FAR 15.404-3 requires you to obtain cost or pricing data from subcontractors above the threshold unless an exception applies.
• Inconsistency with the technical volume: This is the most damaging failure. Run a cross-check between your technical approach and your cost volume before submission. Every resource mentioned in the technical volume should appear in the cost volume, and every major cost element should be traceable to a technical requirement.

A Short Takeaway

A BOE is evidence, not decoration. Build it the way you would build a legal argument: state the claim (the hour or cost estimate), present the supporting data (the methodology and historical reference), and document the logic that connects them. Evaluators and auditors are looking for that chain. If it is not there, they will assume the estimate is unsupported, and they will be right.

If your team is preparing a cost volume and wants a structured review of your BOE approach before submission, reach out for a brief consult. Catching a traceability gap or a rate inconsistency before the government does is worth the time.

Winrove is a product of IT Custom Solution LLC.