本文へ移動
cccskills
無料GitHub で公開

without-prejudice-drafter-andrew-bird

Writes a settlement letter on the right footing — and warns you when marking it 'without prejudice' won't actually keep it out of court. A genuine settlement letter is normally protected (the judge can't see it), but only if the substance is a real attempt to settle, and even then there are exceptions. The skill picks the correct footing — without prejudice (WP), without prejudice save as to costs (WPSATC / Calderbank), or open — drafts the finished letter, and surfaces the Unilever v Procter & Gamble exceptions that get WP material admitted despite the label, which a plain template won't flag. Built for juniors and in-house counsel drafting a settlement or Calderbank offer who need the footing right the first time. Use when the user asks to draft a WP letter, a Calderbank, a settlement letter, or wants to know whether material is likely protected from disclosure.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md10.3 KB
  • README.md3.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

/without-prejudice-drafter

  1. Identify the correct footing: open, WP, or WPSATC.
  2. Apply the right header convention. WP is not protected just because labelled — the substance must be a genuine settlement attempt in an existing or contemplated dispute.
  3. Surface the Unilever exceptions: WP protection is not absolute.
  4. Draft accordingly. Keep open and WP material in separate documents.

Without prejudice / WPSATC correspondence

The three footings

FootingDisclosure at trialUse
OpenYes — fully admissibleStatements of case, demands, pre-action letters not yet in negotiation
Without prejudice (WP)No — inadmissible to prove liability or quantumGenuine settlement negotiations
Without prejudice save as to costs (WPSATC) / CalderbankInadmissible on liability/quantum; intended to be admissible on costs after judgmentSettlement offers where the offeror wants costs protection but cannot use CPR Part 36 (e.g. Employment Tribunal) or wants Calderbank flexibility

Labelling a letter WPSATC signals the intended footing; it does not by itself secure costs protection. Whether the court reads the letter on costs, and what weight it gives it, is a matter for the court's discretion (CPR 44.2) on the facts. The footing is a proposal, not a guarantee.

When WP protection applies

Three conditions:

  1. There is an existing or contemplated dispute.
  2. The communication is a genuine attempt to settle that dispute.
  3. The parties intended the communication to be confidential.

A letter labelled "without prejudice" that does not satisfy these conditions is not protected. A letter that satisfies them but is not labelled is still protected — the label is evidence of intention, but substance prevails (Rush & Tompkins Ltd v Greater London Council [1989] AC 1280).

The Unilever exceptions (Unilever v Procter & Gamble [2000])

WP protection is not absolute (Unilever plc v Procter & Gamble Co [2000] 1 WLR 2436, [2000] EWCA Civ 11). The categories below are illustrative, not a closed or settled set — the courts treat them as fact-sensitive, so confirm the current scope before relying on any one of them. The court has admitted WP material in evidence in situations including the following. Do not over-extend these; treat anything outside a squarely-decided category as in need of verification rather than asserting protection is lost:

  1. The WP communications show the agreement was concluded — to prove or rebut existence/terms of the agreement.
  2. The communications are evidence of misrepresentation, fraud, or undue influence.
  3. The communications give rise to estoppel.
  4. Without admission, exclusion would act as a cloak for "unambiguous impropriety" (e.g. perjury, blackmail, threats).
  5. To explain delay or apparent acquiescence (relevant to limitation).
  6. The communications are relevant to costs (only if WPSATC was the footing).
  7. The communications include a tariff or formula relevant to determining a related issue.

A letter discussing a settlement that also makes a threat or admits a crime is exposed under (4). Practical implication: WP is not a magic shield. Labelling a letter does not make it privileged, and even a properly-footed letter can be admitted under an exception. Don't write anything you'd be embarrassed by if a judge reads it, and don't promise the client the letter is "safe" — the footing can fail.

Calderbank / WPSATC specifics

The Calderbank offer (Calderbank v Calderbank [1976] Fam 93) lets a party put a settlement on the table that the court will see on costs at the end. Mostly displaced by CPR Part 36 in the civil courts, but still alive where:

  • The forum doesn't have Part 36 (Employment Tribunal — use a Calderbank / WPSATC offer instead).
  • The offer is on terms Part 36 cannot accommodate (mixed money and non-money relief; offers including a contribution; offers conditional on third-party action).
  • The offeror wants to avoid the strictures of Part 36 formality.

Calderbank cost consequences in the civil courts are weaker than Part 36 — the court has discretion under CPR 44.2 and 36.17 does not apply. State the WPSATC footing explicitly; if uncertain, run the offer as a Part 36 instead.

Drafting rules

  1. Header: place the words "Without Prejudice" or "Without Prejudice Save As To Costs" prominently at the top of the document, before the salutation.
  2. Don't mix: do not put open content and WP content in the same document. If both are needed, write two letters, one open, one WP, cross-referenced.
  3. No threats: don't put anything in a WP letter that you would not want read out in court if WP fails.
  4. Settlement substance: state clearly that the letter is part of a genuine attempt to settle the [described dispute].
  5. Authority: a WP offer should be authorised by the client and confirm the lawyer has authority to bind on those terms (or expressly state subject-to-client-approval).
  6. Acceptance mechanics: how is acceptance communicated; how long is the offer open; what happens if not accepted.
  7. Costs reservation (WPSATC only): expressly reserve the right to refer to the letter on costs. The reservation states the intended footing; it does not bind the court, which retains discretion under CPR 44.2.

Workflow

Step 1 — Confirm footing

Infer the intended footing from the request:

  • "Settlement offer" or "without prejudice letter" → WP.
  • "Calderbank", "costs protection", "offer with costs consequences", or any ET-context offer → WPSATC.
  • "Demand", "letter before claim", "on the record" → open (use cpr-letter-drafter instead). Surface for confirmation only if ambiguous from the request.

Step 2 — Confirm dispute

Is there an existing or contemplated dispute? If no, WP doesn't apply — use open correspondence.

Step 3 — Draft

Use the appropriate template. Keep separate from any open correspondence going out the same day.

Step 4 — Surface exceptions

Flag any content that risks an Unilever exception (admissions, threats, signals of estoppel).

Output

Produce the finished letter, not the template. Each section below is content to PRODUCE — render it as the completed correspondence, fully drafted on the chosen footing. Do not echo the template skeleton back to the user, and do not fabricate facts to fill a placeholder: for any value you don't have (sums, dates, party names, dispute description), insert [SOLICITOR: confirm X] rather than guessing. The placeholders below (£[X], [21] days, [brief description]) mark exactly the spots that must be confirmed, not copied verbatim.

The two structures below are the WP and WPSATC variants. Pick the one matching the confirmed footing and render only that.

Without Prejudice — sections to produce

WITHOUT PREJUDICE

[Date]

[Recipient]

Dear Sirs,

Re: [Matter — dispute description]

This letter is written without prejudice as a genuine attempt to settle the dispute between our respective clients concerning [brief description of the dispute].

  1. [Statement of position — neutral, not adversarial.]
  2. [Proposal — sum, terms, mechanism.]
  3. [Time limit for acceptance.]
  4. Subject to acceptance on these terms, the matter will be compromised on the basis of [release / settlement deed / consent order].

This letter is intended to be confidential and may not be disclosed to the court without our written consent.

Yours faithfully,

[Signature]

Without Prejudice Save As To Costs — sections to produce

WITHOUT PREJUDICE SAVE AS TO COSTS

[Date]

[Recipient]

Dear Sirs,

Re: [Matter]

This letter is written without prejudice save as to costs.

  1. Our client offers [to pay / to accept] £[X] in full and final settlement of the [dispute / claim / counterclaim].
  2. The offer is open for acceptance for [21] days from the date of this letter.
  3. The sum is [inclusive / exclusive] of [costs / interest / VAT].
  4. Acceptance will be by [signed agreement / consent order / written acceptance].

If the offer is not accepted, our client reserves the right to refer to this letter on the question of costs after judgment.

Yours faithfully,

[Signature]

Markers

  • [FOOTING — review: this content reads more open than WP]
  • [UNILEVER RISK — admission / threat / unambiguous impropriety language]
  • [SEPARATION — keep open correspondence in a different letter]

What this skill does not do

  • Give legal advice or settle the privilege footing. This produces a draft for a solicitor to review, not advice the client can rely on. The footing it proposes is exactly that — a proposal. Counsel or the conducting solicitor must confirm it before the letter is sent, because mischaracterising a letter's footing has real disclosure consequences: an offer the client believed was protected can end up admissible, and open material wrongly treated as WP can frustrate the client's own case.
  • Make a labelled letter privileged that isn't substantively a settlement attempt. The label follows the substance, not the other way round.
  • Guarantee the footing holds. WP protection can fail (see the Unilever exceptions), and WPSATC costs treatment is at the court's discretion under CPR 44.2.
  • Provide costs-protection equivalent to Part 36 in the civil courts — draft a CPR Part 36 offer separately for that.
  • Cover Scottish "tenders" or NI equivalents.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Creates an Agent Authority Charter for enterprise or regulated AI agents before deployment. Use this Skill when a user needs to define what an AI agent is allowed to do, who delegated authority to it, what actions are permitted or prohibited, when human approval is required, what evidence must be preserved, and how the agent can be suspended, revoked, or escalated.

日本語の概要は準備中です。原文の説明を表示しています。

lawve-ai/awesome-legal-skills8632026年10月3日 更新

EU AI Act Knowledge Engine — authoritative regulatory Q&A grounded in 70 official EU source documents (including the 2026 Commission draft guidelines on Art. 6 high-risk classification — general principles, Annex I, Annex III). Answers any question about the AI Act with article-level citations from the full regulation text, Commission guidelines, EDPB/EDPS opinions, codes of practice, harmonised standards, FRIA guides, incident templates, and sector-specific guidance. This skill should be used when the user asks about the "EU AI Act", "AI Act regulation", "Regulation 2024/1689", "KI-Verordnung", asks to "explain an AI Act article", "what does Article X say", "AI Act requirements", "AI Act penalties", "AI Act timeline", "GPAI obligations", "high-risk AI", "prohibited AI practices", "AI Act and GDPR", "fundamental rights impact assessment", "AI Act standards", "AI Act national implementation", "AI literacy", "serious incident reporting", "Digital Omnibus", "AI regulatory sandbox", or any question about EU artificial intelligence regulation. Also triggers on German terms: "KI-Gesetz", "KI-Verordnung", "Hochrisiko-KI", "KI-Kompetenz", "Grundrechte-Folgenabschaetzung", "GPAI-Verhaltenskodex". For assessment workflows that produce a classification decision rather than a knowledge answer, offer to run a structured risk-tier classification in-session.

日本語の概要は準備中です。原文の説明を表示しています。

lawve-ai/awesome-legal-skills8632026年10月3日 更新

This skill builds a structured audit trail of an AI-assisted task: what the tool was asked to do, what materials it was given, what it produced, how the output was verified, and what was ultimately relied upon. It documents the workflow for supervision and later review without ruling on privilege or disclosure, so the record stays accurate rather than self-serving.

日本語の概要は準備中です。原文の説明を表示しています。

lawve-ai/awesome-legal-skills8632026年10月3日 更新

Use this skill when the user wants an AI governance, legal-risk, privacy, compliance, procurement, or vendor-risk review of an internal AI use case, an AI product feature, an LLM workflow, or a third-party AI vendor. The skill asks intake and clarifying questions first when facts or evidence are missing, identifies required documentation and missing evidence, maps the use case to AI governance frameworks and applicable legal domains, and produces a preliminary or final governance review with scorecards, findings, owners, remediation actions, and follow-up questions.

日本語の概要は準備中です。原文の説明を表示しています。

lawve-ai/awesome-legal-skills8632026年10月3日 更新

Turn an interpretive-ambiguity audit of a legal text — contract, statute, regulation, or judicial opinion — into a polished deliverable. Produces a multi-page website (default), a single-page interactive site, a Microsoft Word document, a PowerPoint deck, or a LaTeX/PDF. Use whenever a user has a stress-test result, ambiguity audit, or "where will this be litigated" scenarios and wants to publish, present, or share them. Triggers on "publish the audit," "make a report from this," "turn this into a website / deck / brief / Word doc," "make a Netlify site," "build slides of these ambiguities," "render the scenarios," "package this stress test," "produce a LaTeX version," and similar. Pairs with the ambiguity-stress-test skill (the underlying analysis) but works on any structured or semi-structured ambiguity analysis. Visual design is opinionated but the user can override colors, fonts, and brand label. Most formats need Python and a writable filesystem; single-file HTML works where the host has neither.

日本語の概要は準備中です。原文の説明を表示しています。

lawve-ai/awesome-legal-skills8632026年10月3日 更新

Adversarially stress-tests a legal text — a contract, statute, regulation, or judicial opinion — for interpretive ambiguity: it finds the seams where the people governed by it will later disagree about what it means and turns each into a concrete dispute scenario with both sides' arguments, the likely outcome, and a fix. Use it whenever someone wants to pressure-test, red-team, audit, or find weak spots, loopholes, gaps, ambiguities, or drafting problems in a legal document; whenever a drafter wants to tighten a contract, statute, regulation, or opinion before it issues; whenever a litigator wants to mine an opinion or contract for arguments; or whenever someone hands over a legal text and asks where it will be fought over or for issue-spotting. Trigger it for contract review, statutory-ambiguity analysis, judicial-opinion scope analysis, and drafting QA — even if the user never says "stress-test" or "ambiguity."

日本語の概要は準備中です。原文の説明を表示しています。

lawve-ai/awesome-legal-skills8632026年10月3日 更新

lawve-ai のスキルをすべて見る

このスキルの問題を報告する