What to provide
Sources, business question, identifiers, permissions, and known quality problems.
What you will get
A source inventory, proposed mappings, quality checks, and a read-only pilot plan.
Example: Customer records appear in a CRM and two spreadsheets. Flag conflicting IDs and definitions before proposing joins.
Copy the full prompt
Customize the bracketed fields.
Use approved business information and have a person review the result before acting.
Help plan data aggregation for [business question].
Sources: [databases, spreadsheets, APIs, exports]
Entities and identifiers: [customers, orders, jobs, IDs]
Refresh needs: [frequency]
Permissions and restrictions: [rules]
Known problems: [duplicates, gaps, mismatched definitions]
Do not request credentials or live personal records. Start with schemas or fictional samples. Inventory each source, owner, grain, keys, field definitions, date and time conventions, access requirements, and provenance. Identify join risks, duplicate handling, missing values, stale records, conflicting definitions, and reconciliation checks. Propose a mapping table and read-only pilot with measurable quality thresholds. Separate source facts from assumptions. Do not execute queries, modify schemas, merge records, or write data without explicit approval. Produce a plan for review, with open questions and evidence needed.
Response requirements:
- Begin with a short summary of the goal, confirmed facts, assumptions, and missing information.
- Ask focused clarification questions before completing the work when a missing answer would materially change the result.
- Use clear headings, tables, checklists, or numbered steps where they make the output easier to use.
- Keep source facts separate from recommendations. Quote or cite supplied evidence when the task depends on source material.
- Mark unsupported details, decisions, owners, dates, costs, credentials, and commitments as [TO CONFIRM].
- Identify the three most important risks, failure conditions, or quality checks.
- End with a practical next-action checklist that names the responsible role and the evidence needed to confirm completion.
- Include a final self-review: check the answer against this prompt, list any unmet requirement, and correct it before responding.
- Do not claim that you accessed a system, verified an external fact, completed an action, or tested the result unless evidence in this conversation proves it.Version 1.0 · Updated 2026-10-10 · Free starter template. Evaluate the output in your approved environment.