A machinist loses three fingers on a vehicle-maintenance line at a forward operating base in 2015. Two years later the file lands on your desk. The claimant remembers the base and the job. He does not remember the legal name of the company that signed his paycheck, and the entity on his badge folded into a larger firm before you ever met him. You know an injury happened on a federal contract. You do not know which contractor ran it, and until you do, you cannot name a carrier.
This is the identity problem at the center of most Defense Base Act investigations. The injured worker knows the mission. The federal paper trail knows the party. Bridging the two is the whole game, because the carrier follows the contractor, and the contractor follows the contract. One federal system quietly documents exactly which company performed which job at which location: the Contractor Performance Assessment Reporting System, better known as CPARS.
CPARS was never built for injury lawyers. It was built to grade contractors so the government can decide who gets the next award. But the same evaluation that rates a firm on quality and schedule also fixes that firm to a specific contract, period, and place of performance. That corroboration is the thread this article pulls.
What is CPARS and what does a past-performance record actually contain?
CPARS is the federal government's system of record for documenting how contractors performed on their contracts. Agencies use it to write past-performance evaluations, and source-selection teams read those evaluations when deciding who wins the next competition. It is run on behalf of the government by the Naval Sea Logistics Center in Portsmouth, and it covers civilian and defense agencies alike.
Each CPARS evaluation is anchored to one contract or order. It carries the contractor's name, its CAGE code, its unique entity identifier, the contract number, the period of performance, the place of performance, the dollar value, and the product or service codes. Assessing officials then rate the contractor across areas like quality, schedule, cost control, management and business relations, small-business subcontracting, and regulatory compliance.
The rating scale runs Exceptional, Very Good, Satisfactory, Marginal, and Unsatisfactory. Each rating comes with a narrative explaining why. That narrative is where the human detail lives: what the contractor built, which subcontractors it leaned on, where the work happened, and what went wrong. For an injury investigator, the ratings matter far less than the identity data wrapped around them.
Understand what CPARS confirms and you understand why it is useful here. It does not name an insurance carrier. It never has. What it does is pin a named legal entity to a documented job, and that is precisely the fact most claims start out missing.
Why can't you just pull the CPARS record for a contract?
Here is the accuracy point that trips up attorneys who hear "federal database" and assume public access. CPARS is not public. Past-performance evaluations are treated as source-selection-sensitive and confidential commercial information. They are generally exempt from disclosure under the Freedom of Information Act, and the government withholds them to protect both the contractor and the integrity of future competitions.
That means you cannot file a FOIA request for a competitor's CPARS card and expect to receive it. Access is restricted to authorized government users and, in limited form, to the rated contractor itself. The older Past Performance Information Retrieval System that once fronted this data has been folded into the CPARS environment, but the closed-access posture did not change.
So CPARS is a corroboration concept for outside investigators, not a lookup you run directly. The value is knowing what it captures, because the identifiers CPARS keys on are the same ones that surface in systems you can reach. A CPARS record and a public award record describe the same contract through the same CAGE code, the same entity identifier, and the same contract number. Learn to read those identifiers and you are reading the shadow CPARS casts into open data.
This is where methodical investigation beats guesswork. When you can map a contractor's CAGE code and UEI number across federal records, you reconstruct the same identity spine that a CPARS evaluation is built on, without ever needing the sealed evaluation itself.
How does CPARS corroborate which contractor really ran the job?
Most contested DBA claims are not fights about the law. They are fights about facts: which company, which contract, which day. A carrier that wants to delay will question whether the named employer was even the responsible party at that base on that date. Corroboration answers the question before it becomes a dispute.
CPARS corroborates on three axes at once. It confirms the performing entity, because the evaluation is written about a specific named contractor. It confirms the period, because every evaluation carries a defined period of performance. And it confirms the place, because federal work is tied to a place-of-performance location. Employer, time, and location are the three legs every DBA claim stands on.
The public mirror of this same information lives in procurement data. Learning to read USAspending records for DBA investigations lets you see the award, the recipient, and the country of performance that a CPARS evaluation would grade. The systems overlap by design, because they describe the same contracts from different angles.
Contract-level detail sharpens the picture further. The federal procurement data behind an award ties a contract number to a task-order parent, a recipient entity, and a labor-standards flag that signals whether DBA likely applied. Stack that against the injury date and location, and a vague "he worked for some contractor at that base" becomes a named entity on a specific award during a specific window.
Why does contractor identity matter more than the carrier at first?
Attorneys new to DBA work often want the carrier name on day one. The carrier is the destination, but contractor identity is the road. Name the wrong contractor and every downstream step points at the wrong policy, the wrong period, and the wrong defense counsel.
Contractor identity is hard because companies rarely keep one clean name. They merge, rebrand, spin off subsidiaries, and file overseas work under entities that look nothing like the parent brand a worker would recognize. A claimant who says "I worked for the logistics company" may have been employed by a subsidiary three corporate layers removed from the name on the contract.
This is why resolving the aliases behind a single employer is a foundational step, not a footnote. The same firm can appear under a dozen legal names across federal records, and a carrier search that only checks one of them misses the coverage tied to the others. CPARS-style identity data matters because it forces you to work from the entity that actually performed, rather than the brand the worker remembers.
Once you fix the correct performing entity, verification gets faster. You can confirm the company is a live federal registrant, pull its registration identifiers, and check its status. Running a SAM.gov entity search to verify a DBA employer ties the name to a CAGE code and a UEI, which are the same identifiers CPARS uses to keep one contractor distinct from another with a similar name.
Only after the entity is locked does the carrier question become answerable. The contractor points to its contract, the contract points to its period and agency, and the period and agency point to the coverage that applied. Skip the identity work and the carrier answer you land on is a guess wearing a suit.
How do you turn CPARS-style identity data into a carrier answer?
Think of it as a chain, and CPARS as one of the links that keeps the chain honest. The claimant gives you a base and an approximate date. Public procurement data gives you the contractors that performed there in that window. Entity identifiers separate the real performing company from its look-alikes. And the contract's agency, period, and vehicle narrow the carriers that could have been on risk.
The reason this works is that DBA coverage is not random. Some agencies mandated specific carriers for defined periods. Contract vehicles and task orders carry their own coverage histories. A prime's insurance often flows down to the subs it hired. None of these signals is decisive alone, but stacked against a confirmed contractor and a confirmed date, they converge.
That convergence is exactly what a purpose-built investigation does at speed. ClaimTrove threads contractor identity across 865,232 federal entity records, resolves the aliases and subsidiaries hiding a single employer, and ties the confirmed contractor to the carrier signals for the specific date of injury. Run the employer through a ClaimTrove investigation to corroborate which contractor owned the job and surface the carrier evidence tied to it.
What are the limits of using CPARS as a DBA investigation source?
Honesty about a source makes it more useful, not less. CPARS has real limits, and a good investigator names them before a defense lawyer does.
First, access. You will not hold the actual evaluation in most cases, so you are working from its public shadow rather than the sealed record. Second, coverage. CPARS evaluations are generally written for contracts above defined dollar thresholds, so smaller awards and lower-tier subcontracts may never generate one. Third, silence on insurance. CPARS grades performance; it says nothing about which carrier wrote the policy. It corroborates the party, not the coverage.
None of that makes it useless. It makes it one thread among many. The strongest DBA investigations never rest on a single source. They cross public procurement data, entity registrations, coverage filings, and legal-proceeding records until the same contractor and the same period appear again and again from independent directions. CPARS-style identity data is one of those directions, and its independence from the others is what gives it weight.
The practical takeaway is simple. Do not chase a CPARS report you cannot obtain. Learn what it documents, work the identifiers it shares with open systems, and let the corroboration compound. When you can prove the contractor from several angles at once, the carrier stops hiding. Start that corroboration in ClaimTrove and let the identity thread lead you to the carrier.