Government Contract Compliance: What You Need to Know About Certified Cost and Pricing Data

May 7
3 min read

If your company bids on government contracts, one question will come up sooner or later: do you need to provide certified cost and pricing data to be compliant — and if so, how do you do it properly?

It's one of the most misunderstood areas in government contracting. Get it wrong and you're exposed. Get it right and it becomes a competitive advantage, because most of your competitors are guessing.

Here's what you need to know.

Three factors determine your compliance position

Every proposal you submit to a government customer sits somewhere on a compliance spectrum. Your position on that spectrum is determined by three things.

1. The Threshold

The Truth in Negotiations Act (TINA) sets a monetary threshold above which you're required to provide certified cost and pricing data. That threshold recently increased from $750,000 to $2 million. If your bid is above $2 million, you are legally required to provide certified cost and pricing data. Below it, you generally are not, though you still need to be aware of the simpler Simplified Acquisition Threshold, which triggers different requirements.

The important nuance here: you can't simply bid below the threshold to avoid the requirement if your actual costs exceed it. Compliance isn't something you engineer around — it's something you need to plan for from the start of the bid process.

2. How You're Going to Market

The nature of your bid matters enormously. If you're a sole-source contractor, meaning you're the only bidder for a piece of work, expect significant scrutiny. The government will require you to prove that the price you're charging is reasonable and fair, essentially on behalf of the taxpayer. That means a thorough breakdown of your costs, not just a price.

On the other hand, if you're competing in a multi-bidder environment where price is openly contested, or you're providing commercial pricing that's publicly available, the requirement to provide cost and pricing data typically falls away. The market itself becomes the proof of reasonableness.

3. Your Subcontractor Relationships

This is the one that catches people off guard. TINA compliance doesn't stop at your own bid, it flows through the supply chain.

If you have a subcontractor whose portion of the work exceeds $2 million, they may also be required to provide certified cost and pricing data. And if you're a subcontractor bidding to a commercial prime who is themselves priming a government contract, you could be on the hook for TINA compliance even though you're not bidding directly to the government. The obligation follows the money, not just the direct customer relationship.

If you need to be compliant, here's how you do it.

There are two types of analysis the government may require: price analysis and cost analysis.

Price analysis is the simpler of the two. It asks: what does this thing cost in the market? It's a comparative exercise, benchmarking your price against publicly available data or market rates.

Cost analysis goes deeper. It's a detailed breakdown of what it actually costs your organization to deliver the work – labor, materials, subcontractors, overhead. And this is where most companies struggle, because a proper cost analysis requires you to go into your business history and pull real, traceable data. That means your ERP system. Your actual purchasing records. Your engineering labor data. Your supplier invoices. The historical actuals from projects you've delivered before.

The government isn't looking for estimates or assumptions, they're looking for evidence.

And the key word is traceability: a clear, auditable line from the price you're quoting all the way back to the actual costs you incurred doing similar work in the past.

Why this Matters for How you Build your Estimating Process

The companies that handle TINA compliance well aren't scrambling to find data when an RFP lands. They've built a process that captures cost actuals continuously, so when they need to demonstrate compliance, the evidence is already there.

That means your estimating system and your ERP need to be connected. It means project actuals need to feed back into your cost knowledge base. It means the gap between what you estimated and what you actually spent needs to be visible, measurable, and retrievable.

This is exactly the kind of closed-loop process Twenty5's iPE platform is built to support. When your estimate is tied to real historical data from SAP, and when every project updates that knowledge base for the next bid, compliance stops being a fire drill and starts being a built-in capability.

Twenty5 helps Aerospace & Defense contractors build the estimating and pricing infrastructure that makes compliance a competitive advantage, not a liability. Learn more at twenty5.com.

Listen to Twenty5’s Podcast, Sharp Vision for more insights on Spotify, Apple Podcast, or YouTube.