A paralegal calls a CACI International field office to confirm the DBA insurance carrier on a contractor injured at a forward base in Iraq. The HR contact transfers her three times, then says the claim is being handled internally. No carrier name. No policy number. No NAIC code to look up. She pulls the DOL authorized carrier list, and CACI does not appear there as an insured employer the way KBR or Fluor would. The investigation feels broken before it started. It is not broken. It is just pointing at the wrong kind of answer.
CACI International is a federal technology and intelligence contractor with a deep overseas footprint. That footprint touches Defense Base Act coverage in ways that do not resolve to a simple carrier card. When you search standard DBA records for CACI and find gaps, that absence is itself a data point. It tells you to stop hunting for a third-party carrier and start asking a different question: is this employer carrying its own risk?
This article walks through how a CACI International DBA insurance self-insured defense contractor investigation differs from a normal carrier trace. It explains why CACI's federal contracting profile makes the question worth asking, and where the actual answers live. The short version is that self-insurance changes the entire shape of your investigation. The longer version protects your client's claim from being filed against the wrong responsible party.
What Does "Self-Insured Defense Contractor" Actually Mean Under the DBA?
The Defense Base Act requires federal contractors to secure workers' compensation coverage for employees working overseas. Most contractors satisfy that requirement by buying a policy from one of the authorized DBA carriers. ClaimTrove tracks 637 authorized carriers in the DOL list. The typical investigation matches an employer to one of them for a given contract period.
Self-insurance is the alternative path. Instead of paying premiums to a carrier, a financially strong employer applies to the Department of Labor for authorization to pay claims directly out of its own assets. The DOL reviews the company's financials, sets a security deposit or surety bond requirement, and grants self-insured status. From that point, the employer is the responsible party. There is no separate insurance company standing behind the claim.
This matters enormously for an attorney. When you serve a claim, demand documents, or negotiate settlement, you are dealing with the contractor's in-house risk function or its third-party administrator. You are not dealing with an outside carrier's claims unit. The legal obligations under the LHWCA still apply in full. The party writing the check is just different.
Why would a contractor like CACI choose this route? Scale and predictability. A company with steady revenue and a large, relatively stable overseas workforce can often pay claims more cheaply than buying coverage. That advantage grows when commercial premiums spike. The economics push the biggest, most stable employers toward carrying their own risk. That is exactly the profile a CACI International DBA insurance self-insured defense contractor inquiry has to reckon with.
The catch is that self-insured status is not permanent and not always total. A contractor can be self-insured for some operations and buy coverage for others. It can be self-insured in one period and carrier-covered in another. Subcontractors under a self-insured prime almost always carry their own separate coverage. None of this shows up as a clean single answer, which is exactly why the investigation needs structure.
Why Does CACI's Federal Contracting Profile Raise the Self-Insurance Question?
CACI International is not a logistics or construction prime in the mold of the contractors most attorneys picture when they think DBA. It is an information technology, intelligence, and professional services contractor. Its overseas work has historically included intelligence support, language services, IT systems, and analytical work tied to defense and intelligence agencies. That work places employees in theater, which triggers DBA coverage. The job titles look nothing like a convoy driver or a security operator.
The profile matters because contractor type drives both risk and coverage strategy. ClaimTrove holds 43,298 prime contract awards and 4,315 subcontract awards from federal procurement data. When you pull a technology or professional services contractor's award history, you often see a different pattern than a heavy-logistics prime. You see more contracts, smaller individual headcounts per site, and a workforce spread across many locations. That distribution is one of the conditions that makes self-insurance attractive.
CACI also sits in the same tier as several contractors we have already profiled as self-insured or self-insurance-adjacent. The investigative approach for SAIC and how self-insurance changes your investigation maps closely to what you face with CACI. Both are large federal technology primes with the financial strength the DOL looks for when granting self-insured authority. The methodology transfers almost line for line.
There is a second wrinkle specific to firms like CACI: acquisitions. CACI has grown by absorbing other contractors over the years, and each acquisition can carry its own DBA coverage history. The acquired entity may have used a commercial carrier before the acquisition, then folded into the parent's self-insured program afterward. That creates a temporal seam where the responsible party changes mid-history. If your client's injury date sits near one of those seams, identifying the correct responsible party becomes a date-specific question, not a name-specific one.
Professional services contractors surprise attorneys for a consistent reason. Their coverage does not look like the heavy-contractor template. The lesson holds across consulting, intelligence, and IT primes alike. CACI is one of the clearest examples in the federal technology space.
How Do You Investigate a Self-Insured Employer Differently?
A normal carrier trace ends when you match an employer to an authorized carrier for the relevant period. A self-insured investigation ends somewhere else. The steps in between are different enough that running the standard playbook will leave you stuck.
First, you confirm the self-insured status itself rather than assuming it. The absence of a carrier match is suggestive, not conclusive. You need affirmative evidence that the DOL authorized the employer to self-insure for the relevant operations and period. That evidence exists in federal records, but it does not live on the same page as the authorized carrier list.
Second, you pin the period. Self-insured authorization is granted, renewed, and sometimes lapses. A contractor self-insured in 2018 may have carried commercial coverage in 2012. Because injury date controls which responsible party applies, the period question is not optional. Our breakdown of why injury date drives everything in DBA cases applies with extra force here. A self-insured employer's responsibility is bounded by the exact authorization window.
Third, you identify the administering entity. Self-insured contractors rarely process claims with their own HR staff. They hire a third-party administrator to handle adjudication, medical management, and benefit payments. Knowing whether you are dealing with the employer directly or a TPA changes who you serve and who you negotiate with. The same skills that help you spot a TPA versus an actual DBA carrier apply when a self-insured employer's TPA shows up looking like the carrier of record.
Fourth, you separate the prime from the subs. Even if CACI is self-insured, a subcontractor whose employee was injured almost certainly carried separate DBA coverage. The responsible party may be the sub's carrier, not the self-insured prime at all. Getting this wrong sends a demand to a party with no liability and burns months.
Fifth, you cross-reference the federal identifiers. CAGE codes and UEI numbers tie an employer's many name variations to a single entity across procurement and DOL records. That is how you confirm you are tracking CACI and not a similarly named subsidiary or acquisition.
Where Do the Federal Identifiers Come In?
Self-insured investigations live or die on entity matching. A contractor as large as CACI appears under multiple legal names, subsidiary entities, and acquired-company names across federal data. If you match the wrong entity, you can conclude an employer is self-insured when in fact a separate subsidiary bought a commercial policy.
This is where CAGE codes and Unique Entity Identifiers do the heavy lifting. ClaimTrove cross-references 865,232 SAM.gov entity records. The CAGE code and UEI identifiers that unlock DBA carrier chains are what let you collapse a dozen name variations down to the actual responsible entity. For a contractor with an acquisition history, this step is non-negotiable.
The federal procurement record then confirms the operational footprint. By reading the contractor's award history, you establish where employees were deployed, under which contracts, and during which periods. For a self-insured employer, the award history is doubly important. The self-insurance authorization has to be matched against the specific contracts your client worked under.
None of this replaces primary-source verification. The point of assembling federal identifiers and award history is to build a defensible chain. That chain tells you, for a specific injury date, exactly which entity bore DBA responsibility and how to reach it. The chain is the deliverable. The carrier name you originally went looking for may never appear, and that is the correct outcome when the answer is self-insurance.
What Goes Wrong When Attorneys Assume a Carrier Exists?
The most expensive mistake in a self-insured investigation is refusing to accept the answer. An attorney pulls the authorized carrier list, finds no CACI match, and assumes the search tool is incomplete. So they keep hunting for a carrier that does not exist, file against a placeholder, or wait for the employer to volunteer a name that will never come.
The opposite mistake is just as damaging: assuming self-insurance too early. A no-match result can also mean the employer used a carrier under a name variation you have not resolved yet. It can mean the responsible party is a subcontractor's carrier. Treating an unresolved alias as proof of self-insurance is a classic DBA investigation red flag. The honest answer is that a no-match means investigate further, not self-insured and case closed.
A third failure mode is ignoring the temporal seam created by acquisitions and renewals. Even when self-insurance is confirmed for today, your client's injury may predate the current authorization. The responsible party at the time of injury could be a prior carrier or a since-absorbed entity. A self-insured status confirmed for 2024 tells you nothing about 2014.
The structured fix is to run a disciplined workflow rather than reacting to each dead end. The five-step DBA carrier investigation workflow forces you to confirm entity identity, pin the period, separate prime from sub, and verify the responsible party before you act. For a CACI International DBA insurance self-insured defense contractor case, that discipline is what keeps a clean-looking no-match from quietly becoming a malpractice problem.
Self-insurance is not a gap in the data. It is a specific, verifiable status that changes who pays and how you proceed. The contractors most likely to carry it are the largest and most stable federal primes, and CACI International fits that profile. The work is to prove it for the right entity and the right date rather than assume it.
Ready to Trace CACI's DBA Responsible Party?
Manually chasing a self-insured contractor across SAM.gov, federal procurement records, DOL authorization data, and acquisition history can consume days. A single unresolved name variation can send the whole conclusion the wrong way. ClaimTrove cross-references over a million federal records, resolves entity aliases through CAGE and UEI matching, and surfaces the responsible-party picture for a specific employer and injury date. Start an investigation on CACI International or any defense contractor and get a defensible answer instead of a dead end. Create your ClaimTrove account and run the trace today.