P
AI for Quality Assurance Specialist

Claude Project: Build a Personal GxP Regulatory Reference Library

Claude

For Quality Assurance Specialists

Tools: Claude Pro | Time to build: 1-2 hours | Difficulty: Intermediate-Advanced Prerequisites: Comfortable using Claude for regulatory document analysis — see Level 3 guide: "Claude for Regulatory Document Analysis"

What This Builds

You'll build a Claude Project that contains your core regulatory reference documents — the FDA guidances, ICH guidelines, and ISO standards most relevant to your work. Every conversation inside this project starts with Claude already having read your regulatory library. Instead of "let me search FDA.gov," you ask "what does ICH Q10 say about change control?" and get a cited, specific answer in seconds.

Prerequisites

  • Comfortable using Claude for document Q&A (Level 3 guide completed)
  • Claude Pro subscription ({{tool:Claude.price}}) — Projects are a Pro feature
  • Core regulatory documents downloaded as PDFs or copied as text (publicly available — FDA.gov, ICH.org, ISO excerpts)
  • 1-2 hours for initial setup; reference library improves over time

The Concept

A Claude Project is a persistent workspace where your uploaded documents and instructions stay available across every conversation you start inside it. It's like having a custom regulatory reference library where the librarian has already read everything and can answer specific questions. The difference from a normal conversation: you don't re-upload anything — the documents are always there.

Build It Step by Step

Part 1: Create the Project

  1. Log in to claude.ai with your Pro account
  2. Click Projects in the left sidebar
  3. Click New Project
  4. Name it: "GxP Regulatory Reference" or something specific like "FDA Pharma QA Reference"
  5. You'll see a project home screen with a Project Instructions area and file upload section

Part 2: Write the Project Instructions

Click in the Project Instructions area and paste:

Copy and paste this
You are a GxP regulatory compliance reference assistant for a Quality Assurance Specialist in the [pharmaceutical / medical device / food] industry.

My reference documents are uploaded in this project. When answering questions:
- Always cite the specific document name and section/paragraph number when referencing a requirement
- Distinguish between what is explicitly required vs. what is recommended or guidance
- When multiple documents address the same topic, note any differences between them
- If a question cannot be answered from the uploaded documents, say so clearly rather than speculating

Common question types I'll ask:
- "What does [document] require for [topic]?"
- "What would an auditor look for to verify compliance with [requirement]?"
- "My situation is [X] — is this compliant with [standard]?"
- "How does [document A] compare to [document B] on this topic?"

Keep answers practical and specific — I'm using these to make compliance decisions, not academic study.

Part 3: Upload Your Core Documents

Click Add files in the project and upload your regulatory documents. Start with the highest-priority references for your role:

For pharmaceutical QA:

  • FDA 21 CFR Part 211 (cGMP for Finished Pharmaceuticals)
  • ICH Q10 (Pharmaceutical Quality System)
  • ICH Q8 (Pharmaceutical Development)
  • FDA Process Validation Guidance (2011)
  • FDA CAPA guidance relevant to your products

For medical device QA:

  • ISO 13485:2016 (Medical Device QMS)
  • FDA 21 CFR Part 820 (QSR / Quality System Regulation)
  • FDA Design Controls guidance

For food/dietary supplements:

  • 21 CFR Part 111 (Dietary Supplement cGMP)
  • 21 CFR Part 117 (FSMA Preventive Controls)
  • HACCP principles document

For general manufacturing (ISO):

  • ISO 9001:2015
  • Your industry-specific standard

Upload process: Click the + or file upload icon in the project, select your PDFs. Claude indexes them and they're available in all future project conversations.

Part 4: Test Your Library

Start a new conversation inside the project and ask:

  1. "What does [one of your documents] require for document control? List all requirements with section references."
  2. "My company archives batch records for 1 year past product expiry. Is this compliant with 21 CFR 211.180? What section applies?"
  3. "What's the difference between the requirements for process validation in FDA's 2011 guidance vs. the requirements under ICH Q8?"

What good output looks like: Specific cited answers: "Section 211.68(a) states that backup file data be exact and complete, and that backup files be protected from inadvertent alteration and protected against loss..." — not generic descriptions.

Part 5: Build Usage Habits

The project gets more valuable the more you use it. Establish these patterns:

  • Before every audit: "Based on [standard], what are the 10 most commonly cited deficiencies in CAPA systems?"
  • After receiving new guidance: Upload it and ask "How does this new guidance change what was required under the previous version?"
  • During CAPA writing: "What documentation requirements does [standard] specify for CAPA effectiveness verification?"

Real Example: Pre-Inspection Preparation

Setup: You're preparing for an FDA inspection in 3 weeks. Your library contains 21 CFR 211, ICH Q10, and your recent FDA inspection observation responses.

Session 1 (Document Gap Analysis): "Based on 21 CFR Part 211 and ICH Q10, what are the most common areas where pharmaceutical manufacturers receive FDA 483 observations? List them by frequency."

Session 2 (CAPA System Check): "What specific CAPA documentation does 21 CFR 211.192 require? List each requirement as a yes/no checklist question I can use to audit our own CAPA files."

Session 3 (Training Records): "Based on cGMP requirements in 21 CFR 211, what training records are required to be maintained and for how long?"

Output across sessions: A comprehensive pre-inspection preparation guide drawn from your actual regulatory documents, in the format of specific checklist questions — far more targeted than a generic audit prep guide.

What to Do When It Breaks

  • "Claude can't access the document" → Re-upload the file; confirm it processed successfully (you'll see it listed in the project file section)
  • "Claude gives wrong citations" → Add to project instructions: "Always quote the exact text you're referencing rather than paraphrasing, so I can verify the quote."
  • "Answers are too generic" → Add to project instructions: "Do not give generic regulatory advice. Only answer from the specific documents in this project. If the answer isn't there, say so."
  • "Project is full" → Claude Pro has project storage limits; remove documents you no longer reference and add more current versions

Variations

  • Simpler version: Use the Level 3 Claude guide to upload one document at a time in regular conversations; less persistent but requires no Pro subscription
  • Extended version: Add your own internal SOPs and quality manual (redacted of sensitive information) alongside the regulatory references — Claude can then compare your internal practices against regulatory requirements

What to Do Next

  • This week: Build the project with your 3 most-referenced regulatory documents
  • This month: Use it for your next audit preparation cycle; note where answers are valuable
  • Ongoing: Add new guidance documents as FDA/ICH/ISO release updates — your library stays current

Advanced guide for quality assurance professionals. Claude Pro is required for Projects ({{tool:Claude.price}}). Only upload publicly available regulatory documents — never upload confidential company information, trade secrets, or personal health information to any AI service.