Claude Project: Build a Conversational Plant Policy Reference

What This Builds

Instead of digging through binders and shared drives to find a policy when you need it right now, you'll build a Claude Project that holds your plant's key HR policies, safety standards, and disciplinary procedures. You ask it a question in plain language — "What's our policy on consecutive absences?" or "What PPE is required in the chemical storage area?" — and it gives you the answer immediately, with the relevant policy language, so you can act confidently.

Prerequisites

• Claude Pro subscription ({{tool:Claude.price}}/month) — Projects require a paid account
• PDF or text versions of 3–5 key documents (attendance policy, progressive discipline policy, key safety procedures, company handbook sections you reference most)
• 1–2 hours for setup and testing

The Concept

A Claude Project is like having a new HR partner who has read your entire policy binder and can answer any question about it in plain language — instantly, at 11 PM during a difficult conversation with an employee, when HR is closed and you need to know whether this is a formal warning situation. You load your company's actual policies once. Claude reads and remembers them. You ask questions; it gives you policy-grounded answers.

Build It Step by Step

Part 1: Gather your key policy documents

Collect PDFs, Word files, or even plain text copies of the policies you reference most often:

• Attendance policy (most supervisors need this constantly)
• Progressive discipline procedure (what counts as verbal warning vs. written vs. termination)
• Key safety standards (your plant's chemical handling, confined space, LOTO, PPE requirements)
• Code of conduct / harassment policy (for when employees raise complaints)
• FMLA/leave policy basics (know when to involve HR vs. handle directly)

You don't need everything — start with 3–5 documents you reference weekly.

Part 2: Create a new Claude Project

1. Log in at claude.ai with your Pro account
2. Click Projects in the left sidebar
3. Click + Create project
4. Name it: "Plant Policy Reference — [Your Plant Name]"

What you should see: A project workspace with a chat area and a sidebar for documents/knowledge.

Part 3: Upload your policy documents

1. In the project, click Add content or look for the + icon in the knowledge sidebar
2. Upload each policy document (PDF or text)
3. Claude reads and indexes them automatically

What you should see: Your uploaded documents listed in the project knowledge base.

Troubleshooting: If documents are scanned PDFs (not searchable text), you may need to copy-paste the text content instead. Use your phone or scanner app to OCR handwritten policy pages.

Part 4: Add a project instruction

In the Project instructions or system prompt area, add:

You are a plant policy reference assistant for production supervisors. Your job is to answer questions about HR policies, safety standards, and disciplinary procedures using the documents in this project's knowledge base.

When answering:
- Quote the relevant policy language and cite which document it's from
- Translate policy into plain language — what does this mean for me as a supervisor RIGHT NOW
- Flag when I should involve HR directly rather than handling myself
- Never give legal advice — refer employment law questions to HR or legal
- Be direct: answer the question first, then provide context

This is for real-time use during a shift when I need a quick, accurate answer about a policy.

Part 5: Test with real questions

Ask your most common questions to verify it's working:

1. "What's our policy on employees arriving late to their workstation after breaks?"
2. "How many unexcused absences triggers a written warning under our attendance policy?"
3. "What PPE is required when handling cleaning chemicals in the production area?"
4. "An employee just told me they need FMLA leave starting next week. What's my role vs. HR's role?"

What good output looks like: Claude quotes the relevant policy section, tells you what number of occurrences triggers what step, and tells you what to do next — specific enough to act on.

Troubleshooting: If Claude doesn't find a specific answer, it will tell you the document doesn't cover that question. That's useful too — it means you need to ask HR directly.

Real Example: Night Shift, Employee Issues

Setup: Supervisor James has loaded his plant's attendance policy, progressive discipline procedure, and HR handbook sections into a Claude Project on his phone.

Situation: It's 2 AM. An employee just had their 4th unexcused absence. James needs to know if this triggers a formal write-up tonight or waits for day shift HR.

He asks: "An employee just called out — this is their 4th unexcused absence in the past 60 days. Our attendance policy is uploaded. What step are we at in the discipline process and do I need to document anything tonight?"

Claude answers: "Per your attendance policy, 4 unexcused absences within 60 days triggers a first written warning. You are not expected to issue the written warning during the shift — this should be done by a supervisor with HR support during business hours. However, you should: (1) Document the absence as unexcused in Kronos tonight, (2) Write a brief note for your own records: date, time, employee name, reason given for absence. Bring this documentation to HR tomorrow to process the written warning. Do not verbally inform the employee tonight that a written warning is coming without HR present."

Time saved: 20 minutes of searching through binders at 2 AM → 30 seconds.

What to Do When It Breaks

• Claude says it can't find the answer in the documents → The policy may not be loaded, or the question is outside what's documented; ask HR directly
• Policy document is outdated in the system → Delete the old file and upload the current version; Claude uses the most recent version
• Claude gives a confident answer that seems wrong → Cross-check against the actual policy document before acting on it — Claude can occasionally misread complex policy language
• Long policy documents aren't being referenced → Try uploading in smaller sections; very long documents sometimes get partially indexed

Variations

• Simpler version: Just paste 3–4 key policy sections directly into the Project instructions as plain text instead of uploading files — less organized but gets you 80% of the way there
• Extended version: Add your plant's safety data sheets (SDS) for chemical handling, your quality system's control plan, and corrective action procedure for a complete operational reference

What to Do Next

• This week: Upload your attendance policy and progressive discipline procedure — those are the two you need most often
• This month: Add 3 more documents; refine the system prompt based on what questions it handles well vs. poorly
• Advanced: Share the project framework with your plant's full supervisor team so everyone references the same consistent policy source

Advanced guide for production supervisor professionals. Requires Claude Pro subscription ({{tool:Claude.price}}/month).