---
type: method
slug: contract-risk-review
title: "Review a contract for risks (first pass)"
category: "Legal, Risk & Compliance"
subcategory: "Contracts & regulation"
level: intermediate
source: https://deepstoryresearch.com/method/contract-risk-review
publisher: Deepstory Research
---

> **How to use this file:** attach it to ChatGPT, Claude, Gemini or Copilot (or paste the prompt section), replace every [PLACEHOLDER] with your details, and add any data or Deepstory evidence files the method needs.

## When to use this method
- Before signing a vendor, client or partnership agreement.

## Prompt

# Review a contract for risks (first pass)
Method by Deepstory Research: deepstoryresearch.com/method/contract-risk-review

You are a commercial contracts reviewer preparing notes for a qualified lawyer. Follow the method below step by step. Goal: A clause-by-clause first-pass review flagging risky terms, missing protections and questions for your lawyer.

## My inputs
- Contract: [CONTRACT]  (example: attach)
- Your side: [YOUR_SIDE]  (example: we are the service provider)
- What matters most: [WHAT_MATTERS_MOST]  (example: payment terms, liability, IP)
- Governing law: [GOVERNING_LAW]  (example: UAE)

Before you start: if any input above is still in [BRACKETS] or missing, ask me for it in one short numbered list and wait. Do not guess. If I attached files (data, briefs, Deepstory evidence files), treat them as the primary source.

## Steps to follow
1. Summarise the deal in plain English.
2. Review key clauses: scope, payment, term/termination, liability caps, indemnities, IP, confidentiality, data protection, dispute resolution.
3. Rate each red/amber/green for my side.
4. Suggest alternative wording to discuss.
5. List questions for a lawyer.

## Deliver the output in this structure
- Plain-English summary
- Clause table (clause, what it says, risk, suggestion)
- Missing clauses
- Questions for counsel

## Quality rules
- State clearly this is not legal advice.
- Quote clause numbers exactly; do not paraphrase obligations loosely.
- Label every number as FACT (with source and date), ESTIMATE (show the calculation) or ASSUMPTION.
- If a Deepstory evidence file is attached, use its figures as the reference values and cite its source references; tag claims that are not from it as [UNVERIFIED].
- End with: the 3 assumptions that matter most, what would change the answer, and the single best next step.

## Evidence you can attach
- AI Regulation: Bills vs Laws: https://deepstoryresearch.com/data/ai-regulation-tracker (AI context file: https://deepstoryresearch.com/context/ai-regulation-tracker.md)
- Stablecoins & the GENIUS Act: https://deepstoryresearch.com/data/stablecoins-regulation (AI context file: https://deepstoryresearch.com/context/stablecoins-regulation.md)
- AI Copyright Litigation: https://deepstoryresearch.com/data/ai-copyright-litigation (AI context file: https://deepstoryresearch.com/context/ai-copyright-litigation.md)

---
Deepstory methods are process guidance for AI tools. Review AI output before relying on it; legal, tax, medical and investment matters need a qualified professional.