Work & Productivity·February 24, 2026

200-Page Contract at 4:45 on a Friday? The Lawyer's Playbook.

TL;DR

200-page MSA from opposing counsel at 4:45 PM Friday. Closing Monday. Here's the lawyer's playbook to find the clauses that matter and get a first map of the deal.

Downtown lawyer's desk at 4:45 PM on a Friday — tailored blazer on the chair, weekend bag by the door, city lights glowing outside the window, laptop open to a 200-page MSA with highlighted clauses and color-tabbed sticky notes

It's Friday. 4:45 PM. You were already packed.

Blazer on the chair. Weekend bag by the door. One last glance at the inbox before you left.

Then it came in. Outlook notification, calm as a knife: opposing counsel has sent you a 200-page MSA. Version fourteen. Labeled "FINAL." Again.

You sit back down.

Every lawyer has this Friday. The deal team wants a memo Monday at nine. The client wants a call Sunday night. The file is a minefield of defined terms, cross-references, and clauses that reference other clauses, which reference schedules, which reference other schedules. Two hundred pages to read, cross-check, summarize, and come back with a real position.

Your weekend plans are already a theoretical exercise.

Here is what actually works.

The move: stop reading it cover to cover

The mistake every lawyer makes at 4:45 on a Friday is starting on page one.

A 200-page contract is not a book. It is a structured document with about fifteen sections that actually matter, maybe forty defined terms you need to track, and three to five clauses that will either kill the deal or kill your client. Reading it front to back is how you end up at page 63 at 10 PM having absorbed nothing.

What you need is structure first. Then targeted interrogation. Then the memo writes itself.

The playbook

Step 1. Drop it in

Open CorpGPT. Drag the PDF straight from the email into the Sources pane in My Workspace (Add → upload).

Don't preview it. Don't open it. Don't scroll. The entire point is that you are going to read it through the lens of the tools, not the scroll bar.

While it processes, refill the coffee.

Step 2. Get the structure

Open the Make pane ("Make from these sources") and ask for:

  • Executive brief — one page on the terms it finds, such as scope, term, payment, termination, IP, liability and governing law. A first pass at a term sheet.
  • Glossary of defined terms — the defined terms in the passages it reads, each with its definition. Check it against the definitions section before you lean on it.
  • Mind map of obligations — who owes what to whom, what happens if they don't, and when.

Three outputs. Each one is built from the ten or so passages that best match it — not all 200 pages — so what you have is a first map of the deal, not a substitute for reading the clauses that matter.

Read the executive brief once. Star the two or three things that surprised you. Those are where you'll spend your time.

Step 3. Interrogate Chat

Chat sits in the middle of My Workspace. Same screen, no context-switch.

Ask the questions your partner is going to ask you on Monday:

  • "What's our indemnity exposure? Is it capped?"
  • "Can they terminate unilaterally? Under what conditions?"
  • "Is there an auto-renewal? What's the notice window?"
  • "What's the governing law and venue?"
  • "What counts as a material breach? What's the cure period?"
  • "Are there any exclusivity or non-compete provisions? How broad?"
  • "What happens to the IP we bring into the engagement?"

Answers drawn from the contract end with a numbered source list: Chat names the source document, and the page, slide or section when CorpGPT can place it. The answers often quote the clause number too: §11.6, Schedule 4, item 3. Click the source to open the contract (a PDF opens at the cited page), so you verify before you trust it.

This is the part that used to be a hunt. Ctrl-F through 200 pages, chase the cross-references, read three sections to understand one, and end up unsure whether you missed something. It is now a conversation with the document.

Step 4. Find the traps

Ask Chat to flag the clauses a reasonable counterparty wouldn't accept without negotiation:

  • Uncapped liability or indemnity
  • Unilateral termination without cure
  • Automatic renewal buried deep in the document
  • Unilateral amendment rights
  • Most-favored-customer pricing commitments
  • IP ownership of pre-existing or derivative works
  • Jury trial waivers, class-action waivers, venue lock-ins
  • Any "notwithstanding anything to the contrary" with real teeth

You get a list of what it found, and the answer's source list names the source document, and the page, slide or section when CorpGPT can place it; the answer often quotes the clause number (§4.2, §11.6), so you can go straight to it in the contract. Chat reads the passages that best match your question, so a clause it doesn't list is not proof the contract is clean — check the sections that matter yourself.

You now have a redline target list to check against the contract.

Step 5. Draft the client memo

Ask Chat to draft the factual half of the client memo: what the contract says it does, and the clauses behind the issues you starred, quoted with their section numbers. It works from the same uploaded document, and the answer names the document it drew on. The redlines and the legal reasoning are yours — CorpGPT doesn't give legal advice.

You add the redlines, your analysis and your judgment calls — the tool can't do those — and send it up to the partner.

What you have in hand

A first map of the deal, a redline target list with the clause numbers to check, and the factual half of the client memo in draft. The redlines, the analysis and the call on what matters are still yours.

Why this actually works

Three forces are doing the real work.

First, structure beats scrolling. Contracts are not linear documents. They are graphs of defined terms, cross-references, and conditional obligations. A mind map and a glossary are the native way to read them. A PDF viewer is not.

Second, interrogation beats search. You are not grepping for the word "indemnity" across 200 pages. You are asking, "What's our indemnity exposure?" and getting an answer built from the passages that best match — often the clause and the cap it points to. Cognitive load drops from "find it" to "understand it."

Third, citations make it checkable. Chat names the source document, and the page, slide or section when CorpGPT can place it. You verify before you trust. No "the AI said so." You walk into the Monday meeting knowing where each claim you checked came from.

What this can't do

Be honest about this.

CorpGPT does not practice law. It does not give legal advice. It does not assess materiality, weigh risk tolerance, or negotiate with opposing counsel. It does not know your client's business, your firm's precedent on this type of deal, or the partner's appetite for this particular fight.

What it does is take the slow first pass out of every contract review — the summarization, the glossary-building, the cross-referencing, the Ctrl-F grind. That's the grunt work. The analysis, the redlines, the negotiation call — that's still you.

You are the lawyer. You sign the memo. The tool just makes sure you had time to think before you signed it.

The bottom line

Find the clauses that matter. Read them yourself.

Opposing counsel ambushed a lot of careers by sending MSAs at 4:45 on a Friday. They are going to keep doing it. What changes is what you do about it.

Open CorpGPT. Drop in the contract. Ask Chat where the exposure clauses are.


Keep reading

Ready to try it yourself?

Upload any document and see it in action. Free to start, no credit card.

Start My Free Workspace