Why Does the First Meeting Determine the Speed of Your Entire DBA Case?
A new client walks into your office. She was injured in Bagram, Afghanistan in 2016. She worked for a company she calls "DynCorp." She has no insurance paperwork. She cannot name her supervisor. She thinks someone from "Gallagher" handled her initial claim. She wants to know when you can file.
You have two paths from here. The first: spend four to six weeks chasing employer name variations, calling TPAs that cannot confirm the carrier, and filing FOIA requests that return months later. The second: ask the right questions now and resolve the carrier identification in days. The difference between those two paths is not legal skill. It is intake discipline.
DBA carrier identification is the threshold bottleneck in every Defense Base Act claim. Before you can file the LS-203, before you can calculate benefits, before you can negotiate anything, you need the carrier name. ClaimTrove's database of 2,454 employer-carrier mappings shows that carrier assignments shift every 3-5 years for most contractors. An employer that used AIG in 2012 may have switched to Starr by 2016 and Zurich by 2020. The injury date your client gives you determines which carrier window applies, and a wrong date sends you chasing the wrong insurer entirely.
Every data point you collect at intake either accelerates or delays your investigation. Here are the eight questions that experienced DBA attorneys never skip.
What Was the Employer's Exact Name, and Why Do Variations Matter?
This is the single most consequential intake question. Your client will give you a shorthand name. "KBR." "DynCorp." "Triple Canopy." That shorthand may match zero records in federal databases.
The legal business name on a SAM.gov registration, a DOL filing, and a USAspending contract award are often three different strings for the same company. ClaimTrove tracks 214 employer alias mappings across 30+ corporate families. "DynCorp" alone maps to DynCorp International LLC, DynCorp Technical Services, DI Operated Systems, and several Amentum-era variants after the 2020 acquisition. Searching only "DynCorp" in DOL records misses filings under every other alias. For a deeper look at this problem, see Alias Resolution: When the Same Employer Has 20 Different Names.
At intake, push for specifics. Ask your client to check old pay stubs, W-2s, or offer letters. The name on the W-2 is typically the legal entity name, which gives you the best starting search term. Ask if the company was acquired, renamed, or merged during their employment period. Many clients know about corporate changes even if they do not know the legal implications.
Also ask: "Did your employer operate under any other name while you were there?" Clients who worked for Blackwater often know it became Xe Services and then Academi. Clients who worked for PAE may know it merged into Amentum. These breadcrumbs save days of alias resolution later.
When Exactly Did the Injury Occur, and How Does That Date Drive Carrier Identification?
The injury date is not just a statute of limitations checkpoint. It is the primary temporal key for carrier identification. DBA insurance policies renew annually. The carrier on the policy in March 2015 may differ from the carrier in November 2015 if the employer switched at renewal.
ClaimTrove's investigation engine uses the injury date to filter carrier matches by temporal proximity. Our scoring model weights carrier evidence by time distance: a match within one year of the injury scores at full weight, within two years at 0.9, and evidence more than five years removed drops to 0.55. A vague injury date, like "sometime in 2016," forces the engine to cast a wider temporal net and reduces confidence in the top result.
Push for precision at intake. Ask for the month and day, not just the year. If your client cannot remember the exact date, ask what season it was, what project they were working on, or what base rotation they were in. Military contractor deployments follow predictable rotation patterns. Knowing whether the injury was during a spring or fall rotation can narrow the window from 12 months to 3.
For repetitive stress injuries or occupational diseases, ask for both the first symptom date and the last day of exposure. The DBA uses the date of last exposure for occupational disease claims, and that date may fall under a different carrier than the first symptom date. Getting this wrong means filing against a carrier that will immediately deny coverage based on the policy period.
Where Was Your Client Working, and Why Does Location Unlock the Contracting Chain?
Country and base location are the second-most-powerful search keys in DBA carrier identification. Certain agencies mandated specific carriers for all contracts in certain regions during specific time periods. If your client was working on a USAID-funded project overseas any time after March 2010, the carrier is almost certainly Allied World, because USAID has mandated that carrier through successive contract periods. The State Department mandated CNA from July 2001 through July 2012.
These agency mandates are time-bounded, not permanent. An attorney who assumes the State Department still requires CNA in 2026 will waste weeks pursuing the wrong carrier. The State Department moved to open-market procurement in August 2012 after receiving zero bids on its re-solicitation. Understanding these mandate windows requires the kind of temporal data that ClaimTrove tracks across 8 mandatory agency contract records.
Beyond mandates, location narrows the contract universe. ClaimTrove's database of 43,298 prime contract awards is filterable by country. If your client was in Afghanistan, that immediately connects to our dataset of 29,902 contractor records from FOIA database results covering 2009-2018, with 5,273 distinct prime contractors and 12,456 contracts. A specific base name, like Bagram or Camp Leatherneck, further narrows which primes and subs operated there during the injury period.
Ask your client: "What country were you in? What base or installation? What city or province?" Also ask about nearby landmarks or base names if they are unsure of the official designation. Many clients know the informal name ("the base outside Kabul") but not the military designation.
Who Was the Prime Contractor, and Why Does the Contracting Chain Matter?
Your client may not know the prime contractor, but the question is still worth asking. Subcontractor employees often wear prime contractor badges, attend prime contractor safety briefings, or work alongside prime contractor employees. A client who says "we were all under KBR" may be identifying the prime contractor even though their actual employer was a third-tier sub.
The prime contractor matters because DBA insurance often flows through the contracting chain. When a subcontractor fails to carry its own DBA policy, the prime's policy typically covers sub-tier workers. Section 904(a) of the LHWCA, applied through the DBA, makes the prime contractor statutorily liable if the subcontractor was uninsured. ClaimTrove's investigation engine traces these chains using 4,315 sub-award records that map prime-to-sub relationships. For a complete walkthrough of how this tracing works, see The 5-Step DBA Carrier Investigation Workflow.
At intake, ask: "Who held the main government contract at your work site?" and "Did your company work under or for a larger company?" Many clients can identify the prime even if they do not know the formal relationship. Also ask about the contract name or number if they have it. LOGCAP, AFCAP, and CONCAP are the three mega-contracts that cover most base support operations. A client who says "I was on the LOGCAP contract" has just given you a major shortcut.
If the client names a contract like LOGCAP, you can immediately narrow the prime contractor universe to the handful of companies that held those task orders during the relevant period. That alone may resolve the carrier question without additional research.
How Was Your Client Paid, and What Does Payroll Reveal About the Employer Entity?
Payment records are the most underused intake data point in DBA cases. How your client was paid reveals the legal entity that employed them, which is often different from the company name they use conversationally.
Ask: "Who signed your paychecks? What name appeared on direct deposits? Were you paid through a staffing agency?" Third-country national (TCN) workers are frequently paid through intermediary staffing companies headquartered in countries like India, the Philippines, or Nepal. The staffing company, not the prime or sub, is the legal employer for DBA purposes. ClaimTrove's investigation engine searches across 865,232 SAM.gov entity records to identify these intermediary employers and trace them back to the contracting chain.
Also ask about currency and payment frequency. Employees paid in U.S. dollars through a U.S. entity are straightforward. Employees paid in local currency through a foreign subsidiary create complications because the foreign entity may not carry DBA insurance, triggering red flags that experienced attorneys watch for in every investigation.
W-2 forms, pay stubs, and bank statements from the employment period are the most valuable documents your client can bring to intake. The employer identification number (EIN) on a W-2 is a direct lookup key in federal databases. It eliminates name-variation ambiguity entirely because the EIN is unique to the legal entity.
What Supervisor Name and Contact Information Does Your Client Remember?
Supervisor names serve two functions in DBA investigations. First, they help verify the employment relationship if the employer disputes it. Second, and less obviously, supervisors often appear in OALJ decisions and DOL filings related to the same employer. A supervisor name can be a secondary search term that surfaces carrier information from cases involving other injured workers at the same site.
Ask your client: "Who was your direct supervisor? Do you remember their title? Do you have a phone number or email for them?" If the client was working on a large base, ask about the site manager or project manager. These names often appear in contract documentation and safety inspection records. ClaimTrove's database includes 15,005 OSHA inspection records that list site managers and responsible parties.
Supervisor names also matter for the LS-203 filing itself. The form requires information about the employer's point of contact. If the employer is unresponsive, which happens frequently with dissolved or acquired companies, the supervisor name gives you a human lead to track down insurance information directly. Many supervisors maintained their own records of the DBA carrier because they were responsible for reporting injuries.
What Documents Should Your Client Bring to the First Meeting?
The ideal intake produces a folder of employment documents that your client may not realize they still have. Ask them to search email archives, filing cabinets, and phone photos for any of the following before the first meeting.
Priority documents: W-2 forms (employer EIN and legal name), deployment orders or letters of authorization (contract name and prime contractor), pay stubs (employer entity and payment structure), offer letter or employment contract (employer legal name, work location, and job title), insurance cards or correspondence (carrier or TPA name), and any medical records from the overseas injury (treating facility and initial claim filing).
Secondary documents: badge or credential copies (base name and employer name as printed), performance reviews (supervisor names), travel authorizations or visa documents (employer sponsorship details), and photos from the work site (base identification, company logos on equipment).
Clients frequently have more documentation than they realize. Text messages and emails from the employment period often contain employer names, supervisor names, and base locations embedded in email signatures and message threads. Encourage your client to search their email for the employer name before the meeting. Understanding how DBA differs from state workers' comp will also help you explain to your client why these federal-specific documents matter more than what they might have gathered for a standard state claim.
How Does ClaimTrove Turn These Intake Answers Into Carrier Identification?
Every data point on this checklist maps directly to a search parameter in ClaimTrove's investigation engine. The employer name triggers alias resolution across 214 known name variations. The injury date activates temporal scoring that weights evidence by proximity. The country filters 43,298 contract awards to the relevant geography. The awarding agency checks against mandatory carrier periods. The prime contractor name traces the subcontractor chain through 4,315 sub-award relationships.
ClaimTrove runs all 18 data sources in parallel, not sequentially. While a manual investigation means opening USAspending in one tab, DOL case summaries in another, and OALJ decisions in a third, our engine queries every source simultaneously and cross-references the results in seconds. The carrier waterfall ranks matches by confidence level: deterministic agency mandates at the top, direct DOL evidence next, prime contractor chain inference below that, and statistical correlation as a fallback.
The more intake data you collect, the higher the confidence score on your carrier result. An investigation with employer name, injury date, country, and awarding agency will typically return a HIGH confidence carrier match. An investigation with only an employer nickname and approximate year produces a result, but at lower confidence that requires manual verification. For a full walkthrough of the claims process after you have identified the carrier, see DBA Claims Process: A Step-by-Step Guide for Attorneys.
Stop spending weeks on carrier identification. Run your first ClaimTrove investigation with the intake data you already have and get carrier results in under 10 seconds.