M&E StudioTools

Review a MEL Data Flow Diagram

Review a MEL Data Flow Diagram: Your prompt

You are a senior MEAL specialist reviewing the data flow diagram inside the MEL plan for "program name" (from the material, if given) before it is finalized.

DATA FLOW DIAGRAM TO REVIEW (paste the diagram or its narrative description): "data flow diagram" (from the material, if given)

Review Requirements:

  1. Completeness of flow. Verify the diagram covers the full path from data source to decision-maker, including every collection, entry, storage, analysis, and reporting step. Flag steps that are implied but not drawn.
  2. Role assignment clarity. Check that responsible positions are named at every transition point. Flag handoffs where ownership is ambiguous or unassigned.
  3. System specification. Confirm that the tools and platforms used (specific forms, databases, dashboards, file shares) are named at every storage and transfer point, not described generically.
  4. Quality gates and verification. Verify that validation, cleaning, and review steps are explicit in the flow, with named checks placed before data is used for analysis or reporting.
  5. Feasibility and context fit. Assess whether the flow is realistic given program staffing, field connectivity, device availability, and reporting cycles described elsewhere in the MEL plan. Flag steps that depend on systems that are not yet in place.

If the material is incomplete: Work only from the data flow diagram or its narrative description as provided. If a step, role, system, or quality gate needed to assess a dimension is missing or unclear, say so under that dimension and note how it limits the review, then continue with the rest. Do not invent tools, roles, or verification steps the diagram does not show.

Output Format:

Produce:

  1. A 1-paragraph overall assessment.
  2. A scored review table by dimension (completeness, role clarity, system specification, quality gates, feasibility), with score, evidence, and recommended action.
  3. A prioritized revision list (must-fix vs. should-fix).
  4. A short note on whether the data flow diagram is ready for sign-off or requires another revision.

Where the material is silent, write "Not in the material" rather than guessing.

Document to review: Attached, or pasted below. Base everything above on it and do not invent details that are not in it.

Prompt · Review a Document · about 354 words

A prompt that scores it against the standard, with evidence.

You'll Need

Your document

You Get Back

A scored review with the evidence and the fixes

Parts