What a BABA insufficient data verdict means, and how to clear it

A BABA determination can end in four ways: compliant, non-compliant, waiver-eligible or insufficient data. The first three are easy to read. The fourth is what many people misunderstand. Insufficient data is not a pass, and it is not a fail. It means the facts supplied cannot support a verdict in either direction, so the engine reports the gap instead of choosing a side.

This guide explains what triggers the verdict, what each trigger means, and what evidence closes it. The outputs quoted below come from running the determination engine on the inputs shown. You can reproduce them from the same inputs. It isn't legal advice; the funding agency's guidelines control.

Why the engine will not guess

The engine has one honesty rule that governs this verdict: absence of data is never a pass. A manufactured product with no US-origin cost figure does not count as zero percent domestic, and it does not count as compliant. Reporting either would turn a missing document into a compliance record. A bidder who certifies a guess is exposed in a way that a documented gap is not. So the verdict stays visible until someone supplies the fact it is missing.

The triggers, one input at a time

The engine returns insufficient data for a small set of input gaps. Each one maps to a single field, so the fix is usually one document rather than a rework of the whole bill of materials.

• Manufactured product with no manufacturing location. The manufacturedInUS flag is not set, so the engine cannot tell whether final assembly happened in the United States.
• Manufactured product with no component cost. The domesticComponentCost figure is missing, so the 55 percent test cannot be computed.
• Zero total cost. A ratio needs a denominator, and a total of zero would read as a 0 percent fail on a line that has no cost at all.
• US component cost above the line total. The figures contradict each other, so the engine refuses to report a percentage above 100.
• Iron and steel with no all-US flag. The allManufacturingInUS value is not set, so the engine cannot tell whether every step from melt to coating happened in the United States.
• Agency or obligation date with no standard. The agency is not loaded, or the obligation date falls before the first phase of the standard. The remedy text asks you to confirm the date.

What the engine returns, with real outputs

The table below shows six single-line runs against the EPA state revolving fund ruleset, with an as-of date of 10 November 2026. The first five use a manufactured product, and the last uses a steel plate. The columns are the verdict, the domestic share the engine computed (or null when it computed none), and the reason it gave.

Two rows are worth a second look. The 55,000 row is non-compliant, not insufficient: the engine had every fact it needed and the product fails the test as written. The insufficient rows are the ones where a fact is missing or the figures disagree. The distinction matters because the fix is different. A non-compliant line needs a different supplier, a redesign or a waiver. An insufficient line needs a document.

How to clear each gap

Supply the field the remedy names, then run the determination again. The evidence that usually closes each gap is set out in the guide to what evidence is missing from a bill of materials. For the component-cost gap, the calculation is covered in the domestic content calculation guide. The 55 percent boundary itself, including why exactly 55 fails, is explained in the 55 percent threshold guide.

Where an insufficient line is still open, record it as unverified with the request you sent. Do not fill the field with an estimate to make the verdict go away. A figure you type in without a source becomes the number the next reviewer relies on.

Why one gap stops the whole project

The engine reports a project-level summary as well as line verdicts. The project is marked compliant overall only when there is at least one finding and no line is non-compliant, waiver-eligible or insufficient. A bill with nine compliant lines and one insufficient line is not compliant overall. The analytics layer counts insufficient lines separately from judged lines for the same reason: a long list of passes should not hide an unresolved gap.

A waiver does not clear the verdict

It is tempting to treat a waiver as the way out of an open line. It is not. The engine only applies the project-level de minimis test, and only when it can compute that test from the bill itself. Other waiver routes, such as public interest or nonavailability, depend on facts the engine does not hold, so it names them as routes to investigate and does not apply them. A waiver also has to be granted by the agency before the line counts as compliant. The waiver guide sets out the request, and the waivers explained post covers why none of them is a pass on its own.

If you want to see every line of your own bill of materials sorted this way, the calculator returns a verdict for each entry and shows the gap where one exists.

Sources

• Cornell Legal Information Institute, 2 CFR 184.3, definitions for the Buy America preference
• EPA, job aid for manufacturers on the cost of components
• Federal Register, FHWA rulemaking on the Buy America manufactured products requirement, January 2025