Claude Projects: Build a Persistent Case History System

What This Builds

A Claude Project stores everything Claude knows about a case across multiple conversations. Instead of re-explaining the case every time you open a new chat, the Project remembers: family composition, case history, active services, court dates, safety concerns, and your last update. When you need a court report, case summary, or transfer document, everything is already loaded. When a case transfers to a new worker, the summary is already there.

This directly addresses one of child welfare's biggest safety risks: critical case information lost in transitions.

Prerequisites

• Claude Pro subscription ($20/month — required for Claude Projects)
• Active cases you want to set up (start with 2–3 complex or long-running cases)
• 1 hour to set up your first project; 5 minutes per case update

The Concept

Claude Projects is like a shared notebook between you and the AI. You add information to the project over time — new case developments, court dates, service completions — and Claude can see all of it whenever you start a new conversation in that project.

Imagine if your case file lived inside the AI: every time you needed a document, a summary, or case prep help, Claude already had the full picture. That's what a Project does.

Build It Step by Step

Part 1: Create your first Case Project

1. Go to claude.ai and sign in with your Pro account
2. In the left sidebar, click "Projects" → "New Project"
3. Name it: "[Case Code/Initials] — [Month/Year opened]" (example: "SM-2026-01")
4. Add a brief description: "Active child welfare case — [general situation type, no identifying details]"

What you should see: A new project with a conversation area and a "Project knowledge" section on the right.

Part 2: Build your initial case brief

Click into the Project. In the "Project knowledge" section (right side or bottom), click "Add content." Create a document called "Case Brief" and paste this template filled in with anonymized case facts:

CASE BRIEF — [Case Code]
Created: [date]
Last updated: [date]

FAMILY COMPOSITION:
- Parent 1 role: [e.g., "Mother, mid-30s, primary caregiver"]
- Parent 2 role: [e.g., "Father, incarcerated since X"]
- Children: [e.g., "Child A (age 7, female), Child B (age 4, male)"]

CASE TYPE: [e.g., Neglect / Physical abuse / Domestic violence exposure]
CURRENT STATUS: [In-home services / Foster care — relative / Foster care — non-relative]
COURT: [Dependency / Family court]
NEXT HEARING: [date and type]

HISTORY SUMMARY:
[Brief chronology — when case opened, major decisions, placement changes]

ACTIVE SERVICES:
- [Service 1]: [provider type, start date, completion status]
- [Service 2]: ...

CURRENT SAFETY CONCERNS:
[List any unresolved safety concerns]

PERMANENCY GOAL: [Reunification / Adoption / Guardianship / APPLA]
CONCURRENT PLAN: [if any]

REPORTS DUE:
- Next court report due: [date]
- Next supervisory review: [date]

What you should see: The case brief is saved as project knowledge. Claude can now reference it in every conversation within this project.

Part 3: Add updates as the case progresses

Every time something significant happens — a court hearing, a completed service, a new safety concern — start a conversation in the Project and type a brief update:

"Update case brief: Mother completed parenting class on 3/15 (6 of 6 sessions). Next court hearing moved to 4/22."

Ask Claude: "Update the case brief with this new information and show me the revised version."

Claude updates the document and you paste it back into the Project knowledge.

What you should see: An evolving, always-current case brief that takes 2 minutes to update after each development.

Part 4: Generate documents from the Project

With the full case context loaded, document generation is fast:

In any Project conversation, type: "Draft a 6-month status review court report. The children remain in foster care. I'm recommending continued services. Focus the assessment on [specific issue]."

Claude already knows the family composition, service history, and case background — it uses all of it automatically.

Part 5: Generate a case transfer summary on demand

When a case is transferring to a new worker (or you're going on leave), open the Project and type:

"Generate a comprehensive case transfer summary. Include: case background, current family situation, active services and status, upcoming court dates, pending tasks, key contacts, and any critical safety concerns the incoming worker must know immediately."

What you should see: A complete transfer summary that takes 5 minutes instead of 3 hours — and it's already organized and comprehensive.

Real Example: A Case That Runs for 18 Months

Setup: You opened a Project in January 2025 when the case was assigned to you. You've added brief updates 20 times over 18 months — each update took 3–5 minutes.

Input (in March 2026, preparing for final court hearing): "Generate a comprehensive case summary for the reunification hearing next week. The outcome I'm recommending is return of children to the home with 6 months of aftercare services."

Output: A complete summary of the entire 18-month case arc — key decisions, services completed, family progress, safety factors resolved, and a recommendation narrative — generated in 30 seconds from everything you've added to the Project over time.

Time saved: What would have been a 4-hour case review and document prep → 30 minutes.

When the case closes 2 months later: "Generate a final case closure summary and transfer summary for the archive." Done in 5 minutes.

What to Do When It Breaks

• Claude doesn't seem to remember the case brief → Check that the case brief is in "Project knowledge" (not just in a conversation). Knowledge files are permanent; conversation history may eventually be truncated.
• Case brief is getting too long → Create separate knowledge documents: "Case Brief," "Service History," "Court Hearing Log" — Claude can reference all of them.
• Too many cases to manage as Projects → Prioritize your 5 most complex or long-running cases. Quick cases don't need a Project — use regular conversations.
• Can't find where to add project knowledge → Look for a book/document icon, "Project instructions," or "Knowledge" in the project sidebar. The interface updates periodically.

Variations

• Simpler version: Keep a Google Doc "running case summary" that you paste at the start of each Claude conversation — same concept, no subscription required, but manual
• Extended version: Create a "Master Caseload Project" with all your active cases summarized in one document, and ask Claude to generate your weekly priority list: "Which of my cases has a deadline or required contact in the next 7 days?"

What to Do Next

• This week: Set up one Project for your most complex active case
• This month: Add updates after every court hearing and completed service; generate your next court report from the Project
• Advanced: When you get your first case transfer using this system, compare the experience to previous transfers

Advanced guide for child welfare caseworker professionals. Claude Projects requires Claude Pro ($20/month). Never include real client names, case numbers, or identifying information in your Project knowledge files — use initials, codes, and role descriptions.