DBE/MBE participation and the commercially-useful-function test

The goal is a floor, not the whole test

On federal-aid contracts — highway, transit, aviation work funded or assisted by USDOT dollars — meeting the stated Disadvantaged Business Enterprise (DBE) participation goal looks, on paper, like a percentage exercise: hit the number, satisfy the requirement. It isn't that simple. The DBE program's regulation, 49 CFR Part 26, doesn't just ask whether a DBE was listed on the contract for the right dollar amount — it asks whether that DBE actually did the work. That second question is the commercially useful function test, and it's the one that generates the most serious exposure when a contract gets audited.

Where the goal comes from

Recipients of USDOT funds — state DOTs, transit agencies, airport authorities — set an overall annual DBE goal and, often, contract-specific goals for individual projects, based on the availability of ready, willing, and able DBEs in the relevant market. A prime contractor bidding the work either commits to meeting the contract goal with certified DBE participation or documents good faith efforts to do so, under the standards in Appendix A to Part 26, when the goal genuinely can't be met. Simply falling short without documented good-faith efforts is its own compliance failure, separate from any CUF issue.

The commercially useful function test

49 CFR §26.55 defines when a DBE is performing a commercially useful function: the firm must be responsible for execution of a distinct element of the work, and must actually perform, manage, and supervise that work itself — using its own workforce and equipment where the work calls for it — rather than merely being listed on the contract while someone else does the substantive work. The regulation is explicit that a DBE does not perform a CUF if its role is limited to that of an extra participant in a transaction, contract, or project through which funds are passed in order to obtain the appearance of DBE participation.

• The DBE must have the skills, equipment, and organization to perform the work it's credited with — not just the contractual role.
• If a DBE subcontracts out a substantially greater portion of the work than would be expected given the industry norm for that type of work, that's a factor weighing against CUF.
• A DBE that merely orders materials or supplies and does not itself perform, manage, or supervise the work is generally not performing a CUF, regardless of the dollar amount attributed to it.
• Only the value of the work actually performed by the DBE's own forces — plus a properly limited share for supervised, DBE-managed subcontracted work in some circumstances — counts toward the goal, not the full contract value passed through it.

Why 'pass-through' is the term to fear

The plainest way to fail the CUF test is a pass-through arrangement: a certified DBE is listed at or near its full committed dollar value, invoices flow through its books, and a fee is retained — but the actual labor, equipment, and supervision are provided by a non-DBE firm. Regulators and recipients look for exactly this pattern in claims review, because it produces a compliant-looking DBE percentage without producing genuine DBE participation. It is also the fact pattern most likely to draw federal scrutiny beyond a simple compliance finding, because certifying DBE participation on a federal-aid contract is itself a representation to the funding agency.

The percentage on the form and the work on the ground have to match. That's the whole test.

How it's tracked and reported

Many state DOTs and transit agencies — including agencies handling California federal-aid work — use third-party platforms such as B2Gnow to track DBE payments, monitor commitments against actual disbursements, and flag CUF concerns in something close to real time, rather than waiting for an end-of-project audit. Prime contractors are generally required to report DBE payments as they're made, not just at closeout, which means a pass-through problem tends to surface earlier than it would have under older paper-based reporting — and earlier discovery means less accumulated exposure, but also less room to quietly fix it before it's flagged.

What's at risk beyond the single contract

A CUF failure exposes more than one project. Consequences can include disallowance of the DBE credit toward the goal (which can put the prime out of compliance retroactively), contract remedies up to and including termination for cause, and — for the DBE firm itself — referral for decertification through California's Unified Certification Program (CUCP) if it's found to lack the independence, control, or genuine operational capacity the certification requires. For the prime contractor, a documented pattern of relying on non-performing DBEs can affect eligibility on future federal-aid awards and, in egregious cases, raises exposure under federal false-statement and false-claims authorities, because the DBE participation reported to the funding recipient is a certification, not a formality.

Building a CUF-defensible team from the start

• Verify a prospective DBE's actual equipment, workforce, and prior scope of work matches what it's being scheduled to do — not just its certification status.
• Keep the DBE's invoiced work traceable to work its own forces (or properly limited, supervised subcontracting) actually performed.
• Document good-faith efforts contemporaneously if a contract goal isn't met, rather than reconstructing them after the fact.
• Treat DBE payment reporting as a running compliance record, not a closeout exercise — it's reviewed as one.

This article is educational and does not constitute legal or tax advice. Statutes and agency requirements change; confirm current rules with the California DIR, the U.S. Department of Labor, the IRS, or qualified counsel before relying on them. Aeternus Dynamics is a compliance and advisory firm, not a law or accounting firm.