Back to Details

review-contract

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/review-contract -- Contract Review Against Playbook

/review-contract -- 对照谈判手册审查合同

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Review a contract against your organization's negotiation playbook. Analyze each clause, flag deviations, generate redline suggestions, and provide business impact analysis.
Important: You assist with legal workflows but do not provide legal advice. All analysis should be reviewed by qualified legal professionals before being relied upon.
如果您看到不熟悉的占位符或需要检查已连接的工具，请查看CONNECTORS.md。
对照组织的谈判手册审查合同。逐条分析条款、标记偏差、生成红线修订建议，并提供业务影响分析。
重要提示：您可协助处理法律工作流，但不提供法律建议。所有分析在被采信前，均需由合格的法律专业人士审核。

Invocation

调用方式

/review-contract <contract file or URL>
Review the contract: @$1
/review-contract <合同文件或URL>
审查合同：@$1

Workflow

工作流

Step 1: Accept the Contract

步骤1：接收合同

Accept the contract in any of these formats:
  • File upload: PDF, DOCX, or other document format
  • URL: Link to a contract in your CLM, cloud storage (e.g., Box, Egnyte, SharePoint), or other document system
  • Pasted text: Contract text pasted directly into the conversation
If no contract is provided, prompt the user to supply one.
可通过以下任意格式接收合同：
  • 文件上传：PDF、DOCX或其他文档格式
  • URL：指向CLM、云存储（如Box、Egnyte、SharePoint）或其他文档系统中的合同链接
  • 粘贴文本：直接粘贴到对话中的合同文本
如果未提供合同，提示用户提供一份。

Step 2: Gather Context

步骤2：收集上下文信息

Ask the user for context before beginning the review:
  1. Which side are you on? (vendor/supplier, customer/buyer, licensor, licensee, partner -- or other)
  2. Deadline: When does this need to be finalized? (Affects prioritization of issues)
  3. Focus areas: Any specific concerns? (e.g., "data protection is critical", "we need flexibility on term", "IP ownership is the key issue")
  4. Deal context: Any relevant business context? (e.g., deal size, strategic importance, existing relationship)
If the user provides partial context, proceed with what you have and note assumptions.
开始审查前，向用户询问以下上下文信息：
  1. 您代表哪一方？（供应商/服务商、客户/采购方、许可方、被许可方、合作伙伴——或其他）
  2. 截止日期：需要何时完成审查？（影响问题的优先级排序）
  3. 重点关注领域：是否有特定关注点？（例如：“数据保护至关重要”、“我们需要在合同期限上保留灵活性”、“知识产权归属是核心问题”）
  4. 交易背景：是否有相关业务背景？（例如：交易规模、战略重要性、现有合作关系）
如果用户仅提供部分上下文信息，基于已有信息推进审查，并注明假设条件。

Step 3: Load the Playbook

步骤3：加载谈判手册

Look for the organization's contract review playbook in local settings (e.g., 
legal.local.md
or similar configuration files).
The playbook should define:
  • Standard positions: The organization's preferred terms for each major clause type
  • Acceptable ranges: Terms that can be agreed to without escalation
  • Escalation triggers: Terms that require senior counsel review or outside counsel involvement
If no playbook is configured:
  • Inform the user that no playbook was found
  • Offer two options:
    1. Help the user set up their playbook (walk through defining positions for key clauses)
    2. Proceed with a generic review using widely-accepted commercial standards as the baseline
  • If proceeding generically, clearly note that the review is based on general commercial standards, not the organization's specific positions
在本地设置中查找组织的合同审查手册（如
legal.local.md
或类似配置文件）。
手册应定义：
  • 标准立场：组织针对各主要条款类型的首选条款
  • 可接受范围：无需升级即可同意的条款
  • 升级触发条件：需要资深法律顾问或外部律师介入的条款
如果未配置手册：
  • 告知用户未找到谈判手册
  • 提供两个选项：
    1. 帮助用户设置谈判手册（引导定义关键条款的立场）
    2. 基于广泛认可的商业标准进行通用审查
  • 如果选择通用审查，需明确注明审查基于通用商业标准，而非组织的特定立场

Step 4: Clause-by-Clause Analysis

步骤4：逐条条款分析

Apply the following review process:
  1. Identify the contract type: SaaS agreement, professional services, license, partnership, procurement, etc. The contract type affects which clauses are most material.
  2. Determine the user's side: Vendor, customer, licensor, licensee, partner. This fundamentally changes the analysis (e.g., limitation of liability protections favor different parties).
  3. Read the entire contract before flagging issues. Clauses interact with each other (e.g., an uncapped indemnity may be partially mitigated by a broad limitation of liability).
  4. Analyze each material clause against the playbook position.
  5. Consider the contract holistically: Are the overall risk allocation and commercial terms balanced?
Analyze the contract systematically, covering at minimum:
Clause CategoryKey Review Points
Limitation of LiabilityCap amount, carveouts, mutual vs. unilateral, consequential damages
IndemnificationScope, mutual vs. unilateral, cap, IP infringement, data breach
IP OwnershipPre-existing IP, developed IP, work-for-hire, license grants, assignment
Data ProtectionDPA requirement, processing terms, sub-processors, breach notification, cross-border transfers
ConfidentialityScope, term, carveouts, return/destruction obligations
Representations & WarrantiesScope, disclaimers, survival period
Term & TerminationDuration, renewal, termination for convenience, termination for cause, wind-down
Governing Law & Dispute ResolutionJurisdiction, venue, arbitration vs. litigation
InsuranceCoverage requirements, minimums, evidence of coverage
AssignmentConsent requirements, change of control, exceptions
Force MajeureScope, notification, termination rights
Payment TermsNet terms, late fees, taxes, price escalation
For each clause, assess against the playbook (or generic standards) and note whether it is present, absent, or unusual.
遵循以下审查流程：
  1. 识别合同类型：SaaS协议、专业服务协议、许可协议、合作协议、采购协议等。合同类型决定了哪些条款最为关键。
  2. 确定用户立场：供应商、客户、许可方、被许可方、合作伙伴。这会从根本上影响分析结果（例如：责任限制保护对不同方的利弊不同）。
  3. 先通读完整合同再标记问题。条款之间相互关联（例如：无上限的赔偿条款可能会被宽泛的责任限制条款部分抵消）。
  4. 对照手册立场分析每个关键条款。
  5. 整体评估合同：风险分配和商业条款是否整体平衡？
系统地分析合同，至少涵盖以下内容：
条款类别关键审查要点
责任限制赔偿上限、例外情形、双向或单向、间接损害赔偿
赔偿条款范围、双向或单向、上限、知识产权侵权、数据泄露
知识产权归属已有知识产权、合作期间开发的知识产权、职务作品、许可授予、转让
数据保护DPA要求、处理条款、分包商、 breach通知、跨境传输
保密条款范围、期限、例外情形、返还/销毁义务
陈述与保证范围、免责声明、存续期限
合同期限与终止期限、续约、任意终止、因故终止、收尾安排
管辖法律与争议解决管辖地、 venue、仲裁vs诉讼
保险承保要求、最低保额、保险凭证
转让条款同意要求、控制权变更、例外
不可抗力范围、通知要求、终止权利
付款条款信用期限、滞纳金、税费、价格调整
针对每个条款，对照手册（或通用标准）评估，注明条款是否存在、缺失或异常。

Detailed Clause Guidance

条款审查细节指南

Limitation of Liability
责任限制
Key elements to review:
  • Cap amount (fixed dollar amount, multiple of fees, or uncapped)
  • Whether the cap is mutual or applies differently to each party
  • Carveouts from the cap (what liabilities are uncapped)
  • Whether consequential, indirect, special, or punitive damages are excluded
  • Whether the exclusion is mutual
  • Carveouts from the consequential damages exclusion
  • Whether the cap applies per-claim, per-year, or aggregate
Common issues:
  • Cap set at a fraction of fees paid (e.g., "fees paid in the prior 3 months" on a low-value contract)
  • Asymmetric carveouts favoring the drafter
  • Broad carveouts that effectively eliminate the cap (e.g., "any breach of Section X" where Section X covers most obligations)
  • No consequential damages exclusion for one party's breaches
需审查的关键要素：
  • 赔偿上限（固定金额、费用倍数或无上限）
  • 上限是否为双向或对各方适用不同标准
  • 上限的例外情形（哪些责任不受上限限制）
  • 是否排除间接、特殊或惩罚性损害赔偿
  • 排除规则是否适用于双方
  • 间接损害赔偿排除的例外情形
  • 上限是按单次索赔、每年还是累计计算
常见问题：
  • 赔偿上限设定为已支付费用的一小部分（例如：低价值合同中“过去3个月支付的费用”）
  • 有利于起草方的不对称例外情形
  • 宽泛的例外情形实际上取消了上限（例如：“任何违反第X条的行为”，而第X条涵盖了大部分义务）
  • 一方违约时无间接损害赔偿排除条款
Indemnification
赔偿条款
Key elements to review:
  • Whether indemnification is mutual or unilateral
  • Scope: what triggers the indemnification obligation (IP infringement, data breach, bodily injury, breach of reps and warranties)
  • Whether indemnification is capped (often subject to the overall liability cap, or sometimes uncapped)
  • Procedure: notice requirements, right to control defense, right to settle
  • Whether the indemnitee must mitigate
  • Relationship between indemnification and the limitation of liability clause
Common issues:
  • Unilateral indemnification for IP infringement when both parties contribute IP
  • Indemnification for "any breach" (too broad; essentially converts the liability cap to uncapped liability)
  • No right to control defense of claims
  • Indemnification obligations that survive termination indefinitely
需审查的关键要素：
  • 赔偿是双向还是单向
  • 范围：触发赔偿义务的情形（知识产权侵权、数据泄露、人身伤害、违反陈述与保证）
  • 赔偿是否设限（通常受整体责任上限约束，有时无上限）
  • 流程：通知要求、抗辩控制权、和解权
  • 被赔偿方是否必须减轻损失
  • 赔偿条款与责任限制条款的关系
常见问题：
  • 当双方都贡献知识产权时，要求单向的知识产权侵权赔偿
  • 针对“任何违约行为”的赔偿（过于宽泛；实际上将责任上限转为无上限责任）
  • 无索赔抗辩控制权
  • 赔偿义务在合同终止后无限期存续
Intellectual Property
知识产权
Key elements to review:
  • Ownership of pre-existing IP (each party should retain their own)
  • Ownership of IP developed during the engagement
  • Work-for-hire provisions and their scope
  • License grants: scope, exclusivity, territory, sublicensing rights
  • Open source considerations
  • Feedback clauses (grants on suggestions or improvements)
Common issues:
  • Broad IP assignment that could capture the customer's pre-existing IP
  • Work-for-hire provisions extending beyond the deliverables
  • Unrestricted feedback clauses granting perpetual, irrevocable licenses
  • License scope broader than needed for the business relationship
需审查的关键要素：
  • 已有知识产权的归属（各方应保留自有知识产权）
  • 合作期间开发的知识产权的归属
  • 职务作品条款及其范围
  • 许可授予：范围、排他性、地域、分许可权
  • 开源软件考量
  • 反馈条款（对建议或改进的许可授予）
常见问题：
  • 宽泛的知识产权转让条款可能涵盖客户的已有知识产权
  • 职务作品条款超出交付成果范围
  • 无限制的反馈条款授予永久、不可撤销的许可
  • 许可范围超出业务关系所需
Data Protection
数据保护
Key elements to review:
  • Whether a Data Processing Agreement/Addendum (DPA) is required
  • Data controller vs. data processor classification
  • Sub-processor rights and notification obligations
  • Data breach notification timeline (72 hours for GDPR)
  • Cross-border data transfer mechanisms (SCCs, adequacy decisions, binding corporate rules)
  • Data deletion or return obligations on termination
  • Data security requirements and audit rights
  • Purpose limitation for data processing
Common issues:
  • No DPA when personal data is being processed
  • Blanket authorization for sub-processors without notification
  • Breach notification timeline longer than regulatory requirements
  • No cross-border transfer protections when data moves internationally
  • Inadequate data deletion provisions
需审查的关键要素：
  • 是否需要数据处理协议/附录（DPA）
  • 数据控制方vs数据处理方的分类
  • 分包商权利与通知义务
  • 数据泄露通知时限（GDPR要求72小时）
  • 跨境数据传输机制（SCCs、充分性决定、绑定公司规则）
  • 合同终止时的数据删除或返还义务
  • 数据安全要求与审计权
  • 数据处理的目的限制
常见问题：
  • 处理个人数据时未提供DPA
  • 无条件授权分包商且无需通知
  • 数据泄露通知时限长于监管要求
  • 数据跨境传输时无保护措施
  • 数据删除条款不完善
Term and Termination
合同期限与终止
Key elements to review:
  • Initial term and renewal terms
  • Auto-renewal provisions and notice periods
  • Termination for convenience: available? notice period? early termination fees?
  • Termination for cause: cure period? what constitutes cause?
  • Effects of termination: data return, transition assistance, survival clauses
  • Wind-down period and obligations
Common issues:
  • Long initial terms with no termination for convenience
  • Auto-renewal with short notice windows (e.g., 30-day notice for annual renewal)
  • No cure period for termination for cause
  • Inadequate transition assistance provisions
  • Survival clauses that effectively extend the agreement indefinitely
需审查的关键要素：
  • 初始期限与续约条款
  • 自动续约条款与通知期限
  • 任意终止：是否允许？通知期限？提前终止费？
  • 因故终止：补救期限？何为“因故”？
  • 终止的影响：数据返还、过渡协助、存续条款
  • 收尾期限与义务
常见问题：
  • 长初始期限且不允许任意终止
  • 自动续约的通知窗口过短（例如：年度续约仅需30天通知）
  • 因故终止无补救期限
  • 过渡协助条款不完善
  • 存续条款实际上使协议无限期延续
Governing Law and Dispute Resolution
管辖法律与争议解决
Key elements to review:
  • Choice of law (governing jurisdiction)
  • Dispute resolution mechanism (litigation, arbitration, mediation first)
  • Venue and jurisdiction for litigation
  • Arbitration rules and seat (if arbitration)
  • Jury waiver
  • Class action waiver
  • Prevailing party attorney's fees
Common issues:
  • Unfavorable jurisdiction (unusual or remote venue)
  • Mandatory arbitration with rules favorable to the drafter
  • Waiver of jury trial without corresponding protections
  • No escalation process before formal dispute resolution
需审查的关键要素：
  • 法律选择（管辖地）
  • 争议解决机制（诉讼、仲裁、先调解）
  • 诉讼的管辖地与 venue
  • 仲裁规则与地点（如选择仲裁）
  • 放弃陪审团审判
  • 放弃集体诉讼
  • 胜诉方律师费
常见问题：
  • 不利的管辖地（不常见或偏远的 venue）
  • 强制仲裁且规则有利于起草方
  • 放弃陪审团审判但无相应保护
  • 正式争议解决前无升级流程

Step 5: Flag Deviations

步骤5：标记偏差

Classify each deviation from the playbook using a three-tier system:
使用三级系统分类每个与手册的偏差：

GREEN -- Acceptable

GREEN -- 可接受

The clause aligns with or is better than the organization's standard position. Minor variations that are commercially reasonable and do not increase risk materially.
Examples:
  • Liability cap at 18 months of fees when standard is 12 months (better for the customer)
  • Mutual NDA term of 2 years when standard is 3 years (shorter but reasonable)
  • Governing law in a well-established commercial jurisdiction close to the preferred one
Action: Note for awareness. No negotiation needed.
条款符合或优于组织的标准立场。微小的差异具有商业合理性，不会显著增加风险。
示例：
  • 责任上限为18个月费用，标准为12个月（对客户更有利）
  • 双向保密协议期限为2年，标准为3年（更短但合理）
  • 管辖地为靠近首选地的成熟商业司法管辖区
行动：仅作告知，无需谈判。

YELLOW -- Negotiate

YELLOW -- 需要谈判

The clause falls outside the standard position but within a negotiable range. The term is common in the market but not the organization's preference. Requires attention and likely negotiation, but not escalation.
Examples:
  • Liability cap at 6 months of fees when standard is 12 months (below standard but negotiable)
  • Unilateral indemnification for IP infringement when standard is mutual (common market position but not preferred)
  • Auto-renewal with 60-day notice when standard is 90 days
  • Governing law in an acceptable but not preferred jurisdiction
Action: Generate specific redline language. Provide fallback position. Estimate business impact of accepting vs. negotiating.
  • Include: Specific redline language to bring the term back to standard position
  • Include: Fallback position if the counterparty pushes back
  • Include: Business impact of accepting as-is vs. negotiating
条款超出标准立场但在可谈判范围内。该条款在市场中常见，但并非组织的首选。需要关注并进行谈判，但无需升级。
示例：
  • 责任上限为6个月费用，标准为12个月（低于标准但可谈判）
  • 知识产权侵权赔偿为单向，标准为双向（常见市场立场但非首选）
  • 自动续约通知期限为60天，标准为90天
  • 管辖地为可接受但非首选的司法管辖区
行动：生成具体的红线修订语言，提供备选方案，评估接受vs谈判的业务影响。
  • 包含：将条款拉回标准立场的具体红线修订语言
  • 包含：如果对方反对的备选方案
  • 包含：接受现状vs进行谈判的业务影响

RED -- Escalate

RED -- 需要升级

The clause falls outside acceptable range, triggers a defined escalation criterion, or poses material risk. Requires senior counsel review, outside counsel involvement, or business decision-maker sign-off.
Examples:
  • Uncapped liability or no limitation of liability clause
  • Unilateral broad indemnification with no cap
  • IP assignment of pre-existing IP
  • No DPA offered when personal data is processed
  • Unreasonable non-compete or exclusivity provisions
  • Governing law in a problematic jurisdiction with mandatory arbitration
Action: Explain the specific risk. Provide market-standard alternative language. Estimate exposure. Recommend escalation path.
  • Include: Why this is a RED flag (specific risk)
  • Include: What the standard market position looks like
  • Include: Business impact and potential exposure
  • Include: Recommended escalation path
条款超出可接受范围、触发定义的升级条件或构成重大风险。需要资深法律顾问、外部律师介入或业务决策者签字确认。
示例：
  • 无责任限制或责任无上限
  • 单向宽泛且无上限的赔偿条款
  • 已有知识产权的转让条款
  • 处理个人数据时未提供DPA
  • 不合理的竞业禁止或排他性条款
  • 管辖地为问题司法管辖区且要求强制仲裁
行动：解释具体风险，提供市场标准替代语言，评估风险敞口，建议升级路径。
  • 包含：为何标记为RED（具体风险）
  • 包含：标准市场立场
  • 包含：业务影响与潜在风险敞口
  • 包含：建议的升级路径

Step 6: Generate Redline Suggestions

步骤6：生成红线修订建议

For each YELLOW and RED deviation, provide:
  • Current language: Quote the relevant contract text
  • Suggested redline: Specific alternative language
  • Rationale: Brief explanation suitable for sharing with the counterparty
  • Priority: Whether this is a must-have or nice-to-have in negotiation
针对每个YELLOW和RED偏差，提供：
  • 当前语言：引用合同相关文本
  • 建议的红线修订：具体的替代语言
  • 理由：适合与对方分享的简短说明
  • 优先级：在谈判中是必须达成还是锦上添花

Redline Generation Best Practices

红线修订生成最佳实践

When generating redline suggestions:
  1. Be specific: Provide exact language, not vague guidance. The redline should be ready to insert.
  2. Be balanced: Propose language that is firm on critical points but commercially reasonable. Overly aggressive redlines slow negotiations.
  3. Explain the rationale: Include a brief, professional rationale suitable for sharing with the counterparty's counsel.
  4. Provide fallback positions: For YELLOW items, include a fallback position if the primary ask is rejected.
  5. Prioritize: Not all redlines are equal. Indicate which are must-haves and which are nice-to-haves.
  6. Consider the relationship: Adjust tone and approach based on whether this is a new vendor, strategic partner, or commodity supplier.
生成红线修订建议时：
  1. 具体明确：提供精确语言，而非模糊指导。红线修订应可直接插入使用。
  2. 保持平衡：提出在关键点上立场坚定但具有商业合理性的语言。过于激进的红线修订会拖慢谈判。
  3. 解释理由：包含适合与对方律师分享的简短、专业理由。
  4. 提供备选方案：针对YELLOW项，提供如果主要诉求被拒绝的备选方案。
  5. 划分优先级：并非所有红线修订都同等重要。注明哪些是必须达成的，哪些是锦上添花的。
  6. 考虑合作关系：根据对方是新供应商、战略合作伙伴还是大宗商品供应商调整语气和方法。

Redline Format

红线修订格式

For each redline:
**Clause**: [Section reference and clause name]
**Current language**: "[exact quote from the contract]"
**Proposed redline**: "[specific alternative language with additions in bold and deletions struck through conceptually]"
**Rationale**: [1-2 sentences explaining why, suitable for external sharing]
**Priority**: [Must-have / Should-have / Nice-to-have]
**Fallback**: [Alternative position if primary redline is rejected]
针对每个红线修订：
**条款**：[章节引用和条款名称]
**当前语言**："[合同原文引用]"
**建议的红线修订**："[具体替代语言，新增内容加粗，删除内容划线（概念性）]"
**理由**：[1-2句话，适合对外分享]
**优先级**：[必须达成 / 应达成 / 锦上添花]
**备选方案**：[如果主要红线修订被拒绝的替代立场]

Step 7: Business Impact Summary

步骤7：业务影响总结

Provide a summary section covering:
  • Overall risk assessment: High-level view of the contract's risk profile
  • Top 3 issues: The most important items to address
  • Negotiation strategy: Recommended approach (which issues to lead with, what to concede)
  • Timeline considerations: Any urgency factors affecting the negotiation approach
提供总结部分，涵盖：
  • 整体风险评估：合同风险概况的高层级视图
  • Top 3问题：最需要解决的三个问题
  • 谈判策略：建议的方法（先解决哪些问题，可让步哪些）
  • 时间线考量：影响谈判方法的紧急因素

Negotiation Priority Framework

谈判优先级框架

When presenting redlines, organize by negotiation priority:
Tier 1 -- Must-Haves (Deal Breakers) Issues where the organization cannot proceed without resolution:
  • Uncapped or materially insufficient liability protections
  • Missing data protection requirements for regulated data
  • IP provisions that could jeopardize core assets
  • Terms that conflict with regulatory obligations
Tier 2 -- Should-Haves (Strong Preferences) Issues that materially affect risk but have negotiation room:
  • Liability cap adjustments within range
  • Indemnification scope and mutuality
  • Termination flexibility
  • Audit and compliance rights
Tier 3 -- Nice-to-Haves (Concession Candidates) Issues that improve the position but can be conceded strategically:
  • Preferred governing law (if alternative is acceptable)
  • Notice period preferences
  • Minor definitional improvements
  • Insurance certificate requirements
Negotiation strategy: Lead with Tier 1 items. Trade Tier 3 concessions to secure Tier 2 wins. Never concede on Tier 1 without escalation.
呈现红线修订时，按谈判优先级排序：
Tier 1 -- 必须达成（交易否决项） 组织无法在未解决这些问题的情况下推进：
  • 无上限或严重不足的责任保护
  • 针对受监管数据缺失数据保护要求
  • 可能危及核心资产的知识产权条款
  • 违反监管义务的条款
Tier 2 -- 应达成（强烈偏好） 对风险有重大影响但有谈判空间的问题：
  • 责任上限在范围内调整
  • 赔偿条款的范围与双向性
  • 终止灵活性
  • 审计与合规权利
Tier 3 -- 锦上添花（可让步项） 可改善立场但可战略性让步的问题：
  • 首选管辖地（如果替代方案可接受）
  • 通知期限偏好
  • 微小的定义改进
  • 保险凭证要求
谈判策略：先推进Tier 1问题。用Tier 3的让步换取Tier 2的成果。绝不轻易在Tier 1问题上让步，除非升级审批。

Step 8: CLM Routing (If Connected)

步骤8：CLM路由（如果已连接）

If a Contract Lifecycle Management system is connected via MCP:
  • Recommend the appropriate approval workflow based on contract type and risk level
  • Suggest the correct routing path (e.g., standard approval, senior counsel, outside counsel)
  • Note any required approvals based on contract value or risk flags
If no CLM is connected, skip this step.
如果通过MCP连接了合同生命周期管理（CLM）系统：
  • 根据合同类型和风险等级建议合适的审批工作流
  • 建议正确的路由路径（如标准审批、资深法律顾问、外部律师）
  • 注明基于合同价值或风险标记的必要审批
如果未连接CLM，跳过此步骤。

Output Format

输出格式

Structure the output as:
undefined
输出结构如下：
undefined

Contract Review Summary

合同审查总结

Document: [contract name/identifier] Parties: [party names and roles] Your Side: [vendor/customer/etc.] Deadline: [if provided] Review Basis: [Playbook / Generic Standards]
文档：[合同名称/标识符] 双方：[双方名称与角色] 您的立场：[供应商/客户等] 截止日期：[如果提供] 审查依据：[谈判手册 / 通用标准]

Key Findings

关键发现

[Top 3-5 issues with severity flags]
[带有严重程度标记的Top 3-5问题]

Clause-by-Clause Analysis

逐条条款分析

[Clause Category] -- [GREEN/YELLOW/RED]

[条款类别] -- [GREEN/YELLOW/RED]

Contract says: [summary of the provision] Playbook position: [your standard] Deviation: [description of gap] Business impact: [what this means practically] Redline suggestion: [specific language, if YELLOW or RED]
[Repeat for each major clause]
合同内容：[条款摘要] 手册立场：[您的标准] 偏差：[差距描述] 业务影响：[实际影响]
[重复每个主要条款]

Negotiation Strategy

谈判策略

[Recommended approach, priorities, concession candidates]
[建议的方法、优先级、可让步项]

Next Steps

下一步行动

[Specific actions to take]
undefined
[具体行动]
undefined

Notes

注意事项

  • If the contract is in a language other than English, note this and ask if the user wants a translation or review in the original language
  • For very long contracts (50+ pages), offer to focus on the most material sections first and then do a complete review
  • Always remind the user that this analysis should be reviewed by qualified legal counsel before being relied upon for legal decisions
  • 如果合同为非英语语言，注明这一点并询问用户是否需要翻译或用原语言审查
  • 对于超长合同（50页以上），提议先聚焦最关键的部分，再进行完整审查
  • 始终提醒用户，此分析在用于法律决策前需由合格的法律顾问审核