Product
Analyze
Review
Produce
Draft
Solutions
Litigation
- Early Case Assessment
- Investigations & Subpoenas
- Trial Preparation
- Enterprise eDiscovery
- Cloud eDiscovery
Transactional
Who it’s for
Resources
Learn
Customers
Events & CLE
Track restructuring conditions precedent by linking each operative condition to the affected entity and transaction step, the evidence needed to satisfy it, and the person authorized to determine satisfaction or waiver. Keep contractual requirements separate from supporting deliverables and unresolved legal questions. The resulting company-side tracker should let closing counsel move from a status entry to the controlling clause, supporting evidence, and decision record without reconstructing the transaction from email. It should distinguish conditions blocking a particular step from obligations permitted to continue afterward.
When to use this workflow
Use this workflow when company counsel is preparing an out-of-court merger, asset transfer, or corporate separation involving multiple entities, approvals, or interdependent closing steps. Start when the structure and operative drafts permit conditions to be identified; reconcile the tracker as negotiations progress.
The scope is the closing decision, not every restructuring obligation. Include ancillary deliverables supporting a condition without turning the tracker into a general project plan.
This professional workflow guide uses a US orientation and Delaware corporate-law illustrations. Entity form, incorporation jurisdiction, governing documents, contract language, and structure determine the applicable analysis. Bankruptcy, foreign-law, tax, securities, and regulatory clearance issues require separate specialist analysis linked to the relevant conditions.
What you need
Assemble a controlled source set:
- Current restructuring agreements, amendments, schedules, ancillary agreements, and executed waivers.
- Before-and-after entity charts and a numbered step plan identifying transferors, asset destinations, and merger survivors.
- Governing documents, resolutions, approval records, and relevant filing materials.
- Financing instruments, material contracts, permits, and consent correspondence implicated by each step.
- A closing sequence identifying signatures, funds movements, filings, and intended effectiveness.
- Named decision-makers, evidence custodians, and counsel responsible for specialist issues.
Assign stable document IDs. Maintain version, execution status, repository location, access restrictions, and reviewer in a supporting index. Distinguish documents not supplied from documents confirmed not to exist. Inaccessible or incomplete evidence should remain an express gap.
Use the template
Use the Corporate Restructuring Transactions — Conditions precedent tracker below. You can copy this table into your working document or spreadsheet.
| CP ID / step | Entity / condition | Controlling source | Evidence / gap | Owner / dependency | Status | Waiver authority | Decision / action |
|---|---|---|---|---|---|---|---|
Give each independently decidable condition a stable CP ID. Identify the legal entity, relevant step, and operative test, including timing, materiality, and exceptions. In Controlling source, enter the agreement ID, version, clause, and incorporated schedule or definition; use page references where helpful.
Evidence / gap identifies the supporting document ID and pinpoint reference—not merely a folder link. Owner / dependency identifies an accountable person and predecessor step. Waiver authority records the authority source, required form, and restrictions rather than the person requesting relief.
Use controlled statuses: not assessed, evidence pending, under review, satisfied, or waived. Record “not applicable” only with a reason. Put the verifier, dated decision reference, unresolved issue, and next action in the final column as appropriate. Preserve IDs and clause references alongside hyperlinks so broken links do not erase traceability.
Step by step
1. Fix the transaction perimeter and source versions
Reconcile the entity chart, step plan, and operative agreements. Identify which contribution, merger, distribution, or transfer each condition governs. Satisfaction for an internal contribution does not establish readiness for a later distribution.
Designate the controlling draft or executed version. Preserve earlier versions and record changes to conditions rather than silently overwriting them. If a condition applies at several effectiveness points, identify each required assessment.
Record: CP ID, legal entity, step number, controlling version, and the relevant closing or effectiveness point.
2. Extract conditions without reclassifying every obligation
Read the conditions article with definitions, schedules, cross-references, termination provisions, and incorporated ancillary documents. Separate the condition from the acts and documents used to satisfy it. When a condition incorporates a covenant, record both references.
The executed 3M–Solventum separation agreement illustrates the distinction: § 2.8 addresses shared-contract arrangements, while § 2.12 requires execution and delivery of applicable ancillary agreements at or before the Effective Time. These are negotiated obligations, not a universal list of closing conditions. Agreement, §§ 2.8 and 2.12. (sec.gov)
Record: the operative test and linked deliverables. Place stand-alone covenants and termination rights in separate work products unless needed to explain the condition.
3. Test approval assumptions against the structure
Have responsible counsel identify the approval route before accepting resolutions as sufficient evidence. For Delaware domestic mergers under DGCL § 251, subsection (b) requires constituent-board approval and a declaration of advisability; subsection (c) supplies the ordinary stockholder-adoption and filing route. Test exceptions and alternative routes. Delaware Code § 251(b)–(c). (delcode.delaware.gov)
For asset steps, § 271(a) addresses sales, leases, or exchanges of all or substantially all assets. Section 271(c) generally removes stockholder approval for transfers to a qualifying wholly owned and controlled subsidiary unless the certificate provides otherwise. Assess the threshold, subsidiary definition, charter, and applicable exceptions rather than copying merger tasks. Delaware Code § 271(a), (c). (delcode.delaware.gov)
Record: the approval question, counsel's analysis reference, conclusion, and unresolved dependency. Keep legal prerequisites distinct from contractual conditions even when they share evidence.
4. Specify evidence proving the actual condition
Define acceptable evidence before requesting it. For a consent condition, check the correct agreement, parties, transaction, scope, and any qualifications. For an approval condition, identify adopted resolutions and evidence supporting the selected approval route. For a certificate condition, check the required signatory, date, and assertions.
Separate execution, delivery, and effectiveness wherever the documents distinguish them. Do not equate a circulated resolution with adoption or signature collection with delivery. A delivery acknowledgment may be useful evidence, but do not demand that particular form unless the governing documents require it.
Record: evidence ID, pinpoint reference, completion event, verifier, and remaining gap. Keep the status “under review” until evaluation is complete.
5. Connect sequencing and partial completion
Map each condition to predecessor steps. Check whether consent covers only part of the business, a release depends on repayment, or an ancillary agreement becomes effective only after another step. Use linked component rows where owners or decisions differ; retain an overall condition row when needed.
DGCL § 259(a) addresses statutory vesting of property and rights and attachment of liabilities following a merger, while preserving creditor rights and liens. Do not use that provision alone to clear contract or permit consent questions; assign those for separate analysis. Delaware Code § 259(a). (delcode.delaware.gov)
Record: predecessor CP IDs, partial coverage, remaining company exposure, and whether the gap blocks the relevant step. Do not label partial completion “satisfied.”
6. Verify waiver authority and permitted alternatives
Read the waiver provision and related restrictions. Identify whose benefit the condition serves, who may act, and the required form. Distinguish a proposed contractual waiver from an unresolved legal prerequisite or third-party right; escalate those separately.
In the 3M–Solventum agreement, § 3.3(b) makes the Parent Board's pre-distribution determination concerning satisfaction or waiver binding on the parties and requires specified public disclosure for waiver of a material condition. This is agreement-specific authority, not general permission to waive restructuring conditions. Agreement, § 3.3(b). (sec.gov)
A delayed transfer is not synonymous with waiver. Verify the contractual alternative and continuing obligations.
Record: authority source, decision-maker, written decision reference, qualifications, and continuing workstream.
7. Reconcile the tracker for the closing decision
Review open rows against the intended sequence. Resolve conflicting evidence, check late amendments, and identify conditions requiring confirmation at closing rather than earlier. An earlier certificate or approval may not answer the operative test at the required time.
Prepare a dated snapshot identifying satisfied conditions, documented waivers, unresolved blockers, and permitted deferred items. Separate counsel's recommendation from the authorized determination. Preserve later changes in a new snapshot.
Record: final status, evidence reviewed, decision-maker, decision time, and follow-up. Link deferred obligations to a post-closing record without changing an uncompleted transfer into a completed one.
Worked example
Fictional scenario: Alder Quay Holdings, Inc. is separating its service business into Alder Quay Services, Inc. Step 2 contributes customer contracts; Step 3 distributes the subsidiary and requires completion of Step 2. All parties, documents, and provisions below are fictional.
Executed agreement AGR-01 v4 § 6.2(a) conditions the contribution on listed consents; § 6.2(b) requires specified Holdings board approval. Section 6.3(b) conditions distribution on execution and delivery of the transition services agreement (TSA). Section 6.4 permits a written Parent Board waiver of § 6.3(b), but not § 6.2(a).
Schedule C lists a shared customer agreement. The source set contains an unsigned consent draft, a certified adopted resolution matching Step 2, and the signed TSA. Delivery evidence has not been supplied. A manager reports customer comfort, without supporting customer correspondence.
| CP ID / step | Entity / condition | Controlling source | Evidence / gap | Owner / dependency | Status | Waiver authority | Decision / action |
|---|---|---|---|---|---|---|---|
| CP-01 / 2 | Holdings / listed consent | AGR-01 v4 § 6.2(a), Sch. C item 2 | CON-03 p. 1 unsigned; assent unverified | Commercial counsel / customer execution | Evidence pending | Unavailable under § 6.4 | Obtain effective consent; Step 2 blocked |
| CP-02 / 2 | Holdings / specified board approval | AGR-01 v4 § 6.2(b) | RES-02 pp. 1–3, certified adopted resolution | Corporate counsel / structure confirmed | Satisfied | Not relied on | Verification memo DEC-02: resolution matches contractual test; separate legal analysis retained |
| CP-03 / 3 | Services / TSA execution and delivery | AGR-01 v4 § 6.3(b) | TSA-01 signature pages complete; delivery unverified | Closing counsel / delivery and Step 2 | Under review | Parent Board, written, § 6.4 | Verify delivery; waiver would not cure CP-01 |
These representative rows are not the complete closing checklist. They distinguish established approval evidence from two different gaps. The consent blocks Step 2 and therefore Step 3. Verifying TSA delivery could resolve CP-03 without waiver, but cannot cure CP-01. No supplied provision establishes a delayed-transfer route; counsel should not invent one.
Common mistakes
- One approval row for the group. Split by legal entity and step; parent resolutions do not evidence every subsidiary action.
- Linking only to the conditions article. Include incorporated schedules and definitions controlling the test.
- Treating signature collection as completion. Verify required delivery and effectiveness separately.
- Using “waived” for an unresolved consent. Identify contractual authority and separately assess counterparty rights.
- Moving gaps to post-closing for convenience. Cite the permitted alternative and preserve remaining exposure and ownership.
Final quality check
- Every row identifies the correct legal entity, step, and operative test.
- Controlling references match the current agreement and incorporated materials.
- Evidence references open to the correct record and pinpoint location.
- Satisfaction conclusions address timing, qualifications, and dependencies.
- Waivers identify authority, required form, and the actual decision record.
- Deferred items have a supported route, continuing obligations, and an owner.
- Every open issue is resolved or assigned for decision before the affected step proceeds; assignment alone does not clear a blocker.
Complete the workflow with DecoverAI
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use contract review to examine conditions and cross-references, and due diligence classification to organize sources and prioritize human review. Tabular review supports work across multiple documents; this tracker remains your work product. Company-specific instructions can focus review, while counsel verifies evidence and retains satisfaction and waiver decisions. Book a demo to discuss this closing workflow.
Frequently asked questions
Should each consent have its own row?
Yes, where counterparties, contracts, scope, or owners require independent verification. Link component rows to the overarching condition so one completed consent does not clear the whole requirement.
Can a draft agreement support the tracker?
Yes, for planning, with its version and draft status explicit. Before closing, reconcile every condition against the executed agreement and amendments, preserving unresolved changes as open issues.
Who should mark a condition satisfied?
Separate evidence collection, legal verification, and the authorized closing determination. Identify the responsible reviewer and whoever holds decision authority under the documents and governance arrangements.
How should delayed transfers appear?
Retain the original condition, provision permitting deferral, decision invoking it, and remaining obligations. Link the post-closing record. Do not describe a deferred transfer as accomplished or assume deferral satisfies the original condition.
Sources
- Delaware Code, Title 8, §§ 251 and 259.
- Delaware Code, Title 8, § 271.
- Executed 3M–Solventum Separation and Distribution Agreement, used only as negotiated wording.
Check applicable statutory effective-date provisions against the transaction date before relying on live consolidated text.
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.
