The Case File Trick: Turning A Messy Project Into A Smart Assistant

A simple folder method for turning chaos into clear, shippable work

Turn the chaos into boxes and arrows. Then let the AI do the clicking.

You probably know this pattern:

• A client or boss dumps a folder of documents on you.

• You open an AI chat and paste a few excerpts.

• Three prompts later, the model is clearly confused, and you are re-explaining basic context in every message.

The problem is simple:

You are treating AI like a goldfish with amnesia on a project that actually needs a case file.

This post gives you a pattern I use constantly:

The Case File Trick: turn a messy project into a single, reusable “brain” that AI can reason about, instead of starting from zero every time.

You will get:

• What a “case file” is in AI terms

• How to build one in 15–30 minutes

• Exact prompts to make your AI treat it as a persistent assistant

• Guardrails so it does not drift or hallucinate

---

What A Case File Is (In AI Terms)

In real work, a case file is the single source of truth for a matter, client, or project.

In AI land, a case file is:

One living document that tells the model who you are, what the project is, what good looks like, and what the constraints are.

You keep it outside the chat (Google Doc, Notion, Word, etc.). Then you:

1. Feed it to the AI once at the start.

2. Tell the AI to treat it as the canonical reference for this project.

3. Reuse it in every serious prompt with a short reference (“using the case file you have for Project X…”).

The result:

• Less re-explaining

• More consistent tone and structure

• Better answers on the first try

---

What Goes Inside A Case File

Keep it lean. The point is not to write a novel. The point is to give the AI a solid project brief.

Use this simple structure:

1. Project Snapshot

   • One paragraph: what this project is and why it exists.

   • Example:

“We are advising [Company] on [issue] and need to produce [outputs] for [audience] by [date]. The core question is [X].”

1. Role And Audience

   • Who you are, and who you speak to.

   • Example:

“I am a senior associate in [field]. Primary readers are [titles]. They care most about [1–3 concerns].”

1. Goals And Non-Goals

   • 3–7 bullets each.

   • Goals: what success looks like.

   • Non-goals: what this project is explicitly not trying to do.

2. Key Constraints

   • Deadlines, page limits, tone requirements, legal or confidentiality constraints, banned phrases, etc.

3. Working Definitions / Jargon

   • Short glossary of project-specific terms, acronyms, and how you use them.

4. Outputs We Expect To Produce

   • 3–6 bullet list: memos, decks, emails, one-pagers, talking points, FAQs.

   • Include any preferred structures (e.g., “issue–analysis–recommendation”).

5. Reference Materials (Optional)

   • Short list of the most important documents (titles only), plus 1–2 lines each on what they are.

That is it. You can usually sketch this in 15–30 minutes.

---

Step 1: Build The Case File

Create a document called:

Case File – [Client or Project Name]

Fill in the sections above. Write like you are briefing a new, smart colleague on day one.

Aim for 1–3 pages. If you hit 7 pages of prose, you are writing for yourself, not for the AI.

---

Step 2: Load It Into The Model Properly

Once the case file is ready, you want the AI to internalize it once, not treat it as random input.

Use a prompt like this:

Prompt: Initial ingestion
“I am going to share a case file for a specific project.

Your job is to:

1. Read it carefully.

2. Extract the key information about the project, my role, the audience, goals, non-goals, constraints, and expected outputs.

3. Summarize your understanding in a structured way so I can see if you have it right.

4. From now on, when I say ‘using the case file for [Project Name],’ you will use this information as context unless I explicitly tell you otherwise.

Please confirm that you understand, then I will paste the case file.”

Paste the full case file.

Then ask:

Prompt: Understanding check
“Summarize your understanding of this case file in the following structure:

• Project Snapshot

• My Role

• Primary Audience

• Goals

• Non-Goals

• Constraints

• Expected Outputs

• Definitions / Jargon

Keep it under 400 words. Point out anything that seems ambiguous or missing.”

Fix anything it misunderstood. Add missing pieces back to the case file document, then tell the model:

“Update your internal understanding of the case file with these corrections: [paste corrections].”

Now you have a shared mental model.

---

Step 3: Use It In Every Serious Prompt

From now on, for this project, you start prompts with:

“Using the case file for [Project Name] as context…”

And then describe the task.

For example:

Prompt: Drafting an email
“Using the case file for Project Horizon as context, draft a concise email from me to [Name, Title] that:

• Explains in plain language what we are doing and why.

• Flags the top 3 decisions we will need from them in the next two weeks.

• Uses a professional but direct tone, matching a senior associate writing to a time-constrained executive.

Keep it under 250 words and assume this is the first time they have heard the full shape of the project.”

Or:

Prompt: Structuring a memo
“Using the case file for Project Horizon, give me a proposed outline for a 5–7 page memo to [audience] that:

• Starts with a 1-page executive summary.

• Uses an issue–analysis–recommendation structure.

• Highlights where decisions or tradeoffs will be hardest for them.

Focus on section headings and short annotations, not full text.”

Or:

Prompt: Brainstorming risks
“Using the case file for Project Horizon, list the top 10 practical risks or failure modes for this project from the perspective of [audience]. For each, give a one-sentence description and a one-sentence mitigation idea.”

You are no longer re-explaining who the client is, what the constraints are, or why the project exists.

---

Step 4: Keep The Case File Alive

Projects evolve. The case file should too.

When something big changes (scope, timeline, key decision), update the document and tell the AI.

Prompt: Updating the case file
“The case file for Project Horizon has changed.

Please update your understanding with the following:

• [Describe change: e.g., timeline extended, new stakeholder added, scope narrowed, new non-goal].

Then restate the updated:

• Goals (3–5 bullets)

• Non-Goals (3–5 bullets)

• Constraints (3–5 bullets)

Keep it under 250 words.”

Then actually make the same edits in the external document. The document remains the single source of truth. The model is a temporary copy.

---

Step 5: Patterns Of Use Across A Whole Project

Once the case file is loaded, you can use the AI as a project assistant, not just a text toy.

Typical tasks:

Converting raw notes into structured artifacts

• Meeting notes → action items and decisions

• Brain dumps → structured outlines or issue lists

“Using the case file for Project Horizon, turn these rough notes into a clean action list grouped by owner and timeline.”

Maintaining consistency across outputs

• Memo tone matching the email tone

• Slide bullets that match the memo’s key points

“Using the case file and the memo outline we already drafted, propose 8–10 slide headlines that would carry the same logic into a short presentation.”

Preparing for key conversations

• Stakeholder-specific talking points

• Anticipated questions and objections

“Using the case file, generate a one-page prep note for a 30-minute call with [stakeholder]. Include:

• Their likely concerns

• 5–7 questions they may ask

• Short, direct answers I can give.”

• Sanity checking scope creep

“Using the case file, review this new request from [stakeholder]. Explain in 3–5 bullets whether it fits within project goals and constraints, or whether it represents scope creep. Suggest language I can use to push back diplomatically if needed.”

This is where the payoff appears. The AI starts to feel like a junior team member who already knows the project, instead of a stranger in every chat.

---

Guardrails: Where This Breaks Down

A few ways to misuse the case file trick:

1. Treating the case file as a dumping ground.
   If you paste every email and draft into it, it becomes unreadable. Keep it high level. Use separate docs for details.

2. Never updating it.
   A stale case file is almost worse than none. If the project direction flips, update the file or explicitly say: “Ignore the previous case file. Here is the new one.”

3. Letting the AI override your reality.
   The case file is your artifact. The AI can suggest additions, but you decide what is true and what is not.

4. Using it for 10-minute one-off tasks.
   The overhead is only worth it when a project will last more than a few days or require multiple outputs. For a small, one-off question, keep it simple.

---

A Simple Drill For This Week

Pick one active project that meets these conditions:

• It has more than one output (e.g., memo + email + slides).

• You expect to work on it for at least two weeks.

• You already have a messy folder or thread of related materials.

Do this:

1. Create a Case File – [Project Name] document using the structure above (Project Snapshot, Role, Goals, Non-Goals, Constraints, Definitions, Expected Outputs).

2. Load it into your AI tool with the initial ingestion prompt.

3. Use it to generate one concrete artifact you actually need this week (email, outline, or prep note).

If it saves you real time or gives you a better first draft, keep the pattern and reuse it on the next project.

The trick is simple:

Build a case file once, then stop treating every prompt like a blank slate.

—
The AI Desk Mate
Practical workflows for using AI at your actual job.