返回提示词目录第 1179 页

编制标准合同谈判手册

帮你梳理常被协商的合同条款,形成让步方案、审批规则与回复话术,供业务及律师确认。

完整提示词

<context>
Once a business sends the same contract to many customers or suppliers, the same dozen clauses get negotiated again and again, and each deal is handled differently depending on who is on the call. In-house legal teams solve this with a playbook: for each clause, the standard position, one or two pre-approved fallbacks, a walk-away point, the reason behind each (so negotiators can explain it), and who must approve anything beyond the fallbacks. What makes a playbook usable: positions tied to deal size (a bigger deal can justify a higher liability cap); fallbacks that are real contract wording, not principles; short replies a salesperson can paste; a short "never agree" list (uncapped liability, assigning core IP, unlimited audits, most-favoured pricing, open-ended indemnities, whatever the business has decided); and approval levels that are quick for low-risk changes. A playbook written by someone who has not seen which clauses actually get challenged ends up long and ignored, so it should be built from the real pushback.
{{#jurisdiction}}

Jurisdiction: {{jurisdiction}}
{{/jurisdiction}}

<context_notes>
{{context}}
</context_notes>
</context>

<task>
<contract>
{{contract}}
</contract>

1. Identify the clauses that are actually negotiated, starting with the ones the context names, then the usual pressure points for this type of contract (liability cap and exclusions, indemnities, payment terms, IP, warranties, service levels and credits, termination, renewal, confidentiality, data protection, audit, insurance, governing law). Skip clauses that rarely move.
2. For each negotiated clause: the standard position quoting the clause, one or two fallbacks as contract wording, the walk-away point, the reason in one sentence, and any deal-size condition. Base the standard position on the contract; mark fallbacks and walk-away points as proposals for the business to approve.
3. Write short replies to the most common pushback requests, ready to paste into an email.
4. Propose approval rules: who can agree what (negotiator, manager, founder or legal), with deal-size thresholds left as [BRACKETS] unless stated.
5. A short "never agree" list with the reason for each.
6. Questions for a lawyer before the playbook is used, including clauses whose effect depends on the governing law.
</task>

<constraints>
{{> guardrails/professional-limits}}
- Quote clause numbers. Do not invent the business's risk appetite, thresholds or numbers; use [BRACKETS] and mark proposals as proposals.
- Keep it short enough to use during a deal: no more than about twelve clauses unless the contract demands more.
- Fallback wording must be specific contract language, not a principle.
- Do not claim any position is "market standard" as a fact; say what is commonly asked and let the business decide.
{{> output/uncertainty}}
</constraints>

<output_format>
## How to use this playbook
Three or four lines.

## Clause positions
Table: clause | standard position | fallback 1 | fallback 2 | walk-away | reason | approver.

## Replies to common pushback
Numbered: request - reply.

## Approval rules
Table: change | who approves | threshold.

## Never agree
Bullets with reasons.

## Questions for a lawyer
Numbered.
</output_format>

可替换内容

  • {{#jurisdiction}}
  • {{jurisdiction}}
  • {{/jurisdiction}}
  • {{context}}
  • {{contract}}
  • {{> guardrails/professional-limits}}
  • {{> output/uncertainty}}
  • [BRACKETS]

分类与标签

办公效率、合同谈判、条款让步、审批规则、法律复核

前往 AI 图片创作