A claimant walks into your office with a one-page injury report from a logistics job at Bagram in 2017. No carrier name. No policy number. The employer dissolved two years ago. The claimant does not remember who paid the doctor bills. You have a statute of limitations clock running and almost nothing to work with.
The single document that breaks this case open sits in a Department of Labor file you have not requested yet. The OWCP claim file holds the carrier of record, the LS-202 Employer's First Report, the notice of controversion, and the medical and wage records the prior adjuster pulled together. For Defense Base Act cases, that file is often the only place the insurance carrier identity appears in writing on government letterhead.
Most attorneys treat the OWCP claim file as an afterthought, requested late, when a hearing looms. That is a mistake. The file drives carrier identification, coverage verification, and your theory of liability. The problem is that getting it is slower and more procedurally specific than people expect. A FOIA request to the wrong office, missing a representation form, or a vague description can add months to a timeline that is already tight.
This guide walks through both paths to the file: the direct request as the claimant's authorized representative, and the formal Freedom of Information Act request. You will learn what the file actually contains, where to send the request, what timing to plan for, and how to avoid the delays that sink early case strategy. The goal is simple. Get the document that names the carrier into your hands before the limitations period, not after.
What Is in the OWCP Claim File and Why It Matters?
The OWCP claim file is the government's complete administrative record of a workers' compensation claim under the Longshore and Harbor Workers' Compensation Act, which the Defense Base Act extends to overseas federal contractors. For DBA cases, the file is administered by the Division of Longshore and Harbor Workers' Compensation, known as DLHWC.
A complete file typically contains several categories of documents. The LS-202 Employer's First Report of Injury identifies the employer and, critically, the insurance carrier. The LS-203 Employee's Claim for Compensation establishes the claim itself. You will also find the LS-201 notice of injury, any LS-207 notice of controversion where the carrier disputed the claim, and the LS-208 notice of final payment if benefits were paid and stopped.
Beyond the forms, the file holds correspondence between the carrier and the district office, medical reports, wage statements, and the district director's memoranda. When a case has been litigated, the file may include hearing transcripts and informal conference recommendations.
The carrier name is the prize. In a clean case, the LS-202 names the carrier directly. But DBA files are rarely clean. The named entity is often a third-party administrator, not the actual underwriter. The carrier may have changed between the policy year and the date the claim was filed. The employer may appear under a subsidiary name you do not recognize. Reading these forms correctly is its own skill, and our field-by-field guide to the LS-203 form walks through where the coverage signals hide.
The file also shows you the procedural history. If the carrier filed an LS-207 controverting the claim, you know the dispute is live. If an LS-208 shows benefits terminated, you have a date to anchor your reinstatement argument. None of this is visible from the claimant's memory or a single intake form. It lives in the OWCP file.
How Do You Request the OWCP File as the Claimant's Representative?
The fastest path to the file is not FOIA. It is a direct request as the claimant's authorized legal representative. When you represent the injured worker, you are entitled to the claim file without the procedural overhead of a Freedom of Information Act request, because the records belong to your client's claim.
To do this, you need three things in place. First, a signed representation authorization from the claimant, often the OWCP form or a clear letter of representation on firm letterhead. Second, the OWCP case file number if you have it, which dramatically speeds retrieval. Third, the correct district office that holds the file.
DBA cases are handled by specific DLHWC district offices depending on where the claim was administered. Overseas DBA claims are frequently routed through the district offices that handle Defense Base Act caseloads, and the New York and other district offices carry large volumes of historical DBA filings. If you do not know which office holds the file, the national DLHWC office can direct you, but that adds time.
Your request letter should identify the claimant, the employer, the approximate date of injury, and the case number if known. Attach the representation authorization. Ask specifically for the complete claim file, including the LS-202, all coverage correspondence, and the carrier and third-party administrator information. Vague requests get vague responses. Specificity gets you the carrier name.
The direct-representative route is generally faster than FOIA because it skips the formal disclosure review. But it still depends on the district office locating and copying a physical or scanned file. For older claims, files may be archived offsite, which adds retrieval time. Plan for weeks, not days, even on the fast path.
One trap deserves attention. If your client worked for several contractors overseas, the file you request may not reflect the full employment picture, and the responsible carrier may not be the one named in the first file you pull. This is common in deployment-heavy careers, and it interacts directly with how concurrent employment affects DBA claims. Request files for every employer in the relevant period.
When Should You Use a Formal FOIA Request Instead?
FOIA becomes the right tool when you do not yet represent the claimant in an active OWCP proceeding, when you need records on a related claim you are not party to, or when the direct-representative route stalls and you want a request with statutory teeth and deadlines.
The Freedom of Information Act gives any person the right to request federal agency records. For DBA files, you submit the FOIA request to the Department of Labor, specifically routed to OWCP. The DOL maintains an online FOIA portal and accepts requests by mail. The request must reasonably describe the records you want so the agency can locate them.
A strong FOIA request for a DBA claim file includes the claimant's name, the employer name, the approximate injury date, the OWCP case number if known, and the country where the work occurred. The more identifying detail you provide, the faster the search. A request that says "all DBA records for John Smith" without an employer or date will trigger a clarification letter and reset your clock.
FOIA carries a statutory response framework. The agency must respond to a standard request within 20 business days, though this is a response deadline, not a delivery deadline. In practice, OWCP FOIA processing for claim files routinely runs far longer because of volume, the need to review for exemptions, and the manual nature of pulling longshore files.
Privacy is the major exemption issue. Claim files contain medical records and personal information about the injured worker. If you are not the claimant or their representative, the agency will redact or withhold third-party private information under FOIA Exemptions 6 and 7(C). A privacy waiver signed by the claimant, attached to your FOIA request, removes much of this friction and gets you a far more complete file.
The strategic point is this. If you can represent the claimant and submit a signed authorization, do that first. Reserve FOIA for situations where representation is not yet in place or where you need leverage of a formal statutory request.
How Long Does It Take and How Do You Plan Around It?
Timing is where early case strategy lives or dies. The honest answer is that OWCP claim file requests are slow, and you should build your timeline around that reality rather than hoping for speed.
A direct-representative request to a district office can produce the file in roughly two to eight weeks when the case number is known and the file is recent and onsite. Older files archived offsite stretch that to several months. There is no statutory deadline on this route, so it moves at the office's pace.
FOIA requests carry the 20-business-day response requirement, but for DBA claim files, actual delivery commonly takes 90 days and can run past 200 days for complex or high-volume requests. The DOL publishes annual FOIA reports showing significant backlogs in workers' compensation record requests. You can request expedited processing if you can show a compelling need, such as an imminent statutory deadline, but expedited treatment is granted narrowly.
Here is the planning problem. The DBA statute of limitations under 33 U.S.C. 913 generally requires filing within one year of injury or last payment of compensation. If you are waiting on a FOIA file to identify the carrier before filing, you may run out of clock. The solution is to file the claim to preserve the deadline and pursue the file in parallel, rather than treating file retrieval as a prerequisite to action.
This is exactly where independent carrier identification changes the math. Instead of waiting 90 to 200 days for OWCP to mail you a file that names the carrier, you can identify the likely carrier, prime contractor, and coverage history from public federal records in minutes. ClaimTrove pulls the underlying carrier, employer alias, and DBA decision data so you can file informed and use the eventual OWCP file to confirm rather than discover. The file still matters for the official record. It just stops being the bottleneck.
Build your workflow in this order. Identify the probable carrier and contractor chain immediately from public data. File the claim to stop the clock. Submit the direct-representative request and, where appropriate, a parallel FOIA request. Use the returned file to confirm carrier identity, lock down policy dates, and surface the controversion history.
What Coverage Facts Does the File Reveal That You Cannot Guess?
The OWCP file answers questions that no amount of guessing resolves. The first is the identity of the actual underwriting carrier as opposed to the third-party administrator who handled correspondence. DBA adjusting is dominated by a handful of TPAs whose names appear all over claim files, while the real carrier sits behind them. Confusing the two leads to demands sent to the wrong party and missed coverage.
The second is the policy effective dates. Carriers shift over the life of a contract. The carrier that covered an employer in one fiscal year is frequently not the carrier two or three years later. The file's coverage correspondence pins down which carrier was on the risk on the date of injury, which is the only date that matters for liability.
The third is the controversion posture. Whether and when the carrier filed an LS-207, what grounds it asserted, and whether it ever accepted any portion of the claim all shape your strategy. If the carrier is positioning to shift liability, the file often shows the first signals, including any move toward a Section 8(f) transfer of liability.
The file also feeds downstream decisions. The wage records inform your average weekly wage calculation. The medical history shapes which experts you retain, including vocational rehabilitation experts when loss of wage-earning capacity is at issue. And the documented benefit payments establish the baseline for any Section 28 attorney fee petition down the line.
The point is not that the file is interesting. It is that the file contains specific, dated, carrier-level facts that your case theory depends on, and that you cannot reliably reconstruct from a claimant's recollection. Requesting it early, and pairing it with independent carrier research, is the difference between building a case on evidence and building one on assumption.
Move First, Confirm Second
The OWCP claim file is the authoritative record, and you should always request it. But it is slow, and its arrival cannot be the trigger for your first move. The carrier identity, the prime contractor, and the coverage history are discoverable from public federal contracting and DOL decision data right now, before any FOIA response lands.
Run the investigation first, file to preserve the deadline, and submit your file requests in parallel. Start a ClaimTrove investigation to surface the likely carrier, employer aliases, and DBA decision history in minutes, then use the OWCP file to confirm what your research already told you. The file stops being a bottleneck and becomes what it should be: confirmation, not discovery.