material-contract-schedule
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese/material-contract-schedule
/material-contract-schedule
- Load purchase agreement → Material Contract definition + schedule format.
- Use the workflow below.
- Apply definition to diligence findings. Flag edge cases.
- Format per agreement. Consent overlay feeds closing checklist.
- 加载采购协议 → 获取Material Contract（重大合同）定义及时间表格式。
- 遵循以下工作流。
- 将定义应用于尽职调查结果，标记边缘案例。
- 按照协议格式排版。同意跟踪覆盖层将同步至交割 checklist。
Matter context
事项上下文
Matter context. Check in the practice-level CLAUDE.md. If is (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run or say ." Load the active matter's for matter-specific context and overrides. Write outputs to the matter folder at . Never read another matter's files unless is .
## Matter workspacesEnabled✗/corporate-legal:matter-workspace switch <slug>practice-levelmatter.md~/.claude/plugins/config/claude-for-legal/corporate-legal/matters/<matter-slug>/Cross-matter contexton事项上下文。查看实践层级CLAUDE.md中的部分。如果为（内部用户默认设置），则跳过本段剩余内容——技能将使用实践层级上下文，事项机制不可见。如果已启用且无活跃事项，请询问：“这是针对哪个事项的？请运行或说明。” 加载活跃事项的以获取事项特定上下文和覆盖规则。将输出写入事项文件夹：。除非设置为，否则不得读取其他事项的文件。
## Matter workspacesEnabled✗/corporate-legal:matter-workspace switch <slug>practice-levelmatter.md~/.claude/plugins/config/claude-for-legal/corporate-legal/matters/<matter-slug>/Cross-matter contextonPurpose
目的
The purchase agreement has a rep: "Schedule 3.X lists all Material Contracts." This skill builds that schedule from the diligence findings — which contracts are material per the agreement's definition, in the format the agreement requires.
采购协议中有一项陈述：“附表3.X列出所有Material Contract（重大合同）”。本技能根据尽职调查结果构建该时间表——即根据协议定义判定哪些合同属于重大合同，并按照协议要求的格式呈现。
Load context
加载上下文
- Purchase agreement draft — for the definition of "Material Contract" and the schedule format
- → materiality thresholds (may differ from the agreement definition — use the agreement's)
~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md - Diligence findings from diligence-issue-extraction — contract-level data
- 采购协议草案 —— 用于获取“Material Contract”的定义及时间表格式
- → 重要性阈值（可能与协议定义不同——以协议定义为准）
~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md - 来自diligence-issue-extraction的尽职调查结果 —— 合同层面数据
Workflow
工作流
Step 1: Get the definition
步骤1：获取定义
Pull the definition of "Material Contract" from the purchase agreement — the PA definition controls. Deal-structure differences (stock vs. asset vs. merger) can change how a prong is interpreted, and regulated-industry overlays (healthcare, defense, financial services, telecom, government contracting) can add consent requirements that live outside the PA. If the deal involves any of those overlays, research the applicable anti-assignment or novation rules (for example, federal contracts, government contracting novation, sector-specific consent statutes) and cite the controlling rule.
Common prong categories to look for in the PA definition — these are not a substitute for reading the PA, and the list the PA uses controls:
- Dollar-value threshold (annual or aggregate)
- Term length
- Change-of-control or anti-assignment provision
- Exclusivity or non-compete
- Top N customer or supplier contracts
- Real property leases
- IP licenses (in-bound and out-bound)
- Related-party agreements
- Government contracts
- Contracts outside the ordinary course
The PA's definition is the test. Apply it mechanically — every contract that meets any prong in the PA's definition goes on the schedule.
从采购协议中提取“Material Contract”的定义——采购协议（PA）的定义具有最终效力。交易结构差异（股权交易vs资产交易vs合并）可能会影响条款的解释方式，而受监管行业的附加规则（医疗、国防、金融服务、电信、政府合同）可能会增加采购协议之外的同意要求。如果交易涉及上述任何附加规则，请研究适用的反转让或更新规则（例如联邦合同、政府合同更新、特定行业同意法规）并引用控制性规则。
采购协议定义中常见的条款类别——这些不能替代阅读采购协议，采购协议中列出的类别具有最终效力：
- 金额阈值（年度或总计）
- 期限长度
- 控制权变更或反转让条款
- 排他性或竞业禁止条款
- 前N大客户或供应商合同
- 不动产租赁合同
- IP许可（ inbound和outbound）
- 关联方协议
- 政府合同
- 日常业务之外的合同
采购协议的定义是判定标准。需严格机械地应用该定义——任何符合采购协议中任意条款的合同都应纳入时间表。
Step 2: Apply the definition to the findings
步骤2：将定义应用于调查结果
For each contract reviewed in diligence:
| Contract | Meets prong(s) | Include |
|---|---|---|
| [name] | [$X+ annual value; CoC provision] | Yes |
| [name] | [none] | No |
Edge cases to flag for human decision:
- Contract is $X-1 (just under threshold) but important to the business
- Contract meets a prong but is being terminated anyway
- Oral agreements or side letters that may or may not count
针对每项经尽职调查审核的合同：
| 合同 | 符合的条款 | 是否纳入 |
|---|---|---|
| [名称] | [年度价值≥$X；控制权变更条款] | 是 |
| [名称] | 无 | 否 |
需标记供人工决策的边缘案例：
- 合同金额为$X-1（略低于阈值）但对业务至关重要
- 合同符合条款但已在终止流程中
- 可能或可能不被计入的口头协议或附属函件
Step 3: Gather schedule data
步骤3：收集时间表数据
For each included contract, the schedule typically needs:
| Field | Source |
|---|---|
| Counterparty name | Contract |
| Contract title/type | Contract |
| Date | Contract |
| Term / expiration | Contract |
| Annual/total value | Contract or management data |
| Which materiality prong it meets | Step 2 analysis |
| Consent required for the deal | Diligence finding |
| VDR reference | Diligence inventory |
Pull from existing diligence extractions. If a field is missing, flag it — don't guess.
对于每项纳入的合同，时间表通常需要以下信息：
| 字段 | 来源 |
|---|---|
| 交易对手名称 | 合同 |
| 合同标题/类型 | 合同 |
| 日期 | 合同 |
| 期限/到期日 | 合同 |
| 年度/总价值 | 合同或管理层数据 |
| 符合的重要性条款 | 步骤2的分析结果 |
| 交易是否需要同意 | 尽职调查结果 |
| VDR参考 | 尽职调查清单 |
从现有尽职调查提取结果中获取信息。如果某字段缺失，请标记——切勿猜测。
Step 4: Format per the agreement
步骤4：按照协议格式排版
Disclosure schedules have a format — usually a numbered list or a table, sometimes with sub-parts by contract type. Match the format of the other schedules in the draft agreement.
markdown
undefined披露时间表有特定格式——通常为编号列表或表格，有时按合同类型分为子部分。需与协议草案中其他时间表的格式保持一致。
markdown
undefinedSchedule 3.[X] — Material Contracts
附表3.[X] —— Material Contracts
The following are the Material Contracts as of the date hereof:
以下是截至本日期的Material Contracts：
(a) Customer Contracts
(a) 客户合同
-
[Agreement Title], dated [date], between [Target] and [Counterparty]. [Brief description if the format calls for it.] [VDR: path]
-
[...]
-
[协议标题]，签署日期[日期]，双方为[目标方]与[交易对手]。 [如格式要求，可添加简要说明。] [VDR：路径]
-
[...]
(b) Supplier Contracts
(b) 供应商合同
[...]
[...]
(c) Real Property
(c) 不动产
[...]
[etc. — sub-parts per the agreement's definition structure]
undefined[...]
[依此类推——按照协议定义结构划分子部分]
undefinedStep 5: Consent tracking overlay
步骤5：同意跟踪覆盖层
Separately (not in the schedule itself — this is internal), track which scheduled contracts require consent.
The consent overlay and any pre-delivery working draft of the schedule are derived from privileged diligence materials and inherit their privilege and confidentiality status — distribution beyond the privilege circle can waive privilege. The schedule itself, once delivered as an exhibit to the executed PA, is a deal document and is not privileged; strip any internal annotations before delivery.
| Schedule # | Counterparty | Consent required | Status | Owner | Due |
|---|---|---|---|---|---|
| 3.X(a)(1) | [name] | Yes — CoC §12.2 | Requested | [name] | [date] |
This feeds closing-checklist.
单独（不在时间表本身中——此为内部内容）跟踪哪些已纳入时间表的合同需要同意。
同意跟踪覆盖层及时间表的交付前工作草案均源自保密尽职调查材料，因此继承其保密特权和机密性——超出特权范围分发可能会导致特权丧失。时间表本身一旦作为已签署采购协议的附件交付，即为交易文件，不再享有保密特权；交付前需删除所有内部注释。
| 附表编号 | 交易对手 | 是否需要同意 | 状态 | 负责人 | 截止日期 |
|---|---|---|---|---|---|
| 3.X(a)(1) | [名称] | 是——控制权变更条款§12.2 | 已请求 | [名称] | [日期] |
此内容将同步至交割checklist。
Cross-check
交叉核查
Before delivering:
- Every contract that met a prong is on the schedule (completeness)
- No contract is on the schedule that doesn't meet a prong (no over-disclosure — it's a rep, not a data dump)
- Schedule is consistent with the other reps (a contract on Schedule 3.X that creates a lien should also be on the liens schedule)
- Every entry has a VDR cite so buyer's counsel can find the underlying doc
交付前需核查：
- 所有符合条款的合同均已纳入时间表（完整性）
- 时间表中无不符合条款的合同（避免过度披露——这是陈述，而非数据转储）
- 时间表与其他陈述一致（例如，附表3.X中涉及留置权的合同也应出现在留置权时间表中）
- 每个条目都有VDR引用，以便买方律师找到相关文件
Handoffs
交接
- From diligence-issue-extraction: Contract-level findings are the input.
- To closing-checklist: Consent items go on the checklist.
- 来自diligence-issue-extraction： 合同层面的调查结果为输入内容。
- 至closing-checklist： 需同意的事项将纳入checklist。
What this skill does not do
本技能不执行的操作
- It doesn't decide the materiality definition — that's in the purchase agreement.
- It doesn't obtain consents — it tracks which ones are needed.
- It doesn't draft the rep — it populates the schedule the rep references.
- 不决定重要性定义——该定义由采购协议规定。
- 不获取同意——仅跟踪需要哪些同意。
- 不起草陈述——仅填充陈述所引用的时间表。