Tutorial 06: Legal Workflows with ChatGPT and Custom GPTs

Review this contract against our playbook.
Provide a clause-by-clause analysis with risk ratings (GREEN/YELLOW/RED).
Flag any deviations from playbook positions and recommend negotiation strategy.

## CONTRACT ANALYSIS: Software License Agreement
**Contract Type**: SaaS Subscription Agreement
**Our Role**: Customer/Licensee
**Counterparty**: Acme Software Inc.

### CLAUSE ANALYSIS

#### 1. LICENSE GRANT (Section 2.1)
GREEN - Acceptable
- Grants non-exclusive, worldwide license
- Includes affiliate usage rights
- Standard use restrictions

#### 2. LIMITATION OF LIABILITY (Section 8)
RED - Must Negotiate
Current: "Vendor's liability shall not exceed $10,000"
Issue: Cap is far below contract value ($150,000 ACV)
Playbook Position: Minimum 12 months fees ($150,000)

**Suggested Redline**:
"Vendor's liability shall not exceed ~~$10,000~~ the greater
of (a) fees paid in the twelve (12) months preceding the
claim or (b) $150,000."

#### 3. INDEMNIFICATION (Section 7)
YELLOW - Should Negotiate
Current: IP indemnity excludes "modifications by Customer"
Issue: Overly broad exclusion could limit protection
Playbook Position: Narrow exclusions to material modifications

**Suggested Redline**:
Add: "provided such modification materially alters the
functionality of the Service in a manner not contemplated
by the Documentation"

### NEGOTIATION PRIORITIES
1. RED Liability Cap (critical gap)
2. RED Data Breach Indemnity (missing entirely)
3. YELLOW Indemnity Exclusions (overbroad)
4. YELLOW Termination Notice (60 vs 30 days)
5. GREEN Auto-renewal period (acceptable at 30 days)

### CUMULATIVE RISK SCORE: 7 (HIGH)
Recommend: Partner review before signing

Triage this NDA. Categorize as:
- GREEN - STANDARD APPROVAL: Matches our standard or better
- YELLOW - COUNSEL REVIEW: Minor deviations
- RED - FULL REVIEW: Significant issues

For each category, list specific concerns and recommended action.

## NDA TRIAGE RESULTS

**Document**: Acme Corp Mutual NDA (v2.1)
**Type**: Mutual Non-Disclosure Agreement
**Direction**: Two-way protection

### TRIAGE RESULT: COUNSEL REVIEW

**Reason**: Contains 2 non-standard provisions requiring attorney review

### FLAGGED ITEMS:

1. **Non-Solicit Clause (Section 6)**
   - Not typically included in standard NDA
   - 24-month restriction on hiring
   - May need business approval

2. **Jurisdiction (Section 9)**
   - Specifies Texas courts exclusive jurisdiction
   - Our standard: Delaware or mutual agreement
   - Acceptable but note for negotiation if sensitive deal

### STANDARD ITEMS (No Issues):
- Definition of Confidential Information
- Mutual obligations
- 3-year term
- Standard exclusions
- Return/destruction requirement

### RECOMMENDATION:
Route to associate for 15-minute review of flagged items.
If non-solicit is acceptable to business, can proceed.

I need a vendor status check for [vendor name].

Available information:
- [List active agreements, expiration dates]
- [Renewal dates]
- [Historical notes]

Provide: Active agreements, upcoming renewals, recommended actions.

Create an incident response brief for [data-breach/ litigation hold/ etc.].

Include:
- Immediate actions (0-24 hours)
- Notification requirements by jurisdiction
- Template resources
- Key contacts

Create a daily brief on my pending matters. Include:
- Matters requiring attention today
- Upcoming deadlines
- Status updates needed

Draft a Data Subject Access Request response template.
Include: verification statement, data categories table, rights notice,
retention caveats, supervisory authority contact. Mark internal notes
separately.

Draft a litigation hold notice for [situation].
Include: preservation scope, custodian list, document types,
compliance requirements, acknowledgment section.

You are a legal contract review assistant for [Firm Name].

## PLAYBOOK POSITIONS

### Liability Cap
- Standard: 12 months fees
- Minimum: contract value
- Carve-outs: indemnification, data breach, IP infringement, confidentiality, gross negligence, willful misconduct

### Indemnification
- Required from vendor: IP infringement, data breach, gross negligence
- Required mutual: third party claims from breach
- Unacceptable: customer indemnifies for vendor negligence

### Data Rights
- Ownership: customer owns all customer data
- Vendor usage: service delivery only
- Prohibited uses: AI training, analytics, marketing
- Deletion timeline: 30 days
- Breach notification: 72 hours

### Termination
- Preferred: annual with 30 days TFC
- Acceptable: 60-90 days notice
- Unacceptable: no TFC, >90 day notice

## RISK THRESHOLDS
RED: uncapped customer liability, no vendor indemnity, data used for training
YELLOW: liability cap below 12 months, limited indemnity carve-outs

## OUTPUT FORMAT
Always use RED/YELLOW/GREEN ratings. Provide specific redline suggestions for RED and YELLOW items.

1. Receive contract from business team

2. Open your Contract Review Custom GPT

3. Upload contract

4. Prompt: "Review against our playbook. Provide clause-by-clause analysis with risk ratings."

5. Review output:
   - Check risk ratings
   - Review suggested redlines
   - Verify against your judgment

6. Generate response or manual drafting based on suggestions

7. Document in matter management

Day starts: 15 NDAs in queue

1. Open NDA Triage Custom GPT

2. For each NDA:
   - Upload NDA
   - Prompt: "Triage this NDA. GREEN/YELLOW/RED with specific concerns."

3. Sort results:
   GREEN STANDARD (6): Send to paralegal for execution
   YELLOW COUNSEL (7): Quick 10-min reviews
   RED FULL REVIEW (2): Schedule detailed analysis

4. Process YELLOW queue: Quick review flagged items

5. Process RED queue: Full contract review GPT for detailed analysis

Total time: ~2 hours vs. 6+ hours manually

1. Incident reported (potential data breach)

2. Open ChatGPT, prompt: "Create incident response brief for data breach.
   Include: immediate actions, notification requirements by jurisdiction,
   template resources, key contacts."

3. Review notification requirements

4. Prepare communications using templated response prompts

5. Document privileged analysis in separate conversation

6. Generate status updates as needed