Give every post-close service its own exit test

Build a service schedule before promising to help

First, map every post-close service separately: provider, recipient, inputs, access, authority, dependencies, replacement owner, and exit evidence. Keep company services separate from the former owner's duties. Use service-specific independence tests, not one standard period. Obtain fact-specific legal, tax, employment, accounting, insurance, and security advice. This is not an agreement template or classification conclusion. ¹²³⁴⁵⁶

Begin with the operating result, not a vague activity. “Support accounting” is not a complete service. Identify the exact process, source records, systems, calendar, provider team, recipient team, decisions, expected output, exception route, access, service window, and proof that the buyer can take ownership.

Filed public-company agreements show service schedules and coordinators or representatives rather than relying only on a blanket description. The Vericel-Sanofi filing includes schedule fields for service description, term, location, provider and recipient representatives, maximum time allocation, monthly fee, and other terms. These are document examples, not required fields or market norms. ¹²³

Another SEC-filed agreement uses a services schedule and routes service communications through named coordinators. It is an older public-company example and supplies no private-company standard, fee, duration, or outcome. ⁶

Use separate rows for system access, reporting close, vendor coordination, payroll or benefits support, facilities, procurement, customer handoff, regulatory records, data migration, or any other actual service. Do not assume that a single provider, service level, duration, fee, or exit fits every row.

Keep the service schedule inside the owner handoff after sale so retained work, economics, authority, access, communications, and personal plans are reviewed together rather than negotiated in disconnected documents.

• Name the providing entity and recipient function for every service.
• Define inputs outputs access decisions exceptions and change control.
• Attach each dependency to a buyer-side replacement owner.
• State the exit evidence fallback owner and access-removal action.

Separate enterprise services from the former owner's role

Put entity-provided services in one register and the individual's work in another. The selling company might supply staff, systems, records, premises, vendor relationships, or administrative processes. The former owner might teach, introduce, explain, advise, observe, or escalate. Combining them under one promise makes responsibility, authority, insurance, tax, security, and supervision harder to review.

For the individual role, record the actual duties, time and location expectations, reporting line, permitted decisions, prohibited decisions, system access, customer or employee contact, expenses, compensation, conflicts, confidentiality, intellectual-property treatment, termination, and final handoff. These are issue fields, not proposed clauses.

IRS guidance says federal tax classification depends on the facts and the degree of direction and control rather than the label alone. That guidance does not classify a former owner, decide employment law, or resolve state requirements.

It means the role facts should be documented and sent to qualified tax and legal advisers instead of relying on “consultant” or another heading. ⁴

Use the readiness record to identify pre-sale dependencies before negotiating post-close work. A customer relationship, pricing approval, vendor exception, password, reporting shortcut, regulatory contact, or tacit employee practice that depends on the owner should become a specific handoff record—not an unlimited availability promise.

Keep payment mechanics separate from role scope. Compare work obligations and deferred consideration on distinct records so compensation for actual services, contingent purchase price, seller financing, rollover ownership, and expense reimbursement are not blended without qualified review.

Give the buyer authority while the seller supplies bounded help

For every service and individual duty, list who may decide, who may advise, who performs the work, who accepts it, and who handles exceptions. A former owner who can explain history may not be intended to approve spending, direct employees, bind the company, promise customer terms, change systems, or speak for the buyer.

Filed agreements distinguish provider and recipient responsibilities and use service coordinators, managers, or representatives to route requests and changes. That structure does not prescribe a private-company model. It does show why named interfaces are more reviewable than requests from any buyer employee to any seller employee. ¹²³

Create an authority card for the individual role. It should state permitted actions, prohibited actions, buyer supervisor, escalation contact, approved communication channels, credentials, data scope, physical access, document retention, emergency path, and the event that removes access.

Tell employees, customers, suppliers, advisers, banks, insurers, and other counterparties only what they need, through an approved communication plan. Make clear who owns the business decision after closing and when the former owner is providing context rather than instruction. The actual wording and audiences need transaction-specific review.

Use the terms record to connect service duties to retained risk and economics only after authority is explicit. Compensation, indemnity, insurance, expense, tax, access, security, and termination questions cannot be evaluated reliably while the former owner's decision power remains ambiguous.

Use the terms record to connect service duties to retained risk and economics only after authority is explicit. Compensation, indemnity, insurance, expense, tax, access, security, and termination questions cannot be evaluated reliably while the former owner's decision power remains ambiguous.

Map what must move before each service can end

Every service depends on a transfer path. List the people, process, records, data, system, credential, consent, license, contract, vendor, facility, bank authority, insurance, approval, and communication that the buyer needs. Then name the source owner, buyer recipient, required form, security rule, due date, acceptance evidence, and exception.

Recent filings describe transition services while the recipient separates or migrates to independent services and systems. The 3M-Solventum and TeraWulf examples are large public-company records, not private-company norms or evidence that a migration succeeded. They still make independence—not mere calendar passage—a useful organizing objective. ³⁵

Define entangled items explicitly. One system might serve multiple entities; a vendor contract might need consent; a record may contain seller-retained data; an employee may support both businesses; a license may not transfer; a customer communication may require coordinated timing. Do not solve these issues by assuming the owner will remain available.

Use the readiness checklist to assemble process system and access records before negotiating the service schedule. Use inventories, owners, diagrams, contract lists, access lists, calendars, exception logs, training records, acceptance evidence, and unresolved-item registers that the buyer and qualified advisers can actually inspect.

Add a change gate. A new request should state the service, reason, recipient, provider capacity, access, security, cost, schedule effect, dependency, decision owner, and revised exit. Informal expansion through chat, calls, or personal favors can defeat the purpose of a bounded record.

End a service when the replacement path works

There is no standard period established here. Replace one blanket duration with a term and exit test for each service or duty. End a row when the buyer's replacement owner has the required records, access, authority, training, consents, and tested ability to operate independently—or follow the agreed fallback and qualified advice. ¹²³⁵

Define evidence before the test. A buyer controller might produce and review the next close cycle; a system administrator might provision approved users and complete recovery checks; a vendor owner might direct the supplier under the buyer's authority; a relationship lead might handle the next customer decision and follow-up. These are fictional examples, not service standards.

Record who designs the test, who observes it, who accepts the result, what exceptions remain, and whether a failed test extends, narrows, replaces, or ends the service. Do not assume the seller alone decides that a dependency is gone or that the buyer must accept any demonstration.

Remove access as deliberately as it was granted. Close seller accounts, shared credentials, remote connections, physical access, signing authority, approval rights, distribution lists, data copies, and informal escalation channels according to the actual agreements and professional guidance. Preserve required records without keeping unnecessary operational access.

Return to the tested dependency if a date approaches and independence is not ready. The appropriate response might be remediation, a scoped change, alternative provider, buyer acceptance of a defined exception, or an end under the controlling documents. This guide supplies no extension right or legal result.

Give professional reviewers the actual service facts

Prepare the proposed transaction and transition documents, service register, individual-role register, dependency map, systems and data inventory, access list, decision-rights cards, buyer owners, communication plan, change log, exit tests, and unresolved issues. Preserve versions, approvals, dates, and the source record for each fact.

Ask transaction counsel to review scope, entity authority, access, confidentiality, intellectual property, change control, liability, indemnity, termination, dispute, consent, and document consistency. Ask qualified tax and employment advisers to review the individual's actual role facts. Scope accounting, insurance, cybersecurity, privacy, benefits, licensing, regulatory, and industry questions to the people responsible for them.

Do not convert a filed agreement into a private-company template. The Bristol, Vericel-Sanofi, 3M-Solventum, and TeraWulf records differ in parties, scale, services, schedules, dependencies, and transaction context. They support field observation, not copying or a claim that a provision is suitable. ¹²³⁵

After roles and dependencies are mapped, use a confidential owner intake to frame unresolved transition questions without uploading an agreement, credential, employee record, customer information, or other sensitive source material through the public site. The intake is not professional review or a transaction commitment.

After roles and dependencies are mapped, use a confidential owner intake to frame unresolved transition questions without uploading an agreement, credential, employee record, customer information, or other sensitive source material through the public site.

Stop if a service lacks a recipient, buyer owner, dependency, authority boundary, exit test, or fallback decision owner. The correct result may be narrower services, another provider, different access, more preparation, revised documents, or no owner role. A publishable checklist cannot decide that outcome.