Mandatory, Suggested, and Optional: Understanding and Negotiating Government Contract Flowdown Clauses

By: Daniel J. Gershman and Dennis W. Lind

For companies doing business with the federal government—whether as a prime contractor or as a subcontractor several tiers removed—few contract provisions carry as much practical weight, or receive as little scrutiny, as flowdown clauses. A single subcontract or purchase order may incorporate by reference dozens or even hundreds of government clauses, often presented as a non-negotiable, take-it-or-leave-it schedule. In our experience, that presentation is frequently misleading. While some flowdowns are genuinely required by law, many are included out of habit or caution, and others simply do not fit the transaction at hand. Understanding which is which is the key to managing compliance risk while protecting a company’s commercial position.

This alert explains what flowdown clauses are, outlines the key differences among mandatory, suggested, and optional flowdowns, and describes where contractors and subcontractors have meaningful room to negotiate.

1. What Are Flowdown Clauses?

When the federal government awards a contract, the prime contractor agrees to a long list of terms drawn largely from the Federal Acquisition Regulation (FAR), the primary body of rules governing federal procurement, and, for defense work, the Defense Federal Acquisition Regulation Supplement (DFARS). Many of those terms govern not only how the prime performs, but also how work is performed by the companies the prime hires to help it.

A flowdown clause is a provision in a subcontract or purchase order that passes (or “flows down”) obligations from the prime contract to a subcontractor or supplier. Flowdowns exist for two basic reasons. First, the government relies on them to ensure that public policies, such as equal employment opportunity, anti-human-trafficking rules, cybersecurity protections, and supply-chain security, reach every company performing government work, not just the prime. Second, prime contractors use them to protect themselves: because the prime remains responsible to the government for the entire contract, it wants its subcontractors bound by matching obligations so that it is not left holding a commitment it cannot meet.

Flowdowns typically appear as a list of clause numbers and titles incorporated “by reference,” often with a note that terms such as “Contractor” and “Government” should be read to mean “Seller” and “Buyer.” Because the full text is not reproduced, it is easy to accept the list without appreciating the obligations and costs it contains. Many flowdown clauses also include applicability conditions, such as dollar thresholds, the type of item purchased, where work is to be performed, or whether certain information or government property is involved. Those conditions matter a great deal.

It is common in practice, and helpful, to group flowdowns into three categories: mandatory, suggested, and optional. These are practical labels used by contractors and their counsel rather than formal regulatory terms, and different organizations draw the lines in somewhat different places. The categories nevertheless provide a useful framework for review.

2. Mandatory Flowdowns

Mandatory flowdowns are clauses that the prime contractor is legally required to include in its subcontracts, either because the clause itself says so or because a regulation requires it. The FAR and DFARS typically signal this through clause language directing the contractor to “insert the substance of this clause, including this paragraph, in all subcontracts” meeting specified criteria. For subcontracts for commercial products and commercial services, FAR 52.244-6 and the list in FAR 52.212-5(e) identify a limited set of clauses that must be flowed down; DFARS 252.244-7000 plays a similar role for defense work.

Commonly encountered mandatory flowdowns include:

• Equal opportunity and affirmative action requirements (e.g., FAR 52.222-26).
• Combating trafficking in persons (FAR 52.222-50).
• Employment eligibility verification through E-Verify (FAR 52.222-54), subject to its thresholds and exceptions.
• Prohibitions on certain telecommunications and video surveillance equipment and services (FAR 52.204-25).
• Safeguarding covered defense information and cyber incident reporting (DFARS 252.204-7012), where covered defense information is involved, along with basic safeguarding of contractor information systems (FAR 52.204-21) where applicable.
• Technical data and computer software rights clauses under DFARS Part 227, as stated in each clause.
• Cargo preference requirements for transportation of supplies by sea (e.g., FAR 52.247-64), where ocean shipment is involved.

Generally, mandatory clauses cannot be negotiated away. The prime has no authority to waive an obligation the government has imposed, and a prime that omits a required flowdown may itself be in breach of its contract. For a subcontractor, refusing a properly applicable mandatory clause usually means losing the work. In some cases (e.g., False Claims Act exposure tied to cybersecurity or certification requirements), noncompliance can carry consequences well beyond a contract dispute.

That said, “mandatory” does not mean “automatic.” Many mandatory clauses apply only when specific conditions are met: a dollar threshold, a type of work, or the presence of a particular category of information. A clause that is mandatory in one subcontract may be inapplicable in another. The productive question for a subcontractor is therefore not whether a mandatory clause can be removed, but whether its triggering conditions are actually satisfied, what scope of personnel, systems, or work it reaches, and whether the correct version of the clause has been selected.

3. Suggested Flowdowns

Suggested flowdowns are clauses that the regulations do not require the prime to flow down, but that the prime commonly includes because they help it satisfy its own obligations to the government. The distinction from mandatory clauses is important: the prime wants these clauses, but the law does not demand them. As a result, they are the natural focus of negotiation.

Examples frequently found in this category include:

• Audit and records clauses, which may give the prime or the government access to a supplier’s books, cost data, and facilities.
• Changes clauses, which allow the buyer to unilaterally modify certain aspects of the work.
• Stop-work clauses, which allow the buyer to suspend performance for a period of time.
• Inspection and acceptance clauses, which set the terms for testing, rejecting, and accepting deliverables.
• Termination for convenience clauses, which allow the buyer to end the subcontract when the government terminates the prime contract—or simply when the buyer no longer needs the work.

Parties often include these clauses where the prime faces genuine exposure that should be shared, such as where the government may change, suspend, or terminate the prime contract. Parties often exclude or tailor them where the clause does not fit the commercial deal (e.g., cost-based audit rights in a firm-fixed-price purchase of commercial products, or source-inspection rights that would give outsiders access to a supplier’s proprietary manufacturing process). Because these clauses are tools for allocating risk, the right answer depends on the scope, pricing, and structure of the particular subcontract.

4. Optional Flowdowns

Optional flowdowns are clauses whose inclusion is discretionary and whose relevance depends heavily on the facts. Many address circumstances that arise only in particular programs: construction labor standards, performance outside the United States, government-furnished property, research and development work, hazardous materials, special shipping arrangements, or services rather than supplies. In larger flowdown schedules, optional clauses frequently make up the majority of the list.

Optional does not mean irrelevant. If a clause’s factual predicate is present (e.g., if the subcontractor will in fact hold government property), the clause may impose real obligations and should be addressed carefully. Conversely, when the predicate is absent, an optional clause adds nothing but ambiguity and potential liability. Examples include government property clauses where no property will be furnished, destination-shipping provisions that conflict with agreed FOB origin terms, or vessel-shipment clauses where no ocean transportation will occur.

Strategically, optional clauses deserve a disciplined “fit” analysis. A company should include an optional clause when it reflects the actual work and allocates a real risk sensibly, and should seek deletion, or a written statement that the clause does not apply, when it does not. Leaving inapplicable clauses in place invites disputes over what the parties intended and can create compliance obligations that no one is tracking.

5. Negotiating Rights: Where the Leverage Is

Prime contractors often present flowdown schedules as standard and non-negotiable. In practice, subcontractors (particularly suppliers of commercial products, companies with specialized capabilities, and companies with proprietary technology) frequently have more leverage than they realize. The following are the areas where we most often see productive negotiation.

Challenging inapplicable clauses

The strongest position is often the simplest: a clause should be removed, or expressly marked as not applicable, when its own conditions are not met. Many flowdowns apply only above certain dollar thresholds, only to non-commercial items, only to cost-type contracts, or only to classified, overseas, construction, or research work. A subcontractor is entitled to ask the prime to identify the basis for including a disputed clause. If the prime cannot, deletion or a written notation of non-applicability is a reasonable request.

Narrowing scope

Even when a clause applies, it can often be limited to the transaction. Common requests include limiting obligations to items furnished under the particular order rather than a company’s entire commercial product line; limiting workforce-related obligations to personnel actually performing the work; limiting security obligations to identified systems, personnel, or classified work; and limiting audit rights to verification of delivery, quantity, and conformance, excluding indirect rates, cost data, and proprietary processes.

Selecting the right version

Many FAR and DFARS clauses come in a basic form and one or more “alternates.” Flowdown schedules sometimes list several alternates for the same clause, creating uncertainty about which obligations govern. The subcontract should identify the single applicable version and state that other alternates do not apply.

Protecting price and payment

Flowdowns should not quietly convert a fixed-price commercial sale into a cost-reimbursement arrangement. Subcontractors should resist cost or pricing data requirements and cost-accounting audit rights where pricing is commercial or fixed, and should negotiate express economic protections for changes (an equitable price adjustment), stop-work periods (a shorter maximum period, recovery of costs, and a right to terminate if the suspension continues), inspection (defined acceptance criteria and notice), and termination (payment for completed items, work in process, and reasonable settlement costs).

Preserving intellectual property and data rights

Technical data and intellectual property flowdowns warrant particular care. The key distinction is between data developed specifically under the government work and a company’s pre-existing technology, software, trade secrets, and manufacturing know-how. Subcontractors should ensure that flowdowns do not grant broader rights than the government needs, that background intellectual property is preserved, that data-delivery obligations are limited to data generated under the order, and that proprietary information is properly marked. A failure to apply required legends can, in some cases, result in the loss of rights a company would otherwise retain.

Considerations for prime contractors

Negotiation is not only a subcontractor concern. Primes benefit from tailored flowdowns as well: an overly broad schedule can slow procurement, deter capable commercial suppliers, and obscure the obligations that truly matter. A well-organized flowdown schedule that clearly identifies mandatory clauses and their triggers is easier to administer and to defend in an audit.

6. Practical Takeaways

• Review clause by clause. Treat a flowdown schedule as a list of individual obligations, not a single block of boilerplate.
• Categorize each clause. Identify whether it is mandatory, suggested, or optional, recognizing that the label alone does not end the analysis.
• Verify the trigger. Check dollar thresholds, commercial product or service status, contract type, place of performance, information involved, and government property.
• Confirm the version. Make sure only the correct basic clause or alternate is incorporated.
• Negotiate scope and economics. Seek deletions, carve-outs, defined notice periods, limited audit and inspection rights, price adjustments, and data-rights protections where appropriate.
• Document the outcome. The final subcontract should state clearly which clauses apply, which do not, and what limitations were agreed, and the company should be prepared to comply with what it accepts.

Experienced counsel adds value at each of these steps. Flowdown review requires familiarity with the regulations, the commercial realities of government supply chains, and the points primes are typically willing to concede. Counsel can help identify which obligations are truly required, frame negotiation requests in terms primes recognize, and build compliance processes that keep pace with changing requirements, such as evolving cybersecurity and supply-chain rules.

Conclusion

Flowdown clauses are where public procurement policy meets private commercial risk. Mandatory flowdowns must be respected, but they should be confirmed and properly scoped; suggested and optional flowdowns are frequently open to negotiation and should be tested against the actual deal. Companies that approach flowdowns deliberately, rather than accepting them wholesale, are better positioned to win and perform government work profitably while managing compliance exposure.

Falcon Rappaport & Berkman regularly advises prime contractors, subcontractors, and suppliers on government contract terms and flowdown negotiations. To discuss how these issues affect your business, contact our corporate attorneys or complete the contact form below.

DISCLAIMER: This summary is not legal advice and does not create any attorney-client relationship. This summary does not provide a definitive legal opinion for any factual situation. Before the firm can provide legal advice or opinion to any person or entity, the specific facts at issue must be reviewed by the firm. Before an attorney-client relationship is formed, the firm must have a signed engagement letter with a client setting forth the Firm’s scope and terms of representation. The information contained herein is based upon the law at the time of publication.