How to prepare a post-closing obligations tracker for Share Purchase Transactions

A buyer’s post-closing obligations tracker converts the executed share purchase agreement and ancillary documents into assigned, verifiable actions. Extract each continuing duty, distinguish it from a contractual right or completed closing condition, identify its trigger and delivery requirements, and independently check calculated dates. Link every entry to the operative clause and the evidence needed to close it. The resulting deliverable is a controlled working record showing who must act, when, on what basis, and what remains unresolved—not simply a calendar of dates.

When to use this workflow

Use this workflow when buyer transaction counsel hands responsibility to in-house legal, finance, tax, company secretarial staff, and acquired-company management. Prepare the structure before closing; activate closing-dependent dates only after confirming the actual closing event.

Cover purchase-price adjustments, deferred consideration, escrow arrangements, tax cooperation, records access, continuing covenants, and expressly deferred deliverables. Include buyer rights requiring timely action, but distinguish them from mandatory duties and counterparty rights the buyer must monitor. Keep ordinary integration projects outside the tracker unless transaction documents require them.

This is a US-oriented professional workflow guide. Delaware corporate-law references apply only to Delaware corporations. Contract rights depend on actual wording, governing law, facts, and deal context. Tax, regulatory, and foreign-law requirements need separate analysis; the recommendations below are management practices, not independent legal mandates.

What you need

Collect a controlled source set rather than relying on the signing checklist:

• Executed purchase agreement, schedules, exhibits, amendments, waivers, and side letters.
• Executed escrow, transition services, restrictive covenant, and other relevant ancillary agreements.
• Closing confirmation, funds-flow record, delivery receipts, and unresolved closing-item list.
• Definitions, notice provisions, accounting principles, dispute procedures, and calendar conventions.
• Buyer, target, seller representative, and escrow-agent contacts, with internal approval responsibilities.
• Ownership records and supporting transfer documents for outstanding share-record work.

Give each document a stable ID and identify its operative version. Distinguish an estimated preclosing statement from a buyer’s post-closing adjustment statement. Obtain missing ancillary documents before treating the source set as complete. A binder index does not establish that every listed document was executed or released.

Use the template

The Share Purchase Transactions — Post-closing obligations tracker below can be copied into your working document or spreadsheet. Use linked supporting notes for detailed calculations, notice instructions, and evidence.

ID / type distinguishes duties, buyer rights, counterparty rights, and deferred deliverables. Keep row IDs stable so dependencies remain traceable. Source identifies the executed document ID, section, and page where useful.

Action / parties states the act and contractual actor. A seller obligation still needs a buyer monitoring owner. Trigger / evidence records the activating event and its supporting record.

Timing / due date holds the contractual formula, checked date, and separately labeled internal target. Notice / dependencies captures delivery mechanics, prerequisites, and linked row IDs. Owner / reviewer identifies accountable individuals. Status / completion proof distinguishes preparation, approval, dispatch, receipt, dispute, and verified completion; include a linked next-action date for unresolved issues.

Step by step

1. Establish the operative documents and closing baseline

Reconcile executed documents against the closing checklist. Identify amendments affecting post-closing performance and waivers limited to particular closing conditions. Review the waiver’s scope rather than assuming it also removed a continuing covenant.

Confirm the contractual closing date and any relevant effective time or separate completion event. Signature, payment initiation, and closing may be different events.

Record document versions in the supporting index. Enter unresolved closing facts as assigned issues, identifying downstream dates that cannot yet be finalized. The output is an evidenced timing baseline, not an inferred one.

2. Extract duties and rights across the agreement set

Read operative provisions rather than searching only for “post-closing.” Review adjustment mechanics, earnouts, escrow releases, tax matters, records access, confidentiality, restrictive covenants, further assurances, and any agreed employee or directors’ protection commitments.

Separate independently completable actions. Preparing a statement, delivering it, supporting review, resolving objections, and paying an adjustment should not occupy one row. Distinguish seller cooperation from a buyer request that activates it.

For claims-related rights, capture applicable notice content, recipients, and contractual cutoffs without assuming that survival language alone determines every deadline. Assign legal analysis where interpretation is unresolved.

Record each action’s actor, beneficiary, source, and classification. Exclude completed closing conditions unless a documented deferral creates remaining work. This produces a clause-backed inventory, not a second integration plan.

3. Resolve triggers and independently verify dates

Enter the timing formula before calculating a date. Check definitions, calendar conventions, extensions, time zones where relevant, and whether the period runs from closing, delivery, receipt, or final determination.

For example, the filed Booz Allen Hamilton–PAR agreement requires the buyer’s Closing Statement within 120 days following closing. It requires the seller’s written acceptance or detailed objections within 45 days after receipt. These are negotiated periods with different triggers, not general M&A deadlines. See §§ 2.4(a)–(b).

Have a second person check interpretation and arithmetic. Record the formula, trigger evidence, calculated date, and checker. If receipt is unproven, mark the response date unverified and assign evidence collection; do not substitute dispatch.

4. Capture delivery mechanics and substantive dependencies

Identify required contents, recipients, addresses, permitted methods, copies, and deemed-receipt provisions. Read the specific delivery requirement alongside the general notices clause and resolve any uncertainty before dispatch.

Map substantive dependencies. Finance may need target records and applicable accounting rules before completing an adjustment statement. Escrow release may depend on specified instructions or resolution of a claim. A transition-services termination notice may require business readiness before counsel recommends exercising it.

Record requirements in Notice / dependencies, using linked row IDs. Set preparation and approval targets separately from contractual due dates. Assign missing information to a person who can obtain it, with an internal follow-up date.

5. Assign owners according to the share acquisition structure

Separate the legal obligor from the team doing the work. Target finance may prepare information while the purchase agreement places delivery responsibility on the buyer. The seller representative and escrow agent may have separate roles.

For outstanding ownership records, define the required evidence. Delaware’s stock-ledger definition covers record holders, addresses, registered share amounts, and recorded issuances and transfers. See DGCL § 219(c). Do not treat that definition as proof of clean title or complete beneficial ownership; reconcile the promised record with relevant transfer evidence.

Record an accountable buyer owner, reviewer, and external dependencies for every row. Obtain owner acceptance. Circulating a spreadsheet is not a completed handoff.

6. Define completion evidence before work starts

Write an acceptance test for each row. Statement delivery may require the approved statement, supporting schedules, delivery record, and evidence establishing contractual receipt. Payment may require the approved calculation and confirmation of the payment event specified by the agreement.

Do not equate a draft, payment instruction, or email saying “done” with verified performance. Distinguish reported action from missing proof.

Record required evidence and current status. Separate buyer delivery completion from counterparty review pending. For continuing obligations, record the relevant period and review evidence rather than marking the covenant complete after one compliant action.

7. Resolve exceptions and release the controlled tracker

Review consequential dates, disputed interpretations, and missing triggers with legal and business owners. Assign each unresolved issue a decision-maker and internal resolution date. Commercial risk acceptance is not proof of performance or a contractual amendment.

Check dependent rows and omitted covenants, particularly items assumed to belong to tax, finance, or target management. Release a dated working version with a named custodian.

Preserve amendment history, corrected dates, and completion evidence. Set a review cadence around the nearest obligation and recurring commitments. The cadence is a management choice; it does not replace contractual notices or modify deadlines.

Worked example

Fictional scenario; tracker snapshot as of September 3, 2026. Harborline Systems Inc. acquires all shares of Cedar Relay Corp., a Delaware corporation, from Juniper Holdings LLC. All parties, documents, and terms below are invented.

Closing confirmation CC-01 establishes September 1, 2026 as closing. SPA-01 requires the buyer’s adjustment statement within 30 calendar days after closing. Delivery requires a designated portal upload and receipt confirmation. The seller may object within 20 calendar days after receipt. Closing letter CL-02 requires the buyer to procure delivery of an updated target stock ledger within five calendar days after closing. Both documents exclude the triggering day and provide no weekend extension.

PC-03 requires attention before the adjustment statement: its deadline arrives first, and a draft is not the promised operative ledger. The secretary must obtain and reconcile that record. The available evidence establishes neither completion nor a title defect.

PC-02 also prevents a timing assumption. It records a seller right, not a buyer right or mandatory objection. Counsel must obtain the receipt record before fixing the response endpoint. The example supplies no actual upload or receipt, so the tracker does not invent either event.

Common mistakes

• Reusing the closing checklist unchanged. Add continuing covenants and actionable rights; retain closing items only where work remains documented.
• Treating every period as closing-based. Preserve receipt, determination, and other triggers with separate evidence.
• Combining the entire adjustment process. Separate delivery, review support, objections, determination, and payment where independently actionable.
• Naming only a department. Identify the contractual actor, accountable individual, reviewer, and external dependencies.
• Closing a row on dispatch or a draft. Apply the agreed performance test and retain supporting evidence.
• Treating risk acceptance as a cure. Record the decision separately; determine whether contractual consent, amendment, or further performance remains necessary.

Final quality check

• Every entry cites the operative executed document and provision.
• Duties, buyer rights, counterparty rights, and internal targets are distinguishable.
• Each activated date has a formula, evidenced trigger, and independent check.
• Specific delivery terms and general notice provisions have been reconciled.
• Each action has an accepted owner and appropriate reviewer.
• Completion and continuing-performance statuses have supporting evidence.
• Every material open issue is resolved or assigned a decision-maker and follow-up date.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review and transactional capabilities support review of purchase agreements and ancillary documents, including tabular review across multiple documents. Counsel can provide deal-specific instructions; findings quote and locate clauses, rank severity, and identify missing language as not present. Lawyers retain responsibility for interpretation, date verification, and completion decisions. The tracker remains the team’s work product. To discuss reviewing post-closing provisions, book a demo.

Frequently asked questions

Should seller obligations appear in the buyer’s tracker?

Yes, when they affect buyer rights or performance. Identify the seller as obligor and assign a buyer monitoring owner. Keep seller rights, such as an adjustment objection opportunity, separately classified.

How should we track obligations with no fixed deadline?

Preserve the actual standard or event-based wording. Add a clearly labeled internal review date, identify activating events, and assign assessment responsibility. Do not invent a contractual deadline.

Does uploading a document complete delivery?

Not necessarily. Check contents, permitted method, recipients, and receipt mechanics. Record upload separately from contractual delivery where those requirements differ, and preserve evidence supporting the trigger for subsequent periods.

How should an amendment change existing rows?

Retain row IDs and timing history, cite the executed amendment, and recheck affected dependencies. Independently review revised dates and notify owners. A proposed amendment should not silently replace operative terms.

Sources

• Booz Allen Hamilton–PAR Stock Purchase Agreement, §§ 2.4(a)–(b): negotiated statement-delivery and seller-response requirements, not general legal deadlines.
• Delaware Code, Title 8, § 219(c): stock-ledger definition for Delaware corporations.

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.