P
AI for Operations Manager

Claude Project: Your Persistent Operations Writing Assistant

An AI That Knows Your Standards, Gets Better Over Time

Tools: Claude Pro | Time to build: 1-2 hours | Difficulty: Intermediate-Advanced Prerequisites: Comfortable using Claude for document drafting — see Level 3 guide: "Weekly Ops Report Writing with Claude Pro"

What This Builds

A Claude Project configured with your company's writing standards, document formats, and operational context — so that every time you open it, Claude already knows your SOP structure, your KPI names, your leadership audience, and your writing style. It's the difference between having to re-explain your company every conversation vs. picking up exactly where you left off, every time.

Prerequisites

  • Claude Pro subscription ($20/month at claude.ai)
  • Your key document templates and writing samples
  • 1–2 hours for initial setup

The Concept

A Claude Project is like creating a dedicated workstation for a specific job. Instead of a generic workspace where you start from scratch every time, your Project workspace comes pre-loaded with your context, your files, and your instructions. Every conversation in the Project inherits that foundation automatically.

Think of it as the difference between calling a general-purpose temp agency vs. hiring someone who spent their first week reading your operations manual. The Project is the operations manual.

Build It Step by Step

Part 1: Prepare Your Reference Materials

Step 1: Identify the key documents and standards you want Claude to know:

  • Your best examples of each document type (SOP, RCA, PIP, weekly report, escalation)
  • Your KPI definitions and target ranges
  • Your organizational context (type of operation, size, industry)
  • Your leadership audience profile (who reads your reports? what do they care about?)

Step 2: Anonymize your documents if they contain sensitive information (client names, employee names, specific financial data). Replace with "[CLIENT NAME]", "[EMPLOYEE ID]", etc.

Step 3: Save 1–2 example documents per type as Word or text files.

Part 2: Create Your Claude Project

Step 1: Log into claude.ai (Claude Pro required). In the left sidebar, look for Projects. Click + New Project.

Name it: "Operations Writing Assistant — [Your Facility/Company]"

What you should see: A Project workspace with a system prompt area on the left and a file upload section.

Step 2: Upload your example documents. In the Project Files section, upload your anonymized example documents. Claude will use these as reference for every conversation in this Project.

Step 3: Write your Project Instructions. Click on the Instructions area and paste the following (customize the [brackets]):

Copy and paste this
You are an operations writing assistant for [type of facility — e.g., an e-commerce fulfillment center / manufacturing plant / distribution center]. You help the operations manager produce professional operational documents quickly.

OPERATIONAL CONTEXT:
- Facility type: [describe]
- Operation size: [# employees, shifts, volume]
- Industry: [retail/logistics/manufacturing/etc.]
- ERP/WMS: [SAP/NetSuite/etc.]
- Key metrics tracked: Throughput (target: [X] units/day), OTD (target: [X]%), Labor Cost/Unit (target: $[X])

DOCUMENT FORMATS (follow the uploaded examples exactly):
- SOPs: Use the format from "SOP Example.docx"
- RCAs: Use the format from "RCA Example.docx"
- PIPs: Use the format from "PIP Example.docx"
- Weekly Reports: Use the structure from "Weekly Report Example.docx"

WRITING STANDARDS:
- SOPs: Active voice, numbered steps, specific decision points, no passive constructions
- RCAs: 5-Why format, corrective actions with owner and due date
- PIPs: Specific and measurable performance standards — never vague
- Weekly Reports: Executive summary first, data-backed, under 500 words total
- All documents: No corporate jargon, no filler phrases, no passive voice

AUDIENCE:
- Immediate supervisor: [VP of Operations / COO / etc.] — cares about cost and SLA performance
- Frontline employees: [warehouse associates, production workers] — need clear, simple language

When I ask for a document, draft from the information I provide. If something is missing, note it in brackets (e.g., [FILL IN: supervisor name]) rather than stopping to ask. I'll fill in gaps during review.

Step 4: Save the Instructions.

Part 3: Test Your Project

Step 1: Start your first conversation in the Project. Test each document type:

"Write an SOP for our end-of-shift quality inspection process. Steps: inspector walks each production line, checks defect bins, records count in QMS, flags any line with >2% defect rate for supervisor review, signs off on inspection log."

Step 2: Compare the output to your uploaded example. Does it:

  • Match the section structure of your example SOP?
  • Use the same header format?
  • Apply the same active-voice, numbered style?

Step 3: Refine Instructions if needed. Common refinements:

  • "Always use exactly this header format: [paste your header example]"
  • "Never include a 'References' section in SOPs — we don't use that"
  • "Weekly report executive summary must be 3 sentences maximum"

Part 4: Build Your Personal Template Library

Over time, use the Project to build a library of standard templates you can reuse:

In your Project, start conversations with: "Create a template for [document type] that we can reuse for future [situations]. Make it fill-in-the-blank with [BRACKETS] where the specific information goes."

Save the Claude output in a Word document titled "Template Library." Over time, this library becomes your own, Claude-generated toolkit of operational document templates.

Real Example: A Full Week Using the Project

Monday: Open the Project. "Write an SOP for our new inbound inspection process. [5-sentence description]." Done in 3 minutes. SOP matches your company's format exactly.

Tuesday: "Write an RCA for last Friday's shipping error. [4 bullet points of what happened]." Done in 2 minutes. RCA follows your 5-Why format.

Wednesday: "Draft a vendor escalation to [carrier type] about their 87% OTD last month vs. our 96% contract. Business impact: 12 late deliveries. Request: remediation plan by March 31." Done in 90 seconds.

Thursday: "Prepare my weekly report data template for tomorrow. My KPIs were: [paste data]." Claude writes the report narrative in your standard format.

Friday: Review Claude's draft, add 2 sentences of context, forward to VP.

Total writing time for the week: ~25 minutes.

What to Do When It Breaks

  • Claude ignoring your uploaded documents → Check that the files were actually uploaded to the Project (should appear in the Project Files list). If the files are PDFs, try converting to Word — some PDFs parse poorly.
  • Document format inconsistent between conversations → Your Instructions may need more specificity. Add a section: "REQUIRED STRUCTURE FOR SOPs: (1) Header Table → (2) Purpose → (3) Scope → (4) Procedure → (5) Decision Points → (6) Revision History. Never deviate from this order."
  • Output too long or too short → Add length guidance to Instructions: "Weekly reports must be 400-600 words total. SOPs can be as long as needed to cover all steps — no artificial length limits."
  • Claude adding unsolicited sections → Add: "Only include sections that are explicitly in the template format or that I request. Do not add sections on your own initiative."

Variations

  • Simpler version: Skip the Projects feature and just save a detailed prompt template in a Notes app or Word doc. Paste it at the start of each Claude conversation. Less elegant but works on the free plan.
  • Extended version: Create separate Projects for different audiences — one for leadership documents (executive style), one for frontline documents (simple language), one for vendor communications (firm but professional).

What to Do Next

  • This week: Create the Project with your Instructions and 2 example documents. Test with 3 different document requests.
  • This month: Add more examples and refine your Instructions based on what the Project gets right and wrong. Build your template library.
  • Advanced: Share your Project setup approach (not the specific Project) with a peer ops manager at another site — you'll both benefit from comparing what works.

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