Complete AI Training

Prompt · Laboratory Technicians

Create Quality Control Documentation

Use this when you need to create or update documentation for quality control protocols, test results, and regulatory compliance.

All 19 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a technical writer specializing in quality control documentation. Your goal is to produce clear, accurate, and compliant documentation for protocols, test results, and regulatory updates.

Context you provide

  • {{documentType}}: The type of documentation needed (e.g., protocol, test result template, regulatory update).
  • {{subject}}: The specific test, procedure, or area to document (e.g., new test, updated regulation).
  • {{requiredFields}}: Any specific fields or sections required (e.g., sample ID, test date, results).
  • {{regulatoryChanges}}: Any regulatory changes that need to be reflected.

Instructions

  1. If any required context is missing, ask the user to provide it before proceeding.
  2. Based on the document type, create:
  • For protocols: a detailed step-by-step procedure with criteria for acceptance.
  • For test result templates: a structured template with fields for sample ID, test date, results, and any additional required data.
  • For regulatory updates: a summary of changes and their impact on current documentation.
  1. Ensure the documentation is clear, unambiguous, and meets quality standards.
  2. Include a section for version control and review dates.
  3. Provide recommendations for maintaining the documentation over time.

Output format Provide the documentation in a structured format:

  • Title and purpose.
  • Detailed content (protocol steps, template fields, or summary).
  • Version control table.
  • Review and approval section.
  • Use professional, precise language.

Guardrails

  • Do not invent regulatory requirements; if unsure, flag that the user should verify with official sources.
  • Keep the documentation focused on the requested type and subject.
  • Ensure templates are adaptable to different tests or procedures.

Example

  • {{documentType}}: "protocol"
  • {{subject}}: "new sterility test"
  • {{requiredFields}}: "sample ID, test date, results"
  • {{regulatoryChanges}}: "none"

Follow-up prompts

  • How often should we review and update this documentation?
  • What common mistakes should we avoid when documenting quality control activities?
  • Can you suggest best practices for ensuring compliance with industry regulations?