WRITING

Contract obligation and risk register

Map clauses to obligations, deadlines, owners, playbook deviations, and negotiation questions with exact locators.

PROMPT
Role: an evidence-led professional editor

Objective: Create a traceable contract review aid for qualified counsel, without claiming legal advice or silently rewriting obligations.

Inputs:
- Contract text or redline: {{contract_text}}
- Clause playbook and review standard: {{playbook}}
- Business context and drivers: {{business_context}}
- Contract review goal: {{review_goal}}

Workflow:
1. Confirm version, parties, jurisdiction, effective date, and document precedence while preserving clause and page locators.
2. Extract obligations, rights, deadlines, renewal, termination, notice, payment, data, and security terms by party.
3. Link every item to source location, owner, deadline rule, dependency, evidence, and consequence of noncompliance.
4. Compare with the playbook and flag deviations, ambiguity, conflict, omissions, and business risk without asserting legal conclusions.
5. Prioritize negotiation questions, the purpose of alternative language, and internal decisions required.
6. Mark counsel and contract-owner review, uncertainty, and never edit or approve the agreement automatically.

Output format:
## Contract scope and precedence
## Obligation and right register
## Deadlines, owners, and evidence
## Playbook deviations and risk
## Ambiguity, conflict, and omissions
## Negotiation questions and alternative intent
## Professional review items

Quality rules:
Use only supplied material and verifiable facts. When information is missing, do not guess: state the gap, any necessary assumption, and its effect on the result. Before concluding, check every constraint and required output field.

Negative prompt

Unsupported facts, fabricated citations, vague conclusions, missing constraints, unverified claims, and unrequested scope expansion

Workflow

  1. Fill variables with concrete facts, scope, actors, and desired outcomes rather than abstract adjectives.
  2. Check the assembled prompt for conflicting conditions, then paste it into a compatible tool.
  3. Treat the first answer as a draft and refine one failed condition at a time.

Verification

  • Confirm every goal, constraint, and output field is present.
  • Check figures, dates, quotations, and code against primary sources and real tests.
  • Keep a human responsible for evidence, feasibility, and final approval.