14.3 Subcontract Management & Consent (FAR Part 44)

14.3 Subcontract Management & Consent (FAR Part 44)

Quick Answer: Manage Subcontracts (FAI 4.1.3, about 4 questions) maps to FAR Part 44. Know when consent to subcontract is required, advance notification, contractor purchasing system review concepts, clause flow-down, and that the prime remains responsible. Link post-award oversight to small business subcontracting plan compliance. Consent is a CO business decision, not automatic approval or a shift of privity to the Government.

Large primes rarely perform every hour and every part themselves. Subcontracts can deliver capability—or inject cost, schedule, socioeconomic, and integrity risk. FAR Part 44 — Subcontracting Policies and Procedures is the Government's toolkit for managing that risk without turning the CO into the subcontractor's project manager. Even though FAI weights this competency at only about four questions, the items are crisp: consent, notification, prime responsibility, flow-down, purchasing systems, and plan compliance.

Why subcontract management matters after award

Pre-award source selection evaluated the prime's offer. Post-award, value often depends on who the prime actually uses. Failures look like:

Part 44 exists so the Government can see and influence certain subcontracting actions while keeping the prime as the accountable party.

FAR Part 44 policy themes

Closed-book map:

1. Contractors must buy materials and services efficiently and effectively under their purchasing systems.
2. Government consent is required for certain subcontracts under specified contract types/conditions.
3. Advance notification supports timely Government review.
4. Contractor purchasing system reviews (CPSRs) evaluate the adequacy of a contractor's purchasing system when thresholds/conditions warrant.
5. Flow-down of applicable clauses protects statutory and contractual policies at lower tiers.
6. Consent is not privity—the Government generally contracts with the prime, not the sub.

Consent to subcontract — when and why

Consent to subcontract means the Contracting Officer's affirmative approval (when required) before the prime places a subcontract covered by the consent requirement.

When consent is commonly required (conceptual)

Part 44 and related clauses typically require consent for subcontracts under, among others:

Often less automatic consent machinery: many firm-fixed-price contracts for commercial products/services rely more on the prime's price and performance risk—consent may be limited or not required the same way. Exam judgment: do not claim "every subcontract under every contract needs CO consent." Tie consent to contract type + clause + FAR conditions.

What consent is for

Consent review asks business questions:

• Is the subcontract necessary for performance?
• Is the subcontractor responsible for the work being placed?
• Is the subcontract type and price/cost approach reasonable?
• Are conflicts of interest or affiliate self-dealing concerns addressed?
• Are required flow-downs present?
• Does the action support (or undermine) small business subcontracting commitments?
• Are there organizational conflict, security, or export issues?

What consent is not

Scenario A — Silent critical sub. On a cost-reimbursement services contract requiring consent, the prime places a major technical subcontract with an affiliate at a rich cost-plus fee without notification or consent. Wrong. Advance notice + consent process; scrutinize affiliate deals and reasonableness.

Scenario B — Consent as scapegoat. After consent, the sub fails. Prime tells the CO, "You approved them, so this is on the Government." Wrong. Consent does not transfer performance responsibility or create a Government guarantee of the sub's success.

Advance notification

Advance notification is the prime's required notice to the Government before awarding certain subcontracts (content and timing driven by the clause/FAR). Purpose:

1. Give the CO time to grant or withhold consent when consent applies.
2. Surface risk, competition, and socioeconomic issues early.
3. Preserve an audit trail of major lower-tier placements.

Notification packages conceptually include what is being bought, from whom, type of subcontract, price/cost, and basis of selection. Incomplete notifications that hide affiliate relationships or noncompetitive placements are red flags.

Exam cue: Notification without waiting for required consent is incomplete compliance when consent is mandatory. Notification is the heads-up; consent is the decision.

Contractor purchasing system reviews (CPSR) — conceptual

A Contractor Purchasing System Review evaluates whether a contractor's purchasing system (policies, procedures, and practices for subcontracting/purchasing) is adequate to protect the Government—especially when significant subcontracting under flexible contract types is expected.

You need concept + consequence, not a multi-day CPSR auditor checklist.

Exam trap: "Approved purchasing system means the contractor may ignore all subcontracting plan goals." False—system approval and socioeconomic compliance are related but not identical free passes.

Flow-down of clauses

Flow-down means the prime must include certain mandatory FAR/DFARS (and other) clauses in subcontracts so statutory policies reach lower tiers.

Prime duty: identify required flow-downs and actually put them in subcontract documents. Government duty: check flow-down as part of consent/purchasing system oversight when reviewing packages—not rewrite the entire private subcontract for fun.

Exam trap: "If a clause isn't flowed down, the sub is free of all federal policy and the prime is harmless." The prime remains responsible to the Government for contract compliance even when its subcontract is poorly drafted; missing flow-downs create prime risk.

Prime remains responsible

Anchor sentence for CON 3990V:

The Government's contract is with the prime. The prime is responsible for subcontract performance, quality, schedule, and compliance—including management of its suppliers.

Implications:

1. Government generally directs the prime, not the sub (exceptions for rare direct relationships are not the default exam answer).
2. Quality nonconformance by a sub is still the prime's nonconformance to the Government.
3. Payment issues with a sub are primarily prime-sub commercial/contractual issues (while Government still enforces prime contract terms, withholding, etc., as allowed).
4. Consent and CPSR oversight support Government interests; they do not convert the CO into the sub's CO.

Scenario — Directing the sub. A COR, frustrated with a sub's technician, emails the sub instructions bypassing the prime. Risky/wrong pattern. Direction should go to the prime under the prime contract; side-managing subs confuses privity and creates claims/authority issues.

Small business subcontracting plan compliance (post-award link)

Chapter 9 covered Part 19 programs and plans at pre-award. Post-award, when a subcontracting plan is required and incorporated:

Exam trap: "Plan approved at award = forever compliant." Compliance is performance through the period of performance, including options.

Scenario — Plan vs reality. Prime committed 35% small business subcontracting dollars, then self-performs almost everything with large affiliates and files weak reports. CO actions: engage, document, involve small business specialist, consider contractual remedies and past performance—do not shrug because the pre-award plan checklist was complete.

Practical CO decision path (memory chain)

Is consent required under this contract type/clause?
    -> No: still monitor performance & plan compliance as applicable
    -> Yes: was advance notification complete and timely?
        -> Review necessity, responsibility, price/cost, competition, flow-downs, socioeconomic impact, conflicts
            -> Consent / conditional consent / withhold with reasons
                -> Document decision; continue oversight; prime still owns results

Connecting Part 44 to Parts 42 and 46

• Part 42 admin receives consent packages, monitors reporting, and escalates purchasing issues.
• Part 46 quality still judges prime deliverables—sub defects are prime quality problems.
• Part 19 subcontracting plans are enforced in the post-award file, not only at award.
• Later changes/terminations often require primes to manage their subs in parallel.

CON 3990V closed-book anchors

• Part 44 = subcontracting policies (consent, notification, purchasing systems, flow-down).
• Consent when required—especially flexible contract types—not for every FFP commercial widget by default.
• Advance notification enables timely consent decisions.
• CPSR = system health; approved systems can ease individual consent.
• Prime remains responsible; consent != privity != Government guarantee.
• Subcontracting plans are post-award living obligations.

---

Bottom line: Manage Subcontracts under FAR Part 44 protects the Government when primes buy through lower tiers—using consent, advance notification, purchasing system insight, and flow-down discipline—while never forgetting the prime remains responsible. On CON 3990V, pick answers that require consent when policy demands it, refuse to treat consent as a performance warranty, and keep small business plan compliance alive after award.