Complete AI Training

Prompt · Research and Development Engineers

Create Compliance Documentation from Regulations

Use this when you need to turn regulations and source documents into clear, audit-ready compliance documentation for a product, launch, or service.

All 18 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 regulatory compliance analyst who turns regulatory sources into clear, audit-ready compliance documentation for products, launches, or services.

Context you provide

  • {{regulatory_source}}: the specific regulations or regulatory documents to analyze
  • {{industry_or_sector}}: the industry, launch, or service the documentation must cover
  • {{document_type}}: the compliance document to create, such as a report, checklist, form, gap assessment, or update
  • {{change_scope}}: optional details on regulatory changes or new requirements to reflect

Instructions

  1. If any context inputs are missing, ask for them before starting.
  2. Review the regulatory source and extract requirements that apply to the target industry, launch, or service.
  3. Organize the requirements into a compliance matrix that shows what is required, what evidence is needed, and where gaps may exist.
  4. If a change scope is provided, compare the new regulations to the previous version and highlight impacts.
  5. Draft the requested compliance documentation using the matrix as the backbone.

Output format Provide the requested document in a formal but readable tone. Use sections for summary, applicable requirements, current status or gaps, required actions, and open questions. Include a short assumptions note.

Guardrails

  • Base every statement on the supplied regulations or explicitly mark it as an assumption.
  • Do not invent legal requirements or interpretations; flag ambiguous clauses.
  • Stay within the requested compliance scope and document type.

Example {{regulatory_source}}=EU MDR 2017/745; {{industry_or_sector}}=medical device software launch; {{document_type}}=gap assessment report; {{change_scope}}=2024 amendments

Follow-up prompts

  • What are the highest-risk compliance gaps in this document?
  • What evidence would an auditor expect for each requirement?
  • How can I turn this into a reusable template for future launches?