Client Communication and Plain Language

Translate this legal concept into plain language:

LEGAL CONCEPT: [The concept or term]
CONTEXT: [How it applies to this client's situation]
AUDIENCE: [Business executive / Individual / Non-legal professional]
ACCURACY REQUIREMENT: Must remain legally precise

Provide:
1. Plain language explanation (2-3 sentences)
2. A concrete analogy or example
3. Why it matters for the client specifically
4. Any important caveats or nuances that must be preserved

Translate this legal document into a client-friendly summary:

DOCUMENT: [Paste legal document or section]
CLIENT: [Anonymized description—business or individual]
PURPOSE: [Why the client needs to understand this]

Create a summary that:
1. Explains what the document does in plain language
2. Highlights the key rights and obligations
3. Flags anything the client should be concerned about
4. Identifies decisions the client needs to make
5. Uses concrete language, not legal abstractions

Preserve all legal accuracy. If something can't be
simplified without losing precision, explain the concept
rather than oversimplifying it.

Draft a client status update:

MATTER: [Anonymized description]
RECIPIENT: [Client contact and their role]
KEY UPDATE: [What happened or changed]
IMPACT: [What it means for the client]
NEXT STEPS: [What happens next and any client action needed]
TIMELINE: [Expected dates/milestones]

Structure as:
1. Bottom line (the key update in 1-2 sentences)
2. Context (brief background for this update)
3. What this means for you (client impact)
4. Next steps (what we're doing and what you need to do)
5. Timeline (when to expect the next development)

Tone: clear, confident, professional.
Avoid legal jargon unless defined in context.

Draft a client advisory letter presenting options:

SITUATION: [Brief description of the legal issue]
CLIENT: [Anonymized description]

OPTIONS:
Option A: [Description, pros, cons, estimated cost/risk]
Option B: [Description, pros, cons, estimated cost/risk]
Option C: [Description, pros, cons, estimated cost/risk]

RECOMMENDATION: [Which option you recommend and why]

Structure as:
1. The situation (2-3 sentences in plain language)
2. Your options (presented clearly with pros and cons)
3. Our recommendation (with reasoning)
4. What we need from you (decision and any information)
5. Timeline (when a decision is needed)

Include a clear comparison format (table or structured list)
so the client can evaluate options at a glance.

Draft a client letter about legal risks:

MATTER: [Description]
RISKS IDENTIFIED:
- Risk 1: [Description, likelihood, potential impact]
- Risk 2: [Description, likelihood, potential impact]
- Risk 3: [Description, likelihood, potential impact]

MITIGATION STRATEGIES:
- For Risk 1: [What can be done]
- For Risk 2: [What can be done]
- For Risk 3: [What can be done]

Explain risks in concrete terms the client understands.
Avoid legal probability language ("may," "could potentially")
where you can be more definitive.
Use a risk matrix or visual format if appropriate.

Draft a client letter about an unfavorable development:

DEVELOPMENT: [What happened]
IMPACT ON CLIENT: [How it affects their matter]
WHY IT HAPPENED: [Brief explanation]
WHAT WE'RE DOING: [Our response/strategy]
OPTIONS GOING FORWARD: [Client's choices]

Tone: honest, empathetic, forward-looking.
Don't sugarcoat the news, but focus on the path forward.
Acknowledge the disappointment while maintaining confidence.

Draft an engagement letter:

FIRM: [Your firm]
CLIENT: [Anonymized]
SCOPE: [What you're being retained to do]
FEES: [Fee structure—hourly, flat, contingency]
EXCLUSIONS: [What's NOT included in the scope]
TIMELINE: [Expected duration]

The letter should:
- Clearly define scope (so the client knows exactly
  what they're getting)
- Explain the fee structure in plain language
- Set realistic expectations about timeline
- Describe communication protocols
  (how often you'll update, preferred contact method)
- Include clear termination provisions

Draft a timeline communication for a client:

MATTER TYPE: [Type of legal matter]
CURRENT STAGE: [Where we are now]
ESTIMATED MILESTONES:
- Milestone 1: [Description, estimated date]
- Milestone 2: [Description, estimated date]
- Milestone 3: [Description, estimated date]
VARIABLES: [What could speed up or slow down the timeline]

Present this as a realistic roadmap, not a guaranteed schedule.
Include appropriate caveats about factors outside our control
(court schedules, opposing party, regulatory review).

Draft a response to a client who disagrees with my recommendation:

CLIENT'S POSITION: [What they want to do]
MY RECOMMENDATION: [What I've advised]
REASON FOR DISAGREEMENT: [Why they don't want to follow advice]
RISKS OF THEIR PREFERRED APPROACH: [What could go wrong]

The response should:
1. Acknowledge their perspective respectfully
2. Reiterate the risks clearly and specifically
3. Explain why my recommendation serves their interests
4. If they insist, document the advice given and their decision
5. Confirm you'll support their decision while on record
   with your professional opinion

Draft a communication about fees exceeding the initial estimate:

ORIGINAL ESTIMATE: [Amount or range]
CURRENT FEES: [Amount]
REASON FOR INCREASE: [What changed—scope, complexity, opposition]
PROJECTED ADDITIONAL FEES: [What's left]
OPTIONS TO MANAGE COSTS: [If any]

Be direct and transparent. Explain specifically what
caused the increase. Don't be defensive—just factual.
If possible, offer options to reduce costs going forward.

CLIENT COMMUNICATION LIBRARY
├── Updates
│   ├── Status update (routine)
│   ├── Milestone reached
│   ├── Unfavorable development
│   └── Matter concluded
├── Advisory
│   ├── Options letter
│   ├── Risk assessment
│   ├── Compliance advisory
│   └── Strategic recommendation
├── Administrative
│   ├── Engagement letter
│   ├── Fee estimate
│   ├── Timeline update
│   └── Scope change notice
└── Difficult Conversations
    ├── Bad news delivery
    ├── Cost overrun explanation
    ├── Disagreement with client's approach
    └── Matter complexity increase