Desk reference

Subcontract flowdowns, consent, and post-award teammate changes

Terms for converting proposal promises into subcontract paper after award — , , and teammate changes — without creating Government– .

1 / 2

Subcontract clause flowdowns are the deliberate transfer of -contract and statutory terms to a subcontract, clause by clause, for that subcontract type. Subcontract consent under FAR 52.244-2 is the ’s approval of certain subcontracts when the prime contract or law requires it. Build the subcontract with a clause matrix: flow down what the prime contract and law require, support make-or-buy decisions when required, and obtain consent when demanded. An approved purchasing system may reduce consent events; it does not waive diligence, make-or-buy duties, or the need to read the prime’s actual consent clause.

Watch for

Blanket copy-paste of every prime clause is not thoughtful flowdown. Purchasing-system approval is not Government endorsement of every subcontract term. Consent is not privity between the Government and the sub.

2 / 2

Post-award teammate changes

A post-award teammate change is a substitution, addition, or workshare shift among team members after contract award. Such changes must follow the , contract, and vehicle rules that govern disclosure and consent. The performance promise the Government bought — and the prime’s for it — remains unless the contract is properly modified. Map required flowdowns before first subcontract draft; identify consent and notification triggers in the prime and ordering vehicle; document teammate changes with the same disclosure discipline used pre-award.

Watch for

Award does not license silent substitution of the evaluated team, and vehicle logos do not authorize member swaps without reading the ordering contract and CTA paperwork.

Subcontract clause flowdowns and consent

Post-award teammate changes

Further reading