M&E StudioTools

Draft, check and improve: Inception Workplan Quality

Draft, check and improve: Inception Workplan Quality: Your prompt

Run these one after another in the same chat: send the draft prompt and wait for the draft, then send Check, then Improve.

Writes the draft, with the criteria as the bar it must meet.

You are an expert M&E project manager. Generate an inception report workplan section for the evaluation described in the brief below. The workplan must score Excellent (5) on every dimension of the Inception Workplan Quality rubric.

QUALITY REQUIREMENTS:

Phase Decomposition: Show four distinct phase blocks (inception, data collection, analysis, reporting) each with start and end dates. Decompose into sub-phases where useful (tool development, pretesting, training inside inception; transcription, coding, statistical analysis inside analysis). Make progress trackable phase by phase.

Milestone Definition: Define concrete, dated milestones tied to verifiable deliverables. Typical milestones: inception report submitted, tools pretested, enumerator training complete, fieldwork complete, transcription complete, draft report due, validation workshop held, final report submitted. Give each milestone a date, owner, and acceptance criterion.

Dependency Mapping: Show dependencies between activities explicitly. Use a Gantt chart or dependency table. Make the critical path visible. Common dependencies: tool finalization before training; training before fieldwork; transcription before coding; DQA before draft circulation; donor review before final report.

Buffer Time: Build realistic slack into the schedule for review cycles (donor, program staff), ethics approvals, ground-truth delays (weather, access, holidays, observances), and contingencies. Avoid best-case-only sizing for any activity on the critical path.

Resource Loading: Show team member assignments per phase with effort levels. Avoid double-booking across concurrent activities. Match key role loading (team leader, qualitative lead, quantitative lead, enumerator supervisor) to the personnel days in the budget.

FORMAT: Present as: (1) Gantt chart or timeline table showing phases, sub-phases, and dates; (2) Milestone table with deliverable, date, owner, acceptance criterion; (3) Dependency map or table; (4) Buffer summary identifying where slack is built in and why; (5) Resource loading table by team member and phase.

EVALUATION BRIEF:

[Paste your evaluation scope, methods, geography, team composition, ethics requirements, and target completion date here]

Quality bar: The result must meet these criteria. It will be reviewed against them afterwards.

  • Phase Decomposition: Whether inception, data collection, analysis, and reporting phases are all visible as distinct blocks of work with start and end dates, rather than collapsed into a single timeline bar.
  • Milestone Definition: Whether milestones are concrete, dated, and tied to specific deliverables that a reviewer can verify (inception report submitted, draft report due, validation workshop held).
  • Dependency Mapping: Whether dependencies between activities are shown so a reviewer can see what blocks what (e.g., enumerator training cannot start until tools are pretested).
  • Buffer Time: Whether realistic slack is built in for review cycles, ethics approvals, ground-truth delays, and contingencies rather than every activity sized at best-case duration.
  • Resource Loading: Whether team member assignments are visible per phase so a reviewer can see who does what and when, and whether anyone is double-booked across concurrent activities.

Anything still in [brackets] is not known yet: ask me, or mark it clearly in your answer.

Rubric · Create a Document · about 467 words

Score the workplan section of an evaluation inception report for timeline realism, milestone clarity, and dependency mapping.

You'll Need

Your inception report workplan section

You Get Back

A draft, then a check, then an improved version, in one chat

Criteria