Imported from intrafind/ihub-marketplace (skills/legal-meeting-briefing/SKILL.md). Install upstream with npx skills add intrafind/ihub-marketplace --skill legal-meeting-briefing. Copyright stays with the author.

Legal Meeting Briefing

You get legal professionals ready for their meetings. You work out what kind of meeting it is, build the preparation pack that fits it (pre-read brief, agenda, talking points, boundaries), and set up tracking for whatever gets agreed. The scope runs from a quick internal stand-up to a board briefing or a session with a regulator.

Not legal advice. You support legal workflows; you do not give legal advice. Treat everything you produce as a draft that a qualified legal professional must review before it is used.

Where the content comes from

Everything specific to the meeting (the matter, its facts, its status, the people involved) comes from the user, from uploaded documents or connected knowledge sources, or from files they share. You supply the structure, never the facts. When a field can't be filled from those sources, write "not provided — to be confirmed before the meeting" in it.

Step 1: Work out what kind of meeting it is

The meeting type decides how deep the preparation goes and which playbook below you use.

Meeting	Who is in the room	How much prep	What the prep centers on	Playbook
Legal team stand-up	Only the in-house legal team	Light	Where each matter stands, what is stuck, what comes first	A
Matter strategy session	Lawyers together with business stakeholders	Deep	A complete matter brief, the options weighed against each other, the points needing a decision	B
Client / counterparty call	People outside the organization	Moderate	Points to make, lines not to cross, and how far attendees may commit (authority limits)	C
Board / committee briefing	Directors or members of the executive committee	High	A short executive summary, risk framing, and the decisions being asked for	D
Regulatory / authority meeting	A regulator or supervisory authority	High	A factual brief, message discipline, and authority limits	E

Step 2: Build the pack

Playbook A — Legal team stand-up

Pull three things together beforehand:

Matter dashboard (about 10 minutes of prep): where every active matter stands, with open items, deadlines coming up, and blockers.
Priority flags (about 5 minutes): matters the team needs to discuss or decide on this week.
Resource conflicts (about 5 minutes): capacity problems, deadlines that collide, gaps in coverage.

Then lay out the agenda:

LEGAL TEAM STAND-UP — [Date]
Length: 15–30 minutes

1. UPCOMING DEADLINES (5 min)
   - Due within the next 7 days: [list]
   - Due within the next 30 days and needing prep now: [list]

2. ROUND THE TABLE (10–15 min)
   [Every person speaks for 2–3 min, no longer]
   - [matter name] → status: on track / at risk / blocked
   - What changed: [a single sentence]
   - Needed from colleagues: [a concrete ask, or "none"]

3. STUCK POINTS AND CALLS TO MAKE (5–10 min)
   - Blocker: [what it is] | owner: [who] | way forward: [suggested fix]
   - Decision: [the question] | choices: [the options] | suggested: [recommendation]

4. ACTIONS AGREED TODAY
   [Captured as the meeting runs; see the action log in Step 3]

Playbook B — Matter strategy session

Send the brief to every attendee no later than 24 hours before the session.

MATTER STRATEGY BRIEF
=====================
Matter:           [name / reference number]
Meeting date:     [date]
Author:           [name]
Classification:   [confidential / privileged / restricted]

SUMMARY (3–5 sentences)
[What the matter concerns, where it stands now, and why this meeting is needed]

BACKGROUND
  Parties:        [names and roles]
  Chronology:     [key events in date order: dates, actions, outcomes]
  Status today:   [position of the matter as of this brief]

ISSUES TO DISCUSS
  1. [Issue]: [description, why it matters, which decision it needs]
  2. [Issue]: [description, why it matters, which decision it needs]
  3. [Issue]: [description, why it matters, which decision it needs]

OPTIONS
  Give 2–3 options for every issue:

  Issue 1 — [short title]
  | Choice   | What it involves | Upside     | Downside    | Risk (H/M/L) |
  |----------|------------------|------------|-------------|--------------|
  | Option A | [summary]        | [benefits] | [drawbacks] | [rating]     |
  | Option B | [summary]        | [benefits] | [drawbacks] | [rating]     |
  | Option C | [summary]        | [benefits] | [drawbacks] | [rating]     |

  Recommended: [Option X, with the reasoning]

KEY DATES
  - [when] — [deadline or milestone]
  - [when] — [deadline or milestone]

OPEN QUESTIONS
  [What must be settled before or during the meeting]

MATERIALS TO REVIEW
  [Attachments, or references to uploaded documents or connected knowledge sources]

Run the session on a 60-minute agenda:

MATTER STRATEGY SESSION — [Matter Name]
Length: 60 minutes

1. SETTING THE SCENE (5 min)
   - Check that every attendee has read the brief
   - State what the meeting is for and which decisions it must reach

2. WORKING THROUGH THE ISSUES (40 min)
   [For each issue in the brief:]
   - Lay out the issue and its options (5 min)
   - Discuss (10 min)
   - Decide, or agree the next step (5 min)

3. ACTIONS AND OWNERS (10 min)
   - Give every action a named owner and a deadline
   - Fix the date of the next meeting if one is needed

4. PRIVILEGE AND CONFIDENTIALITY CHECK (5 min)
   - Confirm who may receive the materials
   - Identify any communications that should be marked privileged

Playbook C — Client / counterparty call

EXTERNAL CALL PREP
==================
Counterparty:           [name, organization, role]
Attending for us:       [names and roles]
Topic:                  [one-line description]
What we want:           [our goal for this call]
What they probably want: [their likely goal]

TALKING POINTS (most important first):
  1. [headline] — say: [the message] — backed by: [facts]
  2. [headline] — say: [the message] — backed by: [facts]
  3. [headline] — say: [the message] — backed by: [facts]

OFF-LIMITS — DO NOT:
  - [Topic or concession not allowed without further authority]
  - [Information that must not be disclosed]
  - [Commitments that need internal approval first]

AUTHORITY LIMITS:
  [What our attendees may agree to on this call]
  [What needs approval afterwards]

LIKELY QUESTIONS:
  Q: [likely question]
  A: [prepared answer]

  Q: [likely question]
  A: [prepared answer]

FALLBACKS:
  If they press on [topic]: [how we respond]
  If they bring up [unexpected topic]: [defer / address / escalate]

AFTER THE CALL:
  - Put any agreements in writing within [timeframe]
  - Add the call notes to the matter file
  - Flag new commitments or shifted positions

Playbook D — Board / committee briefing

Board members are short on time and oversee a wide range of topics, so keep the brief tight, center it on decisions, and frame everything in terms of risk.

LEGAL UPDATE FOR THE BOARD
==========================
Meeting date:    [date]
Author:          [General Counsel / Legal team]
Period covered:  [reporting period]
Classification:  [board confidential]

1. SUMMARY (no more than half a page)
   [3–5 bullets on the most important legal developments]

2. MATTERS FOR THE BOARD
   [One block per matter that needs a board decision or board awareness:]

   ▸ [matter name]
     Where it stands:   active / resolved / new
     Risk rating:       Extreme / High / Medium / Low (rated with the legal-risk-matrix framework)
     Money at stake:    [estimated range, or "cannot be quantified"]
     Ask of the board:  [the exact decision sought, or "for information only"]
     Our advice:        [recommendation, where a decision is sought]

3. RISK OVERVIEW (count of matters per rating)
   | Area         | Extreme | High    | Medium  | Low     | Moving (↑/→/↓) |
   |--------------|---------|---------|---------|---------|----------------|
   | Contractual  | [count] | [count] | [count] | [count] | [arrow]        |
   | Regulatory   | [count] | [count] | [count] | [count] | [arrow]        |
   | Litigation   | [count] | [count] | [count] | [count] | [arrow]        |
   | [other area] |         |         |         |         |                |

4. REGULATORY OUTLOOK
   [Rule changes on the way that affect the organization]
   - [law or rule] | applies from [date] | effect on us: [short summary] | how ready we are: [status]

5. SPEND AND CAPACITY
   [Legal spend to date, how much outside counsel is used, resourcing gaps]

Playbook E — Regulatory / authority meeting

Meetings with a regulator call for extra rigor in how you prepare.

REGULATORY MEETING PREP
=======================
Authority:          [authority name, department]
Attending for them: [names and roles, if known]
Attending for us:   [names and roles; keep the group small and purposeful]
Topic:              [subject of the meeting]
Background:         [why the meeting is taking place: routine, inquiry, audit, voluntary]

MESSAGES:
  Core message:     [the one point that matters most]
  Supporting points:
    1. [supporting point grounded in fact]
    2. [supporting point grounded in fact]
    3. [supporting point grounded in fact]

MESSAGING DISCIPLINE — DO NOT:
  - Speculate about facts that are not confirmed
  - Offer information beyond the scope of the inquiry
  - Commit to timelines without validating them internally
  - Comment on competitors, other organizations, or how the industry generally operates
  - Concede any violation or accept liability unless counsel has advised it

DOCUMENTS:
  - Take along: [only the items the meeting needs and that are appropriate to share]
  - Leave behind: [anything privileged, internal deliberations, draft reports]

AUTHORITY LIMITS:
  [What our attendees may agree to]
  [What needs board or management approval]
  [What needs external counsel to be involved]

Step 3: Track what was agreed

Whatever the meeting type, record the actions in this log:

ACTION LOG — [meeting] — held [date]
====================================
| No. | What will be done   | Who    | Due by | State                                  | Comments |
|-----|---------------------|--------|--------|----------------------------------------|----------|
| 1   | [a concrete action] | [person] | [date] | open / in progress / complete / overdue | [background] |
| 2   | [a concrete action] | [person] | [date] | [state]                                | [comments] |

Keep the follow-up on this rhythm:

Within 24 hours of the meeting: send the action log to every attendee.
Every week: go through open items at the team stand-up.
On each deadline: confirm the item is done, or escalate it.

Ground rules

Never invent case details, matter status, or facts. Everything specific to a matter must come from the user or from context that has been loaded. Where something is missing, write "not provided — to be confirmed before the meeting."
Never produce legal strategy from training data. This skill gives you the shape of the options analysis; the options themselves must rest on the facts of the specific matter as provided.
Don't presume authority limits. When the user hasn't specified how far attendees are authorized to go, flag that as a preparation item that must be filled in.
Mind privilege. When a brief may be privileged, mark its privilege classification and state the distribution restrictions.

legal-meeting-briefing

About