You get a call from a former SAIC systems integrator who deployed to a classified site overseas. He developed a spine injury after a vehicle incident on a forward operating base. You start the standard DBA carrier identification workflow. You search the OWCP system. You check the DOL Longshore database. You call the number on his old orientation paperwork. None of it produces a carrier.
This is not a data failure. This is SAIC.
Science Applications International Corporation operates under a coverage structure that breaks the standard DBA playbook. There is no commercial carrier sitting behind most SAIC claims in the way you would find for a typical federal contractor. The claim handler is not an AIG adjuster or a Chubb examiner. The filing procedures you learned for LHWCA cases do not map cleanly onto this employer.
SAIC is a self-insured defense contractor, and self-insurance changes nearly every step of how you investigate, file, and litigate a Defense Base Act claim. It changes who you send the LS-203 notice to. It changes what records you FOIA. It changes the discovery strategy in contested cases. And it changes the 2013 corporate split from Leidos into a live issue that still generates carrier-identification confusion more than a decade later.
This article explains what SAIC's self-insurance structure means for DBA claimants and their attorneys, what records matter, and where the traps sit in federal contracting data.
What does self-insured mean under the Defense Base Act?
Self-insurance under the DBA is not a loophole. It is a specific authorization granted by the Department of Labor under 33 U.S.C. Section 932 and 20 C.F.R. Part 703. An employer that meets capital and bonding requirements can be approved by the Division of Longshore and Harbor Workers' Compensation to pay DBA benefits directly rather than through a commercial carrier.
The practical effect is that the employer functions as its own carrier for claim purposes. Indemnity checks, medical bill payments, and controversion decisions come from the employer's internal risk management team or a retained third-party administrator. There is no policy number to subpoena in the traditional sense. There is no separate insurance company with a financial interest adverse to the employer.
Most large defense contractors with mature risk programs qualify for self-insurance. Our database flags self-insured status on major primes including L3Harris, Huntington Ingalls, CACI, and ManTech. SAIC fits this profile. The company carries investment-grade credit ratings, operates a sophisticated enterprise risk function, and handles volume claim activity that makes self-retention economically rational.
For claimants and their counsel, the first concrete consequence is that a commercial carrier search will not return a useful result. When ClaimTrove flags an employer as self-insured, the investigation pivot point changes. You stop hunting for AIG or Starr policy numbers and start building a record around the employer's own risk management apparatus. Understanding how to identify the correct DBA carrier for your claim requires recognizing early when no traditional carrier exists.
Why does SAIC's 2013 split from Leidos still cause confusion?
In September 2013, the original Science Applications International Corporation split into two publicly traded companies. The legacy commercial and health business was renamed Leidos Holdings. The government services business, including much of the DBA-covered workforce, retained the SAIC name through a new entity, SAIC Inc.
That sentence is simple. The claim consequences are not.
Any worker deployed before September 2013 was employed by the pre-split SAIC, which is the entity now operating under the Leidos name. Any worker deployed after September 2013 was employed by the post-split SAIC, a legally distinct corporation. Workers deployed across that window may have been transitioned administratively between entities mid-contract. The employer of record on a CA-1 or LS-203 depends on deployment dates that are often poorly documented.
This is a textbook case of the alias and entity resolution problem. When you look at federal contracting records in USAspending or SAM.gov, you will find contract awards filed under both names, sometimes for overlapping work. Our database maintains employer alias mappings that track corporate transitions of exactly this type, and the alias resolution problem for employers with multiple names is one of the most common failure modes in carrier investigation.
The stakes are not academic. Filing a claim against the wrong corporate entity can produce jurisdictional objections, delay benefits, and in the worst case trigger statute-of-limitations arguments under Section 913. This pattern is not unique to SAIC, but the prominence of the 2013 split and the continued market presence of both companies makes it one of the most consequential alias mismatches in the DBA space. The broader dynamic is covered in our analysis of defense contractor consolidation and its impact on DBA coverage.
How does filing a DBA claim against a self-insured employer actually work?
The notice and filing mechanics shift when there is no commercial carrier. Under 20 C.F.R. Section 702.201, the LS-203 Employee's Claim for Compensation must be filed with the district director and served on the employer. When the employer is self-insured, the employer is also the party with payment responsibility, so service on the carrier is not a separate step.
The controversion process under Section 914 runs the same way procedurally, but the adjuster on the other side is an employee or contractor of the employer itself. That person is often housed in a corporate risk management department or a retained third-party administrator handling the book under a claim servicing agreement. TPA involvement is one of the most commonly misread signals in DBA investigation. A TPA letterhead on a controversion letter does not mean the TPA is the carrier. It means the TPA is administering claims on behalf of someone, and that someone is usually either a commercial carrier or a self-insured employer.
Our data on carrier confusion patterns shows that TPAs such as ESIS, Gallagher Bassett, and Broadspire frequently appear in claim correspondence without any indication of the actual risk bearer. Treating a TPA as a carrier leads to wasted discovery and incorrect pleadings. The red flags to watch for in DBA investigations include TPA letterhead without accompanying policy information, corporate address blocks instead of insurance company headquarters, and claim numbers formatted differently from commercial carrier conventions.
For self-insured SAIC claims, the correspondence patterns look different from commercial carrier files. Understanding these differences early saves weeks of misdirected investigation.
What federal records matter most for SAIC DBA investigations?
SAIC generates an unusual volume of federal contracting records relative to many DBA employers because of its concentration in IT and intelligence work. Prime contract awards flow through USAspending and SAM.gov. Task order activity under large IDIQ vehicles, including Alliant, SeaPort, and various agency-specific contracts, produces thousands of award actions over a multiyear period.
For DBA purposes, the records that matter most are the ones that establish employment, deployment location, and the contracting pathway. A prime contract award establishes that SAIC held the instrument. It does not by itself prove that a specific claimant worked on that contract or deployed under it. Subcontract awards add another layer, because SAIC both issues subcontracts and receives them as a sub to other primes.
Our database includes 43,298 prime contract awards and 4,315 subcontract awards drawn from USAspending, along with SAM.gov entity records and FOIA-sourced contractor tracking data for Afghanistan operations between 2009 and 2018. For a self-insured employer like SAIC, the contracting records are not going to produce a carrier name because there is no carrier to produce. They serve a different function: corroborating the deployment, establishing the contracting agency, and supporting the jurisdictional predicate under 42 U.S.C. Section 1651.
OSHA inspection records, of which we hold 15,005, can surface workplace safety context. OALJ decisions, of which we hold 5,022, are searchable for prior SAIC-involved cases that establish procedural patterns. None of this replaces the direct records request to the employer's risk management function, but it builds the evidentiary framework around the claim.
This evidentiary triangulation is exactly what the 5-step DBA carrier investigation workflow is designed to execute, and self-insured employers require adapting the workflow rather than abandoning it.
How does SAIC fit into the broader DBA carrier landscape?
The DBA market is concentrated. A small number of commercial carriers handle the majority of policies, and the 637 authorized DBA carriers in our database include many entities that write very low volume or exist primarily as specialty lines within larger groups. Against that backdrop, self-insured contractors function as a shadow segment. They do not appear in authorized carrier lists. They do not show up in the top DBA insurance carriers and their market share analysis in the conventional sense, because they are not carriers at all.
But they account for a meaningful share of total DBA claim volume, particularly in IT services and systems integration work where the large primes are credit-strong enough to self-retain. SAIC sits in that segment along with other major defense IT contractors.
The investigation implication is that a significant percentage of DBA claims, particularly those originating from large prime contractors in high-technology work, will never resolve to a commercial carrier regardless of how thorough the search. Recognizing that pattern quickly is the difference between a two-day carrier identification and a two-month dead end.
ClaimTrove flags self-insured employer status as part of the investigation output. When the system identifies SAIC or a similar self-insured prime, the report routes the user toward self-insurance filing procedures rather than an endless carrier hunt. It also surfaces the alias and entity history, which for SAIC includes the pre-split and post-split corporate identities, any TPA arrangements that appear in our data, and the relevant FOIA sources that corroborate deployment.
Running a SAIC investigation through ClaimTrove takes minutes and produces a structured report that identifies self-insurance status, surfaces relevant corporate history, and flags the specific records you need to request next. Start your SAIC investigation at claimtrove.com to see the full coverage structure and filing pathway.
What discovery strategy changes in a contested SAIC claim?
Contested self-insured claims follow a different discovery arc than contested commercial carrier claims. In a standard LHWCA dispute with a commercial carrier, discovery produces policy documents, reinsurance arrangements, claim committee notes, and correspondence between the carrier and the employer. Each of those documents has a defined custodian and a predictable production path.
Self-insured discovery targets the employer's internal risk management function directly. The relevant documents include self-insurance authorization letters from DOL, internal claim handling protocols, any claim servicing agreements with TPAs, and the internal reserving and reporting practices applicable to the specific claim. The corporate designee under Rule 30(b)(6) becomes a more central figure because there is no carrier witness to shift responsibility to.
Third-party administrator involvement adds another discovery layer. If SAIC has retained a TPA for any portion of the claim administration, the claim servicing agreement governs the scope of the TPA's authority, the reporting lines back to the employer, and the handling standards. That agreement is discoverable and often highly informative about whether specific controversion decisions were made by the employer or the TPA.
Privilege analysis also shifts. When the claim handler is an employee of the employer-defendant rather than an adjuster at an arm's-length insurance company, the line between claim handling and attorney-client communications can be closer than in commercial carrier cases. This is terrain where careful practitioners build the record early.
Practical takeaways for DBA practitioners handling SAIC claims
Three operating principles carry most of the weight. First, confirm self-insured status before spending time on carrier searches. A SAIC claim that returns no commercial carrier is not a data gap. It is a signal. Second, pin down the deployment dates relative to the September 2013 split so the correct corporate entity appears on filings. Third, build discovery around the employer's risk management apparatus and any retained TPA, not around a nonexistent carrier file.
The investigation framework does not disappear for self-insured employers. It shifts. The records that matter change, the parties change, and the correspondence patterns change. What stays constant is that accurate entity resolution and careful verification of the coverage structure are the first two steps, not the last two.
ClaimTrove maintains alias mappings, self-insurance flags, and federal contracting data across more than one million records from 18 federal data sources. For SAIC, for other self-insured primes, and for the broader universe of DBA employers where the coverage structure is not obvious, the tool compresses what would otherwise be a multi-day investigation into a structured report. Run your next SAIC claim through ClaimTrove and see the full employer profile, entity history, and filing pathway in one place.