Red-flag customer contracts for change of control and exit rights

For: M&A associate or corporate development manager on a buy-side review

Pattern: Map, verify, reduceRuns todayDesigned for 4 to 300 agents

The pain today

The value of the target sits in its customer contracts, and the data room holds hundreds with order forms and amendments. Juniors summarise them overnight, and a termination right in a major contract is found after the price is agreed.

The ask

I attached the target's customer contracts from the data room. For each one, tell me whether it has a change-of-control or assignment restriction, exclusivity, most-favoured-customer pricing or termination for convenience, quote the clause, and flag contracts where the documents in the folder disagree.

Plain words, as you would say it to a colleague. Edit it to fit your case before you send it.

What you attach or connect

  • Customer contracts with order forms and amendments
  • Customer list with revenue ranking
  • Red-flag checklist for the deal

The unit of work

One worker task per one customer contract folder.

Why a swarm fits

Each contract folder is reviewed alone against the same short checklist, so context per worker is small. Folders are independent, and every flag can be checked against a quoted clause.

Not for

A target with a handful of customer contracts: counsel should simply read them in full.

The decision tree

6 typed decisions, each with an action for every answer

At fixed moments in a run, the engine puts one narrow question to a decision model. The decision model never writes text: it answers yes or no with a probability, picks from listed options, or gives a score, about a small slice of the material. The engine then does exactly what this tree says, which is what makes the run auditable. The thresholds are the template's design values, not measured results.

  1. Planner, while planning

    Scope checkYes or no, with a probability

    Before work starts on a unit

    Is this folder's main document an executed customer agreement, rather than a template, a quote or a supplier contract filed in the wrong place?

    Sees only: The main document's title, parties and signature page

    Why: Misfiled and unsigned documents are reported, not reviewed as contracts.

    • Yes: 0.60 or higherthenAccept
    • Unsure: 0.30 up to 0.60thenAccept
    • No: below 0.30thenSkip this unit
  2. Before workers, before a task runs

    Small worker or strong modelYes or no, with a probability

    Before a task runs

    Is the agreement on the target's own standard terms, without negotiated riders or the customer's paper?

    Sees only: The agreement's first pages and its list of annexes

    Why: Customer-paper contracts hide their restrictions in unusual places.

    • Yes: 0.60 or higherthenAccept
    • Unsure: 0.40 up to 0.60thenEscalate to a strong model
    • No: below 0.40thenEscalate to a strong model
  3. After workers, the judge checks

    Evidence checkYes or no, with a probability

    After a worker answers

    Does the quoted clause let the customer terminate or withhold consent on a change in ownership of the target, as opposed to an assignment of the contract only?

    Sees only: The flag, the quoted clause and the agreement's definitions

    Why: In a share deal only the ownership trigger matters, and the two are easily confused.

    • Yes: 0.90 or higherthenAccept
    • Unsure: 0.50 up to 0.90thenEscalate to a strong model
    • No: below 0.50thenReject and retry
  4. Evidence checkYes or no, with a probability

    After a worker answers

    Do the sections listed as searched include the assignment, termination and general provisions of this agreement?

    Sees only: The 'no flag' result, its searched-sections list and the table of contents

    Why: A clean result is only worth something if the right sections were read.

    • Yes: 0.85 or higherthenAccept
    • Unsure: 0.50 up to 0.85thenReject and retry
    • No: below 0.50thenReject and retry
  5. Reconciler, while merging

    Conflict checkA choice among options

    While reconciling

    Does an order form or amendment in the folder change the termination or exclusivity terms of the main agreement?

    Sees only: The main clause and the later document's passage on it

    Why: The signed amendment, not the main agreement, is often where the exit right sits.

    • Changes the term and says sothenAccept
    • Changes it without saying which prevailsthenMark unresolved
    • Leaves the term untouchedthenAccept
  6. Accountable person, before anything is settled

    Person decidesYes or no, with a probability

    Before anything is reported as settled

    Does this flag sit in a contract with one of the top-ranked customers by revenue?

    Sees only: The flag and the customer's revenue rank

    Why: Deal counsel confirms every flag that can move the price.

    Accountable: Deal counsel confirms each red flag and decides what goes into the report and the price discussion.

    • Yes: 0.30 or higherthenAsk a person
    • Unsure: 0.10 up to 0.30thenAsk a person
    • No: below 0.10thenAccept

The fleet: who does what

Model tiers by role, not brands: you choose the models. Strong reasoning models plan and reconcile, small fast models do the wide work, and the judge is a decision model from a different family, so it does not share the workers' blind spots.

  1. Planner

    A strong reasoning model turns the red-flag checklist into precise questions and orders folders by customer revenue.

    Decisions here:1. Scope check

  2. Workers

    Small fast workers from an open-weight family review one contract folder and quote the clause behind each flag.

    Designed for 4 to 300 agents, one worker task per one customer contract folder. Each worker receives only its own unit.

    Decisions here:2. Small worker or strong model

  3. Judge, from a different model family

    A decision model from a different family checks that the quoted clause really creates the flagged right or restriction.

    Decisions here:3. Evidence check4. Evidence check

  4. Reconciler

    A strong reasoning model builds the red-flag schedule, weighted by customer importance, and keeps document conflicts visible.

    Decisions here:5. Conflict check

  5. Accountable person

    Deal counsel confirms each red flag and decides what goes into the report and the price discussion.

    Decisions here:6. Person decides

Checked before anything is accepted

  • Every flag quotes the clause with document name and section
  • A 'no flag' result states which sections were searched
  • Amendments and order forms are checked for overrides of the main agreement
  • Missing pages, unsigned copies and referenced but absent documents are reported

What comes back

  • Red-flag schedule per customer contract with quotes
  • Flags ranked by customer revenue
  • Folders with conflicting or incomplete documents
  • Questions for the seller's Q&A log

What to measure

  • Flags confirmed by the reviewing lawyer
  • Red flags found later that the run missed
  • Lawyer hours per contract
  • Cost per reviewed contract against a single-model baseline

Names of measures only. No result is claimed for this template.

Templates open in the workspace chat with the ask filled in. Nothing runs until you send it.

Get early accessSign in to use

Test every claim in the information memorandum against the data room

For: Private equity investment manager or corporate development lead before a binding offer

The seller's memorandum and management presentation make claims about customers, retention, pipeline, capacity and compliance.

Pattern: Adversarial reviewNeeds live models6 decisionsDesigned for 8 to 400 agents

Read each disclosure against the warranty it qualifies

For: Transaction counsel for buyer or seller negotiating the disclosure letter

A disclosure letter arrives late with general and specific disclosures and bundles of documents.

Pattern: Cross-examinationNeeds live models6 decisionsDesigned for 6 to 250 agents