Your Client Filed an LS-203 Three Months Ago. Why Has Nothing Happened?
Your paralegal filed the LS-203 on behalf of an injured defense contractor who worked security at a forward operating base in Afghanistan. The claim went to OWCP. Then silence. Three months later, the client calls asking what is happening. You check the file and realize there has been no acknowledgment, no carrier response, no conference scheduled. The claim is sitting in a queue.
This scenario plays out thousands of times per year. Between FY2004 and FY2015, DOL received over 94,000 DBA cases according to OWCP annual reports. Each one entered a processing pipeline with multiple stages, handoffs between offices, and carrier response periods that can stretch indefinitely without aggressive follow-up. The average DBA claim does not resolve in weeks. It resolves in months or years.
Understanding where delays occur gives you leverage. When you know that OALJ hearing backlogs run 12 to 18 months, you can set client expectations on day one. When you know that carriers routinely request 60-day extensions on initial responses, you can plan your investigation timeline around those gaps rather than waiting passively for DOL to move your file forward.
This article breaks down each stage of DBA claims processing, identifies the bottlenecks that add months to resolution, and explains what attorneys can do to compress timelines where the regulations allow it.
What Are the Stages of DBA Claims Processing at DOL?
DBA claims processing follows a structured sequence, but each stage operates on its own timeline with its own bottleneck risks. The pipeline runs through three DOL offices before a case reaches formal adjudication.
Stage 1: LS-203 Filing and OWCP Intake. The process starts when the employer or claimant files the LS-203 (Notice of Employee Injury or Death) with the Office of Workers' Compensation Programs. OWCP assigns a case number and routes the file to the appropriate district office. This intake step typically takes 30 to 90 days, though complex filings involving overseas employers or missing carrier information can sit longer.
Stage 2: Carrier Notification and Response. Once OWCP identifies the responsible carrier, it sends notice and allows the carrier a response period. Carriers have 14 days to begin benefit payments or controvert the claim under 33 U.S.C. Section 914. In practice, carriers regularly request extensions, and the average response window stretches to 30 to 60 days. Controversion triggers the next phase.
Stage 3: Informal Conference. OWCP schedules an informal conference between the claimant, employer, and carrier. The district director attempts to mediate a resolution. Conference scheduling depends on district office caseloads and can take 60 to 180 days from the date of controversion. Some district offices manage DBA cases faster than others based on staffing levels and geographic assignment.
Stage 4: Formal Hearing (OALJ). If the informal conference fails to resolve the dispute, either party can request a formal hearing before an Administrative Law Judge at the Office of Administrative Law Judges. This is where the biggest delays occur. OALJ hearing backlogs regularly stretch 12 to 18 months from referral to hearing date. ClaimTrove's database contains 5,022 OALJ decisions spanning 1993 to 2025, and the volume of pending cases consistently outpaces ALJ availability.
Stage 5: Benefits Review Board Appeal. After the ALJ issues a decision, either party can appeal to the Benefits Review Board. BRB review adds another 12 to 24 months. Federal circuit court review after BRB adds yet another layer of delay.
Where Do the Biggest DBA Processing Delays Actually Occur?
Three bottlenecks account for the majority of processing time in contested DBA claims. Each one is structural, meaning they persist regardless of how well you prepare your filing.
OALJ Hearing Backlogs. The single largest delay in the DBA system is the wait for a formal hearing. ALJs handle both LHWCA and DBA cases on consolidated dockets. DBA cases compete for calendar time with thousands of domestic longshore claims. When an ALJ in a district office carries 150 or more active cases, new referrals wait 12 to 18 months for a hearing date. During peak DBA filing years from 2008 through 2014, some districts reported backlogs exceeding 24 months.
Carrier Identification Gaps. Before OWCP can even notify the carrier, it needs to know who the carrier is. For subcontractors working under prime contracts overseas, carrier identification alone can consume weeks of attorney time. Employers change carriers every 3 to 5 years on average. Subcontractors may not carry their own DBA policy, relying instead on the prime's coverage. When the LS-203 lists an employer but no carrier, OWCP must investigate, adding 30 to 90 days to the intake stage.
Carrier Extension Requests. Carriers have a financial incentive to delay. Every additional month before benefits begin is a month of reduced liability exposure. Carriers request extensions for medical records, independent medical examinations, and investigation of employment status. These requests are routinely granted, adding 30 to 90 days at the response stage and again before informal conferences.
How Long Does the Full DBA Claims Timeline Take from Filing to Resolution?
Adding up each stage for a contested DBA claim produces a timeline that surprises most clients and many attorneys who are new to the DBA practice area.
Uncontested claims where the carrier accepts liability and begins payments typically resolve within 60 to 120 days. These are the straightforward cases: clear employer-carrier relationship, undisputed injury, and a willing carrier.
Contested claims through informal conference typically take 6 to 12 months. This includes 30 to 90 days for OWCP intake, 30 to 60 days for carrier response, and 60 to 180 days for conference scheduling and completion.
Contested claims through OALJ hearing run 18 to 36 months. The 12 to 18 month OALJ backlog stacks on top of the pre-hearing stages. If the case involves complex medical evidence, multiple employers, or statute of limitations disputes under Section 913, preparation time extends the hearing date further.
Claims appealed to BRB add 12 to 24 months beyond the ALJ decision. A DBA claim that goes through every stage of adjudication and appeal can take 4 to 5 years from initial filing to final resolution. Circuit court review beyond BRB pushes that timeline past 6 years.
What Causes Incomplete Filings to Stall at OWCP?
OWCP returns or holds filings that lack required information. The most common deficiencies that stall DBA claims at the intake stage involve three categories of missing data.
Missing or incorrect carrier information. The LS-203 form asks for the employer's insurance carrier name and policy number. Many injured contractors do not know their employer's DBA carrier. Employers, particularly subcontractors, sometimes cannot identify their own carrier because coverage was arranged through a prime contractor's program or a third-party administrator. When the carrier field is blank or wrong, OWCP must independently verify coverage before processing can continue.
Employer identification problems. Defense contractors frequently operate under multiple corporate names, subsidiaries, and joint ventures. An employer listed as "DynCorp" on the LS-203 may actually be DynCorp International, DI Operated Systems, or a subsidiary acquired by Amentum. ClaimTrove tracks 214 employer alias mappings across 30 or more corporate families because this name confusion directly delays DOL processing.
Incomplete injury documentation. Claims missing physician statements, hospital records, or clear descriptions of how the injury relates to employment get flagged for additional information requests. Each request-and-response cycle adds 30 to 60 days. Overseas injuries compound this problem because medical records from military treatment facilities, host-nation hospitals, or medevac chains arrive in fragments.
What Can Attorneys Do to Accelerate DBA Claims Processing?
You cannot eliminate DOL processing delays, but you can remove the variables you control. The attorneys who move DBA claims fastest share several practices.
Identify the carrier before filing. The single most impactful step is filing the LS-203 with accurate carrier information from day one. When OWCP receives a filing with a verified carrier name and policy number, it skips the carrier investigation step entirely. This can save 30 to 90 days at intake. Rather than waiting for DOL to identify your carrier through its own process, run your own carrier investigation before submitting the claim.
File the LS-203 with complete documentation. Attach all available medical records, employment verification, and contract documentation with the initial filing. Front-loading documentation reduces the number of information request cycles and prevents your claim from entering the "pending additional information" queue.
Track carrier response deadlines. The 14-day payment or controversion window under Section 914 is often treated as a suggestion rather than a requirement. When carriers miss the deadline, document the delay and raise it at the informal conference. ALJs take notice of carrier delay patterns, and documented noncompliance strengthens your position if the claim proceeds to formal hearing.
Request expedited hearings when warranted. OALJ allows motions to expedite hearing dates in cases involving terminal illness, extreme financial hardship, or elderly claimants. These motions do not guarantee faster scheduling, but they move your case ahead of the standard queue in districts where ALJs have discretion over calendar management.
Pursue interim benefits aggressively. While waiting for formal adjudication, pursue every available interim benefit. Carriers are required to pay medical benefits while contesting indemnity amounts. Section 14(f) penalties apply when carriers fail to pay timely. These pressure points create financial incentives for carriers to settle rather than litigate through the full OALJ backlog.
Why Carrier Identification Is the Delay You Can Actually Fix
Most DBA processing delays are systemic. You cannot hire more ALJs or speed up BRB review. But carrier identification is the one bottleneck that sits entirely within your control as the filing attorney.
Our analysis of 4,983 DOL case summary records across FY2009 through FY2024 shows that carrier coverage shifts are common. Employers switch carriers every few years, and the carrier covering your client's employer in 2018 may not be the same one covering them in 2023. Filing with outdated carrier information creates the same intake delay as filing with no carrier information at all.
The traditional approach to carrier identification involves calling the employer, requesting a certificate of insurance, filing FOIA requests with DOL, and waiting for responses. Each step takes days or weeks. When the employer is a dissolved subcontractor or an overseas entity that does not respond, the process stalls entirely.
ClaimTrove was built to eliminate this specific delay. By cross-referencing 18 federal data sources, including 43,298 contract awards, 4,983 DOL case summaries, and 2,454 verified employer-carrier mappings, ClaimTrove identifies the likely DBA carrier in seconds rather than weeks. You get a carrier name, confidence level, and supporting evidence before you file the LS-203, not months after.
Do not wait months for DOL processing to tell you what ClaimTrove can show you now. Run a ClaimTrove investigation and file your LS-203 with verified carrier information from day one.