Claude Project: Build Your Persistent EHS Research Assistant

What This Builds

You'll configure a Claude Project — a persistent AI workspace that retains context across all your conversations — as a dedicated EHS research and drafting assistant. Unlike regular Claude conversations that forget everything between sessions, your Project remembers your facility's industry, your common hazards, your OSHA history, and your document style. Every document you draft, every regulatory question you research, picks up where you left off.

The result: you stop re-explaining your facility context in every AI conversation. Claude already knows you work at a chemical plant with 12 confined spaces and a history of ergonomic incidents in the packaging department — and every output reflects that.

Prerequisites

• Claude Pro subscription ({{tool:Claude.price}}) — Projects require a paid account
• Key facts about your facility: industry, size, major hazards, common compliance challenges
• 3–5 of your most important safety documents (programs, JHAs, incident history summary)
• 30 minutes to configure; 30 minutes to test

The Concept

A Claude Project is like having a safety consultant who has been embedded at your facility for years. Every conversation builds on the last — you don't start from scratch explaining your NAICS code and which state plan you're in every time. You set up the context once, upload your key documents, and then every conversation Claude has for this Project has that foundation baked in. It's the difference between "explain lockout/tagout" (generic) and "how does our LOTO program need to change now that we installed the new packaging line?" (facility-specific).

Build It Step by Step

Part 1: Create the Project

1. Sign in at claude.ai with your {{tool:Claude.plan}} subscription
2. In the left sidebar, click + New Project
3. Name it something like "EHS Compliance — [Facility Name]"
4. You'll land in the Project workspace with a chat interface and a panel for Project instructions and files

Part 2: Write Your Project Instructions

Click the Project Instructions area (pencil icon or settings gear). This is the context that Claude carries into every conversation in this Project. Write a brief but specific description of your facility:

Context about my facility and role:

I am an EHS Specialist at [company name], a [industry] facility located in [city, state]. The facility has approximately [number] employees and operates [shifts].

Key operations and hazards:
- [List 3-5 major operations, e.g., "press operations with LOTO requirements", "confined spaces in utility basement", "chemical handling in mixing area"]

Regulatory context:
- We are in [state] — [Federal OSHA or state plan name if applicable]
- Common standards we work under: [list 3-4 most relevant OSHA standards]
- Our TRIR last year was [X]; most frequent incident types: [list]

My working style preferences:
- When I ask you to draft a document, match the tone and format of the documents I've uploaded
- For compliance questions, always verify the specific standard applies to my state
- Flag any areas where my state may have stricter requirements than Federal OSHA

Things I commonly need help with:
- Incident investigation reports following accidents or near-misses
- JHA development for maintenance and production tasks
- Regulatory research for new processes or equipment
- Training content and toolbox talks
- Written program updates when regulations change

Part 3: Upload Your Key Documents

In the Project Files section, upload your most important documents (PDF or Word):

• Your current written safety programs (LOTO, HazCom, Confined Space)
• Your facility's PPE matrix or hazard assessment
• An anonymized incident summary (last 12 months — types, departments, causes)
• Your most-used JHA templates

Claude will reference these documents in every conversation, so outputs will reflect your actual programs rather than generic examples.

Part 4: Set Up Conversation Templates

Start a few conversations in the Project with standard prompts you'll use repeatedly. Save the ones that work best as favorites or pin the conversation. For example:

Incident Report Conversation: "I need to write an incident investigation report. Here are the facts: [facts]. Write the full report in the format consistent with our existing programs."

JHA Conversation: "I need a JHA for [task]. Write it in the same format as the JHAs I've uploaded."

After a few uses, Claude will naturally match your facility's document style without you having to specify it.

Part 5: Test with Real Work

Before relying on the Project for critical documents, test it with 3 real tasks from your queue:

1. Ask it a regulatory question about your facility and verify the answer reflects your state
2. Ask it to draft a document and verify it matches your facility's format and tone
3. Ask about a hazard specific to your facility and verify it references your uploaded programs

Real Example: EHS Research Assistant in Action

Setup: An EHS Specialist at a plastics manufacturing plant in Michigan sets up the Project with context about Michigan OSHA (MIOSHA), their four major chemical hazards, and uploads their LOTO and HazCom programs.

Input (3 weeks later, new conversation): "We're adding a new injection molding machine next month. What do I need to update in our safety programs and what training is required before startup?"

Output: Claude responds knowing this is a Michigan facility (MIOSHA requirements), knows the facility already has a LOTO program it can reference, identifies that a machine-specific LOTO procedure needs to be written and adds it to the existing program format, notes the HazCom implications if the machine uses hydraulic fluid or mold release agent, and recommends pre-startup review checklist based on the facility's existing programs.

Without the Project: The same question to regular Claude would give generic OSHA advice with no Michigan context, no reference to existing programs, and no facility-specific formatting.

Time saved: 30-minute research session becomes 10 minutes of review and editing.

What to Do When It Breaks

• Forgets context between sessions → You're not in a Project — make sure you're opening conversations from within the Project, not from the main chat page
• Ignores uploaded documents → Ask explicitly: "Based on the LOTO program I've uploaded, what changes are needed?" — explicitly referencing the upload helps
• Gives state-generic advice → Update your Project Instructions to be more explicit: "I am in Michigan under MIOSHA. Always check if Michigan has additional requirements."
• Document format drifts → Paste an example of the exact format you want and say "format all future documents like this"

Variations

• Simpler version: Use Claude Projects without document uploads — just the context instructions. This alone saves 5–10 minutes per conversation from not re-explaining your facility.
• Extended version: Create multiple Projects — one for incident investigations, one for regulatory research, one for training content — each optimized for different types of work.

What to Do Next

• This week: Set up the Project and configure the instructions with your facility context
• This month: Upload your 3–5 most important documents and run 10 real tasks through it
• Advanced: Add your facility's incident history data (anonymized) so Claude can reference actual trends in your operation when identifying high-priority hazards

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