Claude Project: Build Your Store's AI Knowledge Base

What This Builds

A persistent AI assistant that already knows your store's policies, procedures, templates, and common situations — so instead of describing your store from scratch every time you use AI, you open Claude and it's already in context. By the end, you'll have an assistant that can generate policy-accurate HR documents, translate communications to Spanish, create training materials, and prep you for GM conversations in under 2 minutes each.

Prerequisites

• Claude Pro account at claude.ai ($20/month)
• Copies of your key documents: employee handbook, scheduling policies, food safety procedures, write-up templates (PDFs, Word docs, or photos of printed pages)
• 1–2 uninterrupted hours to set it up (do this once; benefits are daily afterward)

The Concept

A Claude Project is like having a new coworker who's read your entire employee handbook before their first day. Every time you start a new conversation in the Project, Claude already knows your store's policies, your document formats, and your preferences. You don't repeat context — you just ask for what you need.

Most people use AI like a search engine: they type a question, get a generic answer, and feel mildly disappointed. This setup makes Claude work like a colleague who knows YOUR restaurant.

Build It Step by Step

Part 1: Set Up the Claude Project (20 minutes)

1. Go to claude.ai and log in with your Pro account
2. In the left sidebar, click Projects → New Project
3. Name it something clear: "QSR Store [Your Number/Name] — Manager Assistant"
4. You'll see a workspace with:

   • A text area at the top for Project Instructions (the "brain" of your assistant)
   • A file section for Documents (the "library" your assistant reads from)
   • A conversation area below

Part 2: Write Your Project Instructions (15 minutes)

The instructions tell Claude who you are, what you need, and how to behave. Click in the Instructions field and type (or copy-paste and customize):

You are the AI assistant for a QSR fast food assistant manager.

ABOUT MY STORE:
- [Your brand — e.g., Taco Bell franchise, independent burger concept]
- Location: [city/region]
- My name: [your first name]
- GM's name: [GM's first name]
- Staff size: approximately [number] employees

WHAT YOU HELP WITH:
1. HR documentation: Write coaching notices, corrective action plans, performance reviews, and job postings using our uploaded templates and policies
2. Scheduling: Help draft, troubleshoot, or adjust weekly schedules
3. Communication: Draft professional messages to GM, employees, vendors, or customers
4. Training: Generate checklists, role-plays, and training materials
5. Compliance: Help interpret and apply our food safety and HR policies

HOW TO BEHAVE:
- Always be specific — ask for details rather than writing something vague
- When writing HR documents, reference our uploaded policies for accuracy
- Keep communications direct and professional but not stiff
- Flag anything that should be reviewed by the GM or HR before finalizing
- If I ask for a Spanish translation, use plain, conversational Mexican Spanish

WHAT TO AVOID:
- Do not make up policy details — reference our uploaded documents
- Do not include legal admissions of liability in any customer-facing communication
- Do not use overly formal or corporate-sounding language in crew communications

Save the instructions.

Part 3: Upload Your Document Library (30 minutes)

Click Add content or the upload icon in the Project panel. Upload every policy document you can find. Priority order:

Tier 1 — Upload first (highest impact):

• Employee handbook (full PDF)
• Attendance and tardiness policy
• Progressive discipline/write-up policy
• Food safety HACCP procedures or checklist
• Any blank HR form templates you currently use

Tier 2 — Upload if you have them:

• Corporate training materials
• Franchise operations manual excerpts
• Opening/closing checklist
• Inventory and ordering procedures

Tier 3 — Create and upload if they don't exist: Ask ChatGPT (in a separate tab, free) to "Generate a basic QSR progressive discipline policy outlining 3 steps: verbal warning, written warning, final warning/termination." Copy the output into a Google Doc and upload it. This gives Claude a policy to reference even if you don't have one on paper.

For each upload, Claude will confirm it can read the file. Image files (photos of printed documents) work — Claude reads the text in images.

Part 4: Test Your Knowledge Base (15 minutes)

Start a new conversation inside the Project (not a regular Claude chat). Test these prompts:

Test 1 — HR document: "Write a first written warning for an employee who has been late 4 times in 3 weeks. Use our attendance policy format."

Expected result: Claude writes a notice that references your specific policy's language — not a generic template.

Test 2 — Spanish translation: "Translate our food safety handwashing reminder into Spanish for our crew."

Expected result: Clean, conversational Spanish translation.

Test 3 — Scheduling help: "I have 12 crew scheduled this week. Three have called out sick so far (it's Wednesday). Help me figure out the coverage gap and suggest who to contact."

Expected result: Claude asks for your schedule details and helps analyze the gap.

If the outputs reference your uploaded documents, your knowledge base is working. If they're still generic, check that your files are showing as uploaded in the Project panel and re-test.

Part 5: Save Your Power Prompts as Notes

Inside the Project, click Notes and add a new note called "Power Prompts." Paste these in for quick access:

WRITE-UP:
"Write a [first/second/final] coaching notice for [name] for [incident description]. Use our discipline policy."

SHIFT HANDOFF:
"Format this shift summary into a structured handoff note: [paste your notes]"

WEEKLY GM SUMMARY:
"Write a weekly ops summary for my GM. Sales: [X%]. Labor: [X%]. Issues: [describe]. Wins: [describe]. What I need: [describe]."

JOB POSTING:
"Write a job posting for a [part-time/full-time] [position]. Pay: $[X]/hr. Perks: [list]. Schedule: [describe]."

SPANISH TRANSLATION:
"Translate this to conversational Mexican Spanish for hourly restaurant workers: [paste text]"

CORRECTIVE ACTION PLAN:
"Write a corrective action plan for [describe the problem]. Include root cause, corrective steps, owner, timeline, prevention."

Now these are one click away every time you open the Project.

Real Example: Full Week in the Manager's Knowledge Base

Monday morning: Open Claude Project → "Write a weekly ops summary for my GM. Sales were 3% under on Saturday due to equipment issue. Labor at 30% (target 28%). We're short 2 crew — I need GM approval to post 2 listings." Claude writes a professional summary in 45 seconds. You send it to your GM.

Tuesday afternoon: An employee was rude to a customer on the drive-thru. Open Claude Project → "Write a coaching notice for an employee for using dismissive language with a drive-thru customer. This is their first formal warning." Claude uses your uploaded discipline template and writes a policy-accurate notice in 60 seconds. You print, have them sign.

Wednesday: Corporate sends a new food safety training requirement in dense policy language. Open Claude Project → paste the email → "Summarize this change in plain language and write a 2-sentence huddle announcement for my crew." Claude reads your uploaded food safety procedures and produces both outputs.

Time saved across Monday–Wednesday: Approximately 90 minutes of documentation and communication work reduced to about 10 minutes.

What to Do When It Breaks

• "Claude doesn't seem to use my uploaded files" → Start your message with "Using our uploaded [document name], write..." — explicitly telling Claude which file to reference improves accuracy significantly.
• "The write-ups don't match our template" → Upload a filled-in example of the form as a reference. Claude learns format from examples better than from blank templates.
• "I can't find the Projects feature" → Make sure you're logged into Claude Pro (not the free tier). Projects is a Pro-only feature. Check billing at claude.ai/settings.
• "Claude's answers keep being too generic" → Add more store-specific context to your Project Instructions (more about your brand, your crew size, your GM's style).

Variations

• Simpler version: Use a free Claude or ChatGPT account with a saved "context message" you paste at the start of each session: "My context: QSR assistant manager at [brand], 20 crew, GM named [name], using our attendance policy which says [paste briefly]." Less powerful but free.
• Extended version: Connect your Claude Project to a Google Drive folder via Zapier so that whenever you update a policy document in Drive, it automatically updates your Claude library (requires Zapier paid plan).

What to Do Next

• This week: Complete Parts 1–4, test all three prompts, and confirm the knowledge base is working
• This month: Add any missing policy documents and refine your instructions based on what worked and what didn't
• Advanced: Invite your GM to test it for their own documentation needs — if they adopt it, the whole management team gets faster

Advanced guide for QSR Assistant Manager professionals. These techniques use more sophisticated AI features that may require paid subscriptions.