Federal subcontracting disputes follow their own rules, and most primes discover those rules at the worst possible moment: when a sub walks off a job, when payment is withheld after a schedule slip, or when an SBA size protest unravels an agreement weeks before award. The FAR is surprisingly thin on prime-sub dispute mechanics. That gap has consequences, and filling it correctly before work starts is the difference between a recoverable situation and a CPARS entry that follows your firm for years.
What the FAR actually covers — and what it doesn't
The FAR governs the relationship between a prime contractor and the federal government. It does not govern the relationship between a prime and its subcontractors directly, except where specific clauses flow down.
FAR 52.244-2 (Subcontracts) requires primes on cost-reimbursement and certain other contracts to get contracting officer approval for first-tier subcontracts above specific thresholds — currently $150,000 for cost-type contracts. FAR 52.244-6 (Subcontracts for Commercial Products and Commercial Services) establishes mandatory flowdown clauses. Neither clause creates a dispute resolution mechanism between prime and sub.
The result: when a dispute erupts, the prime and sub are largely governed by the terms of their subcontract agreement itself, plus applicable state commercial law. If the subcontract is silent on dispute procedures, the sub has no FAR-mandated pathway to escalate to the contracting officer. The contracting officer is not your arbitrator. Primes who tell frustrated subs "take it up with the CO" are sending them somewhere with no jurisdiction.
The one FAR mechanism that does matter internally is the Disputes clause (FAR 52.233-1), but it applies to prime-government disputes only. It does not extend downstream unless the subcontract explicitly incorporates it by reference and both parties agree the CO will hear sub-level claims — which is rare and not enforceable unilaterally.
Miller Act claims: the sub's real leverage
For any federally funded prime contract over $150,000 for construction, the Miller Act (40 U.S.C. §§ 3131-3134) requires the prime to post a payment bond equal to 100% of the contract price. That bond is the sub's primary enforcement tool when the prime withholds payment.
A first-tier subcontractor can file directly on the payment bond. No notice period is required before suit, though filing must happen within one year of the last labor or materials furnished. Second-tier subs (sub-subs) face a stricter requirement: they must give written notice of their claim to the prime within 90 days of last furnishing work or materials. Miss that 90-day window and the second-tier claim on the bond is gone.
Suits on Miller Act bonds are filed in the federal district court for the district where the contract was performed. State courts have no jurisdiction. The practical implication for primes: a Miller Act claim is a federal lawsuit, not a demand letter. Bond sureties become immediately involved, legal costs escalate quickly, and the relationship with the sub is almost certainly finished.
Payment disputes on service and supply contracts are different. The Miller Act applies specifically to construction. On service contracts, subs have no bond to claim against. Their recourse is contractual — the subcontract terms, state prompt payment statutes, and civil litigation. Some states have enacted their own prompt payment laws covering federally funded service contracts, but coverage varies significantly.
SBA size protests and what they do to existing subcontract agreements
An SBA size protest filed against a prime — or against a proposed subcontractor on a set-aside — can destabilize a prime-sub agreement at the worst possible time.
When a prime wins a small business set-aside and a disappointed offeror protests the prime's size status, SBA's Office of Government Contracting has 15 business days to issue a size determination. If the prime is found to be other than small, the agency may terminate the contract for the government's convenience. Any work already performed is billable; future work stops. The sub's position depends entirely on what the subcontract says about termination for convenience.
The more operationally complex scenario involves the ostensible subcontractor rule under 13 C.F.R. § 121.103(h). SBA will find a small business prime ineligible if the prime is unduly reliant on a large subcontractor for the primary and vital requirements of the contract. If a compliance audit or protest reveals this reliance, the prime's size status is invalidated retroactively. Subcontracts executed under that prime's representation may be called into question, and the government will seek repayment of any award incentives tied to small business status.
For primes that use large subs to fill technical capacity gaps on set-asides, document the division of work clearly from day one. The sub's scope should be genuinely secondary to what the prime performs directly.
CPARS: how disputes become permanent record
The Contractor Performance Assessment Reporting System (CPARS) is where prime-sub disputes leave their most durable mark — on the prime, not the sub.
The government evaluates prime contractor performance in CPARS, not sub performance directly. When a dispute with a sub causes schedule delays, cost overruns, or quality failures on the prime contract, those outcomes go into the prime's CPARS record. The underlying cause, whether a sub walking off the job, a payment dispute that paralyzed work, or an SBA determination that forced scope restructuring, is not the government's problem. The prime owns the outcome.
CPARS ratings are accessed by source selection officials through the Federal Awardee Performance and Integrity Information System (FAPIIS) and Past Performance Information Retrieval System (PPIRS). A "Marginal" or "Unsatisfactory" rating in management, schedule, or cost control — categories directly affected by sub disputes — can eliminate a firm from competitive consideration on major programs for three years. That's the lookback window agencies apply when evaluating past performance on new source selections.
Primes that resolve sub disputes quickly, even at financial cost, generally make the right tradeoff. A six-figure settlement with a difficult sub is cheap compared to losing evaluation points on a $50 million recompete.
Three action steps
Audit your standard subcontract template for dispute clauses. At minimum, include: a tiered escalation process (project manager, VP, then mediation), a governing law provision (choose your state), and an explicit termination for convenience clause with payment procedures. A subcontract that is silent on these terms relies entirely on state default rules, which vary widely.
Get the Miller Act notice dates on your calendar for every construction program. For second-tier subs, the 90-day notice window is a hard cutoff. Build a tracking process so your subcontract administrators flag the last-day-of-work date for every second-tier sub on bonded contracts. Missing that window transfers risk to your bond and your surety relationship.
Before any set-aside award, run your proposed teaming structure past legal for ostensible subcontractor exposure. If the sub will perform more than 50% of the primary and vital requirements, or if the sub is providing the key personnel and management, you have a problem. Fix the scope split before award, not after an SBA area office calls.
