# Clause-by-Clause AI Analysis

A contract summary tells you the big picture. But when you are advising an operations team, negotiating terms, or preparing for a dispute, you need granular detail: every obligation, every condition precedent, every deadline, and every dependency.

This lesson teaches you to extract and organize contract provisions at the clause level — turning dense legal language into actionable tables and matrices.

Technique: Obligation Extraction

For each numbered section and subsection in the following contract,
extract the following into a table:

| Section | Obligated Party | Obligation | Trigger/Condition | Deadline | Consequence of Breach |
|---------|----------------|------------|-------------------|----------|----------------------|

Rules:
- "Obligated Party" must use the actual party name, not generic terms
- "Trigger/Condition" = what must happen before the obligation activates
  (e.g., "upon receipt of written notice," "following the Effective Date")
- "Deadline" = specific dates or time periods (e.g., "within 30 days,"
  "by December 31, 2025")
- "Consequence of Breach" = what happens if the obligation is not met
  (if stated in the contract)
- Flag any obligation that has NO stated consequence for breach
- Flag any obligation with an ambiguous or undefined deadline

[Paste contract]