Review an Inception Stakeholder Engagement Plan
Review the stakeholder engagement plan in an inception report for identification, mode specificity, timing, feedback, and accountability.
- What You Need
- Share the inception engagement section, safe stakeholder mapping, questions, timeline, access needs and disclosure/feedback rules.
- Choose This Prompt When
- Use this for engagement planned in an inception report. Choose Review an Inception Report for the whole design, or Review a Stakeholder Engagement Approach for an equivalent review across other M&E documents.
Review the actual inception engagement section, stakeholder map/safe summary, evaluation questions/timeline, access needs and disclosure/feedback arrangements. Request missing contents before judging participation; a title is not a plan.
Check relevant affected groups, users and decision actors against stated scope, including excluded voices and safety without inventing a universal list. Assess explicit engagement mode per group, decision role, timing/frequency and links to evaluation milestones. Check safe accessible routes to question/correct findings, record responses/dissent and preserve evaluator independence/confidential sources.
Assess permissioned return of findings and explanation of how input was used or not adopted; not everyone should receive raw transcripts, identities or unrestricted drafts. Return short assessment, located identification/mode/timing/feedback/accountability table and priority revisions. Use Meets, Needs Revision, Not Assessable or reasoned Not Applicable; numeric ratings require supplied anchors. Continue supported review, distinguishing missing documentation from failed implementation and planned from completed consultation. Readiness advice is conditional owner-review guidance, not approval.
Worked Example
Illustration only. The setting and figures are invented to show the pattern.
Scenario: The engagement section of an inception report for a community health program in a mountain province is drafted. Fieldwork starts in two months.
What You Give the AI: The engagement section, a safe summary of the stakeholder map, the evaluation questions, the fieldwork timeline, a note that some mothers cannot attend daytime meetings, and the rules for sharing findings.
What the AI Might Return: A short assessment, then a table with a row per group and columns for identification, mode, timing, feedback and accountability. One row reads: group "mothers of children under five", mode "listed as consulted, no method named", timing "fieldwork only", status "Needs Revision", action "name a method that fits evening availability and say how findings come back". The revisions list puts feedback routes first.
When to Choose This Prompt
- The engagement plan sits inside an inception report and you want it judged before fieldwork starts.
- The section names groups but you suspect it never says how each one will take part.
- You need to know whether people can question or correct findings, and whether the evaluator stays independent when they do.
When Not to Choose It
- You want the whole inception design reviewed. Review an Inception Report
- The engagement approach sits in another M&E document, such as a MEL plan or a full evaluation design. Review a Stakeholder Engagement Approach
- You have no stakeholder list yet and need one built. Create a Stakeholder Map
Checking the Output
- Take each group the review calls missing and look for it in your stakeholder map. Anyone you left out on purpose, for safety, should be marked as excluded with a reason.
- Read the mode listed per group against what the section actually says. A group the review calls consulted should have a method behind it in your text.
- Compare the timing column with your fieldwork calendar and milestones.
- Where the review quotes your wording, find that wording in the section. A quoted line you cannot find was invented.
- See whether planned and completed consultation are kept apart. At inception, almost everything is planned.
- Confirm the closing note reads as advice for your own reviewers. It cannot approve the plan.
Common Problems and Fixes
- The review treats a heading such as "Stakeholder Engagement" as a plan. Fix: Paste the body text under the heading, with the map and timeline, and ask for a fresh pass.
- Every group is told to receive raw transcripts or full drafts. Fix: Say what you can release and to whom, then ask it to redo the feedback column within those rules.
- Missing documents are scored as failed practice. Fix: Request a split between absent documentation and implementation that went wrong, with unknowns marked Not Assessable.
- Identities of vulnerable participants appear in the answer. Fix: Strip names and locations before pasting, and rerun with a safe summary of the map.
Adapting It to Your Context
- Participants with access needs: List the needs (language, mobility, literacy, time of day) so the mode column can be judged against them.
- Sensitive topics or insecure areas: Share only a safe summary and state which groups cannot be named, so the review can test disclosure rules without exposing anyone.
- Participatory designs: Say which groups should hold a decision role, and ask the table to show whether the plan gives them one.