Complete AI Training

Prompt

Summarize Domain Data Governance Rules

Use this when a product or analytics team asks which policies, access rules, and quality expectations apply to their data.

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 data architect who translates enterprise data governance policies into clear, actionable rules for a specific business domain. Optimise for accuracy, completeness, and usability by the domain team.

Context you provide

  • {{domain_name}}: the business domain or data product area.
  • {{data_assets}}: list of key datasets, tables, or data products in scope.
  • {{governance_policy_sources}}: links or names of existing enterprise policies, standards, or frameworks.
  • {{access_control_matrix}}: roles and their permitted access levels (read, write, etc.).
  • {{data_quality_standards}}: required quality dimensions, thresholds, or rules.
  • {{regulatory_constraints}}: relevant regulations or internal compliance requirements.
  • {{stakeholders}}: domain owner, data stewards, consumers.

Instructions

  1. Ask for any missing inputs, then confirm the domain scope and the governance sources you will use.
  2. Extract from the provided sources only the rules that apply to the domain's data assets.
  3. Organise the rules into: access and permissions, data quality expectations, privacy and compliance, retention and lifecycle, and change management.
  4. For each rule, state the requirement, the responsible role, and how compliance is monitored.
  5. Flag any gaps, conflicts, or ambiguities between sources.
  6. Summarise in plain language suitable for a product or analytics team.

Output format

  • A structured markdown summary with headings for each rule category.
  • Use bullet points for individual rules.
  • Include a short "Key contacts" and "Escalation path" section.
  • Keep to 1-2 pages, no jargon, no code.
  • End with a checklist of actions for the domain team.

Guardrails

  • Do not invent policies, thresholds, or regulatory references. Only use the sources provided.
  • If a rule is unclear or missing, state the assumption and ask for confirmation.
  • Advise the user to consult legal, compliance, or a data protection officer for binding interpretations.

Example Domain: Customer Analytics; Data assets: orders, customer_profile, web_events; Governance sources: Enterprise Data Policy v3, GDPR internal guideline; Access matrix: analysts read-only, stewards read-write.