Prompt to Compare Two Contracts Clause by Clause
Northgate Stage builds the staging, sound, and lighting for a three-day festival that sells 12,000 tickets, and two venues are bidding to host it this September. Harbourfront Pavilion quotes 84,000 dollars with a shared rigging crew; Rowanfield Arena quotes 91,000 with its own crew but a 20 percent cancellation penalty. Producer Dana Okonkwo has both PDFs and one afternoon, and the differences that matter are buried in the indemnity and force-majeure clauses, not the headline price.
Reading two contracts side by side by eye is where money quietly leaks. The prompt below turns both documents into one difference table, flags the clauses that carry real risk, and writes the questions to send your lawyer, so the expensive human review starts from a shortlist instead of page one.
Two Contracts, One Festival, Two Sets of Terms
Both agreements run to fourteen pages and share the same basic shape, but the terms that decide cost and exposure diverge early.
- Load-in window: Harbourfront allows a single 10-hour build; Rowanfield allows two 8-hour builds across nights.
- Insurance: Rowanfield requires a 5 million dollar liability policy; Harbourfront requires 2 million.
- Cancellation: Rowanfield charges 20 percent of the fee if the festival cancels within 60 days; Harbourfront charges nothing before 30 days.
- Damage: Harbourfront assigns floor-damage liability to the renter; Rowanfield caps it at 15,000 dollars.
- Exclusivity: Harbourfront bans competing food vendors on site; Rowanfield permits them.
None of those lines is a dealbreaker on its own. The risk is missing one, which is why the comparison has to be systematic rather than a skim.
The Clause-by-Clause Comparison Prompt
Paste both contracts into the prompt, keep the bracketed labels, and leave the output rules in place. Ask for a table first so the model cannot bury the key difference in prose.
You are a contracts analyst helping a small event production company compare two
venue agreements for the same three-day festival. You are not a lawyer and you must
not give legal advice. Your job is to surface differences and risks for a human
counsel to review.
Party A contract (Harbourfront Pavilion):
[CONTRACT_A]
Party B contract (Rowanfield Arena):
[CONTRACT_B]
Our situation: three-day festival, 12,000 attendees, load-in needs a 10-hour build,
we carry our own rigging, budget is tight and a cancellation is possible if ticket
sales miss 8,000 by August 1.
Return the comparison in this order:
1. Difference table with columns: clause, what Party A says, what Party B says,
which is better for us, and why in one sentence. Cover at minimum: fees and
payment schedule, load-in and load-out windows, insurance, indemnity, liability
and damage caps, cancellation and rescheduling, exclusivity, and termination.
2. Risk flags. List every clause that could cost us more than 10,000 dollars or
delay load-in, ranked high to medium.
3. Missing or one-sided terms. Note anything a venue contract normally contains that
is absent or unusually one-sided in either document.
4. Questions for counsel. Write the five to eight questions a lawyer should answer
before we sign, phrased so the answer is a clear yes, no, or number.
Rules:
- Quote the exact clause text you rely on, in quotes, next to each claim.
- If a clause is not in the document, write "not addressed" rather than guessing.
- Use plain English. Define any term of art in parentheses.
- Do not recommend A or B. Present the trade-off and let us decide.What the rules prevent: without the “quote the exact clause” instruction, the model tends to paraphrase and occasionally invent terms. Requiring quotes forces it to stay inside the text you pasted, and the “not addressed” rule stops it from filling gaps with assumptions.
Values to Swap In
Change these fields for your own pair of documents. The rest of the prompt is structural.
- The two contracts. Replace CONTRACT_A and CONTRACT_B with the full text. Strip headers and page numbers that repeat on every page.
- The situation line. This is the highest-leverage field. State your size, your operating constraints, and the specific risk you are worried about, because it decides what counts as “better for us”.
- The dollar threshold. Change 10,000 to whatever sum is material to you. A 2,000 dollar threshold on a small deal surfaces more flags.
- The required clause list. Add delivery dates, staffing, utilities, parking, noise curfews, or union rules if they apply to your event.
- The role line. Keep “you are not a lawyer”. It keeps the output in the compare-and-flag lane instead of the advise lane.
Reading the Returned Difference Table
For the festival, the table made the price gap irrelevant. Harbourfront was 7,000 dollars cheaper, but its single 10-hour build window collided with the rigging crew’s availability, and its uncapped floor-damage liability was the real exposure. Rowanfield cost more up front and capped damage at 15,000 dollars, which turned a variable risk into a fixed number.
The risk flags came back in a useful order: the uncapped damage clause first, the exclusivity ban second because it would have forced the festival to drop two food vendors, and the cancellation terms third. The questions for counsel included whether the damage liability could be capped, whether the build window could be extended, and what the exclusivity clause covered. Before any of this reaches a signature, keep the output in a format a reviewer can scan, which is the point of the template in our structure output format guide.
One habit that saves time: run the comparison once with both contracts in full, then a second time with only the indemnity, liability, and termination sections. The second pass is short and catches the asymmetry that matters most, because indemnity and liability language is where venues hide the risk they do not want to discuss. The headline fee is rarely the deciding number, and the second pass proves it fast.
Tuning the Prompt for Other Deals
- Vendor or supplier agreements. Swap “venues” for “suppliers” and add payment terms and delivery penalties to the required clause list.
- Software contracts. Add data ownership, uptime guarantees, and termination-for-convenience to the clause list.
- Longer or scanned documents. Split each contract into sections and run the comparison twice, then merge, using the chunking approach in our context window budget guide.
- Machine-readable output. Ask for the difference table as JSON so it can drop into a spreadsheet, following the pattern in our JSON output prompt.
When the two documents use different clause numbering, add one line: “map Party B’s clause numbers to Party A’s by topic before comparing.” Without it the model aligns by number and quietly mismatches sections, which is the single most common source of a wrong comparison. A five-second instruction prevents an error that costs hours to unwind.
Whatever variant you choose, hand the marked-up table to a qualified lawyer before signing. The prompt narrows what they need to read; it does not replace them. Treat its output as a reading aid that points at the risky paragraphs, and note that a comparison is only as good as the text you pasted, so confirm the documents are the final versions rather than a draft one side is still editing.
Sources & Notes
The compare-and-flag sequence here is our own framing of standard contract review practice, reviewed on 2026-10-12. Northgate Stage, Dana Okonkwo, Harbourfront Pavilion, Rowanfield Arena, and the three-day festival are illustrative examples, and the figures are representative rather than actual. This is not legal advice, and no AI comparison should stand in for a qualified lawyer. Language models change between versions, so re-check the prompt and verify every quoted clause against the source document before you rely on it.
