Government Contracting BOE: How to Write One That Wins (July 2026)

Your BOE can have the right numbers and still lose you points if evaluators can't trace the logic. Contracting officers and cost analysts read your BOE alongside your technical volume, and when those two documents tell different stories about staffing levels or task durations, that gap becomes a scoring risk. Building a BOE that actually wins means making sure every cost element connects back to something verifiable.

TL;DR:

• A BOE documents how you priced every cost element and gives agencies a way to verify your estimate connects to actual PWS requirements.
• Cost-reimbursable and T&M contracts almost always require a BOE; sole-source awards above $2.5 million require certified cost or pricing data where a BOE is the primary vehicle.
• Your BOE must match your technical volume exactly: mismatched staffing levels, task durations, or missing cost lines are scored as proposal weaknesses.
• DCAA auditors trace every labor hour back to the SOW; unsupported round numbers, prior-year indirect rates, and pass-through subcontractor lines trigger formal findings.
• GovDash connects solicitation requirements to your cost structure by having Dash read the PWS, extract each requirement, and map it against your defined LCATs and Data Library rates.

What a Basis of Estimate Is in Government Contracting

A basis of estimate is a documented explanation of how a contractor arrived at its proposed costs. It breaks down the labor hours, materials, subcontractor costs, and other direct expenses tied to a specific scope of work, and explains the reasoning behind each figure.

In government contracting, a BOE goes beyond a simple price breakdown. Agencies use it to assess whether a contractor truly understands the work, whether the proposed resources are realistic, and whether the numbers can be traced back to a defensible methodology.

Why Agencies Care So Much About the BOE

Contracting officers and cost analysts are doing more than checking math. They are asking whether the contractor's approach to scoping the work reflects the actual requirements in the PWS or SOW. A BOE that cannot answer that question clearly raises flags during source selection or cost/price analysis.

The document serves a few interconnected purposes:

• It ties proposed costs directly to technical requirements, so reviewers can see that each labor category and hour estimate connects to a specific deliverable or task.
• It creates a paper trail that supports audit by DCAA or other oversight bodies, particularly on cost-reimbursable contracts where actual costs will be compared against the proposal.
• It protects the contractor during contract execution by documenting what was priced, preventing scope creep from being absorbed without a contract modification.

A BOE is not optional on most competitive federal procurements. RFPs for cost-type contracts, IDIQ task orders, and many firm-fixed-price awards above simplified acquisition thresholds will include explicit instructions for submitting cost or pricing data along with supporting rationale.

When a BOE Is Required

Not every proposal requires a standalone BOE document, but contracting officers increasingly expect one whenever cost justification is non-trivial. Here is where a BOE is typically required or strongly expected:

• Cost-reimbursement contracts (CPFF, CPAF, CPIF) almost always require a BOE because the government bears cost risk and needs to see how each labor category, material, and indirect cost rate was calculated before agreeing to fund the work.
• Time-and-materials contracts require a BOE tied to each LCAT, since the hourly rates and estimated hours drive the total contract value and must be defensible against wage determinations and market data.
• Large competitive acquisitions above the simplified acquisition threshold ($250,000 under FAR 2.101) routinely require a BOE as part of the pricing volume, especially when Section L includes explicit cost narrative instructions.
• Sole-source negotiations under FAR 15.403-4 require certified cost or pricing data when the contract exceeds the Truth in Negotiations Act threshold (currently $2.5 million for contracts awarded on or after July 1, 2018, per the October 2025 threshold adjustment), and a BOE is the primary mechanism for presenting that data.

Even on fixed-price bids where a BOE is not formally required, a well-constructed one protects the contractor internally by documenting the assumptions behind the price and giving the team a reference point if the scope changes after award.

Core Components of Every BOE

Every BOE submitted to a government agency follows a predictable structure. Evaluators expect to see the same core elements, and missing any one of them raises questions about your team's ability to manage the work.

The sections below cover what belongs in a complete BOE and what each one needs to contain.

Scope Summary

This section ties your estimate to a specific, bounded body of work. It should reference the relevant PWS or SOW paragraphs, name the deliverables, and call out any assumptions about what is and is not included. Undefined scope boundaries are one of the most common sources of later disputes, so being precise here protects both parties.

Labor Estimation

Labor is typically the largest cost driver, so this section receives the most scrutiny. For each labor category, you need to document the hours, the rationale behind those hours, and the basis for your loaded rates. If you are drawing rates from a GSA schedule, a CBA, or your approved forward pricing rate agreement, name the source explicitly. Applying a rate from an earlier fiscal year when a newer rate agreement is in place is the kind of error that can unravel an otherwise solid estimate.

Materials and Other Direct Costs

List each material or ODC line item separately. Generic placeholders like "miscellaneous supplies" are a red flag to evaluators. Each item should have a quantity, a unit cost, and a citation to the vendor quote or catalog that supports the figure.

Indirect Costs and Fee

Fringe, overhead, and G&A, and fee should be applied in the correct sequence and at the rates your accounting system actually uses. Pulling rates from a prior year's incurred cost submission instead of your current forward pricing agreement is a common error that DCAA auditors will flag.

Assumptions and Exclusions

Document every assumption that underlies the estimate. If the government's technical approach changes and your assumptions no longer hold, this section is what supports a contract modification. Unstated assumptions become scope disputes.

BOE Estimation Methodologies

Government contractors rely on several accepted methodologies when building a BOE, and the choice of approach shapes how well your estimate holds up under scrutiny.

Common BOE Estimation Approaches

There are four methods that appear most frequently in federal cost proposals:

Choosing the Right Method

Most winning proposals combine methods. A program manager might use parametric rates for Phase 1 staffing and bottom-up estimating for Phase 2 hardware integration, with expert judgment filling gaps where data is thin. The key is making the rationale visible to the reviewer so the estimate reads as calculated, not guessed.

How to Build a BOE: A Step-by-Step Process

A solid BOE moves through several discrete stages, each building on the last. Rushing any one of them tends to surface problems during government review.

Scope the Work Before You Estimate Anything

Read the PWS, SOW, or SOO carefully before touching a spreadsheet. Pull every deliverable, milestone, reporting requirement, and performance standard. Map each one to a labor category or resource type. If you can't tie a line item back to a contract requirement, it shouldn't be in the estimate.

Build Your WBS and Assign Labor Categories

Break the scope into a work breakdown structure. Assign labor categories that match your approved job descriptions and, where applicable, your GSA or CIO-SP3 labor category definitions. Mis-mapping LCATs to tasks is one of the fastest ways to draw a deficiency finding.

Estimate Hours Using a Defensible Method

Choose your estimation approach based on what the data supports:

• Analogous estimation draws from past performance on similar contracts, adjusting for scope differences with documented rationale.
• Parametric estimation applies historical productivity rates, such as lines of code per developer hour or deliverables per analyst month, to the current scope.
• Engineering build-up estimates each task from first principles when no comparable history exists.

Document which method you used and why. Undocumented assumptions are the primary failure point in government BOE reviews.

Apply Rates and Indirect Costs

Apply fully loaded labor rates that match your approved forward pricing rate agreement, CAS-compliant cost accounting structure, or GSA schedule rates. Indirect costs including fringe, overhead, G&A, and fee must be applied consistently across the cost structure. Inconsistencies between your BOE rates and your SF 1411 or pricing model will trigger clarification requests.

Cross-Check Against the Evaluation Criteria

Before submission, read Section M. Confirm your BOE covers every factor evaluators will score as part of your price to win strategy. If the RFP calls out staffing rationale or phased ramp-up plans, those must appear in your narrative, beyond the spreadsheet alone.

Documenting Labor Costs in Your BOE

Labor is almost always the largest cost element in a government contract BOE, and evaluators will review it closely. Getting this section right means more than listing headcount; it means showing your work in a way that holds up under audit.

Start by identifying each labor category (LCAT) you plan to use. For each one, you need to document:

• The number of hours assigned, broken down by contract period if the effort spans multiple years
• The fully loaded labor rate, which should reflect your approved forward pricing rate agreement or, if one does not exist, your most recent incurred cost submission data
• The basis for the hour estimate, such as a historical project with comparable scope, a staffing model tied to specific deliverables, or a time study

Avoid the common mistake of applying a single blended rate across all labor categories. Evaluators expect to see rates tied to specific LCATs, and a blended rate signals either a shortcut or a lack of cost accounting discipline.

If your contract uses a Service Contract Act or Davis-Bacon wage determination, you must show that your rates meet or exceed the applicable wage floor for each LCAT in each place of performance. A rate that looks reasonable in one city may fall below the required minimum in another.

Finally, document any escalation assumptions applied across multi-year periods of performance. The Bureau of Labor Statistics Employment Cost Index is a commonly accepted escalation reference, and citing it by name gives evaluators a verifiable anchor for your year-over-year rate increases.

Stating Assumptions, Exclusions, and Risk

Every BOE section carries assumptions and exclusions that define its scope boundaries. Stating these clearly protects your firm if the government later claims your cost estimate should have covered work you never priced.

Assumptions

Assumptions are the conditions your estimate depends on to be valid. A BOE built on unstated assumptions is a liability. List every one explicitly, including expected period of performance, government-furnished equipment availability, staffing classifications under the applicable wage determination, and whether award fees or incentive structures affect labor allocation.

Exclusions

Exclusions tell the contracting officer what your price does not cover. If travel beyond a defined radius, integration with a legacy system, or data migration is out of scope, say so. Leaving exclusions implicit invites disputes during execution when the CO reads the SOW more broadly than you intended.

Risk Factors

Flag any conditions that could shift the estimate materially. Supply chain volatility, uncertain government approval timelines, or dependencies on subcontractor performance are legitimate risk factors worth naming. Reviewers respect specificity here far more than a boilerplate disclaimer about "unforeseen circumstances."

Aligning Your BOE with the Technical Volume

A BOE that lives in isolation from your technical volume is a liability. Evaluators read both documents together, and when the labor categories, task descriptions, or period-of-performance assumptions in your BOE don't match what your technical approach promises, the disconnect raises immediate questions about whether your team actually understands the work.

The alignment check runs in both directions. Your technical volume sets commitments around staffing, schedule, and deliverables. Your BOE has to reflect those commitments with specificity: the same LCATs your technical approach names, the same phasing your project plan shows, and the same assumptions your management approach rests on. If your technical volume promises a dedicated quality assurance lead in Phase 1, your BOE needs a line item for that role with hours and a rate, not a vague "QA support" entry buried in indirect costs.

A few areas where misalignment commonly breaks down:

• Staffing levels that don't match the org chart in the technical volume, such as a BOE showing three analysts when the technical narrative describes a five-person team structure.
• Task durations that contradict the project schedule, where the BOE estimates 200 hours for a deliverable the technical volume places on a 30-day timeline with two staff assigned.
• Assumptions in the BOE that reference contract conditions the technical volume never mentions, leaving evaluators with no way to trace the logic.
• Missing cost lines for activities the technical volume explicitly commits to, like site visits, government-furnished equipment coordination, or a transition period.

Before submission, run a structured cross-check: pull every staffing reference, deliverable, and milestone from the technical volume and verify each has a corresponding cost element in the BOE. Any gap is a scoring risk.

Common BOE Mistakes That Weaken Proposals

Every number in a BOE needs to hold up under review by someone who was not in the room when the estimate was built. The most common failures share one trait: they require the evaluator to accept the contractor's word without a verifiable anchor. These are the errors that most often cause that.

• "Based on experience" without a data reference is not a rationale. Replace it with a prior contract number, a specific productivity metric from a comparable effort, or a named time study. Generic experience language cannot be verified and signals a shortcut.
• Labor hours that are not tied to specific SOW tasks leave reviewers unable to trace the logic. Each LCAT estimate should map to a named deliverable or task area, not a general program phase.
• Escalation rates applied without a cited index, such as the BLS Employment Cost Index or a specific wage determination schedule, will draw scrutiny on any multi-year award where year-over-year cost growth needs to be supported by a named source.
• Subcontractor costs listed as a single pass-through line invite an immediate deficiency. Each subcontractor should support their scope with their own hours, rates, and cost element breakdown.
• Figures that do not match between the BOE narrative and the cost volume spreadsheet signal that no one ran a reconciliation pass before submission. Contracting officers will issue clarification requests, and in competitive source selections, that gap may already be scored.
• BOE assumptions that conflict with staffing levels or timelines already stated in the technical volume tell evaluators the proposal team worked in silos.

A useful internal test: give the BOE to someone unfamiliar with the pursuit and ask them to trace any single line item back to its source without your help. If they cannot, the rationale is not complete.

What DCAA Auditors Look for in a BOE

When a DCAA auditor reviews a BOE, they are not skimming for general reasonableness. They are tracing every cost element back to a documented, defensible rationale. Understanding what they look for helps contractors build BOEs that hold up under scrutiny from the start.

Auditors focus on a few core areas:

• Labor hour estimates must connect directly to the SOW. If you estimate 500 hours for systems integration, the BOE needs to show how you arrived at that number, whether through historical actuals, engineering judgment, or parametric modeling. Unsupported round numbers are a red flag.
• Indirect rates must match your approved forward pricing rate agreement or the rates submitted to the contracting officer. Pulling rates from a prior fiscal year without noting the discrepancy can trigger a formal finding.
• Direct costs beyond labor, including materials, travel, and subcontractor costs, need their own backup. A subcontractor quote should accompany any subcontractor line item; a travel estimate should reference the applicable GSA per diem rates from the Federal Travel Regulation.
• Escalation factors applied to out-year costs need a named source, such as the Bureau of Labor Statistics Employment Cost Index or published wage determination schedules.

Common BOE Deficiencies That Lead to Audit Findings

Knowing the failure modes makes them easier to avoid. The most frequent problems auditors cite include estimates with no traceability to the SOW, labor categories that do not match the work described, indirect rates applied inconsistently across cost elements, and missing documentation for sole-source or sole-justification assumptions.

Each of these deficiencies can result in a cost questioned or disallowed, which means the contractor absorbs that cost instead of recovering it from the government.

How GovDash Supports BOE Development

GovDash is the AI platform for winning government contracts, built for contractors who need to produce accurate, defensible BOEs under real deadline pressure. Assembling estimates across disconnected spreadsheets and documents is replaced by a single platform that connects capture data, labor categories, and historical pricing into one structured workflow.

When you start building a BOE in GovDash, the AI agent Dash reads the PWS or SOW, extracts each requirement, and maps it against your approved LCATs and cost elements, giving your team a structured starting point for review and refinement. That means less time spent manually parsing solicitation language and more time spent on the judgment calls that actually require subject matter expertise.

GovDash also pulls from your Data Library, so prior BOEs, approved rates, and past performance data feed directly into new estimates instead of getting rebuilt from scratch each time. This keeps your numbers consistent across submissions and gives reviewers traceable documentation back to the source.

A few specific ways GovDash supports the BOE process:

• Dash reads the solicitation and surfaces relevant requirements mapped to your cost structure, reducing the manual lift of cross-referencing a 200-page RFP against your labor categories.
• Your Data Library stores previously approved rates and indirect cost structures so estimates stay anchored to figures that have already passed government scrutiny.
• The workflow connects BOE inputs directly to the pricing government contracts volume, so changes to hours or rates propagate without manual re-entry across documents.
• Teams get a reviewable, auditable record of how each estimate was built, which supports DCAA inquiries and color review preparation.

Final Thoughts on Basis of Estimate Best Practices for Federal Proposals

A solid BOE protects your firm at proposal time, during contract execution, and through any audit that follows. The work of connecting each cost line to a specific requirement, a named source, and a documented assumption is what separates a defensible estimate from one that gets questioned or disallowed. Your BOE is a record of how your team thinks, and reviewers read it that way.

FAQ

What should a basis of estimate include for a government contract proposal?

A complete basis of estimate for a government contract needs a scope summary tied to specific PWS or SOW paragraphs, labor hour estimates broken down by LCAT with a documented rationale for each, materials and ODC line items with vendor citations, indirect costs applied at your current forward pricing rates, and a clearly stated list of assumptions and exclusions. Missing any one of these sections raises questions during source selection or DCAA audit. The assumptions section in particular carries substantial weight: it defines what you priced and protects you if the government's requirements shift after award.

How do I choose between analogous, parametric, and bottom-up estimating for a federal BOE?

The right method depends on what your data supports. Use analogous estimating when you have past contracts with comparable scope and can document the differences in complexity or size. Parametric estimating works well when you have reliable productivity rates, such as deliverables per analyst month or lines of code per developer hour, that you can tie to verifiable sources. Engineering bottom-up is the most defensible choice for complex, performance-based contracts where the scope is distinct enough that historical comparisons would require heavy adjustment. Most winning proposals combine all three, using parametric rates for well-understood phases and bottom-up builds for novel or high-risk task areas, with expert judgment filling gaps where data is thin.

Can I build a BOE in GovDash without manually cross-referencing the solicitation?

Yes. GovDash's AI agent Dash reads the PWS or SOW, extracts each requirement, and maps it against your defined labor categories and cost elements, reducing the manual lift of cross-referencing a lengthy solicitation against your pricing model. Your Data Library stores previously approved rates and indirect cost structures so estimates stay anchored to figures that have already passed government scrutiny, instead of being rebuilt from scratch each time. Changes to hours or rates propagate through the pricing workflow without manual re-entry across documents.

What causes the most common BOE deficiencies in DCAA audits?

The most frequent audit findings trace back to four patterns (per DCAA audit guidance): labor hour estimates with no traceable connection to specific SOW tasks, indirect rates that do not match the contractor's approved forward pricing rate agreement, subcontractor costs listed as a single pass-through line without a supporting cost breakdown, and escalation factors applied to out-year costs without a named source such as the Bureau of Labor Statistics Employment Cost Index. Each of these deficiencies can result in costs being questioned or disallowed, meaning the contractor absorbs those costs with no path to recovering them from the government.

How should a BOE align with the technical volume to avoid scoring risk?

Every staffing level, task duration, and deliverable commitment in your technical volume needs a corresponding cost element in your BOE. A mismatch, such as a technical narrative describing a five-person team while the BOE shows three analysts, signals to evaluators that the proposal team worked in silos and did not validate the estimate against the technical approach. Before submission, pull every staffing reference, deliverable, and milestone from the technical volume and verify each one maps to a specific line item in the BOE; any gap is a scoring risk during source selection.