By Raees Rasool
Requirement shaping in government contracting is legal until you draft the work statement or take information no competitor gets. Here is the FAR line. Shaping a federal requirement is mostly legal advocacy. The FAR draws two hard lines: who holds the pen on the work statement, and who holds information nobody else has. Requirement Shaping In Government Contracting Requirement shaping in government contracting is legal far more often than contractors assume. The line does not sit at how hard you push. It sits at two questions. Did you take a role the rules reserve for the government? Did you take information nobody else can have? Advocacy is open. You may tell a program office what good looks like, publish your technical view, and answer every market research notice. Three moves break the rules. Drafting the work statement you intend to bid, holding a document no competitor gets, and touching another firm's proposal information. Everything short of that is competition. What Shaping Actually Means Shaping means educating a buyer before the requirement hardens. The agency runs market research under FAR Part 10 and holds early exchanges under FAR Subpart 15.2. FAR 15.201(c) (https://www.ecfr.gov/current/title-48/chapter-1/subchapter-C/part-15/subpart-15.2/section-15.201) encourages agencies to "promote early exchanges of information about future acquisitions." Two conditions keep that legal. The government keeps the pen. The exchange leaves a record anyone can read. Lose either condition and the same conversation becomes a problem. A phone call that never reaches the contracting officer leaves no record. A marked-up work statement you send as a file leaves the pen in your hand. ! Three exceptions that let a contractor who helped prepare a work statement still supply the work: sole source, did the design work, or other firms helped too (https://mhhifytmrlyksfrjacvi.supabase.co/storage/v1/object/public/blog-images/2026/10/requirement-shaping-government-contracting-figure.png) Miss all three exceptions and the firm that shaped the requirement cannot supply the resulting work. The Work Statement Trap Here is the rule most teams never read. FAR 9.505-2(b)(1) (https://www.ecfr.gov/current/title-48/chapter-1/subchapter-B/part-9/subpart-9.5) says a contractor that "prepares, or assists in preparing, a work statement" generally cannot supply what the agency then buys. The contractor "may not supply the system, major components of the system, or the services" acquired on that basis. Three exceptions open the door again. The firm is the sole source. The firm participated in the development and design work. More than one contractor helped prepare the work statement. The parallel rule bites harder on products. Under FAR 9.505-2(a)(1), a contractor that prepares complete specifications fo
Shaping a federal requirement is mostly legal advocacy. The FAR draws two hard lines: who holds the pen on the work statement, and who holds information nobody else has.
Requirement Shaping In Government Contracting Requirement shaping in government contracting is legal far more often than contractors assume. The line does not sit at how hard you push. It sits at two questions. Did you take a role the rules reserve for the government? Did you take information nobody else can have? Advocacy is open. You may tell a program office what good looks like, publish your technical view, and answer every market research notice. Three moves break the rules. Drafting the work statement you intend to bid, holding a document no competitor gets, and touching another firm's proposal information. Everything short of that is competition. What Shaping Actually Means Shaping means educating a buyer before the requirement hardens. The agency runs market research under FAR Part 10 and holds early exchanges under FAR Subpart 15.2. FAR 15.201(c) (https://www.ecfr.gov/current/title-48/chapter-1/subchapter-C/part-15/subpart-15.2/section-15.201) encourages agencies to "promote early exchanges of information about future acquisitions." Two conditions keep that legal. The government keeps the pen. The exchange leaves a record anyone can read. Lose either condition and the same conversation becomes a problem. A phone call that never reaches the contracting officer leaves no record. A marked-up work statement you send as a file leaves the pen in your hand. ! Three exceptions that let a contractor who helped prepare a work statement still supply the work: sole source, did the design work, or other firms helped too (https://mhhifytmrlyksfrjacvi.supabase.co/storage/v1/object/public/blog-images/2026/10/requirement-shaping-government-contracting-figure.png) Miss all three exceptions and the firm that shaped the requirement cannot supply the resulting work. The Work Statement Trap Here is the rule most teams never read. FAR 9.505-2(b)(1) (https://www.ecfr.gov/current/title-48/chapter-1/subchapter-B/part-9/subpart-9.5) says a contractor that "prepares, or assists in preparing, a work statement" generally cannot supply what the agency then buys. The contractor "may not supply the system, major components of the system, or the services" acquired on that basis. Three exceptions open the door again. The firm is the sole source. The firm participated in the development and design work. More than one contractor helped prepare the work statement. The parallel rule bites harder on products. Under FAR 9.505-2(a)(1), a contractor that prepares complete specifications fo