Your client worked for a defense logistics company in Kandahar in 2014. He filed nothing at the time. By the time he walks into your office in 2026, that company has been sold twice. The name on his old badge no longer exists as a legal entity. The contract that sent him overseas was signed over to a buyer through a process called novation. Now you have to figure out who owns his Defense Base Act claim.
This is one of the hardest fact patterns in DBA practice. A corporate sale does not erase a workers' compensation liability. It also does not automatically move that liability to the buyer. The answer turns on how the deal was structured, which contract was transferred, and the date your client got hurt.
This article explains how a contract novation works, what it does to the DBA claim attached to the transferred vehicle, and who counts as the successor in interest. You will see where the paper trail lives in federal records. You will also learn why the sale date almost never controls which carrier pays.
What is a contract novation in federal contracting?
A novation is the government's formal recognition that a new company has taken over an existing federal contract. It is governed by FAR Subpart 42.12. When a contractor sells the assets tied to a government contract, the government does not automatically start dealing with the buyer. The parties must execute a novation agreement first.
The agreement has three signers: the original contractor as transferor, the new owner as transferee, and the government. Under FAR 42.1204, the government recognizes a successor when assets transfer, not merely stock. A pure stock purchase usually calls for a change-of-name agreement instead, because the original legal entity survives the deal.
That distinction drives your whole investigation. An asset sale puts a brand-new party on the contract. A stock sale keeps the same corporate entity under a new parent. The DBA claim behaves very differently in each case, and the federal footprint looks different too. Reading the wrong footprint sends you chasing the wrong company.
Novation is common in this sector because contract vehicles are valuable. A buyer often wants the backlog of task orders more than the office furniture. The government protects itself by refusing to recognize any transfer it did not approve in writing.
Timing matters too. A novation can take months to finalize while the contractor keeps working under the old name. During that gap, an injured worker's claim may predate the recognized transfer entirely. That is another reason the effective date on the novation agreement deserves close reading against your client's injury date.
Does a novation move the DBA claim to the new owner?
Here is the point most attorneys miss. A novation transfers responsibility for performing the rest of the contract. It does not automatically transfer a workers' compensation liability that already attached to an injured worker. Those are two separate obligations that travel on separate tracks.
Under the Defense Base Act at 42 U.S.C. 1651, coverage runs through the Longshore and Harbor Workers' Compensation Act. The insurance policy in force on the date of injury is the policy that answers the claim. A later sale of the company does not cancel that policy's duty to pay.
Every covered contract carries the workers' compensation clause. The FAR 52.228-3 Defense Base Act insurance clause requires the contractor to keep DBA coverage in force during performance. When the injury happened, some carrier was on that risk. That carrier stays liable even after the contract is signed over to a buyer.
So the buyer inherits the job going forward. The old carrier keeps the open claim. The successor may still surface in your investigation, because it now controls personnel files and sometimes defends open matters. But the benefit dollars usually flow from the policy that existed at the exact moment of injury.
Who is the successor in interest for a DBA liability?
Successor in interest means different things in different rooms. In contracting, it means the company the government now recognizes on the vehicle. In workers' compensation, it can mean the entity that assumed the injured worker's benefit obligations. Those two successors are not always the same business.
A purchase agreement can assign open claims to the buyer, keep them with the seller, or park them with a runoff insurer. The government's novation says nothing about that private allocation. You have to read the deal, not just the contract file, to know who agreed to carry the liability.
This is exactly why the name on the retainer is often not the entity that owns the claim. The company your client remembers, the company on the contract, and the company that owes benefits can be three different legal names living inside one corporate family.
The picture shifts again for self-insured employers. A self-insured contractor pays benefits directly instead of through an outside carrier. When one of these is absorbed during defense contractor consolidation, the buyer often assumes the self-insured obligations along with the assets. There is no third-party policy to fall back on, so the successor entity is your only target.
Get this wrong and you send demand letters to a company with no duty to pay. For an insured employer, the runoff carrier answers. For a self-insured employer, the successor entity answers. Naming the right one is the entire game.
Why does the injury date decide the carrier, not the sale date?
The single most reliable anchor in a novation puzzle is the date of injury. That date fixes which policy was in force. It fixes which carrier underwrote the risk. Corporate events that happen years later do not move that anchor at all.
Carriers rotate on the same contract far more often than attorneys expect. A company can switch insurers at renewal, after a rebid, or when an agency mandate ends. Understanding why DBA carriers change over time is the difference between naming the insurer on the risk and chasing a stale one from the wrong year.
Line up the injury date against the coverage timeline first. Then find the entity and the policy that overlap that exact window. The sale that happened three years later is a distraction until you have pinned that anchor down. Federal fiscal years run October 1 through September 30, so watch the calendar carefully near a renewal.
Novation makes this harder because it scrambles the names. The company on the contract in 2014 may be legally gone by 2020. Search only the current name and you miss the 2014 policy entirely. The claim does not disappear, but the trail to it does unless you search every historical name.
How do you trace a carrier through a novated contract?
Start by resolving every name the employer has ever used. A single contractor can appear under a dozen legal names across federal records. Careful corporate history tracing is the first step, because the transferor, the transferee, and their subsidiaries all filed under different labels over the years.
Next, pull the contract vehicle itself. ClaimTrove indexes 43,298 overseas prime contract awards and 4,315 subaward records. Each award carries a contract number, a place of performance, and the recipient entity that held it at award time. That tells you which company was performing the work when your client was hurt.
Then match that entity against coverage evidence. The platform normalizes thousands of raw carrier name spellings across 51,954 unique employers found in FOIA-sourced insurance filings. It also holds 637 authorized DBA carriers and thousands of employer-to-carrier records mined from adjudicated legal proceedings.
Cross-referencing matters because no single record proves everything. A contract award shows who performed the work. A coverage record shows who insured it. An entity registration shows who held the identifiers. Read together, these sources reconstruct the entity and policy that were live on the injury date, even when the current corporate name tells a different story.
ClaimTrove traces the employer and the carrier tied to a specific contract vehicle, even after a novation splits the name in two. Run the contract number and the injury date through the investigation engine to see which entity held the risk. Start a free investigation and trace the carrier behind any novated contract.
What federal records show that a novation happened?
A novation leaves fingerprints in the federal registration system. The clearest one is the entity identifier. Every federal contractor carries a Unique Entity Identifier and a CAGE code, and those numbers do not lie about who held the contract.
When assets transfer, the buyer's identifiers attach to the ongoing vehicle. The old entity's registration often lapses or shows an expiration date. ClaimTrove indexes 865,232 SAM.gov entity registrations, so you can watch one identifier go dormant as another picks up the same line of work.
Do not confuse a novation with a recompete. A novation hands an existing contract to a buyer mid-stream. A recompete puts the work out for fresh bids and can land it with an unrelated firm. Both change the name on the paperwork, but the coverage logic behind each event is not the same.
The contract file also holds the novation agreement itself under FAR Subpart 42.12. That document names the transferor, the transferee, and the effective date of the transfer. Pair it with the injury date and the coverage timeline, and the responsible carrier usually falls out of the overlap.
You can also cross-check the contracting officer's paperwork. A recognized novation is documented in the award history, and the modification that implements it carries its own action code. Reading that modification tells you the precise date the government began treating the buyer as the contractor of record for that vehicle.
What if the injured worker was a subcontractor employee?
Novation adds another layer when your client worked for a sub, not the prime. The prime and the sub can each be sold on their own schedule. A novation of the prime contract does not touch the sub's separate insurance obligation to its own workers.
Under the DBA framework, the sub's carrier pays first when the sub carried its own policy. If the sub was uninsured, statutory liability can climb to the prime contractor under 33 U.S.C. 904(a). A sale of either company does not erase that statutory ladder.
This is where the trace gets slow. You may need to identify the sub, the prime, the carrier for each, and the corporate successor for each. Every one of those entities can have changed hands during the years between the injury and the filing. Missing one link can leave your client filing against a shell.
Flow-down clauses complicate the trace further. A prime passes DBA insurance duties down to each sub by contract, and each tier can carry a different insurer. When a sub at the bottom of that chain is sold, its historical policy still governs the claim. You have to rebuild the tier that existed on the injury date, not the tier that exists today.
What is the bottom line for a novated DBA claim?
A contract novation turns a simple carrier question into a multi-entity trace. The name your client remembers, the name on the contract, and the name that owes benefits can be three different companies. The injury-date policy remains the spine of the whole analysis, no matter how many times the business was sold.
Treat every novated-contract claim as a corporate-history problem first and a carrier problem second. Build the timeline of who held the vehicle, who insured it, and who was sold and when. Once that timeline is straight, the responsible party is usually obvious. Skip it, and even a strong claim can stall against the wrong defendant.
ClaimTrove connects those names so you file against the right party the first time. Search the contract vehicle, resolve every alias, and match the injury date to the carrier on the risk. Run an investigation to trace the carrier behind any novated contract vehicle before you send a single demand letter.