Why Do Contract Re-Competitions Matter for DBA Insurance?
Federal contracts do not last forever. Every major contract vehicle has a defined period of performance, typically a base period of five years with option years that can extend total performance to ten years or more. When the contract period ends, the government re-competes it. A new solicitation goes out. Contractors bid. A new awardee is selected. And the DBA insurance picture can change overnight.
This matters for DBA attorneys because the re-competition can change the employer, the carrier, or both. A worker who spent five years at a base under one prime contractor may find a different company running operations after the re-competition. That new company brings its own DBA insurance. The old company's carrier is no longer on the risk for new injuries. For claims arising during the transition, the question of which carrier is liable depends on exactly when the injury occurred relative to the contract changeover.
ClaimTrove's database of 43,298 contract awards includes period-of-performance data that shows when contracts started, when they expired, and when successor contracts began. This temporal data is essential for tracing carrier changes across contract generations.
What Are the Major Contract Vehicles That Get Re-Competed?
Several large contract vehicles dominate overseas defense contracting, and each has its own re-competition cycle. Understanding these vehicles helps DBA attorneys anticipate carrier changes.
LOGCAP (Logistics Civil Augmentation Program) is the Army's primary vehicle for base operations support. LOGCAP has gone through multiple generations. As detailed in our profile of KBR's DBA carrier history, each generation involved a re-competition that changed the prime contractor and, consequently, the DBA carrier. LOGCAP contracts cover dining facilities, laundry, maintenance, base construction, and dozens of other support services. Thousands of workers are employed under LOGCAP at any given time, making contract transitions a major event for DBA coverage.
AFCAP (Air Force Contract Augmentation Program) serves a similar function for Air Force installations. Like LOGCAP, AFCAP gets re-competed periodically, and the new awardee may select a different DBA carrier. AFCAP covers base operations, facility maintenance, and construction at Air Force installations overseas.
Worldwide Protective Services (WPS) contracts cover personal security details for State Department personnel overseas. These contracts have been re-competed multiple times, with different security companies winning each generation. The DBA carrier changes with each new awardee.
OMDAC-SWACA and similar theater-specific support contracts cover operations and maintenance at specific installations. These contracts are typically shorter in duration and re-competed more frequently, creating more frequent carrier transitions.
The common thread is that every re-competition creates a potential carrier change. The worker stays at the same base, doing the same job, but the employer changes and the DBA carrier changes with it. For claims arising near a transition date, knowing the exact changeover date is critical to identifying the correct carrier, which is why understanding temporal shifts in DBA coverage is essential for every practitioner.
What Happens During the Transition Period Between Contract Awardees?
Contract transitions do not happen instantaneously. When a new awardee wins a re-competition, there is a transition period during which the outgoing contractor demobilizes and the incoming contractor ramps up. This period typically lasts 60 to 180 days, depending on the complexity of the contract.
During the transition, the workforce composition is in flux. Some workers are retained by the new contractor. Others are released by the outgoing contractor and not hired by the incoming one. Still others may work for both contractors during the overlap, finishing tasks under the old contract while onboarding with the new one.
For DBA insurance, the transition period creates ambiguity. A worker who is injured during the transition may have an unclear employer. Are they still employed by the outgoing contractor? Have they already been hired by the incoming contractor? Are they in a gap between the two? The answer determines which carrier is liable.
The outgoing contractor's DBA policy covers its employees through the end of its contract period. The incoming contractor's DBA policy covers its employees from the start of the new contract. If the transition is clean, the handoff is simple. But transitions are rarely clean. Contract modifications extend the outgoing contractor's performance. The incoming contractor starts early under a "phase-in" arrangement. Workers receive separation notices from one company and offer letters from another on overlapping dates.
Attorneys handling claims from transition periods need precise documentation. The claimant's separation date from the outgoing contractor, the hire date with the incoming contractor, and the injury date relative to both create the factual framework for carrier identification. Payroll records are the best evidence. If the claimant was on the outgoing contractor's payroll on the injury date, that contractor's carrier is liable. If the claimant was on the incoming contractor's payroll, the new carrier is liable.
How Do Coverage Gaps Arise During Re-Competitions?
Coverage gaps occur when a worker falls between the outgoing and incoming contractors' insurance policies. These gaps are not supposed to exist. The DBA requires continuous coverage for workers on covered contracts. But in practice, administrative delays, paperwork errors, and transition confusion create situations where a worker lacks clear DBA coverage.
The most common gap scenario involves retained workers. When the incoming contractor hires a worker who was employed by the outgoing contractor, there may be a period between the worker's last day with the old employer and the first day with the new one. If the worker is injured during this gap, neither carrier may accept liability. The outgoing carrier argues the worker was no longer its insured's employee. The incoming carrier argues the worker had not yet become its insured's employee.
A second gap scenario involves workers who are not retained. A worker laid off by the outgoing contractor may remain at the overseas location while arranging repatriation. If injured during this period, the question arises whether the outgoing contractor's DBA coverage extends to the post-employment period. The BRB has addressed this in several cases, with results that depend on the specific facts, particularly whether the employer was still providing transportation or housing.
A third scenario involves new hires who arrive before the incoming contractor's DBA policy is effective. In the rush to mobilize, an incoming contractor may deploy workers to the overseas site before its DBA insurance paperwork is finalized. These workers may lack coverage for a brief period. The DBA filing requirements exist to prevent this, but compliance during rapid mobilization is imperfect.
For DBA attorneys, the existence of a potential coverage gap should trigger investigation into both carriers. Filing against both the outgoing and incoming carriers preserves the claim against whichever is ultimately found liable. Waiting to determine the "correct" carrier before filing can cost valuable time and may run into statute of limitations issues.
Why Does Fiscal Year Alignment Matter for Contract Transitions?
Federal contracts overwhelmingly align with the government's fiscal year, which runs from October 1 through September 30. Contract awards, funding obligations, and option year exercises cluster around September and October. This creates a predictable pattern of transitions that DBA attorneys can anticipate.
When a contract's option year is not exercised, the contract ends on September 30. The successor contract typically starts on October 1. This fiscal year boundary creates a hard transition point. A worker injured on September 29 falls under one carrier. A worker injured on October 2 may fall under a different carrier. The three-day window around the fiscal year boundary is a high-risk period for carrier disputes.
Not all transitions align perfectly with the fiscal year. Contract extensions, bridge contracts, and continuing resolutions can shift the transition date. A bridge contract is a short-term extension of the existing contract to cover the period between the old contract's expiration and the new contract's start. During a bridge contract, the original contractor and its carrier remain on the risk. But the bridge contract may have different terms, and the carrier may negotiate different conditions for the bridge period.
ClaimTrove's contract data includes modification records that show extensions and bridge contracts. When you search for a contract that ended in September 2015, the data may also show a modification extending performance through December 2015 and a new contract starting in January 2016. This level of detail prevents the assumption that the transition happened at the fiscal year boundary when it actually occurred months later.
For practitioners, the takeaway is clear: do not assume the transition date. Verify it through contract records. The fiscal year pattern is a starting point for your investigation, not the answer.
How Does the New Awardee Select a Different Carrier?
When a new contractor wins a re-competition, it brings its own DBA insurance. The government does not dictate which carrier a contractor must use (with the exception of mandatory carrier contracts for specific agencies, which are time-bounded and limited in scope). The contractor selects its DBA carrier based on price, coverage terms, and existing relationships.
This means that a base that was covered by Carrier A under the old contract may be covered by Carrier B under the new contract. The DBA market has a limited number of active carriers. ClaimTrove tracks 637 authorized DBA carriers, but the market is concentrated among a smaller number of carriers that write the majority of large contractor policies. Still, carrier changes at re-competition are common.
The carrier selection process happens during the bid phase, before the contract is awarded. Contractors include DBA insurance costs in their proposals. A contractor with access to lower DBA insurance rates has a competitive advantage. This dynamic means that DBA insurance pricing indirectly affects which contractor wins the re-competition, which in turn affects which carrier provides coverage at the site.
For DBA attorneys, the practical implication is that you cannot assume the same carrier covers the same base over time. A worker who was at a base for eight years may have been covered by two or three different carriers as the contract changed hands. Each re-competition is a potential carrier transition that must be investigated.
How Should Attorneys Handle Claims That Span a Contract Transition?
Claims that straddle a contract transition require careful analysis. The key principle remains that the carrier on risk at the date of injury bears liability. But several complications arise when the claim spans a transition.
For traumatic injuries, the analysis is straightforward. The injury date determines the carrier. If the injury occurred before the transition, the outgoing carrier is liable. If after, the incoming carrier. The transition date is a hard boundary.
For occupational diseases and cumulative trauma, the analysis is more complex. A worker who develops hearing loss over six years of generator exposure may have been employed by two different contractors during that period. The last responsible employer doctrine applies, but determining the "last injurious exposure" requires establishing which employer (and therefore which carrier) exposed the worker last.
If the worker continued in the same role under the new contractor after the re-competition, the new contractor is likely the last responsible employer, and its carrier bears liability. If the worker's role changed after the transition (moving to a less hazardous position), the analysis becomes more nuanced. The last employer to expose the worker to the specific hazard that caused the condition is liable, even if the worker subsequently worked for another employer in a different capacity.
PTSD cases present particular challenges across transitions. A worker may experience traumatic events throughout a multi-year deployment that spans one or more contract transitions. The "date of injury" for PTSD is typically the date of diagnosis or the date the worker became aware of the condition's work-relatedness. This date may fall under a different carrier than the carrier that was on risk during the traumatic events themselves.
The safest approach for claimant attorneys is to identify all carriers that covered the employer(s) during the relevant period and preserve claims against each. Let the carriers litigate among themselves about which one bears ultimate liability. The claimant's interest is in receiving benefits, not in resolving inter-carrier disputes.
What Data Sources Help Track Contract Transitions?
Tracking contract transitions requires combining several data sources. No single source provides a complete picture of when contracts changed hands and which carrier was on risk during each period.
USAspending contract records, which we break down in our guide on reading USAspending data for DBA investigations, show the prime contractor, the period of performance, and contract modifications. By searching for contracts at a specific location across time, you can identify when one prime's contract ended and another's began. ClaimTrove's 43,298 indexed contract awards include this temporal data.
DOL case summaries from prior claims involving the same employer or location may identify which carrier was on risk during earlier periods. ClaimTrove's 4,983 case summaries provide historical carrier data that supplements the contract records.
OALJ decisions from cases involving the same contract vehicle or employer provide detailed findings about carrier identity and policy periods. These decisions, particularly those that specifically addressed carrier disputes during transitions, create precedent that can be applied to new cases. ClaimTrove's 5,022 indexed OALJ decisions are searchable by employer, location, and date range.
FOIA database results may contain information about contract transitions that is not available in standard public databases. These results can identify specific transition dates, bridge contract arrangements, and workforce retention decisions that affect carrier liability.
ClaimTrove cross-references all of these sources to build a timeline of carrier coverage at specific locations. When you search for a base or an employer, the platform returns carrier information across time periods, flagging transitions and potential gaps. This temporal view is specifically designed for the re-competition scenario where multiple carriers may have covered the same location at different times.
What Should DBA Attorneys Take Away from Contract Re-Competitions?
Contract re-competitions are a predictable feature of federal contracting. They happen on regular cycles, they change the employer and carrier at overseas sites, and they create transition periods where coverage questions arise. None of this is surprising. But it is frequently overlooked by attorneys who assume the carrier identified at the beginning of an investigation is the carrier for the entire relevant period.
The discipline of checking the contract timeline against the injury date is fundamental to DBA practice. It takes minutes to verify. It prevents months of wasted effort pursuing the wrong carrier. And the data needed to perform this check is publicly available through contract databases, case summaries, and investigative tools.
Build the contract timeline early. Verify the carrier at the injury date. Check for transitions within the relevant period. And when the claim spans a transition, preserve claims against all potentially liable carriers until the question is resolved. This approach protects your client's interests regardless of how the inter-carrier dispute is resolved.
ClaimTrove's investigative platform was designed with contract transitions in mind. Search by employer, location, or contract number to see the full timeline of carrier coverage. Start your investigation and identify every carrier that may be liable for your client's claim.