What is the difference between a Claude Project and a normal chat?

A normal chat starts with no memory of your firm. A Project wraps your chats in saved custom instructions and knowledge files, so every chat you start inside it already knows your identity, jurisdiction, voice, and rules — you stop re-explaining the basics every time.

Is it safe to put my templates and standard positions into a Project?

Yes, as long as they are anonymized firm materials — clean templates, checklists, and clause banks with client names and matter numbers removed. The line to watch is privileged client specifics: keep those out of any shared firm-template Project and use a separate, access-controlled Project for confidential matter work.

Do I still have to check Claude's citations and facts if my Project tells it to flag them?

Absolutely. The unverified-citation rule is a safety net that reminds you what to check; it does not do the checking. You remain responsible for verifying every citation, fact, and legal conclusion before anything leaves your office.

Daily WorkflowBeginner15–30 min (one-time setup)

Set Up a Reusable Claude Project for Your Practice

Build a reusable Claude Project loaded with your firm's voice, templates, and default rules so every matter starts pre-configured instead of from a blank chat.

Solo PracticeLaw Firm Operations

When to use this

Most lawyers re-explain who they are, their jurisdiction, and their drafting style at the start of every Claude chat, which wastes time and produces inconsistent output. A Claude Project lets you save those custom instructions plus anonymized templates and checklists once, so every new chat in that Project already knows your context. This is the force-multiplier that makes every other workflow on this site faster and more consistent.

If you use Claude for more than the occasional one-off question, you have probably noticed how much time you spend re-establishing context. Every fresh chat starts cold: you re-explain that you are a solo employment lawyer in Ohio, that you want a measured tone, that you never want invented facts. A Claude Project fixes that by saving your custom instructions and knowledge files in one place that every chat in the Project inherits.

Think of this as the meta-workflow. Spending 15 to 30 minutes once to build a well-configured Project pays off on every matter afterward, because your firm's voice, your standard positions, and your safety rules are already loaded. It also makes your output more consistent, which matters when several chats (or several people at the firm) should sound like the same practice.

This is a setup workflow, not a one-shot request, so the prompts below are text you paste into the Project's configuration rather than questions you ask in a chat. You stay fully responsible for everything Claude produces, and your duty of confidentiality still applies to what you load in. We will flag exactly where that line sits.

The Workflow

1
Decide what to load
Before you open Claude, make a short list of the firm context you find yourself repeating. The goal is to capture the reusable parts of your practice, not any single client's matter. Good candidates: anonymized writing samples that show your voice, your standard contract positions and fallbacks, a short style guide, the practice areas you handle, and your jurisdiction. Keep this list to things that are true across matters.
Prompt
```
My reusable Project should include:
- Who I am: [NAME], [SOLO / FIRM NAME], practicing [PRACTICE AREAS]
- Jurisdiction(s): [STATE / COURTS]
- My writing voice: [e.g., plain, measured, client-friendly; avoids legalese]
- Standard contract positions: [e.g., mutual indemnity preferred; cap at fees paid]
- Documents to attach as knowledge: [anonymized engagement letter], [demand letter template], [intake checklist], [clause bank]
- Default rules I always want followed: [list here]
```
What you get: A clear, short inventory of reusable firm context and a list of the anonymized files you will attach. Nothing client-specific should be on this list.

Create the Project and write custom instructions

In Claude, create a new Project and give it a clear name like "Firm Drafting — [Your Name]." Then write the custom instructions: who you are, your jurisdiction, the tone you want, and your default rules. The safety rules matter most. Tell Claude to flag every case citation as UNVERIFIED until you confirm it, never to invent facts, and to ask before assuming. These instructions apply to every chat you start in the Project.

Prompt

You are assisting [NAME], a [PRACTICE AREA] attorney at [FIRM] licensed in [JURISDICTION]. Apply these rules to every conversation in this Project:

Voice: Write in [plain, measured, client-friendly] English. Avoid legalese unless I ask for it.

Safety rules:
- Flag EVERY case citation, statute, or rule reference as "UNVERIFIED" until I confirm it. Never present a citation as verified.
- Never invent facts, dates, dollar amounts, or party names. If you need one, leave a [BRACKET] for me to fill.
- If a request is ambiguous, ask me before assuming.
- You are a drafting aid, not the lawyer. I review and am responsible for all output.

Defaults: [e.g., American spelling; cite to [JURISDICTION] authority; default deadline assumptions to none].

What you get: A saved Project whose custom instructions encode your identity, jurisdiction, tone, and safety defaults so you never retype them. The unverified-citation rule should appear in Claude's behavior on the next task.

3
Add knowledge files
Upload the anonymized documents from your inventory as Project knowledge: a clean engagement letter, a demand or motion template, an intake checklist, your clause bank or standard positions. These persist across every chat in the Project, so Claude can match your structure and language. Strip client names, matter numbers, and any privileged specifics before uploading — a knowledge file is reusable firm material, not a place for live matter detail.
Prompt
```
Knowledge file outline — "Standard Positions (Anonymized)":
1. Engagement terms: scope language, fee structure options, termination clause
2. Contract fallbacks: indemnity [preferred / acceptable / walk-away]; liability cap [preferred / acceptable]; governing law [JURISDICTION]
3. Demand letter skeleton: facts → liability → damages → demand → deadline
4. Intake checklist: conflicts, jurisdiction, statute of limitations, key documents
5. House style notes: defined-term conventions, heading format, signature block
(Replace all party names with [CLIENT], [OPPOSING PARTY]; remove matter numbers.)
```
What you get: A handful of anonymized reference files attached to the Project. Future drafts will follow your templates and standard positions without you pasting them each time.
4
Test it on a real task and refine
Open a new chat inside the Project and run a genuine task — say, a first draft of a demand letter or a clause comparison. Watch two things: does it match your voice and templates, and does it honor your safety rules (citations flagged UNVERIFIED, no invented facts, questions when unsure)? Where it misses, that is a signal to tighten an instruction. Edit the custom instructions, then re-run to confirm the fix.
Prompt
```
Draft a [demand letter / engagement letter / clause comparison] for [SHORT, NON-CONFIDENTIAL SCENARIO]. Use my standard structure and voice. Remember: flag any citation as UNVERIFIED, leave [BRACKETS] for facts you don't have, and ask if anything is unclear.
```
What you get: A draft that sounds like your firm and follows your templates. Any gaps reveal an instruction to sharpen — e.g., add "never use the word 'utilize'" or "always include a response deadline." Refine and the Project gets better.
Maintain it — fold new decisions back in
A Project is only as good as it is current. When you make a drafting decision you would want repeated — a new standard clause, a tone tweak, a position change — take ten seconds to fold it back into the custom instructions or a knowledge file. Revisit the Project every few months to remove stale templates and confirm the safety rules are intact. On a paid Team or Enterprise plan you can share the Project with colleagues so the whole firm drafts from the same playbook; just keep this kind of shared Project to anonymized firm material and route confidential matter work to access-controlled Projects instead.
What you get: A living Project that improves with use. Over time it captures your firm's accumulated drafting judgment, and — if shared — keeps your team consistent without anyone re-explaining the basics.

Example Output

Illustrative example — names, facts, and figures are fictional.

PROJECT: Firm Drafting — Maple & Crane LLP (Employment)

WHO YOU ARE ASSISTING
You support attorneys at Maple & Crane LLP, a three-lawyer employment firm licensed in Ohio. We represent employees and small employers in wage, discrimination, and severance matters.

VOICE
- Write in plain, measured English a client can read without a dictionary.
- Short paragraphs. No throat-clearing. Avoid "utilize," "herein," "aforementioned."
- Confident but never overstated; we do not guarantee outcomes.

SAFETY RULES (ALWAYS)
- Flag EVERY case, statute, or rule citation as UNVERIFIED until a lawyer confirms it.
- Never invent facts, dates, dollar figures, or names. Leave [BRACKETS] instead.
- Ask before assuming when a request is ambiguous.
- You are a drafting aid. A licensed attorney reviews and is responsible for all output.

JURISDICTION & DEFAULTS
- Default authority: Ohio statutes and Sixth Circuit / Ohio courts.
- American spelling. No deadline assumptions unless I provide them.

HOUSE STYLE
- Demand letters: facts → liability → damages → demand → response deadline.
- Define a party once in bold, then use the short form.
- Always include a signature block with bar number placeholder [BAR NO.].

WHAT NOT TO DO
- Do not include client-identifying details from prior matters.
- Do not offer a legal conclusion as settled; frame options and risks.

Tips

•Lead your custom instructions with the safety rules, not your bio — the unverified-citation and no-invented-facts rules are the highest-value lines in the whole Project.
•Name Projects so you can tell them apart at a glance, e.g. "Firm Drafting (shared)" versus "Smith v. Acme (matter)." The name is your first reminder of what may safely go inside.
•Keep knowledge files small and clean. A tight, anonymized clause bank beats a giant dump of old documents — Claude follows focused references far more reliably.
•Treat the Project as version one. The real value comes from the two-minute refinements you make after each task, not from getting it perfect on setup day.

A note on confidentiality

A Project's knowledge persists and, on Team or Enterprise plans, can be shared with colleagues — so load anonymized templates and firm knowledge freely, but never put privileged client specifics into a shared firm-template Project. Keep confidential matter work in access-controlled Projects, and remember your duty of confidentiality applies to everything you upload.

Prompts used in this workflow

Case Summary for Client Engagement Letter Writer Plain-English Document Translator

Get New Workflows Like This Every Week

Join the free Claude for Lawyers newsletter — practical workflows, prompts, and guides for everyday practice.

Set Up a Reusable Claude Project for Your Practice

When to use this

The Workflow

Decide what to load

Create the Project and write custom instructions

Add knowledge files

Test it on a real task and refine

Maintain it — fold new decisions back in

Example Output

Tips

A note on confidentiality

Prompts used in this workflow

Related Reading

Get New Workflows Like This Every Week