What is an estimating system under DFARS?

An estimating system is the documented methodology a government contractor uses to develop cost proposals: how it forecasts labor hours, prices material, applies indirect rates, and reviews a bid before submission. DFARS 252.215-7002 contains the estimating-system definition and criteria. The estimating system is identified as one of six contractor business systems in DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) when the applicable clauses are included in a covered contract; DFARS 252.242-7006 (or its class-deviation successor 252.242-7999) addresses accounting-system administration specifically. The disclosure, maintenance, and review requirements apply to a large business contractor that received at least $50 million in the preceding fiscal year in DoD prime contracts or subcontracts for which certified cost or pricing data were required, or $10 million to under $50 million in such contracts plus written contracting-officer notification; they do not apply to other-than-large businesses under DFARS 215.407-5-70.

Who reviews a contractor's estimating system?

The auditor conducts estimating-system reviews. The cognizant contracting officer, in consultation with the auditor, determines acceptability and approves or disapproves the system. One or more material weaknesses can lead to system disapproval; if the contract includes DFARS 252.242-7005 (or its class-deviation successor 252.242-7998), payments may be withheld under that clause. DFARS 252.242-7005 applies only to covered contracts subject to the Cost Accounting Standards. Within 45 days of the final determination, the contractor must either correct the weaknesses or submit an acceptable corrective action plan. Effective implementation of an accepted plan ordinarily reduces withholding to 2 percent under paragraph (e)(2) until the contracting officer determines all material weaknesses have been corrected. Discontinuing withholding under paragraph (f)(2) requires the contractor first to notify the contracting officer in writing that all weaknesses have been corrected; after that notification, the contracting officer may discontinue withholding if the officer determines the weaknesses are corrected or, based on submitted evidence, reasonably expects the corrective actions have been implemented and are expected to correct them. Verify current applicability and withholding rules against the clause and acquisition.gov.

What makes an estimating system adequate versus deficient?

Adequacy rests on a documented methodology applied consistently in like or similar circumstances, supported by appropriate source data and sound estimating techniques, integrated with related management systems, reviewed and approved according to defined responsibilities, and supported by comparisons of projected results to actual results and analysis of differences. A deficiency can surface as one of the opposite conditions: an undocumented or informally applied method, unsupported cost data, estimates with poorly documented sources or rationale, or no process for comparing projected and actual results. No single control makes a system adequate; the cognizant contracting officer determines acceptability in consultation with the auditor.

How is the estimating system different from the accounting system?

The accounting system records and reports what a contract actually cost after the fact; the estimating system forecasts what a contract will cost before award. They are separate business systems, with estimating-system requirements in DFARS 252.215-7002 and accounting-system criteria in DFARS 252.242-7006, but they depend on each other. An estimate should be supported by documented sources and rationale, including relevant historical data where appropriate, and the reconciliation step that closes the estimating loop uses actual-cost information from accounting and job-cost records. See the government contract accounting guide for the accounting-system side.

Why does historical cost data quality matter so much to an adequate estimating system?

An estimate is only as defensible as the evidence behind it. The estimating-system criteria call for appropriate source data, sound estimating techniques and good judgment, documented sources, methods, and rationale, and historical experience, including historical vendor pricing data, where appropriate. Clean job-cost history in an ERP, organized by labor, material, and indirect categories, can help an estimator use relevant figures instead of reconstructing them from spreadsheets. Weak or unsupported historical data can contribute to an estimating-system finding.

Does ERP software make an estimating system DFARS-compliant?

No single piece of software makes an estimating system adequate. The contractor's documented methodology, its consistent application, appropriate source data, sound estimating techniques, and review and reconciliation controls matter more than a product feature list. An ERP or project-costing module can support those practices by holding organized job-cost data, structuring it by the categories an estimate needs, and integrating relevant information from related management systems. DFARS does not require the estimate and actual costs to reside in the same ERP or share a direct general-ledger connection. Configuration and process still decide the outcome.

How often should an estimating system reconcile estimates to actual costs?

DFARS requires internal review and accountability for comparisons of projected results to actual results and analysis of differences, but it does not set a fixed calendar interval or require reconciliation at contract completion or milestones. The contractor's disclosed procedures should explain how it performs and documents this comparison. A documented comparison gives the contractor information it can use to improve future estimates; the clause does not prescribe a separate continuous-improvement cadence.

SK Written by Sarika Krishnan with Robert LabardeeSenior Program Manager and Founder and CEO

Last updated August 2026.

Estimating system requirements under DFARS

DFARS 252.215-7002 defines the estimating system as the contractor's policies, procedures, and practices for budgeting and planning controls and generating estimates of costs and other data included in proposals. It is identified as one of six contractor business systems in DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) when the applicable clauses are included in a covered contract, and the cognizant contracting officer determines its acceptability in consultation with the auditor under DFARS 215.407-5-70.

Government contract accounting Talk to an ERP advisor

The estimating system is one of six contractor business systems identified in DFARS.

DFARS 252.242-7005, Contractor Business Systems (or its class-deviation successor 252.242-7998 for new solicitations and contracts), identifies six business systems when the applicable clauses are included in a covered contract. DFARS 252.242-7006, Accounting System Administration (or its class-deviation successor 252.242-7999), addresses the accounting system specifically; it is not the estimating-system clause. Estimating-system requirements are in DFARS 252.215-7002, with review procedures in DFARS 215.407-5-70. The estimating system covers how a contractor develops the cost proposals it submits for new work: forecasting labor hours, pricing material, applying indirect rates, and routing a bid through internal review before it reaches the government.

A material weakness in an estimating system can lead to a disapproved system determination. Payment withholding under DFARS 252.242-7005 (or its class-deviation successor) applies only when that clause is included in a covered contract, so the estimating system is not a paperwork exercise. It sits alongside the other five systems in the same regulatory family.

Accounting system

Segregates direct and indirect costs; identifies and accumulates direct costs by contract, while accumulating and allocating indirect costs to intermediate and final cost objectives through logical groupings and consistent allocation bases. Covered in the government contract accounting guide.

Estimating system

Builds cost proposals and estimates for new work, the subject of this guide.

Purchasing system

Governs how the contractor selects subcontractors and vendors and prices what it buys for a government contract.

Material management and accounting system (MMAS)

Plans, controls, and accounts for material used on government contracts, particularly in manufacturing.

Property management system

Tracks government-furnished and contractor-acquired property used in contract performance.

Earned value management system (EVMS)

Measures cost and schedule performance against a baseline on larger programs. Covered in the earned value management guide.

DFARS 252.215-7002 sets the estimating system disclosure requirements.

A large business contractor is subject to the estimating-system disclosure, maintenance, and review requirements if, in the preceding fiscal year, it received DoD prime contracts or subcontracts totaling $50 million or more for which certified cost or pricing data were required, or $10 million to under $50 million under those conditions and the contracting officer provided written notification. Other-than-large businesses are not subject to these disclosure, maintenance, and review requirements under DFARS 215.407-5-70. The disclosure goes to the Administrative Contracting Officer (ACO) under DFARS 252.215-7002 and describes the system: how the contractor identifies the elements of cost, selects estimating techniques for each element, and applies personnel, procedures, and controls to keep the process disciplined and repeatable.

The auditor conducts estimating-system reviews, and the cognizant contracting officer, in consultation with the auditor, determines the acceptability of the disclosure and approves or disapproves the system. The thresholds and specific procedures have been adjusted over time, so verify current figures against the DFARS on acquisition.gov rather than a fixed number.

An adequate estimating system rests on a defined set of controls.

No single feature or document delivers adequacy on its own. The criteria call for a documented methodology, consistent practice, appropriate source data, sound estimating techniques, defined review responsibilities, and comparisons of projected results to actual results with analysis of differences.

A documented estimating methodology

A written system description, required by DFARS 252.215-7002 for large business contractors that meet the listed applicability criteria, that spells out how the organization builds an estimate: labor hours, material pricing, indirect rates, and the review and approval responsibilities behind a proposal.

Consistent application across proposals

Documented methods have to be applied consistently in like or similar circumstances, using appropriate source data, techniques, and judgment. Different cost elements or circumstances may call for different techniques, but the rationale should be documented.

Appropriate and supportable cost data

Estimates use appropriate source data and historical experience where appropriate, together with current information and sound estimating judgment. Historical cost data should be relevant and supported, not stale figures rolled forward without review. When certified cost or pricing data are required, those data must be accurate, complete, and current as of a date certain; they are broader than historical accounting data and can include vendor quotations, data supporting projections, trends, make-or-buy decisions, and other forward-looking facts.

Reconciliation between estimates and actual costs

The estimating system provides for comparisons of projected results to actual results and analysis of differences. That comparison gives the contractor evidence about how well its estimating methods performed and can inform future estimates.

Integration with related management systems

DFARS requires integration of relevant data and information available from other management systems, but it does not require the estimate and actual costs to reside in the same ERP or to share a direct general-ledger connection. An ERP can support reconciliation by organizing labor, material, indirect categories, and job-cost data in compatible structures.

Internal review and approval controls

The system must establish clear responsibility for preparing, reviewing, and approving cost estimates and budgets, with management review and internal review and accountability. DFARS does not prescribe one fixed technical-pricing-management workflow; the contractor should document and follow its established review procedures.

Historical cost data quality decides whether an estimate is defensible.

An estimate is a forecast built from evidence, and that evidence can include the contractor's cost history alongside other appropriate data. A basis of estimate that cites relevant, comparable historical costs where appropriate, broken out by labor, material, and indirect category, and documents the methods and rationale behind the estimate is more supportable. One that carries forward a figure from an old proposal without checking it against current information is not. When certified cost or pricing data are required, those data must be accurate, complete, and current as of a date certain; they are broader than historical accounting data and can include vendor quotations, data supporting projections, trends, make-or-buy decisions, and other facts relevant to price negotiations.

The estimating-system criteria call for comparisons of projected results to actual results and an analysis of any differences. That comparison gives the contractor and the reviewer a basis for understanding how the estimating methods performed. See the guide to government contract project accounting for how job costs accumulate in the first place.

ERP costing configuration supports adequacy without creating it alone.

No product earns a contractor a DFARS-adequate estimating system. What a well-configured ERP can do is support the underlying practice: a job-cost structure that organizes labor, material, and indirect costs in categories useful to the estimate, historical actuals held cleanly enough that an estimator can use relevant figures instead of reconstructing them in a spreadsheet, and a proposal or costing module that can use relevant information from the indirect-rate pools and other management systems the accounting process produces.

That same configuration can make the reconciliation step more practical. When an estimate and the resulting job cost use compatible categories and identifiers, comparing the two can be simpler even when the information comes from separate systems. Contractors moving off spreadsheets or a disconnected estimating tool may benefit from establishing that shared structure. See the guide to indirect cost rates for how those pools are built.

Lightbridge ERP helps configure the cost data an estimating system depends on.

Lightbridge ERP is an independent, vendor-neutral ERP advisory firm with deep in-house expertise in government contract accounting. It helps contractors structure project costing so relevant historical cost data is organized by the categories an estimate needs, connect that data with related management-system information, and build the estimate-to-actual reconciliation that supports the documented estimating practices described in DFARS 252.215-7002.

Because Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, its advice on where an estimating capability should live inside the ERP is driven by fit rather than commission. For the broader accounting foundation an estimating system relies on, start with the government contract accounting guide or a structured ERP consulting engagement.

This guide is general information, not legal, audit, or accounting advice. Regulations, thresholds, and agency practice change. Verify any specifics against official sources such as acquisition.gov, the DCMA, and the DCAA, and consult qualified advisors before acting.

Estimating system requirements: frequently asked questions

What is an estimating system under DFARS?: An estimating system is the documented methodology a government contractor uses to develop cost proposals: how it forecasts labor hours, prices material, applies indirect rates, and reviews a bid before submission. DFARS 252.215-7002 contains the estimating-system definition and criteria. The estimating system is identified as one of six contractor business systems in DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) when the applicable clauses are included in a covered contract; DFARS 252.242-7006 (or its class-deviation successor 252.242-7999) addresses accounting-system administration specifically. The disclosure, maintenance, and review requirements apply to a large business contractor that received at least $50 million in the preceding fiscal year in DoD prime contracts or subcontracts for which certified cost or pricing data were required, or $10 million to under $50 million in such contracts plus written contracting-officer notification; they do not apply to other-than-large businesses under DFARS 215.407-5-70.
Who reviews a contractor's estimating system?: The auditor conducts estimating-system reviews. The cognizant contracting officer, in consultation with the auditor, determines acceptability and approves or disapproves the system. One or more material weaknesses can lead to system disapproval; if the contract includes DFARS 252.242-7005 (or its class-deviation successor 252.242-7998), payments may be withheld under that clause. DFARS 252.242-7005 applies only to covered contracts subject to the Cost Accounting Standards. Within 45 days of the final determination, the contractor must either correct the weaknesses or submit an acceptable corrective action plan. Effective implementation of an accepted plan ordinarily reduces withholding to 2 percent under paragraph (e)(2) until the contracting officer determines all material weaknesses have been corrected. Discontinuing withholding under paragraph (f)(2) requires the contractor first to notify the contracting officer in writing that all weaknesses have been corrected; after that notification, the contracting officer may discontinue withholding if the officer determines the weaknesses are corrected or, based on submitted evidence, reasonably expects the corrective actions have been implemented and are expected to correct them. Verify current applicability and withholding rules against the clause and acquisition.gov.
What makes an estimating system adequate versus deficient?: Adequacy rests on a documented methodology applied consistently in like or similar circumstances, supported by appropriate source data and sound estimating techniques, integrated with related management systems, reviewed and approved according to defined responsibilities, and supported by comparisons of projected results to actual results and analysis of differences. A deficiency can surface as one of the opposite conditions: an undocumented or informally applied method, unsupported cost data, estimates with poorly documented sources or rationale, or no process for comparing projected and actual results. No single control makes a system adequate; the cognizant contracting officer determines acceptability in consultation with the auditor.
How is the estimating system different from the accounting system?: The accounting system records and reports what a contract actually cost after the fact; the estimating system forecasts what a contract will cost before award. They are separate business systems, with estimating-system requirements in DFARS 252.215-7002 and accounting-system criteria in DFARS 252.242-7006, but they depend on each other. An estimate should be supported by documented sources and rationale, including relevant historical data where appropriate, and the reconciliation step that closes the estimating loop uses actual-cost information from accounting and job-cost records. See the government contract accounting guide for the accounting-system side.
Why does historical cost data quality matter so much to an adequate estimating system?: An estimate is only as defensible as the evidence behind it. The estimating-system criteria call for appropriate source data, sound estimating techniques and good judgment, documented sources, methods, and rationale, and historical experience, including historical vendor pricing data, where appropriate. Clean job-cost history in an ERP, organized by labor, material, and indirect categories, can help an estimator use relevant figures instead of reconstructing them from spreadsheets. Weak or unsupported historical data can contribute to an estimating-system finding.
Does ERP software make an estimating system DFARS-compliant?: No single piece of software makes an estimating system adequate. The contractor's documented methodology, its consistent application, appropriate source data, sound estimating techniques, and review and reconciliation controls matter more than a product feature list. An ERP or project-costing module can support those practices by holding organized job-cost data, structuring it by the categories an estimate needs, and integrating relevant information from related management systems. DFARS does not require the estimate and actual costs to reside in the same ERP or share a direct general-ledger connection. Configuration and process still decide the outcome.
How often should an estimating system reconcile estimates to actual costs?: DFARS requires internal review and accountability for comparisons of projected results to actual results and analysis of differences, but it does not set a fixed calendar interval or require reconciliation at contract completion or milestones. The contractor's disclosed procedures should explain how it performs and documents this comparison. A documented comparison gives the contractor information it can use to improve future estimates; the clause does not prescribe a separate continuous-improvement cadence.
How does Lightbridge ERP help with estimating system adequacy?: Lightbridge ERP is an independent, vendor-neutral ERP advisory firm with deep in-house expertise in government contract accounting. It helps contractors structure the ERP's project-costing and proposal configuration to organize relevant historical cost data by labor, material, and indirect category, connect that data with related management-system information, and build an estimate-to-actual reconciliation that supports the documented estimating practices described in DFARS 252.215-7002. Because Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, its configuration and platform advice is driven by fit rather than commission. This guide is general information, not legal, audit, or accounting advice; confirm current requirements against the DFARS and your contract.

From estimating theory to a reconcilable cost record.

When the question shifts from what DFARS requires to whether your historical cost data can support it, Lightbridge ERP, an independent readiness advisor, can help configure the job-cost structure an adequate estimating system runs on.

Talk to an ERP advisor GovCon project accounting