Regulatory and compliance · Partner, practice-group head, knowledge lead
The weekly partner digest
Most firms' regulatory awareness runs on one partner who reads more than everyone else and forwards what looks important. The digest replaces the forwarded email with a scheduled summary, scoped to the firm's own watches and linked to the matters it touches.
- Agents
- First draft
- The digest is composed from the register on the watch's own schedule; a client update can be dispatched from a linked row in a few minutes.
- Steps
- 5
The problem
Step 01 of 05
Read the top of the digest
Developments that cleared the materiality threshold, in band order, each with the source, the deadline where one exists, and the owner.
Step 02 of 05
Assign the unassigned one
A development with no owner is assigned from the register, which is itself an audit row.
Step 03 of 05
Act on the one with linked matters
A high-materiality development linked to two live matters carries one action: draft a client update.
Step 04 of 05
Sign off and send
The drafted update is read, the action items ticked, Verify all clicked, and the letter shared with a passcode link.
Step 05 of 05
Triage the rest
Lower-materiality items are flagged on the matters they touch or left in the register, which is where low-materiality items belong.
What comes back
A document, not a transcript.
- A weekly list of developments that cleared the materiality threshold, each with a source, a deadline where relevant, and an owner.
- The matters each development touches, identified by matching practice area, jurisdiction or counterparties.
- A client update drafted from a linked development in one action, with its own authorities and verdicts.
- An exportable register covering the week for a practice-group meeting or the month for a risk committee.
What it does not do
- Delivery of the digest by email depends on the firm's own sending domain being verified; the same content is always readable in the register.
- It does not assign owners automatically; an unassigned development stays unassigned until a partner sets one.
- It does not send a client update without sign-off; the partner ticks the action items and clicks Verify all first.