Contract Intelligence
Overview
Analyze procurement contracts to extract structured data (clauses, obligations, milestones, penalties), detect changes, propagate impacts to related orders, validate contract health, and support dispute resolution. Works with contracts in PDF, DOCX, and structured text formats.
Announce at start: "I'm using the contract-intelligence skill to analyze a procurement contract for clauses, obligations, and compliance requirements."
When to Use This Skill
Trigger Conditions:
- Analyzing a new contract for clause extraction and risk identification
- Tracking contract obligations, milestones, and deadlines
- Detecting and analyzing contract amendments or changes
- Validating contract health (signatures, expiration, unfulfilled obligations)
- Supporting dispute resolution with evidence compilation
Prerequisites:
- Contract document accessible (PDF, DOCX, or text format)
- Contract type identified (supply, service, framework, subcontract)
- Related orders/POs identified for change propagation analysis
- Standard contract template available (for change detection)
Step-by-Step Procedure
Step 1: Contract Type Identification
Identify contract type using classification criteria:
| Contract Indicator |
Classified As |
| Goods/materials supply with pricing schedule |
Supply Contract |
| Professional services, time-based billing |
Service Contract |
| Frame agreement with call-off orders |
Framework Agreement |
| Subcontractor arrangement with scope defined |
Subcontract |
| Amendment to existing contract |
Contract Amendment |
| Early works or letter of intent |
Preliminary Agreement |
Step 2: Clause Extraction & Classification
Extract contract clauses and classify by type:
| Clause Category |
Examples |
Priority |
| Commercial |
Pricing, payment terms, penalties, variations, currency |
Critical |
| Performance |
Deliverables, specifications, quality standards, acceptance criteria |
Critical |
| Risk |
Liability limits, indemnities, insurances, force majeure |
High |
| Time |
Duration, milestones, extensions, liquidated damages |
High |
| Termination |
Termination rights, notice periods, consequences |
High |
| Administration |
Notices, change management, dispute resolution, governing law |
Standard |
| Regulatory |
Compliance requirements, permits, safety, environmental |
Standard |
Extraction Format:
{
"contract_id": "CNT-2026-0012",
"clause": {
"title": "Liquidated Damages",
"category": "time",
"priority": "high",
"text": "If Contractor fails to achieve Mechanical Completion by the Target Date, Contractor shall pay liquidated damages at 0.5% of the Contract Price per week of delay, up to a maximum of 10% of the Contract Price.",
"extract_values": {
"damage_rate": "0.5% per week",
"damage_cap": "10% of Contract Price",
"trigger": "failure to achieve Mechanical Completion by Target Date"
}
}
}
Step 3: Obligation Extraction
Extract all obligations, deliverables, and milestones:
| Obligation Element |
Extracted Data |
| Obligation Owner |
Party responsible (employer, contractor, subcontractor) |
| Obligation Description |
What must be done |
| Trigger Condition |
When obligation becomes active |
| Deadline/Milestone |
Target date or condition for completion |
| Consequence |
Penalty, damages, or right exercised if not fulfilled |
| Evidence Required |
What proves obligation was fulfilled |
| Status |
Current status based on contract state |
Obligation Tracking Structure:
{
"obligations": [
{
"id": "OBL-001",
"owner": "Contractor",
"description": "Submit performance bond within 14 days of contract signing",
"trigger": "contract_execution",
"deadline_days": 14,
"consequence": "Employer may suspend work and recover costs",
"evidence": "bond_certificate",
"status": "fulfilled",
"status_date": "2026-03-14"
}
]
}
Step 4: Change Detection & Impact Analysis
Compare contract against baseline or previous version:
| Change Type |
Detection Method |
Impact Areas |
| Clause text modified |
Text diff against baseline |
Related orders, invoices, obligations |
| Pricing schedule updated |
Value comparison |
All POs at old prices, budget projections |
| Timeline changed |
Date comparison |
All scheduled deliverables, milestone tracking |
| Scope expanded/reduced |
Text diff + obligation count |
Resource plans, delivery schedules |
| Risk allocation changed |
Clause addition/deletion |
Insurance, guarantees, bonds |
Impact Analysis Process:
- Identify changed clauses/obligations
- Find all orders/POs referencing changed clauses
- Calculate financial impact (price changes, damage adjustments)
- Calculate schedule impact (date changes, milestone shifts)
- Generate change impact report
Step 5: Contract Health Checking
Validate current contract state:
| Health Check |
Validation Criteria |
Status Output |
| Signatures |
All required parties signed |
Valid / Missing signatures |
| Effective Date |
Past and within contract period |
Active / Not yet effective / Expired |
| Obligations Status |
All critical obligations on track |
On track / At risk / Overdue |
| Expiration |
Date compared to current date |
Valid / Expiring within 30 days / Expired |
| Amendments |
All amendments logged and incorporated |
Current / Missing amendments |
| Insurance/Guarantees |
Current and not expired |
Valid / Expiring / Expired |
| Disputes |
Any active disputes logged |
Clear / Disputed |
Health Report Format:
{
"contract_id": "CNT-2026-0012",
"health_check_at": "2026-03-31T14:00:00Z",
"overall_status": "healthy",
"checks": [
{"check": "signatures", "status": "valid", "details": "All 3 parties signed"},
{"check": "effective_date", "status": "active", "details": "Started 2026-01-15, expires 2026-12-31"},
{"check": "obligations", "status": "on_track", "details": "8/8 obligations on track"},
{"check": "expiration", "status": "valid", "details": "275 days remaining"},
{"check": "amendments", "status": "current", "details": "2 amendments incorporated"},
{"check": "disputes", "status": "clear", "details": "No active disputes"}
]
}
Step 6: Dispute Resolution Support
Compile evidence for dispute scenarios:
| Evidence Type |
Source |
Purpose |
| Contract Clauses |
Extracted clause text |
Legal basis for claim |
| Timeline |
Obligation dates, milestone records |
Shows sequence of events |
| Communications |
Email correspondence, RFIs, NCRs |
Documentary evidence |
| Performance Records |
Delivery notes, inspection reports |
Shows actual vs. contractual |
| Financial Records |
Invoices, payment records, variation orders |
Financial impact evidence |
Step 7: Output Generation
Generate structured outputs:
{
"contract_analysis": {
"contract_id": "CNT-2026-0012",
"contract_type": "supply_contract",
"analysis_at": "2026-03-31T14:00:00Z",
"clauses_extracted": 24,
"obligations_extracted": 8,
"health_status": "healthy",
"changes_detected": 0,
"dispute_support": {
"active_disputes": 0,
"evidence_compiled": false
}
}
}
Success Criteria
Common Pitfalls
- Missing Obligations — Some obligations are implicit in contract language. Look for "shall," "shall ensure," "shall cause" language.
- Ignoring Amendment History — Each amendment may modify obligations. Always incorporate all amendments into the current contract state.
- Skipping Financial Impact Analysis — Pricing changes affect active POs. Always calculate which orders are at old prices and require repricing.
- Overlooking Expiring Elements — Insurance policies, guarantees, and bonds within contracts have expiry dates that may not match contract end date. Check them separately.
- Accepting Unilateral Interpretation — When clauses are ambiguous, flag ambiguity rather than asserting a single interpretation. Disputes often arise from ambiguous language.
Cross-References
Related Skills
procurement-document-generation — Generates contract variation notices, change orders
procurement-compliance — Validates contract terms against regulatory requirements
procurement-order-management — Uses contract terms to validate PO creation
supplier-evaluation — Contract performance data feeds supplier scoring
Related Agents
Contract Administration Specialist (DomainForge) — Primary contract analysis and obligation tracking
Procurement Strategy Specialist (DomainForge) — Negotiation strategy and risk assessment
Financial Compliance Specialist (DomainForge) — Financial impact analysis of contract changes
Example Usage
Scenario: Analyze supply contract CNT-2026-0012 for obligations and health status
- Identify: Contract is a supply agreement for structural steel supply and delivery
- Extract Clauses: 24 clauses across commercial, performance, risk, time, termination categories
- Extract Obligations: 8 obligations with deadlines, 3 already fulfilled, 5 on track
- Check Health: Signatures valid, contract active, obligations on track, 275 days remaining
- Detect Changes: No changes detected from baseline
- Output: JSON with full analysis, obligation tracking, health report
Performance Metrics
Target Performance:
- Clause extraction accuracy: >95% (all clauses correctly identified and categorized)
- Obligation extraction accuracy: >98% (all obligations identified with correct deadlines)
- Change detection accuracy: >99% (all text changes identified)
- Health check completeness: 6/6 checks completed every time
- Analysis time: <2 minutes per standard contract
1---2name: contract-intelligence3description: Analyze procurement contracts for clause extraction, obligation tracking, change propagation, health checking, and dispute resolution support with structured data pipeline4---56# Contract Intelligence78## Overview910Analyze procurement contracts to extract structured data (clauses, obligations, milestones, penalties), detect changes, propagate impacts to related orders, validate contract health, and support dispute resolution. Works with contracts in PDF, DOCX, and structured text formats.1112**Announce at start:** "I'm using the contract-intelligence skill to analyze a procurement contract for clauses, obligations, and compliance requirements."1314## When to Use This Skill1516**Trigger Conditions:**17- Analyzing a new contract for clause extraction and risk identification18- Tracking contract obligations, milestones, and deadlines19- Detecting and analyzing contract amendments or changes20- Validating contract health (signatures, expiration, unfulfilled obligations)21- Supporting dispute resolution with evidence compilation2223**Prerequisites:**24- Contract document accessible (PDF, DOCX, or text format)25- Contract type identified (supply, service, framework, subcontract)26- Related orders/POs identified for change propagation analysis27- Standard contract template available (for change detection)2829## Step-by-Step Procedure3031### Step 1: Contract Type Identification3233Identify contract type using classification criteria:3435| Contract Indicator | Classified As |36|--------------------|---------------|37| Goods/materials supply with pricing schedule | Supply Contract |38| Professional services, time-based billing | Service Contract |39| Frame agreement with call-off orders | Framework Agreement |40| Subcontractor arrangement with scope defined | Subcontract |41| Amendment to existing contract | Contract Amendment |42| Early works or letter of intent | Preliminary Agreement |4344### Step 2: Clause Extraction & Classification4546Extract contract clauses and classify by type:4748| Clause Category | Examples | Priority |49|----------------|----------|----------|50| **Commercial** | Pricing, payment terms, penalties, variations, currency | Critical |51| **Performance** | Deliverables, specifications, quality standards, acceptance criteria | Critical |52| **Risk** | Liability limits, indemnities, insurances, force majeure | High |53| **Time** | Duration, milestones, extensions, liquidated damages | High |54| **Termination** | Termination rights, notice periods, consequences | High |55| **Administration** | Notices, change management, dispute resolution, governing law | Standard |56| **Regulatory** | Compliance requirements, permits, safety, environmental | Standard |5758**Extraction Format:**59```json60{61 "contract_id": "CNT-2026-0012",62 "clause": {63 "title": "Liquidated Damages",64 "category": "time",65 "priority": "high",66 "text": "If Contractor fails to achieve Mechanical Completion by the Target Date, Contractor shall pay liquidated damages at 0.5% of the Contract Price per week of delay, up to a maximum of 10% of the Contract Price.",67 "extract_values": {68 "damage_rate": "0.5% per week",69 "damage_cap": "10% of Contract Price",70 "trigger": "failure to achieve Mechanical Completion by Target Date"71 }72 }73}74```7576### Step 3: Obligation Extraction7778Extract all obligations, deliverables, and milestones:7980| Obligation Element | Extracted Data |81|--------------------|----------------|82| **Obligation Owner** | Party responsible (employer, contractor, subcontractor) |83| **Obligation Description** | What must be done |84| **Trigger Condition** | When obligation becomes active |85| **Deadline/Milestone** | Target date or condition for completion |86| **Consequence** | Penalty, damages, or right exercised if not fulfilled |87| **Evidence Required** | What proves obligation was fulfilled |88| **Status** | Current status based on contract state |8990**Obligation Tracking Structure:**91```json92{93 "obligations": [94 {95 "id": "OBL-001",96 "owner": "Contractor",97 "description": "Submit performance bond within 14 days of contract signing",98 "trigger": "contract_execution",99 "deadline_days": 14,100 "consequence": "Employer may suspend work and recover costs",101 "evidence": "bond_certificate",102 "status": "fulfilled",103 "status_date": "2026-03-14"104 }105 ]106}107```108109### Step 4: Change Detection & Impact Analysis110111Compare contract against baseline or previous version:112113| Change Type | Detection Method | Impact Areas |114|-------------|-----------------|--------------|115| Clause text modified | Text diff against baseline | Related orders, invoices, obligations |116| Pricing schedule updated | Value comparison | All POs at old prices, budget projections |117| Timeline changed | Date comparison | All scheduled deliverables, milestone tracking |118| Scope expanded/reduced | Text diff + obligation count | Resource plans, delivery schedules |119| Risk allocation changed | Clause addition/deletion | Insurance, guarantees, bonds |120121**Impact Analysis Process:**1221. Identify changed clauses/obligations1232. Find all orders/POs referencing changed clauses1243. Calculate financial impact (price changes, damage adjustments)1254. Calculate schedule impact (date changes, milestone shifts)1265. Generate change impact report127128### Step 5: Contract Health Checking129130Validate current contract state:131132| Health Check | Validation Criteria | Status Output |133|-------------|-------------------|---------------|134| Signatures | All required parties signed | Valid / Missing signatures |135| Effective Date | Past and within contract period | Active / Not yet effective / Expired |136| Obligations Status | All critical obligations on track | On track / At risk / Overdue |137| Expiration | Date compared to current date | Valid / Expiring within 30 days / Expired |138| Amendments | All amendments logged and incorporated | Current / Missing amendments |139| Insurance/Guarantees | Current and not expired | Valid / Expiring / Expired |140| Disputes | Any active disputes logged | Clear / Disputed |141142**Health Report Format:**143```json144{145 "contract_id": "CNT-2026-0012",146 "health_check_at": "2026-03-31T14:00:00Z",147 "overall_status": "healthy",148 "checks": [149 {"check": "signatures", "status": "valid", "details": "All 3 parties signed"},150 {"check": "effective_date", "status": "active", "details": "Started 2026-01-15, expires 2026-12-31"},151 {"check": "obligations", "status": "on_track", "details": "8/8 obligations on track"},152 {"check": "expiration", "status": "valid", "details": "275 days remaining"},153 {"check": "amendments", "status": "current", "details": "2 amendments incorporated"},154 {"check": "disputes", "status": "clear", "details": "No active disputes"}155 ]156}157```158159### Step 6: Dispute Resolution Support160161Compile evidence for dispute scenarios:162163| Evidence Type | Source | Purpose |164|---------------|--------|---------|165| **Contract Clauses** | Extracted clause text | Legal basis for claim |166| **Timeline** | Obligation dates, milestone records | Shows sequence of events |167| **Communications** | Email correspondence, RFIs, NCRs | Documentary evidence |168| **Performance Records** | Delivery notes, inspection reports | Shows actual vs. contractual |169| **Financial Records** | Invoices, payment records, variation orders | Financial impact evidence |170171### Step 7: Output Generation172173Generate structured outputs:174175```json176{177 "contract_analysis": {178 "contract_id": "CNT-2026-0012",179 "contract_type": "supply_contract",180 "analysis_at": "2026-03-31T14:00:00Z",181 "clauses_extracted": 24,182 "obligations_extracted": 8,183 "health_status": "healthy",184 "changes_detected": 0,185 "dispute_support": {186 "active_disputes": 0,187 "evidence_compiled": false188 }189 }190}191```192193## Success Criteria194195- [ ] Contract type correctly classified196- [ ] All clauses extracted with correct category and priority197- [ ] All obligations extracted with deadlines and consequences198- [ ] Change detection identifies all modifications from baseline199- [ ] Impact analysis covers affected orders, obligations, and financial elements200- [ ] Health check covers all 6 validation areas201- [ ] Dispute evidence compiled (if dispute scenario applies)202- [ ] All extracted data structured and machine-readable203204## Common Pitfalls2052061. **Missing Obligations** — Some obligations are implicit in contract language. Look for "shall," "shall ensure," "shall cause" language.2072. **Ignoring Amendment History** — Each amendment may modify obligations. Always incorporate all amendments into the current contract state.2083. **Skipping Financial Impact Analysis** — Pricing changes affect active POs. Always calculate which orders are at old prices and require repricing.2094. **Overlooking Expiring Elements** — Insurance policies, guarantees, and bonds within contracts have expiry dates that may not match contract end date. Check them separately.2105. **Accepting Unilateral Interpretation** — When clauses are ambiguous, flag ambiguity rather than asserting a single interpretation. Disputes often arise from ambiguous language.211212## Cross-References213214### Related Skills215- `procurement-document-generation` — Generates contract variation notices, change orders216- `procurement-compliance` — Validates contract terms against regulatory requirements217- `procurement-order-management` — Uses contract terms to validate PO creation218- `supplier-evaluation` — Contract performance data feeds supplier scoring219220### Related Agents221- `Contract Administration Specialist` (DomainForge) — Primary contract analysis and obligation tracking222- `Procurement Strategy Specialist` (DomainForge) — Negotiation strategy and risk assessment223- `Financial Compliance Specialist` (DomainForge) — Financial impact analysis of contract changes224225## Example Usage226227**Scenario:** Analyze supply contract CNT-2026-0012 for obligations and health status2282291. **Identify:** Contract is a supply agreement for structural steel supply and delivery2302. **Extract Clauses:** 24 clauses across commercial, performance, risk, time, termination categories2313. **Extract Obligations:** 8 obligations with deadlines, 3 already fulfilled, 5 on track2324. **Check Health:** Signatures valid, contract active, obligations on track, 275 days remaining2335. **Detect Changes:** No changes detected from baseline2346. **Output:** JSON with full analysis, obligation tracking, health report235236## Performance Metrics237238**Target Performance:**239- Clause extraction accuracy: >95% (all clauses correctly identified and categorized)240- Obligation extraction accuracy: >98% (all obligations identified with correct deadlines)241- Change detection accuracy: >99% (all text changes identified)242- Health check completeness: 6/6 checks completed every time243- Analysis time: <2 minutes per standard contract