DBE Good-Faith Effort Documentation

On a DOT-funded project with a contract-specific DBE participation goal, the bidder either meets the goal or documents a good-faith effort to meet it. The bid response shows the agency which one. A bidder that meets or exceeds the goal submits the schedule of participation, the Letters of Intent, and a summary that demonstrates the goal is met. A bidder that falls short submits the same content for what was achieved, plus the good-faith effort documentation that explains why the gap exists.

The good-faith effort documentation is not a fallback or a workaround. It is a specific evidentiary submission with regulatory standards under 49 CFR Part 26 Appendix A. The agency reviews the documentation against those standards and decides whether the bidder satisfied the participation requirement despite not meeting the numeric goal. A bid that meets the standard is responsive. A bid that does not meet the standard is non-responsive on the participation requirement, regardless of how strong the price is.

Appendix A to 49 CFR Part 26 lists the factors agencies use to evaluate good-faith effort. The list is not a checklist where hitting a fixed number of items produces a passing grade. It is the framework the reviewer applies, and the bidder’s documentation has to demonstrate substantive effort across the relevant factors.

Solicitation of all certified firms

The bidder solicited interest from all certified firms in the relevant scope categories that have the capability to perform the work. The reviewer expects the documentation to show that the bidder identified the relevant scope categories, looked up the certified firms in each, and reached out to those firms with information about the work. A bidder that solicited only firms it had previously worked with, while ignoring others on the UCP directory, is not demonstrating effort across the relevant categories.

Sufficient information about the work

The bidder provided certified firms with adequate information about the plans, specifications, and requirements of the contract. A general “we are bidding this project, please contact us” outreach does not give a certified firm what it needs to decide whether to participate or how to price the scope. Useful outreach includes the project name, the bid date, the relevant scope packages, the prevailing wage determination if applicable, and a contact for follow-up.

Negotiation in good faith

The bidder negotiated in good faith with interested certified firms and considered all bids and quotes received. A bidder that received a quote from a certified firm and rejected it because the price was higher than a non-certified firm’s, without any consideration of whether the difference reflected legitimate cost factors, is not negotiating in good faith. Reasonable price differences attributable to specialty experience, smaller-scale operating costs, or other legitimate factors should be evaluated, not summarily rejected.

Selection on legitimate grounds

The bidder did not reject certified firms as unqualified without sound reasons based on a thorough investigation of their capabilities. A bidder rejecting a certified firm should be able to articulate a substantive reason: the firm did not bid the scope, the firm’s pricing was non-competitive after consideration of legitimate cost differences, the firm did not have the capacity to perform the work in the timeframe required, or specific capability gaps were identified through reasonable investigation.

Reasonable scope packaging

The bidder made reasonable efforts to package the work in scopes that certified firms could realistically bid. Bundling all the electrical work on a project into a single $5 million package when most certified electrical firms in the area can handle $1 million packages is not reasonable scoping. Some agencies and contracts require a bidder to consider unbundling explicitly.

Use of available services

The bidder used the services of available organizations that provide assistance in identifying certified firms, including community organizations, contractor groups, local, state, and federal small business assistance offices. Documenting outreach through these channels strengthens the record of effort.

The substantive content of a good-faith effort submission usually includes the following.

Outreach records

Letters, emails, faxes, and voicemails sent to certified firms during the bid period. Each outreach record carries the date, the recipient (firm name, certification number, contact), the medium, and a brief description of the content. A spreadsheet log alongside the underlying records is the format that holds up under review. The log shows breadth and consistency at a glance; the records support the log if anything is questioned.

Scope packages distributed

The actual content sent to certified firms: the scope summary, the relevant drawings, the specifications, the bid date, the response timeline, and the contact for questions. Including a copy of a representative scope package in the documentation lets the reviewer see what certified firms were given.

Bids and quotes received

A summary table of bids and quotes received from certified firms, with the firm name, the scope, the bid amount, the comparison against the bid the contractor used, and a brief explanation if the certified firm’s bid was not used. The narrative explanation is what shows good-faith consideration of each response.

Follow-up correspondence

When initial outreach did not produce a response, the documentation should show follow-up: a second contact, a phone call log, an attempt to reach the firm through alternate channels. The reviewer reads follow-up records as evidence of genuine effort to engage the certified firms identified.

Narrative summary

A narrative summary that walks the reviewer through the bidder’s overall effort: which scope categories were targeted, why those, how the certified firms in each were identified, what outreach was conducted, what bids were received, why the goal was not fully met. The narrative ties the underlying records into a coherent story the reviewer can follow.

Use of assistance organizations

Documentation of outreach to small business development centers, the relevant UCP, contractor associations, and community organizations. A short note that the bidder contacted these organizations and a record of any responses received are sufficient.

The single most common reason good-faith effort documentation fails review is timing. A bidder who starts outreach in the last few days of a 30-day bid window cannot demonstrate the substantive effort the regulation calls for, regardless of how thick the documentation packet ends up being.

Outreach starts when the solicitation lands

The right pattern is to identify the relevant scope categories within the first day or two of the bid window, pull the certified firms in each category from the UCP directory, and begin outreach. Following up across the bid window. Receiving and evaluating bids as they come in. The documentation accumulates as a byproduct of the actual effort, not as something assembled retroactively.

Reasonable response time

Certified firms need time to evaluate scope packages and prepare quotes. Outreach that gives a certified firm 24 hours to respond on a substantial scope is not reasonable. A bidder reaching out to certified firms with a same-week or shorter response window has not given the firms a real opportunity to participate, and the reviewer will read the timeline as evidence of insufficient effort.

Internal review before submission

Before submission, the good-faith effort packet should be reviewed against the Appendix A factors as if the reviewer is reading it. Gaps that the bidder’s own internal review can identify are gaps that will surface in the agency’s review. Filling gaps before submission is faster than responding to a non-responsiveness finding after the fact.

Several patterns reliably produce non-responsiveness findings. Recognizing them is half of avoiding them.

Boilerplate outreach

A form letter sent to every firm on the UCP directory, with no scope-specific content and no follow-up, does not demonstrate effort. The reviewer can identify boilerplate at a glance. The fix is scope-specific outreach with substantive content.

Documentation built after the bid is submitted

Backdated outreach, retroactive log entries, and documentation that does not match what actually happened during the bid window are visible to a careful reviewer. The records have to be contemporaneous with the effort, not assembled to support a participation claim that cannot be supported.

Rejecting all certified firms on price alone

A bid where every certified-firm quote is rejected as too high, with no consideration of legitimate cost factors and no negotiation, raises the question of whether the bidder ever intended to use a certified firm. The pattern reads as pretextual effort, and the reviewer treats it accordingly.

Using the same documentation across multiple bids

A documentation packet that does not reference the specific solicitation, the specific scope, the specific bid date, and the specific certified firms contacted is not project-specific documentation. Reviewers see the same packet on multiple bids and discount it accordingly. Each bid needs its own documentation built from its own outreach.

Contractors that consistently produce strong good-faith effort documentation have built it into the bid pipeline as a standard practice rather than as an exception. Common elements include a maintained list of certified firms by scope and geography, a templated outreach format that is customized per bid, a tracking spreadsheet that captures every contact during the bid window, and a designated person responsible for the participation workstream on every covered bid.

The practice is not exotic. It is the same operational discipline that produces clean compliance matrices and complete bid responses on any other procurement. The participation workstream runs alongside the rest of the bid effort, with its own owner, its own deliverables, and its own internal review before submission. On a procurement where the documentation is going to be evaluated, treating it as evaluation content from the start is the difference.

The ScalaBid Submission Packageon a participation-required procurement surfaces the relevant program clauses, the participation goal, and the documentation requirements directly in the compliance matrix and the action checklist. The good-faith effort documentation itself is the contractor’s work, built from the contractor’s relationships and the contractor’s outreach during the bid window. What the package does is keep the participation requirements visible from the start of the bid, so the outreach work has somewhere structured to land and the documentation accumulates against the requirement rather than against an assumption that will need to be tested at the end.