Event series · Claude for LegalClaude for Legal nights.
Evening sessions for lawyers, legal ops and in-house teams across Australia. Practitioners show how they actually use Claude on reading, drafting and admin, then we work through it together, guardrails first. New dates land on the events page first.
So much legal work is reading, comparing and turning dense documents into something a client can act on. These nights are where people who've tried Claude on that work show the room what held up, what didn't, and where they draw the line.
- Private practice lawyers
- In-house and government legal teams
- Legal ops and practice support
- Law students and grads
What you'll learn.
Session topics across the series. Every one is worked through hands-on, and every output gets checked the way a lawyer would check it.
Summarising long documents
You'll learn to boil leases, agreements and reports down to what matters, with a clause reference for every point.
First-pass contract review
We walk through running a draft against your own checklist, and reading the output for what's present, missing or non-standard.
Clause comparison
You'll put two versions side by side in a table and work out which way each one leans.
Plain-English client letters
We turn real-style file notes into a clear client update, then edit it into your own voice.
Chronologies from bundles
You'll pull dates, events, people and sources into one table, with conflicts flagged rather than smoothed over.
Matter templates in Projects
We set up a Project with precedents, house style and checklists, so every draft starts the way your team works.
How a Claude for Legal night runs.
Practitioners first, then hands-on with dummy documents. Nothing confidential goes anywhere near the room.
Doors
Grab a drink, find a seat, get on the wifi.
Short talks
Two or three practitioners show what they actually do, about ten minutes each.
Hands-on
Laptops open. We work through the session prompts on real-style examples, with helpers in the room.
Q and A, show and tell
Questions, what worked, what didn't, and a few people show what they made.
- A laptop and charger
- A Claude account
- Dummy or public documents only, never client files
- A question about where the line is
Use it responsibly.
Every night starts here. Claude is not a lawyer and it can be confidently wrong, so we treat everything it produces as a first draft from a bright junior who hasn't been admitted yet.
Verify every citation and authority yourself. Never rely on a case, section or quote you haven't checked in a primary source.
Check your firm's policy before you upload anything. Client confidentiality and privilege come first. If you're not sure a document can go in, it doesn't.
Claude does not give legal advice. It can help you work through the material. The advice, and the call on what to tell a client, stays with you.
A human lawyer stays accountable. Review, edit and sign off on everything before it goes anywhere near a client, a counterparty or a court.
Nine prompts we work through on the night.
Everyone leaves with these. Swap in your own details, strip out anything identifying, and save the ones that work into a Project for your team.
Summarise the long stuff
Ask for the summary in the structure you'd write it yourself, with a clause number for every point so you can check it fast.
Summarise this lease for a busy client: parties, term, rent and reviews, outgoings, break and termination rights, and anything unusual. Quote the clause number for every point.
First-pass review against your checklist
Give it your checklist, not its own. You get a consistent first pass you can mark up.
Review this services agreement against the checklist below. For each item, say present, missing or non-standard, quote the clause, and flag what I should look at first. [PASTE CHECKLIST]
Compare clauses side by side
Tables beat paragraphs when you're comparing drafts.
Compare the limitation of liability clauses in these two drafts. Show the differences in a table and explain in plain English which version favours our client and why.
Plain-English client letters
Turn your file notes into a clear update, then edit it into your own voice.
Turn these file notes into a short letter to the client explaining where things stand and the next three steps. Plain English, warm but professional. Put anything I need to confirm in [brackets].
Chronologies from a bundle
Ask for the source of every entry so you can verify it, and for conflicts to be flagged rather than smoothed over.
From these documents, build a chronology table: date, event, who was involved, source document and page. Flag any dates that conflict between documents.
Matter templates in Projects
Set up a Project per matter type with your precedents, style guide and checklists. Every chat inside it starts from your team's way of working.
Using the precedents and style guide in this project, draft a first version of a letter of demand based on the facts below. Use our standard structure and leave blanks for amounts and dates.
Research starting points, then verify
Use Claude to map the questions and the areas to look into. Then do the actual research in proper sources.
I'm looking into [ISSUE] in [STATE]. List the key questions I need to answer and the areas of law to research. Don't cite cases. Tell me what I'll need to verify in primary sources.
Tidy up the admin
Checklists, templates and handover notes are low risk and high reward. Start there if your team is new to it.
Draft a file closing checklist and a matter handover note template for our team, based on the steps I've listed below. [PASTE STEPS]
Walk into the meeting prepared
Give it your notes and the agenda. You get the questions to ask and the documents to chase, on one page.
Here are my notes on this matter and the agenda for tomorrow's client meeting. List the questions I should ask, the documents I need from the client and the risks to raise. Keep it to one page.
Questions people ask.
Is it safe to put client documents into Claude?
That depends on your firm's policy, your client's instructions and the plan you're using. Check all three first. If in doubt, strip out identifying details or leave it out.
Can it replace legal research tools?
No. It's useful for working out what to look for and for summarising what you've found. Authorities still need to come from, and be checked against, proper sources.
Where should a legal team start?
Low-risk, high-volume work: summaries of documents you've already read, internal checklists, templates and plain-English drafts that a lawyer reviews.
The next Claude for Legal night is being locked in. Register interest and we'll tell you the date, venue and speakers the day they're confirmed.
Speak at a Claude for Legal night.
Come and share what's working, and what isn't. The room learns as much from the guardrails as from the wins.