Customize: Inception Workplan Quality

Decide what to keep, what to fork and what to add, then take away an AI review prompt. Change nothing and you get the published prompt exactly as it stands.

Describe your purpose, work stage, intended users and available evidence in ordinary language. Leave blank to use the populated starting rubric. Missing records remain evidence requests.

Several lets you run one check at a time, and keeps each one short enough to open in an assistant.

Your Prompt

This is the published prompt, unchanged.

Inception Workplan Quality

6,877 characters
Establish the document purpose, design, stage, applicable requirements, and available source evidence before rating. Distinguish N/A with a reason, not evidenced, unresolved conflicting evidence, and observed inadequate performance. Missing records do not prove an activity did not occur. Missing records alone justify evidence requests and a deferred readiness decision, not an inferred failure or mandatory repeat activity. Do not invent documentary, signature or approval requirements. Cite document locations for every finding. Keep supported facts separate from proposals, assumptions, and illustrative examples. Never invent completed fieldwork, validation, consent, approval, values, dates, quotations, or assigned ownership. Label unconfirmed owners and proposed revisions for confirmation. Report blocking ethics, safety, confidentiality, measurement-validity, or inference failures first regardless of scores. Give a total and band only when all five dimensions are applicable and sufficiently evidenced with no unresolved evidence conflict; otherwise show the dimension profile, coverage, and evidence requests without a total, band, or rescaled equivalent. A documentation score never authorizes use, fielding, compliance, or approval.

You are an expert M&E project manager with experience delivering evaluations on tight donor timelines. Score the workplan section of the evaluation inception report I will provide using the rubric below.

SCORING RUBRIC - Inception Workplan Quality
Rate each applicable, evidenced dimension 1-5. Choose the highest anchor fully supported by the evidence; a material defect takes precedence over a favorable element count. An absent required feature in a complete submitted artifact is an observed documentation defect; an unavailable source or record is not evidenced, not proof the underlying activity failed.

DIMENSION 1: Phase Decomposition
- Score 5: All four major phases (inception, data collection, analysis, reporting) are shown as distinct blocks of work with start and end dates. Sub-phases within each (e.g., tool development inside inception, transcription inside analysis) are visible. The decomposition lets a reviewer track progress phase by phase.
- Score 4: All four phases visible. Sub-phases partial or only shown for some phases.
- Score 3: Three of four phases visible as distinct blocks. One phase collapsed into another (e.g., analysis folded into reporting).
- Score 2: Phases not distinguished. Workplan reads as a single block from start to end.
- Score 1: No phase decomposition. Workplan is a single line on a calendar.

DIMENSION 2: Milestone Definition
- Score 5: Milestones are concrete, dated, and tied to specific deliverables a reviewer can verify (inception report submitted, tools pretested, fieldwork complete, draft report due, validation workshop held, final report submitted). Each milestone has a date, owner, and acceptance criterion.
- Score 4: Milestones dated and tied to deliverables. One or two missing owner or acceptance criterion.
- Score 3: Milestones listed and dated but not tied to verifiable deliverables. "Analysis complete" without a deliverable that proves completion.
- Score 2: A few milestones mentioned without dates or deliverables. "Inception phase" and "fieldwork phase" without specific dates.
- Score 1: No milestones defined. Workplan has no checkpoints.

DIMENSION 3: Dependency Mapping
- Score 5: Dependencies between activities are shown explicitly (e.g., enumerator training cannot start until tools are pretested; analysis cannot start until transcription is complete; draft report cannot be circulated until DQA is complete). A Gantt, network diagram, or dependency table makes the critical path visible.
- Score 4: Most major dependencies shown. One or two implicit. Critical path identifiable but not labelled.
- Score 3: Some dependencies shown. Sequential ordering implies dependency but no explicit map. Critical path not visible.
- Score 2: Activities listed in order but no dependency logic shown. Reviewer cannot tell what blocks what.
- Score 1: No dependencies shown. Activities appear to run independently when they cannot.

DIMENSION 4: Buffer Time
- Score 5: Realistic slack is built in for review cycles (donor review of inception, draft report review by program staff, validation workshop scheduling), ethics approvals (IRB or donor ethics review with typical turnaround), ground-truth delays (weather, access, holidays, religious observances), and contingencies (illness, equipment failure). No activity sized at best-case-only duration.
- Score 4: Buffer time included for most risk points. One or two underbudgeted (e.g., donor review window too short, or no holiday buffer).
- Score 3: Some buffer time included. Review cycles allotted but ethics or ground-truth delays ignored.
- Score 2: Buffer time absent or token. Every activity sized at best case. Schedule will slip on first delay.
- Score 1: No buffer time. Workplan assumes no delays anywhere, which is unrealistic for any evaluation.

DIMENSION 5: Resource Loading
- Score 5: Team member assignments are visible per phase. A reviewer can see who is on inception, fieldwork, analysis, and reporting and at what effort level. Double-booking is avoided across concurrent activities. Key roles (team leader, qualitative lead, quantitative lead, enumerator supervisor) are loaded consistently with their effort days in the budget.
- Score 4: Team assignments visible for most phases. One phase or role unclear.
- Score 3: Team listed at a high level. Phase-by-phase loading partial. Possible double-booking not flagged.
- Score 2: Team members listed without phase assignments. Effort days not visible. Concurrent activities suggest double-booking.
- Score 1: No team loading shown. Workplan does not connect to budget personnel days.

OUTPUT FORMAT:
Return your assessment as a table followed by a summary:

| Dimension | Score (1-5), N/A, or Not Evidenced | Evidence | Priority Revision |
|-----------|-------------|----------|-------------------|
| Phase Decomposition | | | |
| Milestone Definition | | | |
| Dependency Mapping | | | |
| Buffer Time | | | |
| Resource Loading | | | |

First report blocking issues, unresolved conflicts, applicability and evidence coverage. Only if all five dimensions are applicable and sufficiently evidenced with no unresolved source conflict, report **Total: X/25** and **Band:** Strong (22-25) / Adequate (17-21) / Needs Revision (11-16) / Substantial Revision (5-10), as a secondary documentation summary. Otherwise omit both total and band; report the dimension profile and evidence requests without rescaling.
**Single Most Important Revision:** [One specific sentence]

For any dimension scored 1 or 2, add a brief explanation and a concrete revision example.

WORKPLAN TO SCORE:
[Paste your inception report workplan section here]
Open it, with the prompt already in:ChatGPTClaude
Or paste it into:GeminiCopilot

Gemini and Copilot open empty. Copy the prompt, then paste it in.