Guides

Guide

SF330 vs SF254 (and SF255): What Changed and What to Use

The SF330 replaced the SF254 and SF255 in 2004. Here's how the old forms map to SF330 Part I and Part II, why they were consolidated, and which form to use today.

Christian Lance

·

Special Advisor

·

8 min read

If you are comparing the SF330 to the SF254 and SF255, the short answer is that the SF330 replaced both older forms. The change took effect June 8, 2004, when the SF330 became mandatory for federal architect-engineer solicitations. The SF254 and SF255 are obsolete - but older templates and some references still mention them, which is why the comparison still comes up.

How the old A-E forms map to the SF330.

Old formWhat it didSF330 equivalent
SF254General firm qualifications questionnairePart II (General Qualifications)
SF255Project-specific qualifications for one contractPart I (Contract-Specific Qualifications)

What the SF254 and SF255 were

The SF254 was a general statement of a firm's qualifications - size, disciplines, and experience - that firms kept on file with agencies. The SF255 was the project-specific submission a firm sent to compete for a particular contract, naming the proposed team and relevant projects. Both were issued in 1975 and changed little over the following decades.

Why they were consolidated

By the early 2000s the A-E industry and federal contracting had changed enough - new technologies, codes, and procurement practices - that the 1975 forms no longer fit. The Federal Acquisition Regulation replaced them with a single consolidated form, the SF330, to modernize and streamline A-E qualifications collection. Part I carries forward the SF255's project-specific role, and Part II carries forward the SF254's general-qualifications role.

Which form to use today

Use the SF330. There is no valid reason to submit an SF254 or SF255 for a current federal A-E pursuit. If a solicitation or template still references the old forms, treat that as shorthand: provide a current SF330 (Part I for the specific contract, Part II for each firm) unless the contracting officer directs otherwise. For a section-by-section breakdown of the current form, see SF330 sections explained.

The origins of the A-E qualifications forms

To understand the SF330 it helps to know where the older forms came from. The Brooks Act of 1972 required federal agencies to select architecture and engineering firms on qualifications rather than price. Agencies needed a consistent way to collect those qualifications, and in 1975 the government issued two standard forms to do it: the SF254 and the SF255. For roughly three decades, those two forms were how nearly every federal A-E pursuit was submitted and evaluated.

What the SF254 collected

The SF254 was the general qualifications questionnaire. A firm completed it once to describe itself - disciplines and staff counts, year established, ownership, annual revenue range, and a profile of representative experience - and kept it on file with the agencies it wanted to work for. It was not tied to any single contract; it was the firm's standing statement of who it was and what it could do. That is exactly the role SF330 Part II plays today.

What the SF255 collected

The SF255 was the project-specific submission. When a firm wanted to compete for a particular contract, it filled out an SF255 naming the proposed team, the key personnel, the relevant example projects, and how the team fit that specific work. It was rebuilt for every pursuit. That is the role SF330 Part I plays today, now expanded across Sections A through I with a dedicated resume section (E), example-projects section (F), and personnel-to-project matrix (G).

What changed in the move to the SF330

The 2004 consolidation did more than staple the two forms together. It modernized the structure to reflect how A-E firms and federal contracting had evolved since 1975:

  • One consolidated form instead of two separate questionnaires to maintain and cross-reference
  • A clearer separation of contract-specific content (Part I) from reusable firm content (Part II)
  • A dedicated Section G matrix making the link between proposed people and example projects explicit
  • An 'additional information' narrative (Section H) for criteria the structured sections do not capture
  • A format better suited to electronic preparation and submission

If you find an old SF254 or SF255 template

Firms occasionally still have SF254/SF255 templates in their proposal archives, and older agency documents sometimes reference the retired form numbers out of habit. Treat any such reference as shorthand for 'current qualifications': provide an SF330 Part II where an SF254 is mentioned, and an SF330 Part I where an SF255 is mentioned. If a solicitation genuinely appears to require the obsolete forms, ask the contracting officer rather than submitting a decades-old format.

A quick way to remember the mapping

If you learned proposals on the old forms, the mnemonic is simple: the SF254 was the firm's general record and the SF255 was the specific project submission. The '254' became Part II (general qualifications) and the '255' became Part I (contract-specific). Everything you knew about the SF255 - the proposed team, key personnel, and relevant projects - now lives in Part I's Sections C through H.

What did not change

The underlying logic is identical to 1975: federal A-E work is still selected on qualifications rather than price, under the Brooks Act, and firms still compete by demonstrating relevant experience and the right people. The SF330 modernized the format and added structure like the Section G matrix, but the qualifications-first principle and the kinds of evidence that win have not changed. If you understood why the old forms existed, you already understand the SF330.

Don't confuse the SF330 with other standard forms

The SF330 is specifically the Architect-Engineer Qualifications form. It is not a bid form, a pricing schedule, or a general commercial solicitation form like the SF1449 - it exists only to collect A-E qualifications so an evaluation board can rank firms. When a solicitation references several standard forms, keep the SF330's narrow purpose in mind: it carries your team and experience, not your price.

Migrating old proposal content to the SF330

Firms with archives of SF254 and SF255 material can still mine them - past project descriptions, staff resumes, and firm data all map into the SF330's structure. Treat the migration as a chance to refresh rather than a copy-paste: update project outcomes, re-point each project's relevance to the work types you pursue now, and drop projects that no longer demonstrate the experience you want to feature. Old content is a starting point, not a finished Part I.

The bottom line

If you take one thing away: the SF330 is the current, consolidated form, and the SF254 and SF255 are historical. Any comparison between them is really a question about the SF330's own two parts - Part II (general firm qualifications, formerly the SF254) and Part I (contract-specific, formerly the SF255). Learn the SF330 well and the old forms become a footnote you only need when clearing out an archive.

Keep Part II current

The old SF254 lives on as SF330 Part II - a reusable firm record agencies encourage you to update annually. Flodoc keeps your firm's staff and project data structured so each Part II and Part I starts from current, criteria-ready content.

FAQ

Frequently asked questions

About the author

Christian Lance

Christian Lance is a Special Advisor at Flodoc, focused on AEC proposal workflows, qualifications-based selection, and how engineering firms assemble SOQs and SF330-style packages under real RFQ deadlines. He authors Flodoc's public guides on municipal SOQs, government RFPs, and compliance discipline.

See Flodoc on your next pursuit

Upload an RFP and watch Flodoc match the right people and past work to every requirement.

No spam. No commitment.