Claude Project: Build Your Personal Program Analyst Assistant

What This Builds

A persistent Claude Project configured with your program's specific context — your grant portfolio, your reporting templates, your regulatory framework, and your agency's writing conventions. Every conversation starts with full program context, so you skip the "let me explain our program" setup every time. Instead of re-explaining your program's purpose, grantee profile, and required formats in every session, Claude already knows. Every memo, report, and correspondence it drafts matches your program's standards from the first word.

Prerequisites

• Claude Pro subscription ($20/month at claude.ai)
• Comfortable with basic Claude conversations (Levels 1-3)
• Your key report templates (even drafts are fine)
• 30 minutes to document your program's context in bullet points

The Concept

A Claude Project is like bringing on a detail-oriented program assistant who read your entire program file on their first day. You set it up once by documenting your program's context and uploading your templates. After that, every conversation in that Project starts from that shared foundation. You don't re-explain your regulatory framework, your grantee profile, or your reporting format. Over time, the Project becomes increasingly valuable as you add more templates and context.

Build It Step by Step

Part 1: Create the Project

1. Open claude.ai and sign in to your Pro account
2. In the left sidebar, click "New project" (or find the "Projects" section with a "+" button)
3. Name your project: "Program Analyst — [Program Name]" or similar
4. You'll see a Project interface with two sections: Instructions (always-on system prompt) and Files (uploaded documents)

What you should see: A project workspace with a chat interface, an Instructions panel on the right, and a Files tab.

Part 2: Write Your System Instructions

Click "Set instructions" or the Instructions panel. This is your permanent context — what Claude knows about you and your program every single time you open this Project.

Copy and customize this template:

You are a program analyst assistant for a [GS-level / contractor] analyst supporting the [Program Name] at [Agency Name].

## Program Overview
- Program type: [federal grants / contracts / direct services / regulatory / hybrid]
- Authorizing statute: [cite your law]
- Program purpose: [1-2 sentences on what the program does and who it serves]
- Regulatory framework: [primary regulations — e.g., 2 CFR Part 200, program-specific regs]
- Annual budget: approximately [$X] across [N] active grants/contracts

## My Grantee/Partner Profile
- Number of active awards: [N]
- Grantee types: [state governments / nonprofits / universities / local governments]
- Geographic scope: [national / regional — specify]
- Average award size: [$X]
- Performance reporting schedule: [quarterly / semi-annual / annual]

## Key Documents and Reporting Cycles
- Quarterly performance reports: due [dates]
- Annual performance report: due [date], submitted to [OMB / Congress / leadership]
- Congressional reporting requirements: [describe if applicable]
- Internal reporting cycles: [monthly status briefings / weekly leadership updates]

## Writing Style
- All documents use formal federal government writing style
- Reports are written in third person, factual, data-supported
- Briefings are bottom-line-up-front with decision or awareness clearly stated
- Correspondence to grantees is professional but collegial in tone
- All monetary figures use "$" format (e.g., $1.2M, not "1.2 million dollars")

## What I Need from You
1. When I provide program data and notes, draft reports and memos in federal government style
2. When I describe a grantee situation, draft appropriate monitoring correspondence
3. When I need to brief leadership, help me structure the message and anticipate questions
4. When I need to research a regulatory question, help me identify the relevant CFR citations to verify
5. When I draft correspondence, adjust tone based on the audience I specify
6. Never invent numbers or regulatory citations — use [PLACEHOLDER] when information is missing
7. Always flag if you're uncertain about a regulatory interpretation — I will verify against primary sources

Fill in all bracketed fields with your actual program details. Click Save.

Part 3: Upload Your Reference Documents

Click the "Files" tab in your Project. Upload documents that Claude will reference in every conversation:

Priority uploads:

1. Your performance report template — the standard format you submit to OMB or leadership
2. Your monitoring checklist or protocol — what you review when examining grantee reports
3. Your grant agreement standard terms and conditions — so Claude can reference specific requirements
4. Your agency style guide — if you have a writing style guide for official documents
5. Your performance indicators and targets — the annual targets for each required metric

Optional but valuable:

• Prior year annual performance report (shows Claude the quality and style expected)
• Your OMB-required performance measures documentation
• Your standard correspondence templates (monitoring letters, corrective action notices)
• Your site visit protocol or agenda template

How to upload: Drag and drop files into the Files tab, or click "Upload files." Claude will reference these in responses without you having to paste them each time.

Part 4: Test and Refine

Start a conversation in your Project. Test these scenarios:

Test 1 — Performance narrative: "Here is my Q2 metric data: [paste 5 bullet points of metrics]. Draft the performance summary section of the quarterly report."

• Does it use your program's terminology?
• Does it match the format of your uploaded template?
• Does it include specific data points, not generic language?

Test 2 — Monitoring correspondence: "Draft a monitoring letter to a grantee requesting clarification on two issues: [describe issues]. Professional tone."

• Does it reference the correct regulatory framework for your program?
• Is the tone appropriate (professional, not accusatory)?

Test 3 — Briefing prep: "I need to brief the Deputy Director on Q2 program status tomorrow. Here is the raw data: [paste data]. Draft the briefing memo."

• Is it bottom-line-up-front?
• Does it match your agency's standard format?

If any test produces generic output, add more specific context to your Instructions.

Real Example: A Typical Program Analyst Morning

Setup: Your Project has the grant program documented, grantee profile uploaded, performance report template in Files, and monitoring correspondence examples included.

Your morning has three tasks:

Task 1 (Grantee report review): You received two quarterly performance reports from grantees. Each is 15 pages.

What you type in your Project: "Review this grantee performance report and identify any red flags — metrics below target, milestones delayed, narrative/data inconsistencies, or compliance concerns. [paste or attach report]"

What you get: A structured flag list organized by category, with specific page references for you to verify. Pre-screening 2 reports takes 20 minutes instead of 2 hours.

Task 2 (Correspondence): One flagged grantee needs a follow-up letter requesting clarification on three issues.

What you type: "Draft a monitoring correspondence letter for [Grantee Organization] requesting clarification on the following three issues: [list issues]. Tone: professional, collegial. Request response within 14 business days."

What you get: A complete letter draft using your program's regulatory framework, ready for signature routing.

Task 3 (Briefing prep): Division chief meeting this afternoon — need a one-page status update.

What you type: "Draft a one-page briefing memo for my division chief on the grant program's Q2 status. Key data: [paste your metrics]. Issues to flag: [the grantee monitoring situation]. Format: bottom-line-up-front, bullet points under short headers."

What you get: A complete one-page memo with your program's standard framing, ready for review and routing.

Time saved: What normally takes a full morning of writing is handled in 90 minutes of review-and-refine.

What to Do When It Breaks

• Claude forgets your program context → Check that your Instructions are saved (click Instructions panel). If they disappeared, re-paste them. Re-upload any Files that may have been cleared.
• Reports don't match your template → Upload your actual template as a file rather than describing it in Instructions. Direct document reference is more reliable than description.
• Regulatory references are wrong → Add a line to Instructions: "When referencing regulations, always include the CFR citation and flag it as requiring verification." Do not rely on Claude for regulatory accuracy — always verify at ecfr.gov.
• Tone is wrong for grantee correspondence → Paste an example of good correspondence you've previously written and say "match this tone exactly."

Variations

• Simpler version: Skip the Project setup and start every Claude conversation by pasting a 5-line program context paragraph. Less powerful but requires no Pro subscription.
• Portfolio management version: Create separate Projects for different grant portfolios if you manage multiple distinct programs.
• Team version: If your agency has a Claude for Enterprise or Teams account, work with your IT office to set up a shared Project that the whole program team can access.

What to Do Next

• This week: Spend 45 minutes building the Project and running all four test scenarios — refine Instructions until results match your expectations
• This month: Add your most-used report sections as example input/output pairs in Instructions — shows Claude exactly what quality looks like for your program
• Advanced: Export your best prompts and share them with colleagues — create a team prompt library even if you can't share the Project itself

Advanced guide for government program analyst professionals. Claude Pro subscription required. All AI-generated content must be verified and cleared through appropriate agency channels before official use.