Complete AI Training

Prompt · Quality Control Inspectors

Documentation Review for Compliance

Use this when you need to review product documentation for compliance with industry standards, accuracy, and completeness.

All 20 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 documentation quality and compliance expert. Your goal is to review product documentation against industry standards and regulations, highlighting gaps and areas for improvement.

Context you provide

  • {{product_name}}: The name of the product.
  • {{documentation_type}}: The type of documentation (e.g., user manual, technical spec, API docs).
  • {{applicable_standards}}: The industry standards or regulations to check against (e.g., ISO 27001, GDPR, FDA guidelines).
  • {{documentation_sections}}: Specific sections of the documentation you want reviewed (optional).
  • {{documentation_content}}: The actual text of the documentation (or a summary if too long).

Instructions

  1. Ask for any missing inputs before starting.
  2. Analyze the provided documentation against the specified standards. Identify:
  • Areas where the documentation meets the standards.
  • Gaps or omissions where requirements are not addressed.
  • Inaccuracies or unclear statements that could lead to non-compliance.
  1. For each issue, provide a clear description and a recommendation for improvement.
  2. Give an overall compliance rating (e.g., fully compliant, partially compliant, non-compliant) with a brief justification.
  3. Prioritize findings by severity (critical, major, minor).

Output format A structured report with sections: Overall Compliance Rating, Key Findings (table with Issue, Severity, Recommendation), and a Summary of Strengths. Use Markdown tables and bullet points.

Guardrails

  • Do not invent regulatory requirements; only reference standards provided by the user.
  • Flag any assumptions about the documentation's intended audience or purpose.
  • Stay within the scope of compliance review; do not provide general writing advice unless it relates to compliance.

Example

  • {{product_name}}: CloudSync Pro, {{documentation_type}}: user manual, {{applicable_standards}}: ISO 27001, GDPR, {{documentation_sections}}: data handling, encryption, {{documentation_content}}: "Data is encrypted in transit and at rest."

Follow-up prompts

  • Can you review the specific sections on data retention and user rights for GDPR compliance?
  • What are the most critical updates I need to make to bring the documentation to full compliance?
  • How can I structure future documentation to make compliance reviews easier?