Letter of Intent in Construction Bidding

In the participation-program context, a Letter of Intent is a structured document signed by both the prime contractor and a certified firm that documents the certified firm’s commitment to perform a specific scope of work at a specific dollar value if the prime is awarded the contract. The LOI is the unit of evidence the bidder submits to support the schedule of participation, which aggregates the LOIs into the bidder’s overall participation commitment.

The LOI is not a subcontract. The full subcontract is negotiated and executed after award. The LOI is also not merely a quote: a quote is a price submitted by a bidder, while the LOI is a mutual commitment signed by both parties. And the LOI is not informal. It is the binding commitment the agency relies on when evaluating the participation count.

The mechanical effect of the LOI is significant. If the bidder is awarded the contract, the certified firms named in the LOIs become contractually committed participants. Substituting them out, removing them from the project, or running scope to them at materially different values than the LOI specified all trigger compliance review and may require formal substitution approval from the agency.

The specific format varies by agency. Some agencies provide a mandatory LOI form that must be used. Others accept the bidder’s own format as long as the required content is present. The required content is broadly consistent across programs, with regulation-specific variation.

Identification of both firms

The prime contractor’s legal name, address, and contact information. The certified firm’s legal name, address, contact information, and a clear statement of the certifying body and certification number. The certifying body and certification number are the verification anchor: a reviewer reading the LOI uses the certification number to confirm the firm is currently certified in the relevant program.

The project

The project name and any agency-assigned project or solicitation number, the bid date, and a brief project description. This anchors the LOI to a specific procurement so that the document cannot be reused on different bids or applied to different scopes than the one it was signed for.

Scope of work

A specific description of the scope of work the certified firm will perform. The scope description has to be substantive: trade categories, specific work items, references to the relevant specification sections or scope packages where applicable. A vague scope description (“general construction support” or “various trades”) does not let the reviewer assess whether the certified firm is performing a commercially useful function or whether the scope is realistic for the firm’s capabilities.

Dollar value

The dollar value of the scope the certified firm will perform. The value has to be specific and reasonable: a round number that does not align with the bidder’s actual subcontractor breakdown raises questions, and a value that exceeds what the certified firm can realistically perform creates a commercially-useful-function problem.

Signatures and dating

Authorized representative signatures from both the prime contractor and the certified firm. Each signature should include the printed name, the title, and the date. The dates have to be current relative to the bid date: an LOI signed six months before the bid is not current and may not be accepted as a valid commitment.

Program-specific requirements

Some programs require additional content on the LOI: a statement that the certified firm is performing a commercially useful function, an attestation regarding race-conscious or race-neutral participation, or specific format elements. The solicitation specifies what the program requires, and the bidder should match the requirements rather than rely on a default LOI template.

A working LOI is short and clear. One page is the typical format. The structure that holds up under review:

• Header identifying the document as a Letter of Intent for a specific project.
• Identification block for the prime contractor.
• Identification block for the certified firm, including certification body and number.
• Project block identifying the bid by name, number, and date.
• Scope-of-work paragraph or table identifying what the certified firm will perform.
• Dollar-value statement, expressed as a specific number and as a percentage of the prime’s total bid where the program format calls for it.
• Signature block for the prime, with authorized representative name, title, and date.
• Signature block for the certified firm, with authorized representative name, title, and date.

When the agency provides a mandatory form, the structural choice is made for the bidder. When the agency does not, the bidder’s template should be developed once, reviewed for completeness against the relevant program requirements, and reused with project-specific information substituted in. Building each LOI from scratch on every bid invites omissions.

The schedule of participation is the summary table that aggregates the LOIs. Each row in the schedule corresponds to one LOI, and the schedule’s column structure mirrors the LOI’s content: certified firm name, certifying body, certification number, scope summary, dollar value, percentage of total contract value.

Reconciliation between the LOIs and the schedule is one of the things reviewers look at first. A schedule listing a certified firm at $400,000 for excavation, where the firm’s LOI shows $300,000 for excavation, is an internal inconsistency that calls the entire participation submission into question. A schedule listing a firm with a certification number that does not match the LOI’s number is the same problem in a different form.

The reconciliation is also internal to the bid. The dollar values in the schedule have to be consistent with the prime’s subcontractor breakdown and the prime’s overall bid. A schedule total that does not align with what the prime can actually pay out as subcontract dollars at the bid value is going to surface during evaluation, and the agency will ask for clarification or find the bid non-responsive on the participation requirement.

Missing or unsigned LOIs

An LOI listed on the schedule of participation without the underlying signed document attached, or an LOI document signed by only one party. The schedule is not the substantive evidence; the LOI is. A schedule with phantom LOIs behind it does not establish the participation count.

Stale signatures

Signatures dated months before the bid date raise the question of whether the certified firm is still committed to the work. The fix is to refresh signatures within a reasonable window of the bid date, even if the underlying scope and pricing did not change.

Vague scope descriptions

Scope language that does not describe what the certified firm will actually do. “Construction services” is not a scope. “Site grading per Spec Section 31 22 13, including 80,000 cubic yards of cut and fill” is. The reviewer is assessing commercially useful function, and vague scope language reads as an indicator that the substance is not there.

Wrong-program certification

An LOI that names a firm with MBE certification on a procurement that requires DBE certification, or vice versa. The certifying body and number on the LOI must match the program the solicitation is calling for. Verification at LOI preparation time prevents this from surfacing at submission.

Inconsistent values across documents

A dollar value on the LOI that does not match the value on the schedule of participation. A dollar value on either that does not align with the prime’s overall bid math. Internal reconciliation before submission catches this; absence of internal reconciliation produces the inconsistencies that reviewers find.

Reused LOIs from other bids

An LOI dated for a different project, with the project name and bid date imperfectly updated, or signed for a different scope of work than the current bid calls for. Reused LOIs read as a shortcut and are weighted accordingly. Each bid produces its own LOIs.

The contractors that consistently produce clean LOIs treat them as production work that runs alongside the rest of the bid. A maintained internal LOI template, a designated owner for the participation workstream on every covered bid, a tracking spreadsheet that follows each LOI from outreach to scope confirmation to final signature, and an internal review of the schedule of participation against the underlying LOIs before submission. None of this is exotic. It is the same documentation discipline that produces clean compliance matrices, complete proposal narratives, and reliable bid responses on any other procurement.

The ScalaBid Submission Packageon a participation-required procurement surfaces the LOI and schedule of participation requirements directly in the compliance matrix and the action checklist. The LOIs themselves come from the contractor’s relationship work and the certified firms the contractor is working with on the bid. What the package does is keep the requirements visible and structured: which forms the agency requires, what content each LOI must carry, how the schedule reconciles, and the deadlines that drive the production timeline.