Most contractors think about DCAA in the context of auditing invoices or reviewing incurred costs. That's only part of the picture. DCAA also audits your estimating system — the processes, documentation, and controls you use to build cost proposals. And if your estimating system is found to be inadequate, the consequences go beyond a finding: the government can withhold up to 10% of your contract payments until you fix it.
If you're serious about cost-reimbursable federal work, or if you're competing on major GWAC and MAC vehicles like OASIS+ or Alliant, you need a defensible estimating system before you need it.
What Is a Government Contract Estimating System?
Your estimating system is the sum of your policies, procedures, controls, and documentation for developing cost proposals submitted to the government. It's not one document — it's the entire system that produces your proposals: how you estimate labor, how you determine material costs, how you apply escalation factors, how you justify subcontractor pricing, and how you document all of it.
A strong estimating system serves two purposes: it makes your proposals more accurate and defensible, and it demonstrates to DCAA (and to your evaluators) that your pricing is credible.
From where I sat as a Contracting Officer, this mattered at both ends of the process. On the pre-award side, a contractor with a known-adequate estimating system got less scrutiny on their price proposal — I trusted the cost elements more because I knew the process that generated them. On the post-award side, a weak estimating system meant more oversight, more back-and-forth, and a higher likelihood of audit findings that ate into everyone's time.
Who Is Subject to DCAA Estimating System Audits?
Under DFARS 252.215-7002, the formal estimating system requirements apply to large businesses that, in the prior fiscal year:
- Received $50 million or more in DoD prime contracts or subcontracts requiring certified cost or pricing data, OR
- Received $10–50 million in DoD awards requiring certified cost or pricing data AND received written notification that the system requirements apply
If you're a small business or haven't hit those thresholds yet, you're not formally subject to DFARS 252.215-7002. But here's what most small and mid-size contractors don't realize: building a compliant estimating system before you need it is a competitive advantage, not just a compliance burden.
On competitive evaluations — especially on OASIS+, Alliant 3, and other GWACs that include cost realism analysis — a contractor with a documented, consistent estimating system produces proposals that score better. Evaluators can trace how you got to each cost element. That traceability is credibility.
The Three Situations That Trigger an Audit
DCAA or your Administrative Contracting Officer (ACO) can initiate an estimating system audit in three scenarios:
- Initial review after a trigger event — when your contract portfolio crosses the threshold thresholds under DFARS 252.215-7002
- Periodic cycle — roughly every four years for contractors already subject to the requirements
- Secondary trigger — when findings from another audit (incurred cost, forward pricing, or business systems review) point to weaknesses in your estimating
You don't always get advance warning for scenario three. This is why being proactively audit-ready matters more than waiting for a scheduled review.
What DCAA Is Actually Looking For
The audit will assess whether your estimating system is adequate — meaning it produces proposals that are current, accurate, and complete. Specifically, auditors look at:
Written policies and procedures. Do you have documented estimating procedures for each cost element — labor, materials, subcontracts, indirect costs, escalation? Are they actually followed, or are they theoretical?
Roles and approval authority. Who can approve a proposal? Who reviews for cost reasonableness? Are these roles documented and communicated? Auditors want to see a clear chain of accountability, not just one person who "handles proposals."
Basis of Estimate (BOE) documentation. For every cost element in a proposal, you should have a documented BOE that explains how you derived the estimate — historical data, market rates, engineering judgment, vendor quotes. A number without a traceable source is an unsupported estimate.
Historical data use. Are you using your own historical cost data to inform estimates where applicable? Ignoring your own actuals and proposing from scratch every time is a red flag.
Proposal repository. Can you produce a list of all proposals submitted in the past year, with their status, amounts, and associated contract IDs? Auditors ask for this. If you can't produce it, that's a documentation finding before they've looked at a single proposal.
Subcontractor pricing review. For significant subcontract costs, have you assessed the reasonableness of their pricing? Just passing subcontractor quotes through without analysis is insufficient.
Error controls. Do you have a review and approval process that catches errors before proposals go out? Who checks the math? Who validates the indirect rate application?
What Happens If Your System Is Disapproved
If the ACO issues a final determination that your estimating system is inadequate, you face payment withholds on your cost-type contracts:
- Up to 5% for a single business system deficiency
- Up to 10% if you have multiple business system issues simultaneously
Payment withholds hit cash flow directly and can affect your ability to meet payroll and fund ongoing performance. Beyond the financial impact, a disapproved estimating system affects your past performance record and may come up in future source selections.
After a disapproval, you have 45 days to either correct the deficiencies or submit a corrective action plan with clear milestones. The CAP buys you time, but the clock is running and the withholds continue until the deficiencies are resolved.
Building an Estimating System That Works
The good news: the gap between "no formal system" and "audit-ready system" is smaller than most contractors think. You're already generating proposals — which means you're already doing the underlying work. The difference between a good estimating habit and a formal system is structure, documentation, and consistency.
Start here:
Write it down. Create a written estimating procedures document that covers each cost element you include in proposals. Doesn't need to be long. Needs to be specific, accurate, and actually followed.
Standardize your BOE format. Use the same template for every labor estimate, every material estimate, every subcontractor justification. Consistency is what lets auditors trace your methodology across multiple proposals.
Build a proposal log. A simple spreadsheet with every proposal submitted in the last 12 months — date, solicitation number, dollar amount, win/loss outcome, location of proposal file — satisfies the repository requirement and takes about 30 minutes to set up.
Document your training. If you have anyone involved in proposal development, document their training. Dated records showing who was trained on what is an audit requirement, not a nice-to-have.
Set up a review cycle. Create a standard process for who reviews proposals before submission and what they're checking. Even a two-person shop can have a meaningful review process if it's documented and followed.
The OASIS+ and Alliant 3 Connection
Both OASIS+ and Alliant 3 include cost realism analysis as part of task order evaluation for cost-type work. Agencies using these vehicles are looking for cost proposals that are traceable, reasonable, and based on documented assumptions.
Contractors who come in with well-structured BOEs, consistent indirect rate applications, and clearly sourced cost elements don't just score better on cost realism — they also move through negotiations faster because there's less for the CO to question. That speed matters when there are multiple competitive task orders in a pipeline.
Your estimating system is either a competitive asset or a liability. Build it right and it pays for itself.