thinkhard.SI

Prompt repository Legal & compliance

Draft a contract amendment from the changes you agreed

You and the other party agreed changes to an existing contract, and you need an amendment that changes exactly those clauses and leaves the rest untouched.

Registry no.
LEG-031
Collection
Legal & compliance
Laid out for
Any chat model
Score
10 out of 10
Blanks to fill
7
Added

Legal & complianceAny chat

The prompt

Score 10 of 10, Excellent

Use it when You and the other party agreed changes to an existing contract, and you need an amendment that changes exactly those clauses and leaves the rest untouched.

  • {{reviewer}}
  • {{original_agreement}}
  • {{current_clauses}}
  • {{agreed_changes}}
  • {{amendment_clause}}
  • {{effective_date}}
  • {{signatories}}
Full prompt and why it works
Prompt
Draft an amendment to an existing contract from the changes we agreed, for {{reviewer}} to review before it is signed, so that it changes exactly what was agreed, clause by clause, and nothing else. This is a draft for legal review, not legal advice.

The original agreement, as named on its first page (title, parties, date), and any earlier amendments: {{original_agreement}}

The clauses being changed, copied exactly as they read now, with their numbers:
"""
{{current_clauses}}
"""

What we agreed, and where the agreement is recorded (email, call notes, signed term sheet):
"""
{{agreed_changes}}
"""

The amendment clause of the original agreement, if it has one (how changes must be made and signed): {{amendment_clause}}
Effective date of the changes: {{effective_date}}
Who will sign for each party (titles are enough): {{signatories}}

Produce:
1. The amendment, with: a title such as "Amendment No. [number] to [agreement title]"; a short opening that identifies the parties and the original agreement exactly as given; a line that terms defined in the agreement have the same meaning here; numbered changes, each in one of these forms: "Clause 4.2 is deleted and replaced with: '...'", "In clause 7.1, '30 days' is replaced with '45 days'", or "A new clause 9.4 is inserted after clause 9.3: '...'"; the effective date; a statement that all other terms remain unchanged and in effect; how the amendment may be signed, following the amendment clause; and signature blocks.
2. A change table for the reviewer, with the columns Clause, Current wording, New wording, Where it was agreed.
3. Knock-on effects to check: other clauses, defined terms, schedules or cross-references the changes may affect, listed for the reviewer and not changed.

For example, a change might read: "In clause 5.1, 'twelve (12) months' is replaced with 'twenty-four (24) months'." That example shows the form only.

Keep the amendment as short as the changes allow. A good amendment reads cleanly beside the original and leaves no doubt about which words changed.

Rules:
- Change only what the agreed changes cover. Do not tidy, modernize or improve any other wording.
- Quote current wording exactly as pasted.
- Do not add obligations, warranties or terms that were not agreed.

If an agreed change is vague, such as "extend the deadline" with no new date, or if it conflicts with a clause not pasted here, write [CHECK: what is needed] in the amendment and list it for the reviewer, rather than choosing the wording yourself.

Variables

{{reviewer}}
Who reviews the amendment, for example "our lawyer" or "the legal team".
{{original_agreement}}
The agreement's title, the parties as named in it, its date, and any earlier amendments.
{{current_clauses}}
Each clause being changed, copied exactly with its number.
{{agreed_changes}}
What was agreed for each clause, and where it is recorded, for example "email from their CFO, [date]: extend term to 24 months".
{{amendment_clause}}
The original agreement's clause on how it can be amended, copied, or "none".
{{effective_date}}
When the changes take effect, for example "on signing" or a date.
{{signatories}}
Who signs for each side, for example "our CEO; their head of procurement".

Why it works

  • What to avoid. Only the agreed changes are made and no other wording is tidied, because an amendment that strays reopens terms nobody meant to discuss.
  • An example. Sample formats for each kind of change, from replacing a clause to inserting a new one, show the precise wording reviewers expect.
  • If unsure. A vague agreed change gets a [CHECK] marker and goes to the reviewer instead of becoming wording nobody agreed.

How to use it

  1. Press Fill in blanks and type your details into each blank. What you type stays in this browser.
  2. Copy the filled prompt into the AI tool you already use, such as ChatGPT, Claude or Gemini, or open it in the Grader or the Prompt Tester here.
  3. Before you rely on it, try it on three or four real examples. The Prompt Tester runs them all at once and shows which ones go wrong.
Use it from code

Get this prompt as JSON from the free REST API, with your own text in the blanks, or let an AI assistant fetch it through the MCP server. No key.

curl -s https://thinkhard.si/api/v1/prompts/contract-amendment-draft

With the MCP server added to Claude, ChatGPT, Cursor or VS Code, call get_prompt with {"prompt": "contract-amendment-draft"}, or just ask for it by name.