Government forms · Legal background
The law behind the SF330: why the form works the way it does
Every quirk of the SF330 — why price appears nowhere on it, why the signature attests that information is "current and factual," why the same experience shows up in three different sections — traces back to one statute and one FAR subpart. Understanding them is the difference between filling out the form and competing on it. This companion to our SF330 practical guide covers the legal framework and the mistakes that protest decisions punish most often.
The Brooks Act: selection without price
The SF330 exists because of the Brooks Act of 1972, codified at 40 U.S.C. §§ 1101–1104. It commits the federal government to qualifications-based selection (QBS) for architect-engineer services: agencies publicly announce every A/E requirement, evaluate firms solely on demonstrated competence and qualifications, rank at least three of the most highly qualified, and only then negotiate a fair and reasonable price with the top-ranked firm. If negotiations fail, the agency formally terminates them and moves to the next firm on the list.
That structure has consequences an SF330 author feels directly:
- Price competition never enters the selection. Your SF330 is not a proposal — courts describe it as a capability statement. There is no price volume to fall back on; the qualifications narrative carries the entire competition.
- "Firm" is a legal term. The Act defines an eligible firm as a legal entity permitted by law to practice architecture or engineering. In Accura Engineering & Consulting Services, Inc. v. United States (Court of Federal Claims, 2023), an award was overturned because the prime relied on a subcontractor's license — the court held the prime must itself hold the required licensure. A teaming arrangement doesn't create a licensed entity; a joint venture can.
- The QBS rule follows the work. Task orders for A/E services under IDIQ vehicles are also qualification-based selections under the same framework — agencies can't convert them into price shootouts.
FAR Subpart 36.6: the machinery
The Brooks Act is implemented by FAR Subpart 36.6, and the SF330 itself is prescribed by FAR 53.236-2 (current edition: Rev. 7/2021) and mandated by FAR 36.702. The pieces worth knowing:
| Provision | What it requires | Why you care |
|---|---|---|
| FAR 36.602-1 | The evaluation criteria: (1) professional qualifications; (2) specialized experience and technical competence; (3) capacity to perform in the required time; (4) past performance on cost control, quality, and schedule; (5) location/knowledge of the locality; (6) other criteria the synopsis adds. | This list, plus whatever the synopsis adds, is the whole scoring universe. Organize Section H (and really the whole Part I) around the announced criteria, in their announced order of importance. |
| FAR 36.602-2/-3 | A qualified evaluation board reviews submissions, evaluates against the criteria, holds discussions with at least three of the most highly qualified firms, and writes a documented selection report. | Real professionals read the form, and the discussion stage exists by statute — write for a technical reader who may soon interview you. |
| FAR 36.603 | Part II (General Qualifications) is filed with agency offices; agencies review files at least annually, encourage annual Part II updates, and discard material not updated within three years. | An annual Part II refresh isn't optional hygiene — a stale Part II can age out of the agency's files entirely. |
| FAR 36.606 | Negotiations start with the most preferred firm; the extent of subcontracting is a key negotiation topic, and subcontracting is limited to firms agreed upon in negotiations. | The team you name in Sections C–D is a commitment, not decoration. Changing named subconsultants later requires contracting-officer approval. |
What protest decisions teach SF330 authors
Disappointed firms can protest A/E selections to the Government Accountability Office (GAO) or the Court of Federal Claims. Both apply a deferential standard — they won't re-score your form — but the decided cases map the failure modes with unusual precision. Six lessons recur:
1. Every claim must be current and factual — the signature says so
Block 31's signature "attests that the information provided is current and factual." That language has teeth. GAO has repeatedly upheld agencies that terminated negotiations with the top-ranked firm after discovering inflated qualifications — a firm that counted part-time and could-be-hired individuals in its staff totals (Paul F. Pugh, 1980), and a firm claiming 21 employees that actually had one, the sole proprietor (Vertrans Design Associates, 1991). Winning the ranking with inaccurate data isn't winning anything.
2. Part I must be current as of this submission
GAO's Mounts Engineering decision (1985) drew the line that still governs: the general form (now Part II) is refreshed annually, but the contract-specific form (Part I) must be accurate as of the particular project. Copying last year's Part I forward — old staff counts, departed key personnel, stale workload — is a misrepresentation risk, not a shortcut.
3. Bare-bones submissions rate bare-bones scores
In Electronic Interiors (2011), GAO upheld low ratings where a firm repeated the same generic sentences for each key person and never said what work was actually done. The burden is on the firm to submit a well-written capability statement detailed enough for meaningful review. Generic prose isn't a style problem; it's scored as an experience deficit.
4. Watch what your capacity statements imply
In HydroGeoLogic (2008), a firm wrote that it would be at 50% capacity in six months and 80% in twelve — and GAO upheld the agency's weakness finding on the capacity criterion. Statements about workload and availability are read literally, at the moment of contract inception.
5. Key personnel must be real
In OLBN Architectural Service (2010), GAO upheld the downgrading of a firm whose three named architects had never worked for it — the firm planned to hire them after award. Section E resumes carry the evaluation; contingent people carry contingent credibility. And under Evergreen JV (2020), agencies must evaluate qualitatively — the years-with-current-firm block (14b), license depth, and the Section G matrix get compared across offerors, not just checked for presence.
6. If you protest, the clock is 10 days — and debriefings don't extend it
Because a Brooks Act selection is not a "competitive proposal" procurement, GAO's debriefing exception does not apply: a protest must be filed within 10 days of when the firm knew or should have known its basis (McKissack-URS Partners, 2012; Battelle Memorial Institute, 2022). Firms that wait for a post-award debriefing routinely lose on timeliness without any review of the merits.
The quiet asymmetry worth remembering
Agencies get deference on judgment but not on process: protests succeed when an evaluation applied criteria the synopsis never stated (Risk Analysis and Mitigation Partners, 2014), mechanically counted experience instances instead of assessing them (Evergreen JV), skipped the required discussions (Mounts), or left no documentation of its reasoning (Wadell Engineering, 1980). For the firm, the practical inverse holds: write to the stated criteria, in their stated weighting, with specific verifiable facts — because that is the exact record a review would examine.
Scope note: this page summarizes public statutes, regulations, and protest decisions for background; it is not legal advice, and agency supplements (like the DFARS provisions that apply to Department of Defense work) add requirements beyond the baseline described here. Verify against the current text at acquisition.gov and your solicitation's own instructions — the synopsis always controls. For the form's mechanics — sections, blocks, and managing it in Word — see the practical SF330 guide.