Contracts

Subcontractor Management: What the Prime Owes the Government (And What You Actually Control)

The government has no contract with your subcontractor, which is exactly why the sub's problems become yours. Both playbooks, government and prime, plus the one piece of math that sinks programs.

TL;DR. The government has no contract with your subcontractor. Everything it wants from the sub tier, it gets through the prime, and everything the sub gets wrong lands on the prime's record.

  • New to this? Think landlord and tenant. You can inspect the apartment. You can't tell the tenant's plumber how to fix the sink. That's the government's relationship with a sub: insight, not oversight.
  • Government PM (program manager)? You direct the prime, in writing, never the sub. Four things to ask the prime for at every monthly review are below.
  • Prime PM? Your pull peaks the day before you sign the subcontract. Six terms to lock in, and one piece of math: a $1.0M funded line and a $1.4M subcontract is a $400K hole you dug yourself.
  • Everyone: the most dangerous sub isn't the one who's behind. It's the one who went quiet. Silence is the signal, not the status report.

You hired a contractor to redo your kitchen. He hired a tile guy.

Week three, the tile guy stops showing up. You can't call him. You never hired him, and he doesn't owe you a thing. So you call your contractor, who says he's "handling it." The kitchen is still a construction site.

That is the prime-sub relationship in one paragraph. Now let's do the real version, with the parts that cost money.

Privity: Why the Prime Is Always on the Hook

The prime contractor is accountable to the government for all work on the contract, including everything done by subcontractors.

Privity of contract means a direct legal relationship between the two parties who signed. In federal contracting, the government has privity with the prime. Only the prime. The contracting officer (CO) may have consented to the subcontract; consent doesn't move the responsibility (FAR 52.244-2).

So when a sub misses a milestone or fails a security check, the cure notice goes to the prime, the liquidated damages hit the prime, and the CPARS (Contractor Performance Assessment Reporting System) rating lands on the prime's record. The source selection board at your next competition never sees "the sub was at fault." They see your rating.

The flip side matters just as much for government PMs. You get insight: see the data, sit in the reviews, ask hard questions. You do not get oversight: directing the sub's work. Direct the sub yourself, even informally, and you've handed the sub an argument that the government took over their performance, and a bill the government never agreed to pay.

From Lucas

The most common trap on the prime side: treating the sub like a vendor handling their own little corner, and assuming that because they signed a contract, they'll figure it out. They won't always. And when they don't, it doesn't matter how good your relationship with them is. What matters is what you have in writing, how closely you were watching, and how fast you escalated. The government judges the prime. Only the prime.

Don't Write Checks You Can't Cash

Here is the math that sinks otherwise fine programs, and it fits on a napkin.

The government funds the prime $1.0M for a piece of work. The sub seems capable. Everyone's excited. The prime signs the sub up for $1.4M. No modification, no new money.

$1.0M funded. $1.4M promised. $400K owed to the sub with nothing behind it.

Don't let your subcontract value outrun your own funding without a modification. The sub didn't do anything wrong. The math just didn't care how capable they seemed.

Related rule: never fully fund a sub upfront. Pay in tranches, tied to milestones or accepted deliverables. A sub who still needs your signature to get paid returns your calls a lot faster than one who's already been paid in full.

Before You Sign: Six Terms to Lock In

Your pull with a subcontractor peaks the day before signature and fades every day after. Six terms that decide who controls whom:

  1. Timecards in your system, not theirs. Hours logged straight into your cost accounting system mean you bill the government the same month. Their invoice on their schedule means you wait, every month, for the life of the contract.
  2. Net 30, tied to invoice approval. Not 100% upfront. Not Net 90, unless you only want desperate subs bidding your work.
  3. Rate caps across every option year. Uncapped escalation is option year three's surprise.
  4. Audit and records access. When DCAA (the Defense Contract Audit Agency) reviews your purchasing system, you need the sub's cost data, not a sub who stopped answering email.
  5. A named owner for flowdown compliance. Somebody reads FAR 52.244-6 and decides which clauses apply. In writing, before signature.
  6. Termination rights that match your own contract, both ways. If the government can terminate you for convenience, you need the same right over your sub, plus a real Termination for Cause clause for when they simply fail to perform.

The government can't enforce contract terms against your sub directly, so it requires you to push them down through flowdown clauses: provisions from your prime contract that you must include in your subcontracts. Some flow down to every sub at any dollar value (anti-trafficking, the ban on certain Chinese telecom gear, basic safeguarding when the sub holds federal contract information). Others trigger on thresholds or the kind of work: subcontracting plans, certified cost or pricing data, labor standards, and the cybersecurity clauses whenever the sub touches controlled information.

Two cautions on any flowdown checklist. Older ones still lead with FAR 52.222-26 (Equal Opportunity); the executive order behind it was revoked in January 2025, so don't copy it forward on autopilot. And since DoD moved most solicitations to the rewritten FAR text by class deviation on 1 February 2026, some clause numbers have changed. Work from the clause list in your actual prime contract.

Have a contract administrator check every new subcontract against that list. Missing flowdowns get cited as a management deficiency in a DCMA (Defense Contract Management Agency) review, and if the sub breaks a rule you were supposed to flow down, that's on you.

Two Playbooks: When the Sub Slips

Everything above about privity means government PMs and prime PMs play by completely different rules when a sub falls three months behind. Here they are side by side.

The move Government PM Prime PM
Call the sub? No. Direct the prime, in writing, dated: what's wrong, which requirement it violates, when you first saw it. Yes. You hold the contract. Go straight to the sub's PM.
First move A corrective action plan (CAP) from the prime, with a date. My rule: 30 days max for anything critical. "We're working on it" is not a plan. Hold the next funding tranche, reject the deliverable, or pause the option. All of these get attention without burning the relationship down.
The cure clock A cure notice from the CO (FAR 49.402-3), usually 10 days. Coordinate with legal first; you can't easily walk it back. The cure clause written into your own subcontract. The FAR cure notice governs government to prime, not prime to sub.
Biggest lever Escalate to the prime's senior leadership, through the CO. Termination for Cause. It only works if you actually negotiated one. Go check now, not after the missed milestone.
Before any termination Legal and the CO in the room. Reprocurement cost liability is real. Your own contracts and legal team, early. There's no CO to lean on; your company's exposure is on the line.

Government PMs: Four Things to Ask the Prime For

You can't manage the sub. You can manage how well the prime manages the sub. At every monthly review, the prime should be able to show you:

  1. The critical subs, by name. If one failing would blow up the schedule or leave you with no second source, it's critical. Make the prime say the names.
  2. Status you can see, not a slide that says "green." Real progress, staffing, open risks on each critical sub, every month, without you chasing it.
  3. A one-sentence answer to "what happens when a sub misses a milestone?" No sentence, no process.
  4. Proof the flowdowns landed. DFARS 252.204-7012 especially. Audits find that gap at the worst possible time.

Then build your own eyes. On programs with earned value management, the prime's EVMS clause (DFARS 252.234-7002) flows down to large subcontracts, so sub-level data should already exist. Ask for it. And make sure the prime's IPMR (Integrated Program Management Report) Format 2 shows which organization, and therefore which sub, is driving the variance.

The Sub Goes Silent. Now What?

The most dangerous sub isn't the one who tells you they're behind. It's the one who goes quiet.

Skipped status calls. Vague one-line updates. Their PM "isn't available" three weeks running. That's the signal. Not an official notification letter. The silence itself.

At that point, stop waiting for the prime to bring it to you. They may be trying to fix it quietly so they don't look bad at the review. Call the prime PM and ask one specific question:

"Walk me through exactly where your sub stands on [deliverable], today."

If they can't give you specifics, that's your answer. Hold the next funding tranche. Put the corrective action request in writing. If it's on the critical path, put a 30-day cure period on the table.

From Lucas

In my experience, by the time a subcontractor failure shows up in the prime's IPMR data, you're already three to six months behind on fixing it. You have far more pull before a missed milestone than after one. Spend it early, not late.

Three More Ways It Goes Wrong

  • The slip you hear about in passing. Every CDRL (Contract Data Requirements List item) and milestone the sub owns goes on a log with a due date and a status. If the CO asks how your sub is doing, produce it in five minutes.
  • The team that doesn't match the proposal. You proposed a cleared, certified team; newer people showed up. The government holds you to what you proposed. Verify sub staffing at kickoff and watch for departures.
  • The cybersecurity gap. CMMC flows down to any sub handling Federal Contract Information or Controlled Unclassified Information, and you confirm their status before award (DFARS 252.204-7021). As of October 2026 that means Phase 1 self-assessments; Phase 2, third-party certification, has been suspended since 13 July 2026 with no new date. Know their status. Don't assume.

Protecting Your CPARS When the Sub Is the Story

Your CPARS rating includes how well you managed your subs. If a sub shows up in your narrative, the record should show you managed it, not that you let it slide: dated notes of what went wrong and what you directed, the cure notice you issued under your own subcontract, and the escalation you made to the CO yourself, mitigation plan in hand. If sub performance is cited, you have up to 14 calendar days from notice to comment (FAR 42.1503). Use them.

One More Prime Obligation: The Subcontracting Plan

Large businesses on contracts expected to exceed $900,000 ($2 million for construction) generally need a Small Business Subcontracting Plan (FAR 19.702) with percentage goals by category. Small business primes are exempt. CPARS grades it. Track your goals quarterly, not in the last month of the year.

One sentence to teach your team: everything you want from the sub tier, you get through the prime, and confusing insight with oversight is how a program creates a commitment it will spend a year unwinding.

Drafted with AI from public sources. Spot a mistake? Email lucas@acqlerate.com and I'll fix it.

The Program Operations & Leadership module at Acqlerate covers subcontractor management: what you can and can't do with a sub, what to lock in before you sign them, and how to catch a problem early, in plain English.

Lesson: Subcontractor Management (Program Operations & Leadership Module)

Open This Lesson → Or start with a free account first