Why Does the LS-203 Matter More Than Any Other DBA Form?
Your new client hands you a crumpled LS-203 form. She worked as a logistics coordinator for a defense contractor in Kandahar. The employer name on the form says "AECOM." But the prime contract was held by a subsidiary that operated under a completely different name in Afghanistan. The carrier field is blank. The injury date listed is three weeks after the actual incident. Every one of these problems will create delays, and you need to catch them before OWCP routes the claim to the wrong parties.
The LS-203, officially titled "Employee's Claim for Compensation," is the foundational document in every DBA case. It is the form that puts the Department of Labor on notice that a worker is seeking benefits. Without it, there is no claim. With it filled out incorrectly, there is a claim that stalls in administrative limbo while OWCP tries to match it to the right employer, the right carrier, and the right district office.
Understanding every field on this form is not optional for DBA practitioners. The information your client enters on the LS-203 drives carrier identification, triggers employer reporting obligations, and sets the timeline for the entire administrative process. This guide walks through each section so you know exactly what to look for, what to correct, and what gaps require further investigation.
What Claimant Information Does the LS-203 Capture?
The top section of the LS-203 collects basic claimant identification: full name, Social Security number, date of birth, mailing address, and contact information. These fields seem straightforward, but they create matching problems downstream. OWCP uses this information to assign a case number and link the claim to any prior filings. If your client has filed a previous DBA or LHWCA claim, the name and SSN must match exactly or OWCP may create a duplicate file.
The address field determines district office assignment. OWCP has four district offices handling DBA claims: Jacksonville, New York, San Francisco, and the national office in Washington, D.C. Assignment depends on the claimant's home address, not the injury location. A contractor injured in Iraq but living in Texas gets routed to Jacksonville. One living in Oregon goes to San Francisco. Filing with the wrong district does not kill the claim, but it adds transfer time.
Pay attention to the marital status and dependent fields. DBA compensation rates change based on dependents. A claimant with a spouse and two children receives a higher maximum weekly rate than a single claimant. If your client's family situation has changed since the injury, update these fields. The difference in weekly benefits can be substantial over the life of a long-term disability claim.
What Do the Employer Fields Reveal About Your Case?
The employer section is where the LS-203 becomes a carrier identification tool. Three fields matter here: employer name, employer address, and insurance carrier name. Getting any of these wrong does not invalidate the claim, but it creates routing friction that delays the process by weeks or months.
The employer name field is the single most problematic entry on the entire form. Defense contractors operate under multiple names, subsidiaries, and joint ventures. Your client may know her employer as "AECOM," but the entity that held the DBA policy might be "AECOM Technology Corporation" or "URS Federal Services" (a predecessor company). ClaimTrove's database tracks over 214 employer alias mappings precisely because a single employer can appear under 20 different names in federal records.
The employer address should match the employer's principal place of business or the address on file with DOL. Overseas project office addresses are not helpful here. OWCP needs the U.S. business address to identify the employer in their systems and route correspondence. If your client only has an APO or overseas address, research the employer's registered U.S. office before filing.
The insurance carrier field is the one your client will almost certainly leave blank or fill in incorrectly. Most overseas contractors have no idea who their employer's DBA carrier is. They may guess their health insurance provider. They may write down a third-party administrator like Gallagher Bassett or ESIS, neither of which is the actual carrier. A TPA processes claims on behalf of the carrier, but the carrier is the entity legally responsible for paying benefits. This distinction matters for every filing you make after the LS-203.
How Should You Interpret the Injury and Medical Sections?
The injury description section asks for the date of injury, the nature of the injury, and how it occurred. For traumatic injuries, the date should be specific. For occupational diseases or hearing loss, the date is when the claimant first became aware the condition was work-related. Getting this date wrong has statute of limitations consequences under Section 913 of the LHWCA. The two-year clock starts from this date.
The location of injury field is critical for DBA jurisdiction. The DBA covers injuries occurring "outside the continental United States." If your client was injured on a U.S. military base in Germany, that qualifies. If she was injured at the employer's office in Virginia during a stateside rotation, it likely does not, though LHWCA coverage may apply if the work involves maritime or harbor activities. The country and specific location (base name, project site) help OWCP confirm DBA jurisdiction applies.
The medical treatment section asks the claimant to list treating physicians and hospitals. This information feeds into the LS-207 (medical report) process. Ensure your client lists all providers, including military medical facilities where they received initial treatment overseas. Military treatment records can be harder to obtain later, so documenting the facility name and dates early preserves your ability to request records through proper channels.
Watch for clients who describe their injury too narrowly. A client who writes "hurt my back" when she actually has a lumbar disc herniation with radiculopathy is underselling the claim from the start. While the LS-203 is not a medical document, the injury description sets OWCP's initial impression. Brief but medically accurate language serves your client better than vague descriptions.
What Does the Wage Information Section Tell You?
The wage section asks for the claimant's average weekly wage at the time of injury, pay rate, hours worked per week, and employment start date. These numbers directly determine the compensation rate. Under the LHWCA (which governs DBA benefits calculations), the average weekly wage determines the base for temporary total disability, permanent partial disability, and death benefits.
Overseas contractor wages create complications that domestic claims rarely face. Many DBA-covered employees receive a base salary plus danger pay, hardship differentials, overtime premiums, and housing allowances. Whether these components count toward the average weekly wage depends on how they are structured. If danger pay is a regular, recurring part of compensation, it generally gets included. One-time bonuses typically do not.
The employment start date matters for coverage verification. If your client started work on March 15 but the employer's DBA policy did not take effect until April 1, there is a gap. Carriers will scrutinize this. Cross-reference the employment start date against DOL records to verify the policy was in force on the date of injury. If there is a coverage gap, the employer may be liable as a self-insurer under Section 904(a) of the LHWCA.
Double-check the math on average weekly wage. Claimants frequently calculate it wrong, either by using gross pay without accounting for the correct statutory formula or by leaving out variable compensation components. An incorrect AWW on the LS-203 can reduce benefits for the entire life of the claim if no one catches it early.
How Does the LS-203 Connect to the LS-204 and LS-208?
The LS-203 does not exist in isolation. It triggers a chain of required filings from the employer and carrier. Understanding this chain helps you spot problems before they compound.
The LS-204 (Employer's Report of Injury) is the employer's version of events. The employer must file it within 10 days of learning about the injury. Compare the LS-204 against the LS-203 field by field. Discrepancies in injury date, injury description, or employment details signal factual disputes the carrier will exploit. If the LS-204 says the injury occurred "off duty" while the LS-203 says it happened during a convoy, you have a coverage fight brewing.
The LS-208 is the carrier's report of payments. Once the carrier begins paying (or controverts the claim), the LS-208 tracks what has been paid and when. If your case involves a carrier dispute, the absence of an LS-208 tells you the carrier has not accepted the claim or has not been properly notified. Either scenario requires action. If you are stepping into a case mid-process, check whether an LS-208 exists. No LS-208 often means the claim is stuck.
A fourth form worth knowing is the LS-202 (Employer's Supplementary Report). This updates the LS-204 with additional information about the claimant's return to work status, ongoing medical treatment, and wage changes. Missing LS-202 filings from the employer can indicate the employer has disengaged from the claims process, which may trigger penalties under Section 930(e) of the LHWCA.
What Are the Most Common LS-203 Mistakes That Delay Claims?
After reviewing thousands of DOL case records, certain LS-203 errors appear repeatedly. Catching them at intake saves months of administrative delay.
The most frequent error is using the wrong employer name. A claimant writes "KBR" when the actual employing entity was "Kellogg Brown & Root Services, Inc." or "KBR Technical Services, Inc." OWCP may not be able to match the filing to the correct employer record. When your client first comes in, run the employer name through federal contracting databases to identify the exact legal entity. Your initial intake process should include this verification step before any forms are filed.
The second most common error is listing a TPA instead of the actual carrier. Broadspire, Gallagher Bassett, and ESIS are claims administrators, not insurance companies. When a claimant writes "Gallagher Bassett" in the carrier field, OWCP cannot route the claim to the responsible insurer. You need the underlying carrier: the company that issued the DBA policy and bears the legal obligation to pay benefits.
Incorrect injury dates rank third. Claimants sometimes list the date they first sought medical treatment rather than the date the injury occurred. For occupational diseases, they may list a date years after the actual onset. Because the injury date triggers statute of limitations calculations, an error here can have consequences far beyond initial routing.
Missing or incomplete wage information rounds out the top errors. If the wage section is blank, OWCP cannot calculate a compensation rate. The claim sits until the information is provided, and carriers have little incentive to move quickly on claims with incomplete filings.
How Can You Fill LS-203 Gaps Before Filing?
The best time to fix LS-203 problems is before the form reaches OWCP. Every correction you make at intake eliminates a potential delay in the claims process.
Start with employer verification. Federal contracting databases, SAM.gov registrations, and DOL records all contain employer information that can confirm the correct legal entity name. ClaimTrove's database includes 865,232 SAM.gov entity records and 43,298 prime contract awards that help pin down exact employer names, addresses, and organizational structures. When a contractor operates through subsidiaries, the parent company name on the LS-203 may not match the entity that holds the DBA policy.
For carrier identification, the LS-203's blank carrier field is your research trigger. The claimant rarely knows this information, and the employer may not volunteer it. OWCP coverage records, DOL case summaries, and OALJ decisions all contain carrier-employer associations. ClaimTrove aggregates over 2,454 confirmed employer-carrier mappings across multiple federal data sources. When your client cannot name the carrier, these records can fill the gap before filing.
Verify the injury date against any available documentation: military incident reports, medical records from the initial treatment, supervisor reports, or the claimant's own contemporaneous notes. If there is any ambiguity, use the earliest supportable date. A date that is too late risks statute of limitations problems. A date that is too early can be corrected without the same consequences.
For wage information, request pay stubs, employment contracts, and W-2 forms from the period surrounding the injury. Overseas contractor compensation structures can be complex, and the claimant's memory of exact figures is unreliable months or years after the fact. Documentary evidence locks in the correct average weekly wage before the carrier has a chance to dispute it.
If the informal conference process reveals that the LS-203 contained errors, you can file an amended form. But prevention beats correction. Every hour spent verifying LS-203 information before filing saves days of back-and-forth with OWCP after filing.
ClaimTrove was built for exactly this pre-filing verification. Run an investigation on the employer name to confirm the correct legal entity, identify known carrier associations, and surface any alias or subsidiary complications before the LS-203 reaches OWCP. Start your investigation and file with confidence.