contract-redliner について
Contract Redlinerは、契約を扱う法務・商務チーム向けのレビュー用スキルです。条項ごとの分析、リスク評価、修正表示、交渉計画を再現可能な手順にまとめています。
主な機能
- 01契約の初期確認と構成レビュー
- 02条項ごとのリスク分析
- 03リスク評価と登録テンプレート
- 04修正表示のルール
- 05交渉と交渉力の計画
- 06署名前チェックリスト
活用シーン
- 01SaaS契約やサービス契約のレビュー
- 02責任・補償条項の懸念点の特定
- 03条項の修正案の準備
- 04署名前の契約課題の管理
インストール
コマンドをコピーしてターミナルで実行します。
$
npx skills add https:/ / github.com/ travisjneuman/ .claude --skill contract-redlinerインストール後、Claude Code で/contract-redlinerを入力して読み込まれたか確認します。
詳細
契約書のレッドラインレビュー
条項ごとの分析、リスク評価、レッドラインの記入、商業契約の交渉戦略を含む、体系的な契約レビュー手法です。
契約レビューの方法論
体系的なレビュー手順
PHASE 1: TRIAGE (5 minutes)
- Identify contract type (SaaS, services, licensing, employment, NDA)
- Determine your party's position (buyer/seller, licensor/licensee)
- Note contract value and term
- Flag overall risk level for appropriate review depth
PHASE 2: STRUCTURAL SCAN (10 minutes)
- Verify all standard sections present
- Check for missing critical clauses
- Note any unusual structure or ordering
- Identify exhibits, schedules, and SOWs
PHASE 3: CLAUSE-BY-CLAUSE REVIEW (bulk of time)
- Review each clause against standard/market terms
- Score risk level per clause
- Draft redline markup for non-standard terms
- Note clauses requiring business input
PHASE 4: RISK SUMMARY AND REDLINE (10 minutes)
- Compile risk register
- Prioritize redlines (must-have vs nice-to-have)
- Draft negotiation talking points
- Prepare executive summary
契約金額に応じたレビューの深さ
| 契約金額 | レビューの深さ | レビュアーのレベル | 所要期間 |
|---|---|---|---|
| < $25K | 簡易確認、テンプレートとの比較 | パラリーガル/ジュニア | 1-2日 |
| $25K - $250K | 標準的な条項レビュー | アソシエイト | 3-5日 |
| $250K - $1M | リスクメモを含む詳細レビュー | シニアアソシエイト | 5-7日 |
| $1M - $10M | 全面的なレビュー+交渉戦略 | シニア弁護士 | 7-14日 |
| > $10M | 複数弁護士によるレビュー+専門家の意見 | パートナー主導のチーム | 14-30日 |
よくある条項の種類
標準条項と非標準条項
| 条項 | 標準/市場慣行 | 注意点 |
|---|---|---|
| 契約期間 | 1-3年、自動更新あり | 解約が難しい自動更新 |
| 任意解約 | 30-90日前の通知 | 任意解約権がない |
| 責任制限 | 支払済み料金の12か月分を上限 | 上限なしの責任、一方的な内容 |
| 補償 | 相互に適用し、知的財産権侵害と契約違反に限定 | 無制限、一方的、広範な適用条件 |
| 秘密保持 | 2-5年間存続し、相互に適用 | 無期限、義務が非対称 |
| 知的財産権の所有権 | 各当事者が既存の知的財産権を保持 | 派生著作物の広範な譲渡 |
| 保証 | 業界標準の保証 | 過度な保証や広範な免責 |
| データ保護 | 適用法に準拠したDPA | DPAがない、データに関する義務が不十分 |
| 不可抗力 | 相互に適用し、標準的な事由を対象とする | 一方的、範囲が広すぎる、または狭すぎる |
| 準拠法 | 相手方の法域または中立的な法域 | 不便または不利な裁判地 |
リスク特定のフレームワーク
リスクのカテゴリー
LEGAL RISK:
- Uncapped liability exposure
- Broad indemnification obligations
- Unfavorable dispute resolution
- Non-compliant data handling terms
- IP ownership ambiguity
FINANCIAL RISK:
- Unfavorable payment terms (net 90+, prepayment)
- Auto-renewal with price escalation
- Penalties and liquidated damages
- Hidden fees or pass-through costs
- No cap on expense reimbursement
OPERATIONAL RISK:
- Unrealistic SLA commitments
- Exclusivity or non-compete restrictions
- Key person dependencies without backup
- Audit rights without reasonable limitations
- Change control process gaps
REPUTATIONAL RISK:
- Press release or reference rights
- Non-disparagement clauses (asymmetric)
- Association with controversial terms
- Public disclosure of agreement terms
リスク評価マトリクス
RISK SCORE = LIKELIHOOD (1-5) x IMPACT (1-5)
Impact Scale:
1 = Negligible (< $10K exposure)
2 = Minor ($10K - $100K exposure)
3 = Moderate ($100K - $1M exposure)
4 = Major ($1M - $10M exposure)
5 = Critical (> $10M or existential risk)
Likelihood Scale:
1 = Rare (< 5% probability)
2 = Unlikely (5-20%)
3 = Possible (20-50%)
4 = Likely (50-80%)
5 = Almost Certain (> 80%)
RISK RESPONSE:
20-25: CRITICAL - Must negotiate before signing
12-19: HIGH - Strong redline, escalate if rejected
6-11: MEDIUM - Request change, may accept with mitigation
1-5: LOW - Note for record, accept if needed
主要条項:詳細分析
責任制限
STANDARD MARKET TERM:
"Each party's aggregate liability shall not exceed the total fees
paid or payable in the 12 months preceding the claim."
COMMON CARVE-OUTS FROM CAP (typically unlimited):
- IP infringement indemnification
- Breach of confidentiality
- Gross negligence or willful misconduct
- Data breach obligations
- Payment obligations
RED FLAGS:
- No liability cap at all
- Cap set at contract value (too high for vendor)
- No carve-outs for data breach or IP infringement
- Consequential damages excluded for only one party
- "Super cap" carve-outs that effectively eliminate the cap
REDLINE POSITIONS:
Conservative: Cap at 12 months fees, mutual carve-outs
Moderate: Cap at contract value, reasonable carve-outs
Aggressive: Lower cap (6 months), broad exclusions of damages
補償
ANATOMY OF INDEMNIFICATION CLAUSE:
TRIGGER:
"Party A shall indemnify Party B against claims arising from..."
- IP infringement by Party A's deliverables
- Breach of representations and warranties
- Gross negligence or willful misconduct
- Violation of applicable law
PROCEDURE:
- Prompt written notice requirement
- Control of defense (indemnifying party typically controls)
- Cooperation obligations
- Settlement approval rights
- Mitigation obligations
RED FLAGS:
- Indemnification for "any and all claims" (too broad)
- No notice requirement or short notice window
- Indemnified party controls defense at indemnitor's expense
- No right to approve settlements
- Indemnification survives indefinitely
REDLINE POSITIONS:
Standard: Mutual indemnification for IP, breach, negligence
Protective: Add reasonable notice period, defense control, settlement consent
Aggressive: Narrow triggers, cap indemnification at liability cap
契約解除
TERMINATION PROVISIONS:
FOR CAUSE:
- Material breach with cure period (30-60 days standard)
- Insolvency or bankruptcy filing
- Change of control (sometimes)
- Failure to meet SLAs (after remediation period)
FOR CONVENIENCE:
- Written notice period (30-90 days standard)
- Pro-rata refund of prepaid fees
- Wind-down obligations
- Transition assistance
POST-TERMINATION:
- Return or destruction of confidential information
- Data export / transition period
- Survival of certain clauses
- Final invoicing and payment
RED FLAGS:
- No termination for convenience right
- Immediate termination without cure period
- No refund of prepaid fees on termination
- Excessive termination penalties
- No transition assistance period
- Automatic destruction of your data
知的財産
OWNERSHIP FRAMEWORK:
BACKGROUND IP:
Each party retains ownership of pre-existing IP
License granted only as needed to perform under agreement
FOREGROUND IP (work product):
- "Work made for hire" vs assignment vs license
- Who owns custom developments?
- Joint ownership provisions
- Rights to derivative works
RED FLAGS:
- Vendor retains ownership of all custom work
- Broad license to use customer data/content
- "Work for hire" language without proper assignment
- No license back for vendor's tools/methodologies
- Vague "improvements" ownership
- Restrictions on using competitive products
REDLINE POSITIONS:
Customer-favorable: Customer owns all custom deliverables
Balanced: Customer owns custom; vendor retains tools/methodologies with license
Vendor-favorable: Vendor retains all IP, customer gets license
データ保護
DATA PROTECTION CLAUSE ESSENTIALS:
MUST INCLUDE:
- Definition of personal data and processing activities
- Roles (controller vs processor)
- Processing instructions and limitations
- Sub-processor management (notice, approval)
- Security measures (technical and organizational)
- Breach notification (timing, content)
- Data subject rights assistance
- Audit rights
- Data return/deletion on termination
- Cross-border transfer mechanisms (SCCs, adequacy)
RED FLAGS:
- No Data Processing Agreement (DPA) at all
- DPA not GDPR/CCPA compliant
- Unrestricted sub-processor appointment
- No breach notification obligation
- No data deletion on termination
- Broad rights to use customer data
- Missing cross-border transfer safeguards
業界固有の傾向
SaaS契約
| 条項 | 一般的な条件 | 交渉で求める条件 |
|---|---|---|
| SLA | 稼働率99.9%、クレジットのみ | 実効性のあるクレジットまたは解約権 |
| データ | ベンダーが保管し、顧客が所有 | 明確なデータポータビリティ、エクスポート権 |
| セキュリティ | SOC 2、暗号化 | ペネトレーションテスト権、侵害通知SLA |
| 価格設定 | 年間値上げの上限 | CPI上限、複数年の価格固定、ボリュームディスカウント |
| 統合 | APIアクセスを含む | API SLA、後方互換性の確約 |
プロフェッショナルサービス契約
| 条項 | 一般的な条件 | 交渉で求める条件 |
|---|---|---|
| 業務範囲 | SOWで定義 | 明確な変更注文手続き、料金の固定 |
| 人員配置 | ベンダーの裁量 | 主要担当者条項、交代の承認 |
| 知的財産 | ベンダーが保持 | 顧客がカスタム成果物を所有 |
| 検収 | X日後に検収済みとみなす | 明示的な検収基準、UAT期間 |
| 勧誘禁止 | 相互に適用、12か月 | 適用範囲の縮小、採用手数料による代替 |
ソフトウェアライセンス
| 条項 | 一般的な条件 | 交渉で求める条件 |
|---|---|---|
| 付与 | 指名ユーザー/同時接続 | ライセンス数調整の柔軟性、監査通知期間 |
| 制限 | リバースエンジニアリング禁止など | 合理的な利用、相互運用性の権利 |
| 保守 | 年間18-22% | 複数年の上限、パッチのサービスレベル |
| 監査 | 年次、ライセンサーの裁量による | 合理的な事前通知(30日以上)、是正期間 |
| エスクロー | 標準的ではない | ミッションクリティカルな用途向けのソースコードエスクロー |
レッドライン表記の規則
MARKUP FORMAT:
[ADDITION] = New language to add (shown in brackets)
[DELETION] = Language to remove (strikethrough in Word)
[MODIFICATION] = Changed language (tracked change)
COMMENT NOTATION:
[MUST-HAVE] - Non-negotiable position
[STRONG PREFERENCE] - Strongly prefer this change
[NICE-TO-HAVE] - Would improve terms, but can concede
[BUSINESS INPUT NEEDED] - Requires business team decision
[LEGAL RISK] - Flagged for legal review
PRIORITY CODING:
P1: Must resolve before signing (deal-breaker if rejected)
P2: Strong preference, expect to negotiate
P3: Opening position, prepared to concede
P4: Cosmetic or clarification only
交渉戦略
交渉力の分析
ASSESS YOUR LEVERAGE:
HIGH LEVERAGE (you have options):
- Multiple competing vendors
- Large deal value relative to vendor revenue
- Long-term commitment being offered
- Strategic account for vendor
- Vendor initiated the deal
LOW LEVERAGE (they have options):
- Sole-source / no alternatives
- Small deal value
- Short-term engagement
- Commodity service
- You initiated / urgently need solution
LEVERAGE TACTICS:
High leverage: Lead with must-haves, concede P3s as goodwill
Balanced: Trade concessions (give on term, get on liability cap)
Low leverage: Focus on P1s only, accept standard terms elsewhere
交渉の手引き
ROUND 1: INITIAL REDLINE
- Include all P1, P2, and P3 positions
- Provide brief rationale for each change
- Set professional, collaborative tone
ROUND 2: RESPONSE TO COUNTER
- Accept reasonable P3 counter-positions
- Hold firm on P1 items with explanation
- Propose compromise language on P2 items
- Identify trade opportunities
ROUND 3: FINAL POSITIONS
- Resolve remaining P1 and P2 items
- Escalate unresolved P1 items to business sponsors
- Document any agreed exceptions
- Prepare final execution version
DEADLOCK RESOLUTION:
- Suggest alternative language that addresses both concerns
- Propose risk mitigation (insurance, escrow, guarantees)
- Escalate to executive sponsors
- Consider side letter for sensitive terms
- Walk away if P1 items cannot be resolved
リスク登録簿テンプレート
RISK REGISTER:
| # | Clause | Section | Risk Level | Issue | Redline Position | Priority |
|---|--------|---------|-----------|-------|-----------------|----------|
| 1 | Liability Cap | 8.1 | HIGH | Uncapped liability | Cap at 12 mo fees | P1 |
| 2 | Indemnification | 9.2 | HIGH | One-sided | Add mutual indemnity | P1 |
| 3 | Data Protection | 11 | HIGH | No DPA | Add GDPR-compliant DPA | P1 |
| 4 | Termination | 6.2 | MEDIUM | No convenience right | Add 90-day notice | P2 |
| 5 | IP Ownership | 10.1 | MEDIUM | Vendor retains custom | Customer owns custom | P2 |
| 6 | Auto-Renewal | 6.1 | LOW | 60-day notice | Extend to 90 days | P3 |
EXECUTIVE SUMMARY:
Total clauses reviewed: ___
Critical risks identified: ___
High risks identified: ___
Must-negotiate items: ___
Estimated negotiation rounds: ___
Recommendation: Proceed / Proceed with changes / Do not proceed
署名前のチェックリスト
FINAL REVIEW:
PARTIES AND EXECUTION:
- [ ] Legal entity names correct and complete
- [ ] Signatories have authority
- [ ] Effective date specified
- [ ] All exhibits and schedules attached
- [ ] All blanks filled in (no TBDs remaining)
COMMERCIAL TERMS:
- [ ] Pricing matches proposal/negotiation
- [ ] Payment terms acceptable
- [ ] Term and renewal provisions clear
- [ ] SLAs and metrics defined
LEGAL PROTECTIONS:
- [ ] Liability cap in place
- [ ] Indemnification is mutual
- [ ] Termination rights adequate
- [ ] IP ownership clear
- [ ] Confidentiality provisions mutual
COMPLIANCE:
- [ ] Data protection addendum attached (if personal data)
- [ ] Governing law and jurisdiction reviewed
- [ ] Insurance requirements reviewed
- [ ] Regulatory compliance addressed
- [ ] Export control provisions (if applicable)
INTERNAL APPROVALS:
- [ ] Legal approval obtained
- [ ] Finance/procurement approval obtained
- [ ] Business owner approval obtained
- [ ] Any required board/executive approval obtained
See Also
コメント
Markdown 対応