Create a Data Use Plan
Map out who needs what data, when, and how it will inform decisions at each level of your program.
Your Prompt
- What You Need
- Provide the decisions, users and their authority, available datasets and systems, reporting cycle, data protection rules, and known quality issues.
- Choose This Prompt When
- Choose this for how evidence reaches a decision; choose a learning agenda for open strategic questions and a MEL plan for the wider system.
Describe your goal, audience, available information and constraints. Your words are added to the prompt as supplied. You can also use the guided fields below.
Kept in this tab while you work. Copy and Start includes this description.
Copy this prompt and paste it into your AI chat to start. If it needs source material, the AI will ask for it.
Evidence and applicability: use only supplied or verifiable evidence for historical facts, values, quotations, completed activities and approvals. Preserve conflicting sources with their provenance; do not choose a preferred value without adjudication. Mark missing evidence as unknown or not evidenced, not as proof an activity never occurred. Keep proposed plans and illustrative examples separate from findings. Never invent a baseline, quote, pilot, validation or sign-off to complete a template. Match methods to the purpose and population; a suitable single-method design is valid. Distinguish descriptive change from causal attribution. Check obligations in the applicable funding agreement rather than assuming a universal donor rule.
Use only program material supplied in this chat. Ask me to paste program decisions and users, plus the existing data sources, systems, access rules, and timeframe if essential details are absent. Do not treat this request as evidence that those materials exist.
Design a data-use plan centered on the decisions the supplied program actually faces. If no decision, intended user, or data source is identified, ask for the missing essentials before describing a real data flow. Treat new systems and roles as proposals, not existing arrangements.
Provide a matrix of decision, decision owner, question, minimum necessary data, source, quality check, analysis, accessible product, timing, and feedback or action record. Show the source-to-decision flow as a compact text diagram when enough information is available. Identify who can see identifiable data, what can be shared in aggregate, retention or security constraints, and where disaggregation is useful and safe. Prefer existing systems when suitable; propose integration only where feasible. Give a cadence based on decision timing rather than defaulting to weekly or real-time feeds. Finish with gaps, responsibilities requiring confirmation, and examples explicitly labeled hypothetical.
Include short, explicitly hypothetical examples of how an analysis might inform action, showing the decision owner and what would be checked before acting.