A corporate acquisition can change the owner, the contracting party or only its name. Establish which change is proposed, identify the affected contracts and prepare the evidence the responsible contracting officer needs.
The government-contract workstream of a corporate acquisition begins with the legal change being proposed. Buying shares, buying a business's assets and changing a company's name can have different consequences for its contracts. A transaction announcement or a new brand does not establish which entity now holds the customer's contractual rights and obligations.
For a defense business, this distinction belongs in acquisition planning alongside the product, employee and financial reviews. The team needs to identify the affected contracts, the proposed performing entity and the government process that may be required. Leaving that work until after a public announcement can expose gaps in both the integration plan and the expected customer revenue.
FAR 42.1204 addresses government recognition of a successor where all assets, or the entire portion involved in contract performance, transfer. It distinguishes a stock purchase with no legal change in the contracting party, where that party retains control of the assets and performs the contract. Other ownership-related issues can still require a formal agreement.
Consider a hypothetical software group acquiring a smaller maintenance-data business. In one structure, the target company remains the contracting party and continues performing with its existing assets. In another, relevant assets move into a different group company. The transaction team needs to explain the proposed structure precisely enough for the contract implications to be assessed.
A useful internal diagram identifies each legal entity before and after the transaction, the assets moving and the entity expected to perform each customer obligation. Avoid using the buyer's group brand as a substitute for the name on the contract. Several subsidiaries may share that brand while remaining distinct contracting parties.
The purpose of this exercise is to give the responsible legal and commercial advisers a concrete transaction to review. It does not allow the project team to decide that approval is unnecessary simply because customer delivery is intended to continue without interruption.
FAR 42.1204 calls for information including the transaction document, the affected contracts, amended values, approximate unpaid balances and evidence of the proposed successor's ability to perform. Additional supporting documents may be required as applicable. Assemble the inventory from authoritative contract and financial records rather than from a sales presentation.
For the software acquisition, the commercial team should connect each contract to its legal holder, responsible office and current status. Finance can then reconcile the remaining balance and distinguish amounts already billed from work still to be billed. Disagreements between the systems should be resolved or explicitly recorded.
The inventory should also make the proposed scope of the acquisition visible. If a contract is excluded from the transaction, identify why and establish how its continued performance is expected to work. A product division's revenue total may combine several legal entities or customer arrangements; it is not automatically a list of contracts moving with the acquired assets.
Keep the inventory dated and under a named owner's control. Amendments, payments and deliveries can change the position while the transaction is being prepared. The team needs to know which date the figures describe and how subsequent changes will be reflected in the submission.
FAR 42.1202 determines responsibility for processing the agreement. It takes account of administrative contracting-officer assignments and, in specified circumstances, the largest unsettled contract balance. The customer contact best known to the sales team is not necessarily the person responsible for this process.
Use the contract inventory to establish the applicable administration structure. Where several offices or transferors are involved, the transaction team should identify the coordination needed instead of sending different accounts of the acquisition to each customer. The objective is a consistent factual position with a clear route for questions.
For the hypothetical acquisition, appoint an internal coordinator who can bring together the seller's contract administrator, the buyer's integration lead and the relevant advisers. That person need not answer every substantive question, but should know who owns each item and whether the records supplied by different teams agree.
Plan this work around the actual proposed transaction timetable. Government processing is a dependency to investigate; it should not be represented internally as a routine administrative task with a guaranteed completion date unless the applicable facts support that expectation.
The acquisition's commercial rationale may focus on technology and market access. The contract review also needs an intelligible account of performance. In the software example, identify the people providing support, the business controlling the relevant assets and the arrangements needed to deliver the customer's existing service.
If the integration plan changes those arrangements, explain the change instead of describing everything as continuity. A proposed move to a shared support team may be sensible, but the contract workstream needs to understand its implications. The same applies to a transfer of a necessary supplier relationship or a change in the organisation maintaining customer records.
FAR 42.1204 states that the original contractor remains obligated where the government does not concur in the transfer. That makes delivery responsibility a present issue for the transaction parties. Their internal allocation of obligations must be considered alongside the government's contractual position.
The team should maintain a transition plan that identifies who performs each obligation while decisions are pending. This is particularly useful where commercial staff are eager to introduce the acquirer as the new customer-facing organisation before the underlying contract record has been addressed.
Under FAR 42.1203, the contractor submits a written request to the responsible contracting officer. The process includes gathering necessary information, coordination with affected offices, government-interest assessment and legal-sufficiency review. Execution is followed by distribution and contract-modification steps.
The practical implication is that the workstream needs more than a milestone labelled “novation sent”. Track the request, outstanding evidence, questions received and the resulting executed documents and modifications. The company should be able to establish the current position for each affected contract without relying on a general transaction-status email.
DFARS PGI 242.1203 adds defence-specific coordination, distribution and reporting procedures. Confirm the applicable process with the responsible office. A generic transaction checklist can help organise the work, but it does not replace those requirements or the officer's requests for information.
After the relevant documents are issued, make the updated position available to invoicing, delivery and customer-facing staff. Reconcile the contract inventory with the outcome so that records left outstanding remain visible.
FAR 42.1205 addresses a change of name where the parties' rights and obligations remain unaffected. It provides for an agreement and supporting evidence of the legal name change, including an affected-contract list. A refreshed logo or trading style should not be confused with that formal change.
For the software group, the customer communication can explain the business change accurately while the contract team manages the underlying records. Keep the legal entity, brand and contracting role distinguishable in internal materials. This helps avoid an invoice or proposal using a name that colleagues assume has already been recognised everywhere.
Our guide to prime and subcontract responsibilities explains why the identity of the contractual supplier matters. The UEI and SAM guide provides the related registration context. Acquisition integration is easier to manage when the transaction structure, government-contract process and operating records describe the same intended business change.
FAR sections 42.1202 through 42.1205 and DFARS PGI 242.1203 were directly read on 6 September 2026. The transaction example and management workstream are BDI analysis. No conclusion about a particular acquisition's novation requirement is made; the actual legal structure, agency requirements and contracting-officer determination matter.
Suggest a correction