How to track conditions precedent with source references for Acquisition Financing Transactions

Track acquisition-financing conditions precedent by turning each operative condition into a source-linked record that distinguishes agreement effectiveness, acquisition completion, and loan funding. For each record, identify the testing time, satisfaction evidence, responsible reviewer, dependencies, and waiver or deferral authority. Reconcile the records against the executed financing documents and acquisition agreement before requesting funds. The deliverable is a borrower-side conditions tracker that explains why each requirement is verified, unresolved, waived, or expressly deferred—not merely which documents have arrived.

When to use this workflow

Use this workflow when borrower’s counsel or an in-house legal team needs to establish readiness for acquisition borrowing: while negotiating commitments, reviewing definitive financing documents, and preparing for funding. Keep its scope on conditions analysis rather than the entire closing checklist.

Effectiveness does not necessarily establish borrowing readiness. Portland General Electric’s filed credit agreement separates effectiveness conditions in Section 4.1 from closing-date borrowing conditions in Section 4.2 (Sections 4.1–4.2).

This is a general workflow for US transactional practice. Apply the actual documents, governing law, acquisition structure, and facts. The filed agreements discussed below concern separate transactions; their provisions are examples, not a combined contractual framework or evidence of market standards.

What you need

Assemble these inputs before assigning satisfaction statuses:

• Operative commitment letter, conditions annex, fee provisions relevant to availability, credit agreement, amendments, waivers, and incorporated definitions.
• Acquisition agreement, amendments, relevant schedules, closing conditions, and notices affecting termination or cure rights.
• Borrower and guarantor authority documents, certificates, opinions, and required borrowing notices.
• Funds flow, equity evidence, payoff and release arrangements, collateral deliverables, and acquisition-completion confirmation requirements.
• Document index showing stable IDs, execution status, versions, locations, and named financing, acquisition, collateral, and treasury contacts.

Tie each missing-document request to its financing question. “Provide the final acquisition amendment to assess the financing consent condition” is more useful than “upload outstanding documents.” Distinguish a missing source from a reviewed source containing no relevant requirement. Include prior amendments even when the latest document appears complete.

Use the template

Use the Acquisition Financing Transactions — Conditions precedent tracker. You can copy this table into your working document or spreadsheet. Assign one row per independently testable requirement, with linked subrows where a clause contains several components.

In Condition / source, enter the document ID, operative version, clause, relevant definition, and amendment reference. Add page citations where useful, but retain clause references when pagination changes. A hyperlink without a description does not explain the obligation.

In Evidence / location, identify the evidence document and pinpoint supporting passage. Explain what it establishes. In Test time, preserve the contractual event, date, notice interval, and relevant time zone. Record dependencies by CP ID rather than repeating another row’s analysis.

Use distinct statuses: open, delivered pending review, verified as of a stated time, waived, and expressly deferred. Put the reviewer and review timestamp in the status entry or linked review note. The coordinating owner is not necessarily the person authorized to approve an exception.

Step by step

1. Establish the operative source set

Identify which documents govern availability for the contemplated borrowing. Determine how commitment-stage conditions relate to definitive documentation; do not assume an early checklist remains controlling. Read amendments, side letters, annexes, and incorporated definitions before extracting requirements.

Create a dated reference set. When revised documents arrive, compare affected provisions and reopen impacted rows instead of silently replacing citations. Preserve the history of a removed condition so the team can explain why it disappeared.

Record: governing document IDs and versions in source cells, with superseded references retained in working history.

2. Separate conditions by event and testing time

Classify requirements as effectiveness, acquisition completion, or borrowing. Identify the financing provision before treating an acquisition closing condition as a loan-funding condition. Track commitment availability separately where expiry or another termination trigger could prevent funding.

Distinguish completed acts from statements that must remain accurate at borrowing. A certificate signed earlier may need refreshing; conversely, an effectiveness requirement should not automatically be retested if the documents do not require that result.

Record: phase, exact testing event, required notice timing, and refresh requirements. Link related rows without allowing effectiveness approval to clear borrowing conditions.

3. Preserve qualifications and cross-references

Break long conditions into testable components without discarding materiality thresholds, exceptions, defined terms, or consent mechanics. For acquisition representations, read the financing condition alongside the referenced acquisition provisions and relevant notice and cure rights.

Portland General Electric’s Section 4.2(vii) links acquisition-representation inaccuracies to acquisition closing conditions or termination rights, accounting for notice and cure provisions. Read that limitation alongside the Specified Representations and remaining funding conditions (Section 4.2(vii)).

Keep diligence risk separate from funding relevance: a significant finding needs analysis, not an automatic funding-blocker label.

Record: condition logic, linked definitions, factual uncertainties, and any interpretation requiring counsel’s decision. Avoid shorthand such as “all representations true.”

4. Define satisfaction evidence before chasing documents

Specify what each reviewer must establish. For authority, connect resolutions and incumbency evidence to the correct entity, transaction, and signatory. For payoff arrangements, distinguish an agreed payoff amount from the required release authorization. For acquisition completion, identify the confirming lawyer and expected contemporaneous evidence.

Separate preparation, execution, delivery, and substantive review. Identify contractual recipient-acceptance requirements without inventing additional approval rights. Maintain a review note where the reasoning exceeds the table’s practical capacity.

Record: evidence IDs, page or paragraph references, reviewer, deficiencies, and the basis for verification. Do not treat a filename or an assurance that documents are forthcoming as proof.

5. Map acquisition and funding dependencies

Read conditions against the funds flow. Connect sponsor equity, available cash, loan proceeds, acquisition consideration, refinancing, and release arrangements. For concurrent performance, agree who confirms each event and in what sequence; do not demand pre-funding proof of an event contractually permitted to occur concurrently.

Portland General Electric’s Section 4.2(ii) addresses substantially concurrent acquisition consummation, arranger consent for specified adverse acquisition-agreement changes, and express purchase-price exceptions (Section 4.2(ii)). Treat changed consideration as a prompt to apply the actual clause, not proof that consent is required.

Record: prerequisite CP IDs, confirmation sequence, revised funds-flow reference, and owner for each unresolved dependency.

6. Validate waivers and permitted deferrals

Identify who can authorize the particular exception, in what form, and for which borrowing. Distinguish a waiver from a contractual permission to complete an item later. Check conditions attached to that permission, including efforts requirements and excluded collateral.

Shutterfly’s commitment letter permits certain unavailable perfection and insurance items after closing, following commercially reasonable efforts, within agreed timing capped at 60 days unless extended by the collateral agent. Its UCC Filing Collateral and Stock Certificate exclusions limit that permission (Certain Funds Provisions). This is not a general grace period.

Record: authorizing provision or written waiver, approving parties, scope, residual requirement, and linked post-closing record. Keep eligibility open until exclusions are checked.

7. Reconcile and issue the funding-readiness view

Review unresolved rows with financing counsel, acquisition counsel, and treasury. Recheck the borrowing date against commitment availability, acquisition timing, and defined extension mechanics.

Shutterfly’s Section 11 includes automatic termination triggers tied to acquisition completion without the facility, a defined outside-date mechanism, and valid acquisition-agreement termination or publicly announced abandonment; it also preserves specified obligations (Section 11). Do not reduce availability review to one calendar date.

Issue a dated report distinguishing verified conditions, authorized exceptions, concurrent confirmations, and blockers. State assumptions expressly rather than declaring the tracker “complete” from delivery counts.

Record: review timestamp, contemplated borrowing, remaining decision owners, and evidence required before the borrower’s funding authorization.

Worked example

Fictional scenario: Alder Quay Holdings proposes to acquire Beacon Valve Manufacturing using a $120 million acquisition term loan and sponsor equity. All parties, documents, amounts, and provisions here are fictional.

Signed credit agreement FIN-01 separates effectiveness from borrowing. Section 4.2(c) requires substantially concurrent acquisition completion and restricts specified adverse acquisition amendments, subject to stated price exceptions. Section 4.2(f) requires pledged share certificates at funding; Schedule 6 excludes them from permitted post-closing work.

The team receives a complete authority package, an unsigned acquisition amendment, and an email reporting unavailable share certificates. The revised funds flow assumes higher consideration, but the team has not established whether that reflects the amendment or a permitted adjustment. Financing commitments otherwise remain available for the proposed date.

CP-01 establishes only the authority condition, not every effectiveness requirement. CP-02 does not yet establish that consent is necessary: counsel needs the final amendment and adjustment analysis. CP-03 identifies a funding obstacle because the stated deferral excludes the missing item.

The borrower should not authorize funding on this record. Its readiness report assigns the amendment analysis and certificate issue, while preserving acquisition-completion confirmation as a separate concurrent dependency. No missing execution, receipt, or completion evidence is inferred from the draft documents.

Common mistakes

• Treating every closing task as a funding condition. Tie each asserted blocker to an operative provision; identify convenience deliverables separately.
• Marking receipt as satisfaction. Check entity, transaction, execution, substantive coverage, and testing time before verification.
• Losing limited-conditionality language. Preserve exceptions and linked acquisition rights rather than expanding the negotiated funding test through shorthand.
• Assuming collateral work can follow closing. Check permitted scope, efforts requirements, exclusions, deadline, and extension authority.
• Leaving source references stale. Reconcile amended acquisition terms and revised funds flows; reopen affected conditions rather than retaining an earlier approval.

Final quality check

• Every condition cites an operative document, version, clause, and relevant definition.
• Effectiveness, acquisition completion, borrowing, and availability remain distinguishable.
• Qualifications and amendments have been checked against source text.
• Evidence supports the correct entity, transaction, and testing time.
• Concurrent confirmations have an agreed sequence and named participants.
• Waivers and deferrals have documented authority, scope, and evidence.
• Open issues are resolved or expressly assigned, and unresolved blockers remain visible in the dated readiness report.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use contract review and tabular review across financing documents to support the analysis. In Word, choose the borrower as represented party and provide deal-specific instructions; findings quote clauses, rank severity, locate text, and identify missing language as not present. The tracker remains the team’s working document, and lawyers verify sources, interpret conditions, and decide statuses. To discuss this acquisition-financing workflow, book a demo.

Frequently asked questions

Should each deliverable have its own row?

Separate deliverables when owners, timing, or acceptance criteria differ. Link them to the governing condition so several received documents do not conceal one unresolved substantive requirement.

Can borrower’s counsel verify a condition without lender confirmation?

Distinguish counsel’s verification from contractual recipient acceptance. Apply any express acceptance or deemed-acceptance mechanics; do not assume silence is approval or invent a confirmation requirement.

How should concurrent acquisition completion be tracked?

Keep it pending until the agreed confirmation occurs. Record the contractual concurrency standard, confirming contact, evidence, and sequence. An earlier forecast of completion is not contemporaneous confirmation.

What happens to an expressly deferred condition?

Retain its source and authorization in the closing tracker. Link a post-closing record containing the trigger, contractual deadline, owner, extension authority, and completion evidence. Deferral changes timing, not completion status.

Sources

• Portland General Electric credit agreement, Sections 4.1–4.2: separate effectiveness and borrowing conditions and acquisition-related qualifications.
• Shutterfly commitment letter, Certain Funds Provisions and Section 11: negotiated deferral exclusions and commitment termination mechanics.

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.