How to prepare a post-closing obligations tracker for Private Company Acquisitions

Prepare a buyer-side post-closing obligations tracker by extracting continuing duties, payment mechanics, notice requirements, and release conditions from the executed acquisition documents. Separate each obligation from its trigger, verified deadline, responsible person, and completion evidence. Reconcile purchase-price adjustments, escrow releases, tax cooperation, transition services, and claims procedures across the relevant agreements. The deliverable is a source-linked working record showing buyer counsel and the integration team what must happen next, who must act, and what evidence permits an item to be closed.

When to use this workflow

Use this workflow at closing or immediately afterward, when buyer deal counsel hands continuing responsibilities to finance, tax, operations, and the team assuming responsibility for the acquired business. Start earlier where post-closing deadlines require advance preparation.

The scope is contractual post-closing administration, not the entire integration plan. Include operational tasks that implement a sourced obligation or preserve a contractual right. Keep discretionary integration projects elsewhere, with links where necessary.

This guide takes a US transactional perspective. Interpret obligations against the acquisition structure, obligated entities, governing law, amendments, and facts. Separately assign applicable statutory, regulatory, and tax-filing requirements; this contractual tracker is not a substitute for those calendars.

What you need

Collect the authoritative closing set and evidence establishing relevant triggers:

• Executed acquisition agreement, amendments, disclosure schedules, exhibits, side letters, and written waivers.
• Escrow agreement, transition services agreement, tax arrangements, and executed representation-and-warranty insurance policy, if applicable.
• Closing memorandum, funds flow, payment confirmations, and evidence of closing and any separate effective time.
• Estimated closing statement, accounting definitions, calculation examples, and supporting finance records.
• Notice provisions, party and representative contacts, and permitted delivery methods.
• Closing checklist carryovers, consent correspondence, and internal responsibility assignments.

Give each document a stable ID and preserve its execution status and version. Identify missing documents rather than substituting unsigned forms. Ask deal counsel to identify unresolved closing undertakings; distinguish documented amendments from unverified recollections.

Use the template

The companion template is Private Company Acquisitions — Post-closing obligations tracker. You can copy this table into your working document or spreadsheet. Use one row for each independently actionable duty, deadline, or decision.

In Source / evidence, enter document IDs and clause or page references, distinguishing the operative provision from evidence establishing its trigger. Duty / beneficiary identifies the obligated party, required performance, and recipient or protected party.

Use Trigger / date basis for the event, contractual interval, applicable business-day definition, and counting assumptions. Put the resulting date in Due / checkpoints, alongside clearly labeled internal targets. An internal reminder is not a contractual deadline.

Assign named people in Owner / backup. Use Dependency / question for missing evidence, disputed interpretations, and linked row IDs. Action / status records the next action and escalation date. Completion proof identifies retained evidence and the verifying reviewer. Keep longer calculations and notice instructions in linked working papers.

Step by step

1. Establish the controlling document set and closing baseline

Confirm what closed, which entities acquired or retained obligations, and whether closing and effectiveness occurred at different times. Reconcile executed documents against amendments and side letters before extracting deadlines.

Check document hierarchy rather than assuming schedules prevail. For example, the Molina–Bright Health agreement gives its body precedence over inconsistent schedules and related agreements, subject to expressly stated disclosure exceptions. That is an agreement-specific drafting choice, not a universal rule. See the SEC-filed agreement, § 13.11.

Record the controlling document ID and trigger evidence in affected rows. Mark derived deadlines provisional where the applicable version or trigger remains unresolved, and assign verification immediately.

2. Extract obligations by post-closing workstream

Read continuing covenants and ancillary agreements alongside purchase-price, tax, indemnity, records-access, confidentiality, and notice provisions. Follow definitions and cross-references rather than relying on keyword results alone.

Create rows for adjustment statements, objection periods, settlement payments, tax cooperation, escrow instructions, transition-service notices, deferred remediation, and required record preservation. Add earnout reporting or deferred consideration where the transaction includes them. Distinguish buyer duties, seller duties, and buyer rights requiring timely action.

Do not convert an unsatisfied closing item into an authorized post-closing undertaking. Check whether it was waived, deferred by agreement, or remains unresolved. Record that treatment and its source. The output is an obligation inventory stating who owes what to whom.

3. Calculate deadlines from verified triggers

Transcribe timing language before calculating dates. Identify whether the clock starts at closing, receipt of a statement, delivery of supporting records, final determination, or another event. Check business-day definitions, counting rules, weekend adjustments, notice effectiveness, and any specified time zone or cutoff.

Have a second reviewer verify consequential dates, particularly objection windows, claim notices, and escrow instructions. Preserve calculations in linked working papers. If receipt is uncertain, label the date unconfirmed and establish a conservative internal response target without presenting it as the legal deadline.

Record the due date, trigger evidence, reviewer, and checkpoints. Arrange reminders through the team's chosen calendar or task process; a tracker row does not itself create one.

4. Separate adjustment mechanics from claims and recovery

Treat adjustment preparation, review, disagreement, determination, and payment as distinct stages. Link them rather than compressing everything into “finalize working capital.” Identify accounting inputs and information-access rights needed at each stage.

In the Molina–Bright Health example, § 3.3 separates price determination, disagreement procedures, and settlement; § 3.3(e) makes the adjustment escrow the buyer's sole recovery source for a negative adjustment. This illustrates why adjustment recovery must be distinguished from indemnity recovery. See § 3.3 of the filed agreement.

Record the next action, funding source, and dispute dependencies in separate linked rows. For claims, identify the relevant notice and survival provisions and separately check policy requirements. Do not assume indemnity funds or insurance cover an adjustment shortfall.

5. Map conditional releases and ancillary obligations

Reconcile escrow instructions with the acquisition agreement. Identify authorization requirements, release calculations, and the treatment of pending disputes. A scheduled date may require joint instructions, not an unconditional payment.

The Granite Southeast–Roberts Family agreement places seller-funded remediation efforts and staged specific-indemnity escrow instructions in § 8.9. The scheduled releases are reduced for specified disputed or claimed amounts; the provision does not establish that remediation was completed or releases occurred. See the filed agreement, § 8.9.

Apply the same discipline to transition-service termination, tax information delivery, and records access. Record each performance test, supporting evidence, approval requirement, and linked dependency. Do not add a completion-certificate requirement unless the controlling documents contain one.

6. Assign ownership and executable instructions

Give each row an accountable buyer owner and backup, even when the seller must perform. The buyer owner monitors receipt, evaluates sufficiency, and escalates nonperformance; that assignment does not transfer the contractual duty.

Specify the action. “Tax team—cooperate” is insufficient: identify requested records, recipient, timing standard, and questions for counsel. For external notices, capture required recipients, copies, delivery methods, and effectiveness rules from the relevant agreement rather than an ordinary correspondence list.

Record a next action and escalation date. Have owners confirm source-document access and decision authority. Escalate unresolved authority questions rather than treating silence as approval.

7. Verify completion and preserve the record

Close a row against its performance test. Sending a statement, receiving it, accepting its calculation, and paying the final amount are different events. Retain delivery evidence, substantive responses, approvals, and payment or release confirmations under stable references.

For transition services, retain termination evidence and identify continuing duties. For claims, preserve notices and transmission records while counsel separately assesses sufficiency and recourse. Link records-retention tasks to applicable access commitments and separately assigned preservation requirements.

Record completion date, evidence location, and reviewer. When performance creates a new trigger, activate the linked row before closing the old one. Set review frequency around active deadlines and unresolved dependencies.

Worked example

Fictional scenario: Alder Quay Holdings acquires all shares of Brookmere Controls on September 8, 2026. Its fictional SPA requires the buyer's closing statement within 60 calendar days after closing, excluding closing day, with no weekend extension for this obligation. A separate fictional escrow agreement requires a completion certificate and dispute check before joint remediation-release instructions. A fictional TSA provides payroll support terminable on 30 calendar days' effective written notice.

Finance lacks part of the inventory reconciliation. The seller requests a $120,000 remediation release, but no completion certificate has been located. Operations wants to end payroll support without specifying an end date. All parties, documents, provisions, and amounts are invented.

PC-01 has a calculable November 7 deadline despite missing support; escalate the reconciliation rather than assume an extension. PC-02 requires evidence before authorization, but the missing certificate does not excuse ignoring any separate instruction deadline. PC-03 needs an operational end date before counsel can work backward to the required notice timing. Those distinctions determine the next action rather than merely changing a status color.

Common mistakes

• Using closing as every trigger. An objection period may instead run from receipt. Identify and evidence the actual event.
• Combining adjustment and indemnity escrows. Record each fund's permitted uses and recovery limits separately.
• Treating operational handover as legal completion. Payroll migration does not prove effective TSA termination notice. Retain both kinds of evidence.
• Closing seller obligations without verification. Compare the seller's evidence with the actual performance test, including any required certificate or records.
• Assuming insurance follows contractual recourse. The Granite agreement directs specified representation-and-warranty losses to insurance, except Fraud, but that allocation does not establish coverage. Check policy exclusions and claims conditions separately; see § 8.6(d) of the filed agreement.

Final quality check

• Each substantive row cites the executed source and applicable amendment.
• Trigger evidence is retained, or its absence is flagged and assigned.
• Consequential dates have checked calculations and counting conventions.
• Internal checkpoints are distinct from contractual deadlines.
• Owners, backups, notice recipients, and approval authority are confirmed.
• Release calculations identify relevant conditions and dispute dependencies.
• Completed rows contain proof; open issues have decision-makers and next actions.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review and tabular review capabilities can support comparison across acquisition and ancillary documents. In Word, counsel can select the represented party and provide deal-specific instructions; findings quote and locate clauses and identify missing language as not present. Counsel retains responsibility for legal interpretation, date verification, and completion decisions. The tracker remains the team's work product, not an automated monitoring system. To discuss this transactional workflow, book a demo.

Frequently asked questions

Should every surviving covenant become a tracker row?

Capture covenants requiring action, monitoring, or preservation of rights. Group continuing duties only where owners, timing, and performance tests align. Avoid a single “surviving covenants” row that hides deadlines.

Who should own the purchase-price adjustment process?

Assign finance to calculations and counsel to contractual mechanics, notices, disputes, and recourse. Name one accountable coordinator, with separate preparation and approval responsibilities recorded in linked instructions.

How should tax cooperation with no fixed date be tracked?

Record the activating request or event, required information, and contractual timing standard. Assign an owner and internal review date without inventing a deadline. Keep separate statutory filing dates in the tax calendar and link dependencies.

When can an escrow-release row be marked complete?

After applicable conditions, calculations, and authorization requirements have been checked and required release evidence retained. Preparing instructions does not prove disbursement. If instructions and payment have different owners or timing, use linked rows.

Sources

• Molina–Bright Health Stock Purchase Agreement, §§ 3.3 and 13.11.
• Granite Southeast–Roberts Family Equity Purchase Agreement, §§ 8.6(d) and 8.9.

These filed agreements illustrate negotiated wording, not general law or market standards. This is a professional workflow guide, not advice for a particular transaction.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.