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 have attached or pasted using the rubric below.
SCORING RUBRIC - Inception Workplan Quality
Score each dimension 1-5 using these criteria:
DIMENSION 1: Phase Decomposition
| 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. |
|---|---|
| 4 | All four phases visible. Sub-phases partial or only shown for some phases. |
| 3 | Three of four phases visible as distinct blocks. One phase collapsed into another (e.g., analysis folded into reporting). |
| 2 | Phases not distinguished. Workplan reads as a single block from start to end. |
| 1 | No phase decomposition. Workplan is a single line on a calendar. |
DIMENSION 2: Milestone Definition
| 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. |
|---|---|
| 4 | Milestones dated and tied to deliverables. One or two missing owner or acceptance criterion. |
| 3 | Milestones listed and dated but not tied to verifiable deliverables. "Analysis complete" without a deliverable that proves completion. |
| 2 | A few milestones mentioned without dates or deliverables. "Inception phase" and "fieldwork phase" without specific dates. |
| 1 | No milestones defined. Workplan has no checkpoints. |
DIMENSION 3: Dependency Mapping
| 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. |
|---|---|
| 4 | Most major dependencies shown. One or two implicit. Critical path identifiable but not labelled. |
| 3 | Some dependencies shown. Sequential ordering implies dependency but no explicit map. Critical path not visible. |
| 2 | Activities listed in order but no dependency logic shown. Reviewer cannot tell what blocks what. |
| 1 | No dependencies shown. Activities appear to run independently when they cannot. |
DIMENSION 4: Buffer Time
| 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. |
|---|---|
| 4 | Buffer time included for most risk points. One or two underbudgeted (e.g., donor review window too short, or no holiday buffer). |
| 3 | Some buffer time included. Review cycles allotted but ethics or ground-truth delays ignored. |
| 2 | Buffer time absent or token. Every activity sized at best case. Schedule will slip on first delay. |
| 1 | No buffer time. Workplan assumes no delays anywhere, which is unrealistic for any evaluation. |
DIMENSION 5: Resource Loading
| 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. |
|---|---|
| 4 | Team assignments visible for most phases. One phase or role unclear. |
| 3 | Team listed at a high level. Phase-by-phase loading partial. Possible double-booking not flagged. |
| 2 | Team members listed without phase assignments. Effort days not visible. Concurrent activities suggest double-booking. |
| 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) | Evidence | Priority Revision |
|---|---|---|---|
| Phase Decomposition | |||
| Milestone Definition | |||
| Dependency Mapping | |||
| Buffer Time | |||
| Resource Loading |
Total: X/25 Band: Strong (22-25) / Adequate (17-21) / Needs Revision (11-16) / Substantial Revision (5-10) 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:
(See the attached or pasted document.)
Document to review: Attached, or pasted below. Base everything above on it and do not invent details that are not in it.