Federal Construction Bidding: A Working Guide for U.S. General Contractors

The U.S. federal government is the largest single buyer of construction in the country, and it does that buying through a comparatively small number of agencies that each run their own procurement shops. Most of the construction dollars flow through five places. The General Services Administration owns and operates federal civilian buildings, which means GSA procures most courthouse work, federal office building work, and a significant share of border-station and land-port construction. The U.S. Army Corps of Engineers runs civil works (locks, dams, levees, navigation projects) alongside military construction for the Army and the Air Force. Naval Facilities Engineering Systems Command, NAVFAC, handles construction for the Navy and the Marine Corps and is one of the larger design-build customers in the federal portfolio. The Department of Veterans Affairs procures construction across the VA hospital system. The Department of Transportation operating administrations, principally FHWA and FAA, procure construction directly and pass federal money through to state DOTs for highway and airport work.

A handful of other agencies move enough volume to matter. The Department of Energy procures heavy industrial construction at its national labs and at sites like Hanford and Oak Ridge. The National Park Service procures construction across the park system through the Denver Service Center. The Bureau of Reclamation procures water-resource construction in the western states. The U.S. Postal Service procures construction on its facility portfolio. None of these agencies are huge buyers individually, but each runs a steady program and each has its own procurement culture.

Why the agency matters more than the project

The thing contractors who do federal work for a living understand is that the agency shapes the procurement at least as much as the project shapes it. Two airfield-paving projects of similar size can look completely different depending on whether they are procured through USACE, NAVFAC, or the FAA. The contracting officer culture is different. The technical requirements are different. The forms are different. The way addenda flow, the way questions get answered, and the way the post-award contract administration runs are all different. A contractor whose recent federal work has been with one agency cannot assume the next one runs the same way.

The other thing worth understanding up front is that federal construction is a documentation-heavy environment relative to private and most state-and-local public work. The bid response is longer. The compliance load is heavier. The post-award reporting is more involved. None of that is unmanageable, but it is the reason firms that do federal work successfully tend to develop dedicated federal-bid practices rather than treating federal work as an extension of their commercial bid pipeline.

SAM.gov is the primary publication channel

Federal procurement above the simplified acquisition threshold is required to be posted on SAM.gov, the System for Award Management run by GSA. This includes the synopsis of the procurement, the full solicitation documents on most procurements, the addenda issued during the bid period, and the award notice after the contract is executed. Contractors looking for federal construction work start at SAM.gov.

SAM.gov filtering for construction work runs primarily on NAICS code. The 236 series covers construction of buildings (236210 industrial, 236220 commercial and institutional). The 237 series covers heavy and civil engineering construction (237110 water and sewer, 237310 highway and street, 237990 other heavy and civil). The 238 series covers specialty trade contractors. NAICS code is the structural filter, and a contractor whose work spans multiple codes has to track multiple feeds.

SAM.gov has a search interface that works, an export function that mostly works, and an API that works for contractors who want to build their own pipeline. The search interface is the right starting point for contractors new to federal work. The API becomes useful once a firm is bidding federal work consistently and wants to filter by geography, dollar value, agency, and solicitation type at the same time without paging through SAM.gov screens.

Agency portals are the secondary source

Most agencies that procure construction at scale also publish their solicitations on their own portals, sometimes with additional context that does not appear on SAM.gov. The Corps of Engineers publishes through a combination of SAM.gov and district-level publication. NAVFAC publishes through its own contracting opportunity pages alongside SAM.gov. GSA publishes most opportunities on SAM.gov but the regional offices sometimes carry context useful for the bid. The VA publishes through SAM.gov and through VA-specific contracting pages. DOT publishes through SAM.gov and through agency-level pages where the operating administrations call out priority programs.

The practical implication is that a contractor working a particular agency lane cannot rely on SAM.gov alone. The agency-level pages carry the program-specific context that explains what the agency is actually trying to buy this year, which procurements are part of larger programs, and which contracting officers are running which work. None of that shows up clean on a SAM.gov filter.

DOT-funded work runs through state DOTs

A large share of federal-funded construction is the federal-aid highway program, which is administered by FHWA but procured by state DOTs against a federal funding stream. The procurement happens at the state level through state DOT bid systems, and the federal requirements (Davis-Bacon, Buy American, DBE participation, FHWA design standards) flow through the state’s solicitation. Contractors working federal-aid highway are looking at state DOT bid calendars rather than SAM.gov for most of the work.

The Federal Acquisition Regulation, codified at 48 CFR Chapter 1 and published at acquisition.gov, is the rulebook for federal procurement. It runs to several thousand pages and applies to every executive-branch agency, with agency-specific supplements (DFARS for DoD, AFARS for Army, NMCARS for Navy, EFARS for the Corps of Engineers, GSAR for GSA, VAAR for VA) layered on top. Contractors are not expected to memorize the FAR. Contractors are expected to recognize the parts that flow into their solicitations and respond to them correctly.

FAR Part 36 covers construction

FAR Part 36, Construction and Architect-Engineer Contracts, is the part most relevant to bidding GCs. It covers construction-specific contract clauses, payment provisions, performance and payment bond requirements, and the Brooks Act selection process for architect-engineer services. Part 36.6 specifically governs A-E selection and is the part that drives the SF-330 qualifications submission used on federal A-E procurement and on the design side of design-build.

FAR Part 19 covers small business

FAR Part 19 covers small business programs and the set-aside framework. It defines the size standards by NAICS code, the rules around 8(a) and HUBZone and SDVOSB and WOSB set-asides, and the contractor representations required at proposal submission. A contractor’s size status, set-aside eligibility, and subcontracting plan obligations all trace back to FAR Part 19.

FAR Part 22 covers labor

FAR Part 22 covers labor-related provisions including Davis-Bacon prevailing wage, the Service Contract Act (rarely relevant to construction), Equal Employment Opportunity, affirmative action programs, and the various reporting obligations contractors carry on federal work. The Davis-Bacon clauses at FAR 22.4 are the ones a federal-construction contractor sees most frequently.

FAR Part 25 covers Buy American

FAR Part 25 covers Buy American Act compliance and the related foreign-acquisition restrictions. The Buy American Act requires that domestic construction materials be used on federal construction unless a specific waiver applies, and the rules around what counts as domestic, what counts as a covered material, and what waivers are available are mechanical and worth understanding before pricing the bid.

Other FAR parts surface depending on the procurement. FAR Part 15 covers contracting by negotiation, which is the procedural framework for most RFP-style construction procurements. FAR Part 14 covers sealed bidding, which is the framework for ITB-style procurements. FAR Part 12 covers commercial item acquisition, occasionally relevant on small construction work. FAR Part 52 contains the contract clauses that get incorporated into the solicitation, and a federal solicitation typically includes a long list of FAR Part 52 clauses by reference.

A meaningful share of federal construction is set aside for specific business categories. The contractor’s size and certification status determine which procurements are open to the firm and on what basis. The categories that matter most on federal construction are small business (under the SBA size standard for the relevant NAICS code), 8(a) (the SBA Business Development Program for socially and economically disadvantaged firms), HUBZone (firms in Historically Underutilized Business Zones), Service-Disabled Veteran-Owned Small Business, and Women-Owned Small Business with the Economically Disadvantaged WOSB subset.

Size standards run by NAICS code

SBA publishes size standards by NAICS code in 13 CFR Part 121. For most construction codes the size standard is a revenue ceiling (in the $39 million to $45 million range for most building construction codes as of recent revisions, with periodic adjustments). A firm above the size standard for the procurement’s NAICS code is not eligible to bid as a small business on that procurement. A firm at the borderline has to track the size calculation method, which uses three-year average annual receipts, and the rules around affiliates and joint ventures.

Set-aside type drives the procurement pool

When an agency sets aside a procurement for a specific category, only firms in that category can submit. An 8(a) set-aside accepts only 8(a)-certified firms. A SDVOSB set-aside accepts only SDVOSB-certified firms. A HUBZone set-aside accepts only HUBZone-certified firms. The set-aside type appears in the solicitation synopsis and on the SAM.gov record. A contractor checking solicitations has to filter on set-aside type alongside NAICS and geography to avoid bidding work the firm is not eligible for.

Some procurements are full-and-open (any qualified firm can bid). Some are small-business set-asides (any small business under the NAICS size standard). Some are full-and-open with a small-business goal at the prime or subcontract level. Some are sole-source awards under specific authorities. The contractor’s eligibility and competitive position depend on which type the solicitation is.

Certification verification matters

Each set-aside category has its own certification process and its own verification requirement. SAM.gov shows representations the contractor has made about the firm’s status, but agencies generally verify status against the relevant program’s certification database before award. SBA runs the 8(a), HUBZone, and WOSB certifications. SDVOSB certification runs through SBA’s verification process. A firm representing itself as eligible without holding the underlying certification at the time of bid is exposed to size protests and to award reversal.

Federal procurement requires a specific set of registrations before a contractor can submit a bid. The list is finite and the registrations are not difficult, but missing any of them at submission disqualifies the bid. Worth doing well in advance of any active procurement.

SAM.gov registration

Active registration at SAM.gov is required for any entity that wants to do business with the federal government. Registration is free, runs through sam.gov directly, and includes the firm’s business information, NAICS codes, certifications, and representations and certifications (the reps-and-certs). Registration has to be renewed annually. A lapsed SAM.gov registration is one of the more common reasons a federal bid gets rejected at submission.

UEI replaces DUNS

The Unique Entity Identifier (UEI) replaced the DUNS number as the federal entity identifier in 2022. UEI is assigned through SAM.gov registration. A contractor with an old DUNS number from previous work has been transitioned to a UEI; a new contractor gets a UEI through the SAM.gov registration process directly.

CAGE code

The Commercial and Government Entity (CAGE) code is a five-character identifier assigned by the Defense Logistics Agency to entities that do business with the federal government. CAGE is assigned automatically through SAM.gov registration in most cases. Some federal contracts require a CAGE code at bid; SAM.gov registration handles this without the contractor needing to do anything separately.

NAICS code selection

The contractor’s primary NAICS code on SAM.gov is one factor in eligibility for set-asides and in the size determination. A contractor whose work spans multiple codes (for example, a GC that does both commercial buildings and heavy civil) registers under multiple NAICS codes on SAM.gov and has to track size status under each. The size standard for the specific procurement is the one that controls eligibility.

Certification under specific programs

Set-aside eligibility requires actual certification in the relevant program. 8(a) certification runs through SBA. HUBZone certification runs through SBA. SDVOSB verification runs through SBA. WOSB and EDWOSB run through SBA’s third-party certifier network or SBA self-certification depending on the procurement type. State DBE certification runs through state DOTs under the Unified Certification Program. Each certification has its own application process, processing time, and renewal cycle.

Federal solicitations specify how the bid response is submitted, and the method varies by agency, by procurement type, and increasingly by the year. Most agencies are moving toward electronic submission. Some still use paper. Most large procurements use a hybrid where the technical proposal is submitted electronically and the priced bid form is submitted on paper or through a separate channel.

Electronic submission portals

SAM.gov supports electronic bid submission for some procurements. Many agencies use their own portals: PIEE (Procurement Integrated Enterprise Environment, used widely across DoD), NECO (Navy Electronic Commerce Online for NAVFAC work), and various GSA, VA, and USACE-specific systems. Each portal has its own login, its own file-format constraints, its own size limits, and its own cutoff handling. The solicitation specifies which portal to use and any portal-specific requirements.

Paper submission still happens

Sealed-bid construction procurements (FAR Part 14) sometimes still use paper submission with a specified delivery time and a specified delivery location. The bid envelope is opened publicly at the time stated in the solicitation, and bids that arrive late are rejected without consideration. The strict-time-of-receipt rule on federal sealed bids has produced more lost bids than most contractors would expect. Paper submissions need couriered delivery with documented delivery time.

Page limits and formatting

Federal RFPs typically impose page limits on the technical proposal, formatting rules (font size, margins, line spacing), and section ordering. The page limit is firm. A 50-page narrative submitted into a 40-page limit will often be evaluated only on the first 40 pages, with the remainder discarded; some agencies reject the submission outright. The formatting rules are checked, and a non-conforming submission can be rejected before substantive evaluation begins.

Addenda handling

Federal solicitations are routinely amended during the bid period. The amendments (called amendments on FAR procurements; some agencies still use the term addenda) appear on SAM.gov and on the agency portal. Each amendment has to be acknowledged in the bid response, usually through a signed acknowledgment on the bid form itself. Failing to acknowledge an amendment can void the bid. Amendments also routinely modify the solicitation requirements, the technical specifications, the bid form, or the deadline. Each amendment has to flow through the contractor’s compliance matrix and the proposal narrative before submission.

Pre-bid meetings

Many federal construction solicitations include a pre-bid meeting (sometimes called a pre-proposal conference). Some are mandatory, meaning the contractor has to attend or be disqualified. Some are discretionary. The solicitation specifies which. Mandatory pre-bid meetings on federal construction are not negotiable, and a contractor that misses a mandatory pre-bid for any reason is out of the procurement.

A bid protest is a formal challenge to a federal procurement, filed by an interested party (typically an unsuccessful bidder, or sometimes a prospective bidder objecting to the terms of the solicitation). Protests can be filed at the agency level, at the Government Accountability Office, or at the U.S. Court of Federal Claims, with different rules and timelines at each.

Where to file

Agency-level protests go to the contracting officer or the agency’s protest authority and are governed by FAR Part 33.103 and the agency’s supplements. They are faster and cheaper than GAO protests but produce decisions that are sometimes less rigorous. GAO protests are governed by the Competition in Contracting Act and 4 CFR Part 21. GAO is the most common forum for federal-construction protests; the procedural rules are well-established and the decisions are reasoned. Court of Federal Claims protests are the most expensive and most formal forum and are usually reserved for protests where the stakes are high enough to warrant the cost.

Timelines are short

Protest deadlines are short and strict. A protest of solicitation terms (a pre-award protest) generally has to be filed before bid opening on a sealed bid or before the proposal due date on a negotiated procurement. A protest of an award (a post-award protest) generally has to be filed within 10 days of the date the protester knew or should have known the basis for the protest. Missing the deadline is fatal. The 10-day window is calendar days, not business days, and the trigger is typically the agency’s debriefing or the post-award notice.

Automatic stay

A timely GAO protest filed within the protest stay window triggers an automatic stay of contract performance under the CICA stay provisions. The stay can be overridden by the agency in some circumstances, but the default is that performance pauses until the protest is decided. This matters both for protesters (who want the stay) and for awardees (who do not).

When to use protests

Bid protests are not a routine response to losing a bid. They are a tool with specific use cases: when the contractor has a real basis to believe the procurement was conducted improperly, when the loss is large enough that the protest cost is justified, or when the contractor needs to preserve a position on future procurements. A protest filed without a strong basis damages the contractor’s relationship with the agency and rarely produces a useful outcome. Most contractors who file protests successfully have done their work in advance: they have read the agency’s evaluation, they know what went wrong, and they have legal counsel familiar with GAO procedure before they file.

Federal construction carries a stack of compliance obligations that flow into the solicitation through specific FAR clauses and agency-specific supplements. The compliance considerations affect pricing during the bid and execution after award. Contractors who do federal work consistently price these in; contractors new to federal work routinely underestimate them.

Davis-Bacon prevailing wage

The Davis-Bacon Act (40 U.S.C. §§ 3141-3148) requires federal-construction contractors to pay laborers and mechanics no less than the locally prevailing wages and fringe benefits, as determined by the Department of Labor for each labor classification and geographic area. The wage determination is attached to the solicitation. Contractors price labor against the determination, classify workers correctly during execution, and file weekly certified payrolls on Form WH-347. Davis-Bacon flows down to subcontractors at every tier, and the prime contractor is responsible for sub compliance.

Buy American and domestic preference

The Buy American Act (41 U.S.C. Chapter 83) requires that domestic construction materials be used on federal construction unless a waiver applies. The thresholds for what counts as domestic, what waivers are available (commercially-available-off-the-shelf, public interest, unreasonable cost), and how compliance is documented are spelled out in FAR Part 25 and have been adjusted in recent rulemakings. Contractors price Buy American compliance into the bid and document compliance during execution. The Build America, Buy America Act (BABA) extends similar requirements to federally-funded infrastructure beyond direct federal procurement.

DBE participation on DOT-funded work

Federal-aid highway and federal-aid transit projects carry DBE participation requirements under 49 CFR Part 26. The participation goal appears in the solicitation, the bidder commits to a level of certified-firm participation, and good-faith effort documentation is required if the goal is not met. State DOTs administer the program at the project level, and the certification recognized is the state’s UCP-certified DBE list.

Section 3 on HUD-funded work

HUD-funded construction (CDBG, HOME, public housing) carries Section 3 requirements under 24 CFR Part 75. Section 3 obligates contractors to direct economic opportunities (employment, training, contracting) to low-income residents and Section 3 business concerns. The compliance plan is part of the bid response and the reporting continues through project execution.

Other compliance areas

Other compliance obligations surface depending on the procurement: cybersecurity requirements under DFARS 252.204-7012 on DoD work that handles controlled unclassified information, accessibility requirements under the Architectural Barriers Act on federal buildings, environmental requirements under NEPA for the project’s environmental review, and procurement integrity provisions that govern contractor employee gift-giving, hiring of former government employees, and confidential procurement information. Each of these has compliance cost and documentation cost that flows into the bid.

Federal procurement rejects more bids on procedural grounds than most state and private work does. The grounds are usually mechanical, and the loss is usually preventable. The patterns repeat across agencies and across solicitation types, which means a contractor working federal work consistently can build the avoidance discipline into the bid pipeline.

Lapsed registrations

SAM.gov registration that expired during the bid period. UEI that was not migrated when DUNS was retired. A representation on SAM.gov that does not match the certification status the contractor is claiming on the bid. Each of these stops a bid at the door, and each is something the contractor could have caught at the start of the bid window with five minutes on SAM.gov.

Missing or unsigned amendment acknowledgments

An amendment was issued during the bid period, the bid form has a line for acknowledging amendments, and the contractor either missed the amendment entirely or filed the bid without signing the acknowledgment. The bid is non-responsive. The contracting officer has limited discretion to overlook this on a competitive procurement.

Page-limit violations

The technical narrative ran long, the contractor submitted the full document, and the agency evaluated only the first N pages. Sometimes the agency rejects outright. Either way, the technical content the contractor needed evaluated did not get evaluated, and the bid scored lower than it should have.

Bond non-conformance

A bid bond from a surety not on the Treasury’s Listing of Approved Sureties (the T-Listing) on a federal procurement. A bid bond at the wrong percentage. A bid bond on a non-conforming form. Each of these voids the bid. A contractor whose surety relationship is in good order does not run into this; a contractor scrambling to put together a bid bond at the last minute does.

Late submission

The bid arrived after the time stated in the solicitation. On federal sealed bids the rule is strict: bids received after the time of receipt are rejected without consideration unless very narrow exceptions apply. Couriered submission with documented delivery time is the standard practice for paper bids. Electronic submission with submission timestamps in the contractor’s possession is the standard practice for portal bids.

Signature problems

The bid was not signed by an authorized representative. The signature was wet-ink where electronic was required, or vice versa. The corporate seal was missing where required. The notarization was missing where required. The bid form’s signature block had a different name from the SAM.gov authorized representative. Each of these can void the bid depending on the agency and the procurement type.

Compliance matrix gaps

A solicitation requirement was not addressed in the proposal. The compliance matrix did not catch it during the contractor’s pre-submission review. The agency caught it during evaluation. The bid scored lower than the price would have suggested, or the bid was found non-responsive on the missed requirement. This is the failure mode that sits closest to the documentation discipline the contractor’s bid team controls directly.

The structural challenge of federal construction bidding for a mid-market GC is that the documentation load is heavier than commercial work, the bid windows are not always longer to compensate, and the firm’s preconstruction department is usually staffed for commercial bid volume. A federal RFP that lands on Monday with a Friday-of-next-week deadline is two weeks of documentation effort compressed into the same calendar window the firm uses for a commercial bid response of half the size.

Firms that do federal work successfully tend to handle this in one of three ways. Some staff a dedicated federal-bid practice with estimators and proposal writers who only work federal procurement and have built their familiarity with the FAR clauses, the agency-specific quirks, and the documentation patterns. Some maintain a tight library of federal-bid templates (proposal narrative scaffolding, compliance matrix templates by agency, action checklist templates by agency) that compress the documentation work without compressing the substantive review. Some outsource the documentation production to a service that produces the package and hands it back to the firm’s preconstruction team for the substantive decisions.

Whichever approach a firm takes, the documentation discipline is what determines whether the federal-bid pipeline scales. A firm running federal bids on the same workflow as commercial bids hits a capacity wall quickly: the estimators end up spending the bid window on documentation work and have less time on pricing strategy, sub selection, and competitive positioning. The pricing suffers. The win rate suffers. The firm starts declining federal opportunities it could have priced well, because the bandwidth is not there.

The ScalaBid Submission Packageexists in this gap. On a federal procurement, the package returns the proposal narrative scaffolded against the agency’s evaluation factors, the compliance matrix mapped to the FAR clauses and the agency supplements that flowed into the solicitation, the indexed drawing set, and the action checklist of the contractor-supplied items (bonds, certifications, signatures, registrations, the SF-330s if the team includes A-E partners) that have to land before submission. The contractor’s preconstruction team works the substantive decisions on a documentation foundation that is already built, rather than on a documentation foundation the team is building from scratch in parallel with the pricing work.

That is the framing on the federal side. The same logic applies to state and municipal public-works bidding, to private institutional work with formal solicitation processes, and to design-build procurement on any of the above. The difference on federal work is the volume and specificity of the compliance load, which is also the reason federal work rewards firms that get the documentation discipline right.