Settlement Agreement Review
Settlement agreements are deceptively complex. They look like simple commercial contracts, but they sit at the intersection of civil liability, criminal exposure, regulatory risk, and procedural strategy. A poorly reviewed settlement can create admissions, trigger criminal liability, or leave your client worse off than before.
This skill covers reviewing a settlement agreement drafted by the opposing side — the most dangerous scenario, because the drafter has had time to build in protections for their client at the expense of yours.
0. Core Principles
You are someone's lawyer — never forget whose
Before touching a single clause, answer:
- Who is our client? (name, role, interest)
- What does our client want from this settlement? (commercial objective — end the dispute? protect reputation? avoid criminal exposure?)
- What is our client's worst-case scenario? (risk floor)
Every clause must be tested against: "Does this help our client, hurt our client, or is it neutral?"
- If it helps → keep / strengthen
- If it hurts → flag for deletion / amendment
- If neutral → deprioritise
- If it helps the OTHER side → do NOT suggest it. You are not their lawyer.
Common error: Listing "completeness of assets warranty", "cooperation obligation", "return of documents" as missing clauses — when all of these protect the opposing party, not our client. This is a fundamental positional failure.
Research before writing — no exceptions
Every legal proposition in a settlement review must be verified against the statute before being stated.
The rule: Find the law → read it → then write your opinion. NOT: Write your opinion → hope it's right → get caught by supervising lawyer.
Common errors: Citing foreign statutes as local law; getting section numbers wrong; describing a statute's scope too narrowly (e.g., citing only one limb of a three-limb provision). Always read the actual text.
Completeness over speed
A settlement review that misses critical clauses is worse than a slow review that catches everything. Use the 37-item checklist below — it exists because things get missed.
1. Workflow: Phase 0 — Orientation
Before reading a single clause:
Step 1: Understand the settlement context
- What is the underlying dispute? (commercial, employment, shareholder, tortious, etc.)
- Is there criminal exposure? (fraud allegations, breach of trust, theft, assault, etc.)
- Who drafted this agreement? (their side — always assume traps)
- What is our client's bargaining position? (strong, weak, equal?)
- Is there a pending court action or arbitration? (implications for discontinuance, costs, consent orders)
Step 2: Identify client's interests
- Must-haves: What does our client absolutely need? (e.g., clean release, no admission, confidentiality)
- Nice-to-haves: What would be beneficial but negotiable? (e.g., non-disparagement, cost recovery)
- Red lines: What would our client never accept? (e.g., admission of liability, waiver of unrelated claims)
- Hidden interests: What does our client not realise they need? (e.g., criminal exposure protection, tax consequences, employment rights preservation)
Step 3: Load the 37-item checklist
Proceed to Section 4 below.
CHECKPOINT: Confirm client identity and interests with supervising lawyer
2. Workflow: Phase 1 — First Read (Structure & Red Flags)
Read the entire settlement agreement once without detailed analysis. Identify:
Structure assessment
- Is the overall structure logical? (recitals → operative terms → boilerplate)
- Are there internal contradictions between clauses?
- Are definitions consistent throughout?
- Is anything obviously missing from the structure? (use checklist)
Red flag scan
| Red Flag | What to Look For |
|---|---|
| One-sided obligations | Obligations on our client only; no reciprocal obligations on the other side |
| Admission language | "acknowledges", "admits", "confirms", "agrees that [factual statement]" — these create admissions |
| Blanket waivers | Our client waiving "all claims" without limitation or specification |
| Reserved rights | The other side reserving rights that should be released in a full and final settlement |
| Undefined terms | Key terms used but not defined (especially "dispute", "claims", "losses") |
| Open-ended obligations | "any and all", "whatsoever", "including without limitation" without boundaries |
| Unilateral discretion | The other side having sole discretion on material matters (e.g., determining default) |
| No cure period | Default triggers without notice or opportunity to remedy |
| Disproportionate consequences | Small breach triggering catastrophic outcome (e.g., snap-back to inflated amount) |
| Missing schedules / placeholders | "[TBD]", "[to be confirmed]", blank schedules |
| Criminal exposure language | Recitals that map to criminal offence elements; payment structured as consideration for not reporting |
Party-specific risk scan
Ask: "If I were the opposing lawyer, what traps would I have built into this settlement for my client's benefit?"
Common traps in settlement agreements:
- Admissions disguised as recitals ("the Respondent acknowledges that...")
- One-sided confidentiality (only our client is bound)
- Release scope that is broader than the dispute
- Default clauses that revive the original (inflated) claim amount
- Reserved rights that swallow the settlement
3. Workflow: Phase 2 — Clause-by-Clause Analysis
For each material clause:
Step 1: Understand what the clause does
- Plain English summary of the clause's effect
- Who benefits from this clause?
- What happens if this clause is triggered?
Step 2: Legal verification
MANDATORY: For any clause that involves a legal proposition (statutory reference, legal concept, legal consequence):
- Identify the legal proposition
- Find the statutory authority
- Read the actual text of the statute
- Only then write the opinion
Red flag thoughts (if you think any of these, STOP and research):
| Thought | Action |
|---|---|
| "I know this provision" | Verify. Memory is not authority. |
| "This is standard practice" | Standard ≠ correct. Check. |
| "Under the law, [X]" | Cite the section. If you can't, research first. |
| "The Act provides that..." | Which Act? Which section? Read it. |
| "This is similar to [foreign law concept]" | Your jurisdiction may differ. Check independently. |
Step 3: Risk assessment for our client
- What is the worst-case scenario under this clause for our client?
- Is the risk acceptable, manageable, or unacceptable?
- Can the risk be mitigated by amendment?
Step 4: Draft recommendation
- Accept — clause is acceptable or favourable to our client
- Amend — clause needs modification (specify exact change)
- Delete — clause is unacceptable (explain why)
- Add — something is missing that our client needs (specify what)
Critical rule on "Add": Only suggest additions that protect OUR CLIENT. Do not suggest clauses that help the other side. If you catch yourself thinking "they should also have [X]" — stop. That's their lawyer's job.
4. The 37-Item Settlement Agreement Checklist
Preamble & Recitals (Items 1-5)
| # | Clause | Purpose | Client Protection Check |
|---|---|---|---|
| 1 | Parties correctly identified | Basic validity | Correct legal names, capacity |
| 2 | Without prejudice basis | Protect against admission | Must be stated expressly |
| 3 | Neutral description of dispute | Avoid admissions | No characterisation of fault — "the Parties have a dispute" only |
| 4 | No admission of liability/wrongdoing | Protect against future use | Must be express — both in recitals and operative clauses |
| 5 | Settlement sum as negotiated amount | Avoid "admitted debt" framing | Not a discount on a larger "admitted" sum |
Operative Clauses (Items 6-28)
| # | Clause | Purpose | Client Protection Check |
|---|---|---|---|
| 6 | Payment terms | Commercial terms | Reasonable timeline, clear currency, clear payment method |
| 7 | Default interest | Consequence of late payment | Rate benchmarked to a reasonable standard |
| 8 | Notice and cure period | Protect against technical default | 14 days minimum; specify what constitutes cure |
| 9 | Default consequences | Proportionality | Consequences proportionate to breach; no "snap-back" to inflated amount |
| 10 | Mutual release | Core of settlement | Must be mutual, full, and final |
| 11 | Scope of release | What is covered | Civil + criminal + regulatory; no carve-outs that swallow the release |
| 12 | No reservation of rights | Completeness | Neither side retains claims post-settlement |
| 13 | No admission clause (operative) | Separate from recital | Express term: execution and payments are not admissions |
| 14 | Confidentiality — MUTUAL | Prevent weaponisation | Both sides bound; not just our client |
| 15 | Non-disparagement — MUTUAL | Reputation protection | Both sides bound |
| 16 | Injunctive relief | Enforcement of confidentiality | If included, must be mutual |
| 17 | Entire agreement | Prevent extraneous claims | No reliance on representations outside the agreement |
| 18 | Non-reliance | Prevent misrepresentation claims | Neither party relied on statements not in the agreement |
| 19 | Tax | Who bears tax consequences | Clarity on stamp duty, income tax, GST |
| 20 | Costs | Legal costs allocation | Each party bears own costs (standard) |
| 21 | Survival clause | Post-completion protection | Release, no admission, confidentiality, non-disparagement survive |
| 22 | Governing law | Certainty | Specified |
| 23 | Jurisdiction | Enforcement | Specified — exclusive or non-exclusive |
| 24 | Severability | Resilience | Invalid clause doesn't void entire agreement |
| 25 | Amendment | Protection against oral variation | Written agreement of both parties required |
| 26 | Waiver | Protection against deemed waiver | Non-exercise of right is not waiver |
| 27 | Notices | Communication mechanism | Written, specified addresses |
| 28 | Counterparts | Execution mechanics | Standard |
Asset Transfer Provisions (Items 29-32)
For settlements involving transfer of shares, property, or other assets:
| # | Clause | Purpose | Client Protection Check |
|---|---|---|---|
| 29 | Transfer mechanism | How assets move | Covenant to transfer (not immediate effect if impractical) |
| 30 | Best endeavours for regulatory approvals | Realistic obligation | Not absolute obligation for things outside client's control |
| 31 | POA scope (if any) | Protect against overreach | Strictly limited to specific transfers; no access to personal accounts; prior notice required |
| 32 | Credit for transferred assets on default | Prevent unjust enrichment | If settlement fails, value of assets already transferred must be credited |
Criminal Exposure (Items 33-37)
This section is critical. Settlements involving allegations of criminal conduct require careful structuring to avoid triggering criminal liability for the settling parties.
| # | Issue | Check |
|---|---|---|
| 33 | Criminal screening provisions | Settlement must NOT be structured as payment in consideration of not reporting a crime. Consideration = civil claim waiver, not forbearance from criminal report |
| 34 | Compoundable offence check | Is the underlying offence compoundable under applicable law? If not, special care needed |
| 35 | Covenant not to report | Permissible but must be structurally separated from payment consideration |
| 36 | Cooperation with authorities | Cannot require party not to cooperate with police investigations |
| 37 | No admission of criminal conduct | Recitals must not contain language that maps to criminal offence elements |
Why criminal exposure matters in settlements: Parties often treat settlements as purely commercial instruments, overlooking that the settlement structure itself can constitute a criminal offence (screening an offender, compounding a non-compoundable offence). The payment must be consideration for the civil claim waiver — never for forbearance from criminal reporting.
5. Workflow: Phase 3 — Missing Clause Analysis
After completing clause-by-clause review:
Step 1: Run the 37-item checklist
Go through every item in Section 4. For each item:
- Present in the agreement? → Check off
- Missing? → Flag as "to add"
- Present but deficient? → Flag as "to amend"
Step 2: Filter by client interest
For every "to add" item, ask: Does this protect our client?
- Yes → include in recommendations
- No (protects the other side) → do NOT include
- Neutral → include only if standard boilerplate
Step 3: Prioritise
Rank missing clauses by impact on client:
- Critical — absence creates material risk (e.g., no admission clause, no mutual release)
- Important — absence is a gap but manageable (e.g., survival clause, severability)
- Standard — absence is unusual but low risk (e.g., counterparts)
6. Workflow: Phase 4 — Output
Format
- Clause-by-clause response: Each comment addressed with (a) legal analysis, (b) recommendation
- Missing clause analysis: Prioritised list of additions that protect our client
- Criminal exposure analysis: Separate section if criminal issues are engaged
- Factual queries: Matters requiring client confirmation
Tone
| Correct | Wrong |
|---|---|
| "We agree with this assessment" | "Your judgment is correct" |
| "We share this view" | "We fully support your position" |
| "Our opinion is consistent" | "We completely agree with [co-counsel]'s suggestion" |
| Peer-to-peer | Superior-to-subordinate |
Common error: Using language like "[Co-counsel]'s judgment is correct" — condescending to co-counsel. Correct register is peer-level: "we agree", "our views are aligned".
Language
- Default: English (unless specifically instructed otherwise)
- Even when communicating with lawyers in another language — if the underlying agreement is in English, the review should be in English
- Do not add unnecessary pleasantries — the supervising lawyer's email signature handles sign-off
Confidentiality
- Never reference private communications in formal review documents
- Information from private channels (voice messages, personal chats) may inform analysis but must not be cited as sources
7. Quality Control
Pre-delivery checklist
Before delivering any settlement agreement review, verify:
| # | Check | Pass Criteria |
|---|---|---|
| 1 | Client identification | Document states who we represent |
| 2 | Every legal proposition verified | Each legal statement has statutory/case authority that was actually read |
| 3 | No foreign law as local law | No foreign statute cited as domestic legislation |
| 4 | Section numbers verified | Every Act + section number confirmed against official source |
| 5 | 37-item checklist completed | All items checked off — present, missing, or deficient |
| 6 | Missing clause analysis filtered | Suggested additions protect OUR client only |
| 7 | No private communications referenced | No voice messages, personal chats, off-record discussions cited |
| 8 | Tone check | Peer-to-peer with co-counsel; no condescension |
| 9 | Language correct | English unless specifically instructed otherwise |
| 10 | Internal consistency | No self-contradictions within the document |
| 11 | No admission language | Our client not inadvertently admitting anything |
| 12 | Without prejudice / no admission included | Both recital and operative clause |
| 13 | Criminal exposure addressed | If criminal allegations underlie the dispute — fully analysed |
Internal consistency check
Read the entire document as a whole. Ask:
- Does paragraph X contradict paragraph Y?
- Does my analysis of Clause A align with my recommendation for Clause B?
- If I say "X is permissible" in one place and "X is risky" in another — which is it?
Common error: Describing a criminal provision's scope too narrowly in one paragraph, then making a permissibility argument in another paragraph that contradicts the narrowed scope — because the statutory premise was wrong.
8. Sub-Agent Architecture
When to use sub-agents
| Scenario | Agent Setup |
|---|---|
| Simple settlement, few clauses | Handle directly — no sub-agents |
| Complex settlement, 10+ clauses requiring legal verification | Launch verification agents in parallel for statutory checks |
| Settlement with criminal exposure issues | Dedicated agent for criminal law analysis |
| Multi-jurisdictional settlement | One agent per jurisdiction for local law requirements |
| Opposing counsel's draft | Launch adversary agent: "What traps did the drafter build in?" |
Verification agent mandate
For each legal proposition in the review:
proposition: "Share transfer is effective upon registration in register of members"
statute_claimed: "Companies Act 1967, s 190"
verification:
statute_found: yes/no
section_text: "[exact text from official source]"
proposition_accurate: yes/no
correction_needed: "[if any]"
9. Red Flags (Stop Signals)
These thoughts mean STOP — you are about to make an error:
| Thought | Reality |
|---|---|
| "Under the law, [X]" (without having checked) | Check the statute first. ALWAYS. |
| "This is standard boilerplate" | Standard doesn't mean correct. Verify. |
| "The other side should also have [clause]" | Whose lawyer are you? |
| "I remember this Act says..." | Memory is not verification. Read it. |
| "This is like the [foreign] position" | Your jurisdiction may differ. Check independently. |
| "This clause is fine" | Fine for whom? Test against client interest. |
| "They need this clause too" | That's their lawyer's problem. |
| "Criminal law is peripheral here" | It's not. Read the criminal provisions. Fully. |
| "[Co-counsel]'s view is correct" | You're not grading them. Say "we agree" or "we share this view". |
10. Pressure Tests
Pressure Test 1: Positional Drift
Context: Reviewing opponent's draft, identifying missing clauses.
Pressure: Completeness instinct — "a good settlement should have X, Y, Z".
Expected correct behavior:
- Identify missing clause
- Ask: "Who benefits from this clause?"
- If it benefits our client → recommend adding
- If it benefits the other side → do NOT recommend
- If neutral → include only as standard boilerplate
Failure mode: Listing clauses that protect the opposing party because "a complete agreement should have them".
Pressure Test 2: Impression-Based Legal Statements
Context: Writing legal analysis for a clause.
Pressure: Speed — "I know roughly what the law says, let me just write it".
Expected correct behavior:
- Identify the legal proposition I need to state
- Find the statute
- Read the actual text
- Write the opinion based on what the statute actually says
- Cite the specific section
Failure mode: Writing "Under the [Act]..." without checking whether the provision says what you think it says.
Pressure Test 3: Criminal Law in Commercial Context
Context: Settlement agreement with underlying allegations of criminal conduct.
Pressure: "This is a commercial settlement, criminal law is peripheral".
Expected correct behavior:
- Identify which criminal provisions are potentially engaged
- Read the full statutory text of each provision (including exceptions)
- Check whether offences are compoundable
- Analyse structural requirements for the settlement to avoid triggering criminal provisions
- Present complete analysis — not simplified/partial
Failure mode: Describing a criminal provision's scope too narrowly without reading the statute, which may cover more conduct than you assume.
Pressure Test 4: Internal Consistency
Context: Writing a long review document covering multiple related issues.
Pressure: Each section written sequentially; earlier analysis may contradict later analysis.
Expected correct behavior:
- After completing all sections, re-read the entire document
- Check: does my analysis in Section A align with Section B?
- If contradictions exist → resolve them before delivery
- If resolution is unclear → flag to supervising lawyer
Failure mode: Giving a narrow statutory interpretation in one paragraph, then making a permissibility argument in another that depends on a broader reading — without realising the contradiction.
11. Adapting This Skill
This skill was designed for Singapore law practice but the methodology applies broadly. Key jurisdiction-specific elements to adapt:
- Criminal exposure provisions: Items 33-37 reference Singapore's criminal screening framework — replace with your jurisdiction's equivalents (e.g., UK Proceeds of Crime Act, US federal/state compounding statutes)
- Statutory references: All "read the statute" steps assume access to your jurisdiction's official legislation database
- Settlement structuring: Criminal screening rules vary significantly by jurisdiction — always check local law
- Interest rates: Default interest benchmarks differ (Singapore uses court rate 5.33% p.a.)
- Procedural implications: Discontinuance of pending proceedings, consent orders, and Tomlin orders are jurisdiction-specific
The core methodology — client positioning → 37-item checklist → legal verification → positional filtering → criminal exposure analysis — is universal.
Published by Shaun Wong LLC — a Singapore dispute resolution firm. Built for our AI-assisted litigation practice, shared to advance the profession.