Inception Workplan Quality

Last Updated:

On this page

Prepare Your Assessment

Purpose: Score the workplan section of an evaluation inception report for timeline realism, milestone clarity, and dependency mapping. Paste the workplan to assess whether the evaluation will deliver on time.

Materials: The ToR or inception draft, agreed scope and questions, proposed methods and sampling rationale, workplan, roles, resource constraints and ethics provisions.

Stage: State the stage and intended decision. Assess a plan by its documented provisions; completed work requires actual records.

Use: Read the criteria and record located evidence, applicability, ratings and priority revisions. Request missing records. Check AI quotations, source locations, requirements, and scores against the sources; missing evidence does not justify a low score.

Limits: Document quality does not establish readiness, authorization or compliance. Scores remain provisionally checked.

Adaptation and Comparability

Presentation and answer-language changes generally preserve meaning. Changing criteria, anchors, scale or strictness can change the assessment: label it adapted and do not compare its totals with the original rubric. Short mode removes two anchors and requires interpolation. Missing evidence calls for a request for records, not removal of the criterion. These scoring bands are provisionally checked, not practitioner-validated.

Related Reviews and Focused Checks

Start with a full review, then use a focused check for a specific weakness. Do not combine related rubric totals.

AI Prompt Templates

Add your material in the same chat. Context is optional; completed records must come from you.

Assess supplied evidence, report blockers and gaps, and give located findings and priority revisions. Incomplete evidence means no total.

6,877 characters
Adapt this rubric
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.

Governing evidence and applicability rules (take precedence over aggregate bands): establish the document purpose, design, stage and available evidence before rating. A fit-for-purpose single-method design can earn the highest applicable rating; do not require complexity, mixed methods or two sources for every finding. Distinguish applicable, not applicable with reason, not evidenced, and observed inadequate. Report applicable coverage and the raw denominator. If any dimension is N/A or not evidenced, report the profile and gaps without a 25-point band or an unvalidated rescaled equivalent. Never interpret missing documentation as proof no activity occurred. Use source-linked historical facts only; keep proposed work and illustrative examples separate. Preserve unresolved source conflicts. Do not invent baseline values, quotations, fieldwork, pilots, validation, consent or approvals to improve a score. A serious consent, confidentiality, safeguarding, measurement-validity or unsupported-inference failure is a blocking issue regardless of the total, including 22/25. High document-quality scores do not establish legal compliance, instrument readiness, field authorization or donor approval. Accountable human review against the applicable protocol is separate. A well-documented failed pilot may score 25/25 for documentation while remaining not ready for fielding.

Use This Rubric

Bring: the evaluation scope, deliverables, effort-day budget, team availability, dependencies, review windows, and approval requirements.

Stage: State whether this is a proposed design, a draft, or a report of completed work. Assess planned procedures as plans; require records before claiming they occurred. A complete submitted document can have an observed documentation defect even when the underlying activity is unknown.

Limits: Apply requirements to the stated purpose, methods, population, and risk. Do not impose extra methods or sensitive data collection solely to increase a score. These editorial anchors are provisionally checked, not practitioner-calibrated.

Scoring Criteria

Phase Decomposition
5Excellent

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.

4Good

All four phases visible. Sub-phases partial or only shown for some phases.

3Adequate

Three of four phases visible as distinct blocks. One phase collapsed into another (e.g., analysis folded into reporting).

2Needs Improvement

Phases not distinguished. Workplan reads as a single block from start to end.

1Inadequate

No phase decomposition. Workplan is a single line on a calendar.

Milestone Definition
5Excellent

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.

4Good

Milestones dated and tied to deliverables. One or two missing owner or acceptance criterion.

3Adequate

Milestones listed and dated but not tied to verifiable deliverables. "Analysis complete" without a deliverable that proves completion.

2Needs Improvement

A few milestones mentioned without dates or deliverables. "Inception phase" and "fieldwork phase" without specific dates.

1Inadequate

No milestones defined. Workplan has no checkpoints.

Dependency Mapping
5Excellent

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.

4Good

Most major dependencies shown. One or two implicit. Critical path identifiable but not labelled.

3Adequate

Some dependencies shown. Sequential ordering implies dependency but no explicit map. Critical path not visible.

2Needs Improvement

Activities listed in order but no dependency logic shown. Reviewer cannot tell what blocks what.

1Inadequate

No dependencies shown. Activities appear to run independently when they cannot.

Buffer Time
5Excellent

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.

4Good

Buffer time included for most risk points. One or two underbudgeted (e.g., donor review window too short, or no holiday buffer).

3Adequate

Some buffer time included. Review cycles allotted but ethics or ground-truth delays ignored.

2Needs Improvement

Buffer time absent or token. Every activity sized at best case. Schedule will slip on first delay.

1Inadequate

No buffer time. Workplan assumes no delays anywhere, which is unrealistic for any evaluation.

Resource Loading
5Excellent

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.

4Good

Team assignments visible for most phases. One phase or role unclear.

3Adequate

Team listed at a high level. Phase-by-phase loading partial. Possible double-booking not flagged.

2Needs Improvement

Team members listed without phase assignments. Effort days not visible. Concurrent activities suggest double-booking.

1Inadequate

No team loading shown. Workplan does not connect to budget personnel days.

Score Interpretation

Report blockers, the dimension profile, and evidence coverage first. Use these aggregate bands only when all five dimensions are applicable and sufficiently evidenced with no unresolved evidence conflict. Otherwise give no total, band, or rescaled equivalent. High documentation quality does not establish readiness, legal compliance, or approval.

Total (out of 25)BandNext Step
22-25StrongStrong documentation profile only. Resolve blocking issues and obtain the applicable human review; this score does not authorize use.
17-21AdequatePrioritize source-linked revisions in the weakest dimensions. Request missing records before proposing additional activity; confirm the need for any new work from evidence.
11-16Needs RevisionUse located findings as a revision brief. Distinguish reporting gaps from demonstrated design or implementation failures and label proposed work for confirmation.
5-10Substantial RevisionRework the evidence-backed weaknesses with accountable review. A low documentation profile alone does not establish that the underlying activity failed or must be repeated.
Did this page help?