ANALYST TRACK · DAY 2 OF 5
Day 1 Day 2 Day 3 Day 4 Day 5

Build Your Status Vault.

A Project that holds your stakeholders, your formats, and your reference docs. Set it up once so your chats start with context already loaded.

Start Day 2 Day 3 →
A note before you start: The Status Vault uses Claude Projects with custom instructions, which requires Claude Pro ($20/month). On the free tier, you can adapt the same approach by pasting context manually at the start of each chat — slower, but the prompts in this track still work.

Your context, ready before the chat starts

A Status Vault is a Claude Project you build once and reuse for most briefs, updates, and syntheses.

It holds three things: the stakeholders you work with and how they make decisions, examples of the formats you keep getting asked for, and the reference documents you check every week.

Once it's set up, your chats start with those materials available — so you don't have to re-paste them every time. Less rewriting the same intro lines. Less explaining who your operations leader is.

Stop repeating your background. Start using it.

Three parts

1. Stakeholder roster

A short doc that lists who you work with and how they make decisions. Focus on style, not just titles.

Example: "Operations leader — prefers 3-bullet status, no preamble. Cares about timelines slipping, not technical detail. Finance leader — wants risk-adjusted views and dollar impact. Product head — reads everything, prefers tables to prose."

You write it once. It's available whenever you use this Project.

Don't have a stakeholder roster yet? Start with this template — 3 minutes:

# Stakeholder Roster ## [Name 1] — [Role] - Prefers: [3 bullets / one paragraph / table] - Cares about: [timeline / dollars / risk / strategy] - Avoid: [technical jargon / political framing / over-explaining] ## [Name 2] — [Role] [same pattern] ## [Name 3] — [Role] [same pattern]

Three stakeholders is enough to start. Refine over the next month as you notice patterns.

2. Format library

Upload 2-3 examples of briefs, updates, or memos you've actually shipped. Not your best ones — your most representative ones.

Tip: include the messy ones too. These examples help Claude match how your team actually communicates.

3. Reference documents

The 3-5 docs you check constantly. Org charts. Active project trackers. Current OKRs. Last quarter's board deck. Whatever you'd open in another tab during a normal Tuesday.

Curate, don't dump. High signal beats high volume — irrelevant context dilutes focus.

Today's exercise (15 minutes)

Step 1. Open Claude.ai. Sidebar → New Project. Name it "Status Vault" or whatever fits your work.

Step 2. Upload exactly 5 items: 1 stakeholder roster + 2 format examples + 2 reference documents. You can add more later.

Step 3. Paste this into the custom instructions field:

You are supporting a business analyst working across stakeholders. When reviewing documents: - Identify the decision that needs to be made - Highlight risks or inconsistencies - Quote specific lines when making claims When generating outputs: - Lead with the bottom line up front - Match the tone of the uploaded format examples - End with a clear next action If information is unclear: - State what's missing - Suggest what to ask for next

Step 4. The First Pull. Run yesterday's Decision Frame on a recent doc — once outside any Project, then once inside the Vault. Compare.

Stuck? If the output feels generic, your roster might be the issue. Add one sentence to each stakeholder entry: "What did they push back on most recently?" That single detail sharpens every reshape downstream.

Same prompt. Without the Vault vs. with the Vault.

Same vendor SOW. Same prompt: "What's the decision I need to make and what are my real options?"

Without the Vault

Decision: whether to approve or delay this vendor agreement. Options: - Approve as-is - Approve with conditions - Decline Recommend approving with conditions, requiring SLA clarifications and audit-finding closure within standard timelines.

Generic. Defensible. Doesn't know who's asking, what format you'll deliver, or what your org cares about.

With the Vault loaded

Decision: approve with conditions or delay 30 days. For your operations leader (per roster — 3 bullets, timeline focus, no preamble): • Approving with conditions keeps Q2 launch on schedule. • Delaying 30 days pushes integration testing into the launch sprint — high risk. • Recommend approve with conditions; require findings closure before integration begins. For your finance leader (per roster — dollar impact, risk-adjusted): • Annual cost: $480K. Remediation: vendor cost, not ours. • Delay cost: ~$60K in slipped launch revenue. • Risk-adjusted recommendation: approve with conditions.

Same prompt. The Vault did the audience tailoring without you asking. That's the lift — your context becomes infrastructure.

Why this matters

Standard chats don't retain your working context. Every session, you re-explain who you are, who your stakeholders are, what format they want, what the current state of the project is.

A Project removes that overhead.

A single well-built Project is more reliable than a stack of generic prompts. Set it up once, refine it over time.

A quick note on Memory

Claude Memory stores general preferences across chats. A Project is different — it groups specific documents, formats, and stakeholders for a single type of work.

Memory is broad. Projects are scoped.

Memory is for your name and your coffee order. The Status Vault is for the Q3 budget revision you're working on today. Use both.

Tomorrow

Day 3 is where the Vault starts paying off. Most of your work isn't producing one brief — it's reshaping the same insight for different rooms. Engineering wants the technical version. Finance wants the dollar version. The board wants the one-line version.

Tomorrow you'll learn one prompt that handles audience and format together — so a single brief turns into whatever the room needs, in seconds.

Analyst Track Progression

Your 5-day path to a weekly analyst rhythm.

Day 1 → Day 2 → Day 3 → Day 4 → Day 5