How to redline terms against a negotiation playbook for Guarantee Agreements

Redlining a guarantee from the guarantor’s perspective starts with mapping the promised support to the underlying debt, then testing each operative provision against the client’s approved negotiation positions. Trace incorporated definitions, model the cap and its exceptions, and coordinate payment triggers, waivers, amendments, and release mechanics. Record proposed language, permitted fallbacks, approval owners, and unresolved dependencies in a clause-level playbook. The deliverable is a coordinated tracked-changes draft and decision record showing what the guarantor will cover, when it must respond, and which risks remain unapproved.

When to use this workflow

Use this workflow when finance counsel or an in-house team receives a lender’s guarantee draft, a replacement guarantee, or an amendment expanding an existing guarantor’s support. It suits a parent supporting subsidiary borrowing, an affiliate joining a facility, or a seller retaining limited support after a disposal.

The task is an authorized negotiation draft, not a complete closing or release exercise. This guide assumes US commercial finance, not consumer guarantees. New York-specific points apply only where relevant; other states and cross-border structures require separate analysis. Contract rights depend on the documents, governing law, facts, and transaction context. The practical checks below are workflow recommendations, not legal requirements.

What you need

Collect the guarantee and the documents determining its reach: the credit agreement, definitions, schedules, joinders, amendments, relevant side letters, assignments, and existing releases. Include hedging or ancillary documents if their obligations may be covered. Identify missing dependencies before drafting around them.

Obtain the client’s approved instructions for:

• Covered borrowers, beneficiaries, facilities, and guarantors.
• Maximum exposure, currency, and treatment of interest, indemnities, and enforcement costs.
• Payment triggers, amendment consent, waivers, and release conditions.
• Preferred wording, permitted fallbacks, prohibited expansions, and exception approvers.

Assign document IDs and record version, source, and execution status. A negotiation playbook means the team’s own checklist and instructions, not an assumed software feature. If no approved baseline exists, obtain business instructions before labeling provisions acceptable.

Use the template

Use the Guarantee Agreements — Redlining playbook below. You can copy this table into your working document or spreadsheet. Keep one row per negotiable issue; split a provision when its cap, trigger, and waiver require different decisions.

In Source / evidence, record the document ID, section and page, and a short excerpt or precise paraphrase. Cite incorporated definitions as well as the guarantee clause. Distinguish “not present in reviewed draft” from “incorporated document unavailable.”

Approved position identifies the instruction version. Deviation / consequence explains an exposure scenario, not merely “unfavorable.” Proposed redline contains replacement wording or a reference to the tracked edit. Fallback / authority records the permitted alternative and approver. Use Status / version to distinguish proposed language, internal approval, and counterparty acceptance. Close a row only when the language and decision are verified.

Step by step

1. Establish the guarantor’s mandate and review perimeter

Confirm the represented entity and every entity undertaking liability. Identify separate, several, or joint-and-several exposure and whether later guarantors can join. Do not assume group-wide instructions authorize every subsidiary to support every debt.

Fix the working versions of the guarantee, credit agreement, and playbook. Record a dependency row for each missing incorporated document, identifying its owner and affected negotiation issues. A missing obligations definition blocks reliable scope review; it does not establish narrow coverage. Preserve the received draft so later changes can be attributed correctly.

Template output: represented entities, source versions, instruction version, and unresolved dependencies.

2. Trace the guaranteed obligations before editing the promise

Follow each defined term into the underlying documents. Test future advances, refinancing, amendments, interest, fees, indemnities, hedging, and affiliate debt. Separate monetary payment from performance duties and identify whether the creditor must first pursue the borrower or security.

Section 1 of the SEC-filed Bakkt guaranty illustrates payment and performance coverage, no requirement to pursue the debtor or security first, and payment on default without demand. This is contractual wording, not a legal rule or market benchmark.

Draft scope restrictions in the operative promise and controlling definitions. If counsel cannot amend a shared credit-agreement definition, consider a guarantee-specific definition or express exclusion and verify its priority over inconsistent language.

Template output: covered debt chain, excluded categories, payment trigger, and coordinated edits.

3. Model the cap and remove conflicting expansions

Specify currency, aggregate versus per-obligation treatment, and whether interest, indemnities, and enforcement costs fall inside the ceiling. Decide whether payments permanently reduce available exposure or whether the cap limits outstanding liability that may later revive. These produce different economic outcomes.

Do not rely on headings. Section 2 of the filed Bakkt guaranty, headed “Limited Guaranty,” refers to obligations due rather than stating an independent dollar ceiling.

Test the proposed wording against principal reaching the ceiling, additional fees, and a returned payment. Identify included, excluded, and uncertain amounts. Check nonmonetary performance promises separately: a dollar cap on payment may not clearly limit them. Escalate insolvency-related savings language for legal analysis rather than treating it as a substitute for an exposure limit.

Template output: cap mechanics, scenario result, conflicting clauses, and exception approval requirements.

4. Negotiate triggers, waivers, and amendment consent separately

Review default demands, notice waivers, defenses, collateral impairment, and amendments as distinct issues. Acceptance of a payment guarantee does not establish approval of every waiver.

Identify changes requiring consent under the client’s instructions, such as increased commitments, new borrowers, added debt categories, or extended maturity. These are proposed negotiation boundaries, not asserted legal requirements. Check that the obligations definition does not independently restore excluded coverage, and reconcile consent language with provisions preserving liability after amendments.

Review subrogation postponement, contribution, and intercompany-debt subordination separately because they concern different recovery paths. For each, state the affected right, proposed restriction, business consequence, and unresolved enforceability question rather than marking the package “standard.”

Template output: separate trigger, waiver, recovery-right, and consent rows with authorized fallbacks.

5. Coordinate termination, release, and reinstatement language

Distinguish termination of future coverage from release of existing obligations. Examine payoff, commitment termination, outstanding letters of credit, contingent claims, disposal-related release conditions, and confirmations insofar as they affect the draft.

Give reinstatement its own row. Section 7 of the filed Bakkt guaranty continues the undertaking until indefeasible payment or performance and reinstates liability when payment or value is rescinded or returned. Test whether proposed release language preserves, limits, or conflicts with that exposure.

Borrower discharge is not equivalent to guarantor release. Subject to its express § 524(a)(3) exception, 11 U.S.C. § 524(e) provides that discharge does not affect another entity’s liability on the debt or another entity’s property securing it. Separate releases, injunctions, defenses, and a guarantor’s own bankruptcy require further analysis. (uscode.house.gov)

Template output: release trigger, surviving exposure, reinstatement treatment, and unresolved questions.

6. Verify notice and execution dependencies

Compare demand requirements with notice waivers and general notice provisions. If adding written demand, specify recipient, delivery method, effectiveness, required content, and any negotiated response period. Preserve notices still required elsewhere rather than assuming a waived default demand eliminates all notice obligations.

Check execution requirements under applicable law. New York General Obligations Law § 5-701(a)(2) places a special promise to answer for another’s debt, default, or miscarriage within its subscribed-writing requirement. Whether an undertaking falls within that provision, satisfies it, or implicates an exception requires legal and factual analysis; this is not a nationwide execution standard. (nysenate.gov)

Template output: coordinated demand wording, missing recipient details, and assigned execution questions.

7. Reconcile the redline and obtain exception decisions

Read the revised guarantee as a whole and compare it with the received draft. Check repeated definitions, precedence language, and cross-references affected by edits. Confirm that the ceiling controls separately stated costs, indemnities, and reinstatement as intended.

Give approvers the baseline, counterparty wording, proposed fallback, consequence, and residual uncertainty. Record approval evidence against the precise draft version; approval of one formulation does not authorize a later expansion. Return the tracked draft with unresolved objections and dependencies identified. Keep internal approval separate from counterparty acceptance.

Template output: reconciled draft version, approval evidence, negotiation status, and outstanding owners.

Worked example

Fictional scenario: Alder Quay Holdings LLC must review a guarantee of its subsidiary Bracken Instruments LLC’s loan. Fictional instructions P-01 authorize payment support for the identified loan, with a USD $4 million outstanding-liability ceiling including enforcement costs. Returned payments may revive liability only within that ceiling. New debt categories need general counsel approval, and payment requires written demand.

Fictional draft G-03 covers obligations under Credit Agreement C-02 as amended, excludes collection costs from the ceiling, and reinstates liability after returned payments without expressly applying the ceiling. C-02 references an unavailable hedging schedule. The notice schedule is also incomplete. Counsel prepares G-04; neither missing schedule’s contents are assumed.

The ceiling is not enough: excluded costs breach the mandate, and reinstatement needs explicit coordination. R3 does not promise a lifetime payments cap; P-01 authorizes a ceiling on outstanding liability that can revive. The missing hedging schedule prompts an exclusion and evidence request, not an invented finding about its contents.

Written demand belongs in a separate playbook row, omitted from these three representative entries. Counsel adds demand mechanics in G-04 but reserves completion until treasury supplies the notice details. No row is treated as accepted merely because a redline was drafted.

Common mistakes

• Editing only the operative promise. An incorporated definition may preserve broader coverage. Coordinate both and check precedence.
• Recording only the cap amount. Costs, performance duties, payment reductions, and revival can change exposure. Model the mechanics.
• Deleting waivers as one package. Separate protections and obtain authority for each fallback.
• Adding demand without delivery mechanics. Align recipient, effectiveness, content, and response timing with notices.
• Treating missing documents as exclusions. Record an evidence gap and propose express limits where authorized.

Final quality check

Before circulating, confirm:

• Material rows identify document version and clause or page.
• Obligations trace to complete definitions or assigned gaps.
• Cap mechanics address costs, indemnities, payments, and reinstatement.
• Payment triggers and notices operate together.
• Consent and release edits survive cross-reference review.
• Legal propositions match primary sources and jurisdictional limits.
• Exceptions have version-specific approval; open issues have owners and next actions.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. In contract review and redlining, choose the represented party in Word and provide deal-specific instructions. Findings quote clauses, rank severity, locate text, and identify missing language as not present. The lawyer edits or inserts suggestions as ordinary tracked changes in the signed-in Word user’s name and can dismiss findings with reasons. Tabular review supports work across multiple documents; counsel retains scope, legal analysis, and approval decisions. To assess the workflow against your guarantor instructions, book a demo.

Frequently asked questions

Should the guarantor insist on a collection guarantee?

Treat that as a client decision. Explain when payment arises and whether pursuit of the borrower or security is required. Record the authorized trigger before editing.

Can a public guaranty supply the negotiation baseline?

It can illustrate wording, not establish market practice or client authority. Use approved instructions as the baseline and identify public wording as an example.

What if the lender accepts the cap but rejects other edits?

Check excluded costs, expanded debt, performance duties, and revival. Present each remaining deviation for approval; acceptance of the number alone does not resolve exposure.

Can counsel circulate before receiving every schedule?

Where appropriate, circulate a controlled negotiation draft expressly reserving material dependencies. Identify affected clauses and owners. Do not describe scope or notice details as verified while controlling documents remain unavailable.

Sources

• New York General Obligations Law § 5-701: subscribed-writing requirement for specified promises.
• 11 U.S.C. § 524: discharge and other-entity liability.
• Bakkt Global Guaranty Agreement, SEC Exhibit 10.3: example-specific scope, limitation, and reinstatement wording.

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.