ManTech DBA Insurance Carrier: How to Trace Coverage for a Federal IT Contractor

A paralegal opens a new file for a contractor who deployed to a forward operating base in Afghanistan to keep classified networks running. The employer line on the LS-203 reads "ManTech." The claimant remembers the badge, the deployment, the systems work. What nobody in the file knows is which insurance carrier actually wrote the Defense Base Act policy that has to pay the claim. That single missing fact stalls everything.

ManTech International is one of the largest IT and intelligence-services contractors in the federal space. It has spent two decades supporting the Army, the intelligence community, and combat-zone network operations. That work places thousands of employees overseas under DBA coverage. Yet finding the ManTech DBA insurance carrier for a specific worker, on a specific contract, in a specific year is rarely a one-step lookup.

The reason is structural. Federal IT contractors like ManTech run dozens of overlapping contract vehicles, win and lose recompetes, change corporate names, and operate through subsidiaries and joint ventures. Each of those moving parts can change who insured a worker. A carrier that covered ManTech on one Army contract may have nothing to do with an intelligence-community task order signed the same fiscal year.

This profile explains how to investigate ManTech DBA coverage the right way. It covers where ManTech sits in the federal contracting landscape, why its carrier history is harder to trace than a single security firm's, and the records that actually resolve the question. It will not hand you a carrier name for a given year, because that answer depends on the exact contract and date, and getting it wrong defeats a claim. The goal is to make you faster and more accurate at finding the real answer.

Who is ManTech and why does its DBA coverage span so many contracts?

ManTech International Corporation was founded in 1968 and grew into a major provider of technology services to the U.S. government. Its work concentrates in cybersecurity, systems engineering, intelligence analysis, and mission IT for defense and national-security agencies. In 2022 the company was acquired by the private-equity firm Carlyle Group and taken private, which added another layer to its corporate identity over time.

For DBA purposes, the relevant fact is where its people go. ManTech does not just write code in Virginia office parks. It deploys engineers, analysts, and IT specialists to bases and facilities overseas, including high-threat theaters. Any employee working outside the United States on a covered federal contract falls under the Defense Base Act, which means a DBA policy must respond if they are injured.

ManTech's federal footprint is large. Across the USAspending prime contract dataset, ClaimTrove tracks tens of thousands of prime awards spanning the agencies that drive overseas work, including the Army and the intelligence community. ManTech appears across many of those agencies, not a single one. That breadth is exactly why a "what carrier covers ManTech" question has no universal answer.

Different agencies impose different insurance arrangements. Some contracts let the contractor buy DBA coverage on the open market. Others fall under a mandatory program where the government picks the carrier for everyone on that vehicle. We break down how that works in our guide to mandatory agency contracts where the government picks your carrier. If ManTech worked under one of those arrangements, the carrier is dictated by the contract, not by ManTech's general buying habits.

That distinction matters from the first hour of an investigation. Before you guess a carrier, you have to know which contract the injured worker was attached to and which agency funded it. The contract drives the coverage, and ManTech holds many contracts at once.

Why is ManTech harder to trace than a standalone security contractor?

Security firms like Triple Canopy or SOC built their overseas business around a handful of large protective-services contracts. Trace the contract, and you are close to the carrier. ManTech is different. It is a diversified IT and intelligence company with hundreds of active awards, and its overseas exposure is spread thin across many of them.

This creates three specific tracing problems. First, the volume of contracts. A single fiscal year can include dozens of ManTech awards across multiple agencies, only some of which involve overseas labor that triggers DBA coverage. You cannot assume the largest contract is the one your claimant worked under.

Second, subcontract relationships. On many large programs ManTech is a subcontractor rather than the prime, which means a different company's DBA policy or flow-down arrangement may control. Untangling that requires tracing the chain, a process we cover in prime versus subcontractor DBA insurance tracing. The employer on the injury form is not always the entity that bought the policy.

Third, corporate change. ManTech has acquired companies, operated subsidiaries, and gone through the Carlyle take-private. Each event can shift how filings name the employer and which entity holds coverage. Defense-contractor consolidation reshapes DBA coverage across the entire sector, and ManTech is no exception.

Put together, these factors mean a ManTech investigation is closer to the pattern seen with other large IT primes than with a single-mission security firm. Attorneys who have worked the Leidos federal technology contractor profile or the SAIC profile will recognize the shape of the problem: many contracts, several agencies, and a carrier that depends entirely on which award you are looking at.

How do you actually find the ManTech carrier for a specific claim?

The reliable method works backward from the worker, not forward from the company. You are not asking "who insures ManTech." You are asking "who insured this person, on this contract, on this date." Those are very different questions, and only the second one resolves a claim.

Start with the injury record itself. The LS-203 and any DOL case filing should name the employer and ideally the contract or duty station. If a carrier is already listed, verify it rather than trusting it. Carrier names on early filings are frequently a third-party administrator, not the actual insurer. We explain that trap in how to spot a TPA versus the actual DBA carrier.

Next, pin down the contract and the date. The carrier that covered ManTech in one period may not be the carrier two years later, because DBA coverage shifts on recompete, renewal, and policy cycles. Our piece on why DBA carriers change over time shows how often coverage moves under a single employer. The date of injury is not a detail. It is the axis the whole answer turns on.

Then resolve the employer name. ManTech filings appear under variations, acquired-company names, and subsidiary labels. If you search only the exact string "ManTech," you will miss records filed under an alias. Name variations routinely hide relevant filings across federal datasets, so alias resolution is part of every thorough search.

Finally, cross-reference federal contract data with coverage records. ClaimTrove links USAspending prime and subcontract awards, FOIA-sourced DBA coverage filings, SAM.gov entity records, and OALJ decisions, then resolves them against SME-confirmed employer-carrier mappings. That cross-referencing is what turns a contract name into a defensible carrier identification. No single public database does it alone.

What records prove ManTech DBA coverage, and which mislead you?

Not all records carry equal weight. Some establish coverage. Others look authoritative but point you at the wrong entity. Knowing the difference protects the claim and your time.

The strongest evidence ties a named carrier to a named contract during the injury period. FOIA-sourced DBA coverage filings are valuable here because they record the insurer associated with overseas labor, and ClaimTrove holds more than 150,000 such filings. Matched against the contract the worker served under, these filings move you from theory to documentation.

Federal contract data is the connective tissue. USAspending and FPDS records show which agency funded the work, the period of performance, and whether ManTech was prime or sub. That context tells you which insurance regime applies. Contract data rarely names the carrier directly, but it tells you which agency, period, and contract vehicle to look under.

The records that mislead are usually administrators and stale assumptions. A claims-handling firm listed on correspondence is not the insurer, and naming it as the carrier in a filing creates a defect you may have to cure later. Likewise, a carrier that covered ManTech five years ago tells you little about a current injury. Coverage is a moving target, and prior knowledge becomes a liability when it goes unverified.

SAM.gov entity records and identifiers like CAGE codes and UEIs help confirm you are looking at the correct ManTech entity rather than a similarly named firm or an acquired subsidiary. With more than 800,000 SAM.gov entity records in the dataset, identifier matching is how you avoid attaching a claim to the wrong corporate body. The point is convergence: when contract data, coverage filings, and entity records all point at the same carrier for the same period, you have an answer you can defend.

What should attorneys do first on a new ManTech DBA file?

Move fast on the facts that decide the carrier, and resist the urge to name an insurer early. The most expensive mistake in a ManTech file is committing to a carrier before the contract and date are nailed down.

Build the timeline first. Get the precise dates of overseas service, the duty station, and the program the worker supported. A contractor may have rotated across multiple ManTech contracts during a single deployment, and the carrier can differ between them. The injury date anchors which policy was in force.

Identify prime versus sub status next. If ManTech was a subcontractor on the relevant program, the responsible policy may sit with the prime under a flow-down clause. Confirming this early prevents you from chasing the wrong company's insurer for weeks. A structured carrier investigation workflow puts this check near the top of the sequence for exactly that reason.

Then run the name across variations and datasets. Search ManTech's aliases, acquired entities, and subsidiary labels so you do not miss filings indexed under a different name. The same discipline that surfaces hidden filings for any large prime applies here, and it is the difference between a thin file and a complete one.

Finally, document your chain. Whatever carrier you identify, record the contract, the period, the source filing, and the entity match that support it. A carrier identification that cannot be traced back to records is not usable in a dispute. ClaimTrove produces that sourced chain automatically by linking contract awards, coverage filings, and confirmed mappings, so the answer you bring to an informal conference or hearing stands up to scrutiny.

This tool provides information from public DOL records. It is not legal advice. Always verify with primary sources.