Carve-Out Data Rooms: Define What Transfers

Organize a carve-out data room around the deal perimeter, shared dependencies, standalone assumptions, TSA evidence and controlled bidder access.

A carve-out data room must answer a question that a normal company sale can often take for granted: what exactly is the buyer receiving? A division may use the parent's contracts, systems, employees and intellectual property without owning them separately.

The room should connect each proposed transfer to supporting evidence and identify what remains shared, retained or unresolved. This guide gives sell-side coordinators a practical document plan for that work. It does not determine the legal transaction perimeter or replace accounting, tax, employment or competition advice.

Establish one working definition of the deal perimeter

Create a perimeter schedule before uploading the parent's files. Name the businesses, entities, locations, products and assets in scope. Distinguish the proposed commercial boundary from the legal entities that currently hold the rights or liabilities.

For each item, record its current owner, its proposed treatment and the evidence supporting that treatment. Use explicit states such as proposed transfer, retained, proposed licence, shared dependency or unresolved. Do not mark an asset transferred simply because it is used by the division.

Have deal counsel and the relevant functional owners review the schedule. Keep a version and decision date. If the sale structure changes, identify which schedules and disclosures need revision rather than letting outdated scope documents remain alongside the current presentation.

A perimeter disagreement is substantive, not a filing inconvenience. If the seller expects to retain a software platform while the buyer's model assumes ownership, highlight the mismatch before it becomes buried inside an annex. The room's job is to expose that dependency clearly enough for the parties to resolve it.

Use a perimeter table to guide collection

The following table is an editorial preparation example. The actual transaction documents and professional advice determine the treatment of each item.

Attach references rather than copying entire documents into the table. Where a contract contains information about retained units, prepare an appropriately approved disclosure copy. Keep the original in the established internal repository.

Give unresolved items owners and deadlines. A blank cell is ambiguous: it might mean not applicable, not collected or disputed. A clear unresolved status makes the buyer's question visible without creating a false impression of completeness.

Separate historical results from standalone assumptions

Buyers need to understand both how the division performed inside the parent and what it might cost to operate separately. Label these as different views. Shared-service allocations do not automatically equal future standalone expenses.

Request a bridge between reported divisional results, carve-out adjustments and the proposed standalone case. Explain allocation methods, excluded costs, one-off separation expenses and assumptions about replacing parent services. Keep the assumptions editable in the model and described in an accompanying note.

A historical SEC-filed carve-out example explicitly distinguishes prepared statements from standalone operations and warns about omitted expenses. This illustrates why the basis of preparation matters; it is not a template for every deal's accounting requirements. SEC-filed carve-out financial statement example: basis of preparation

Ask accounting advisers which statements and assurance are appropriate for the transaction. Do not label management schedules audited or compliant merely because they resemble financial statements. A document's cover should state its author, period, basis and assurance status accurately.

Map dependencies before drafting a TSA schedule

A transition services agreement, or TSA, may describe temporary services supplied after closing. The evidence behind it should explain what the service does, who depends on it and how the buyer will leave it. A list of IT, HR and finance headings is too vague for operational review.

Map each dependency to the process it supports. For payroll, identify the service population, input responsibilities, cut-off dates and operating contact. For IT, distinguish identity access, hosting, software licences, support and data migration. These can have different owners and exit constraints.

Use this matrix for preparation, not as final contractual language. Pricing, liability, service standards, consent and termination rights need appropriate negotiation and review. The room should make those decisions easier to assess rather than suggesting they are already settled.

Design separate working and bidder environments

Internal separation planning produces drafts, employee detail, budget scenarios and negotiating positions. Keep that workspace distinct from the approved buyer disclosures. A team moving quickly should not be able to expose an internal document by dragging it into the wrong external folder.

Maintain a release queue. Functional owners supply evidence, the assigned reviewer checks perimeter and sensitivity, and the administrator publishes the approved edition. Record which bidder groups received it and when. Changes to documents or group access should be visible in the release record.

Different bidders may require different handling. A strategic competitor is not interchangeable with a financial sponsor. Competition counsel should determine the sharing protocol, including any clean team and permitted outputs. A folder labelled clean team does not establish an adequate protocol.

FTC guidance discusses risks from exchanging competitively sensitive information before a merger and the need for appropriate safeguards. Its U.S. context does not settle every jurisdiction or transaction. Seek deal-specific advice on the actual people, information and proposed use. FTC: Avoiding antitrust pitfalls during pre-merger negotiations and due diligence

Check for parent information inside division documents

Review schedules for retained customers, product lines, commercial terms and personal data outside the requested perimeter. A division contract export can still contain parent-wide tabs or attachments. Inspect the whole package, not only its first visible sheet.

Prepare customer aliases or aggregated schedules where appropriate, but test whether other files reveal the identity. A narrow market, a distinctive revenue amount or a named case study can undo the intended masking. The correct treatment depends on the disclosure purpose and professional assessment.

Keep a controlled alias key internally and allow authorized reviewers to trace approved information when needed. Removing identifiers without a reconciliation method can make evidence unusable. The aim is a proportionate release that still answers the diligence question.

Check notifications and indexes as well as file contents. A document title mentioning a retained acquisition plan can reveal information before anyone opens it. Test the room as a representative bidder and confirm exactly what the group can see, search, download and export.

Worked example: a shared CRM changes the plan

This fictional example concerns a manufacturer selling its service division. The division has thirty employees and uses the parent's CRM, payroll team and purchasing agreements. The first sale presentation assumes a clean separation at closing.

The perimeter review finds that the CRM contains records for both the service division and a retained product business. The division does not have a standalone licence or an approved migration plan. Rather than uploading a parent-wide export, the seller creates a data-scope schedule and tasks IT with a test extraction using authorized sample data.

The working plan now identifies temporary CRM service and a migration milestone. The financial case includes an explicit estimate for replacement software, while a separate schedule identifies one-time migration work. These are management assumptions pending review, not agreed TSA obligations.

A strategic bidder asks for detailed customer pricing. Counsel specifies a restricted review process and approves an aggregated output for the broader deal team. The room administrator implements the approved groups but does not decide who qualifies as a clean-team member.

When the bidder is eliminated, access is removed and the team follows the agreed handling obligations for material already received. It does not claim that link revocation wipes the bidder's downloaded files or derived analysis. The release record helps identify which editions were distributed and which follow-up is required.

Make Q&A updates change the relevant schedules

A buyer question often uncovers a scope issue. If the buyer asks who owns a licence, do not answer only in an isolated message. Update the ownership schedule or explain why the answer does not change it, then link the approved response to the evidence.

Use a change register for assumptions affecting the price model, separation cost or service plan. Show previous position, new position, owner and affected documents. A small contract correction can materially change an operating dependency even when the headline transaction perimeter stays the same.

Reconcile responses across workstreams. Finance may assume a function continues under a TSA while operations plans to replace it immediately. The room should not publish both positions without explanation. Ask the responsible deal lead to resolve or clearly label the disagreement.

Prepare a closing and separation handover

Before closing, identify what becomes the buyer's operational repository and what remains a diligence archive. Access suitable for bidding is not necessarily suitable for employees running the separated business. Reassess roles, data purpose and document ownership.

Create a handover index connecting transferred records, signed transaction documents, agreed service schedules and outstanding implementation tasks. Reference the correct final editions. Keep draft separation assumptions distinguishable from obligations actually agreed by the parties.

Test that the recipient can use the exported package without the original room. Files should have meaningful references, dependencies should be understandable and the responsible contact should be named. Preserve necessary seller records under the applicable retention and preservation process.

Know when to stop and escalate

Stop a release if it includes unrelated parent information, contradicts the current perimeter or lacks an approved audience. Escalate disputed asset ownership, personal-data transfer questions, employee treatment and competitive information requests to the designated specialists.

Do not promise that better folders eliminate separation risk. A well-organized room makes dependencies visible and decisions traceable. It cannot create missing licences, obtain required consent or build a replacement system. Those tasks need accountable owners outside the document platform.

Frequently asked questions

What makes a carve-out room different from a normal M&A room?+

It must show what belongs to the transaction and what depends on the retained parent. Shared contracts, systems, people and costs require explicit schedules instead of assuming the target is already standalone.

Does every carve-out need a clean team?+

That depends on the parties, information and applicable competition rules. Counsel should assess the need and design any protocol. Creating a restricted folder alone does not resolve competitive-information risks.

Can a TSA schedule be drafted directly from a folder index?+

A folder index can organize evidence, but it does not define service obligations. Scope, operating responsibilities, costs, exit requirements and legal terms require substantive work by the relevant functional and professional teams.

Before you proceed

Make the transaction perimeter the organizing principle. Buyers should be able to trace every proposed transfer and shared dependency to evidence, an accountable owner and a clearly labelled decision status.

Related articles

• Post-Merger Document Handoff: A Practical Guide

• Commercial Due Diligence: Test the Revenue Story

• Legal Data Rooms: Share Documents With Control

Sources and editorial disclosure

Primary documentation reviewed October 11, 2026. The operational templates and worked examples are editorial recommendations, not claims of completed transactions or product testing.

• SEC-filed carve-out financial statement example: basis of preparation

• FTC: Avoiding antitrust pitfalls during pre-merger negotiations and due diligence

VDR Directory is published by the team behind SendNow. This ownership is relevant when considering product recommendations. Stock photos illustrate general workflows. Legal, tax, regulatory and security decisions depend on the transaction and applicable requirements; involve the responsible specialist. No platform can guarantee confidentiality, transaction success or search rankings.