Stakeholder engagement record template
Keep the original contribution connected to the meeting record, the interpretation made by the team, the decision taken and the response returned. This editable pack helps an engagement coordinator hand over a record that can be checked without treating a summary, a decision and participant agreement as the same event.
The eight-page DOCX contains instructions, four reusable blank sheets and a three-page fictional completed example. The matching PDF is a print copy. The fields are ordinary editable text and tables; there are no macros, scores, automatic reminders or automated privacy checks. Copy the sheets into your controlled working file and expand them for the actual exercise.
Download the editable stakeholder engagement record template (DOCX).
Download the print stakeholder engagement record template (PDF).
Keep the contribution separate from its interpretation
A single workshop note often mixes a participant’s account, the facilitator’s interpretation and the organisation’s intended response. Use the input sheet to separate those layers. Give each contribution an input ID and an exact evidence locator. Record whether the wording is a quotation, a paraphrase, a translated summary or the team’s own interpretation. An unconfirmed summary stays labelled that way.
For a paraphrase, retain the source record and its version. If someone corrects the summary, create a dated revision with the corrected scope and its evidence. Keep the earlier version accessible to authorised reviewers. A correction to the wording is a change in the record; it does not establish that the underlying concern has been resolved.
When several contributions concern the same question, link their IDs in the synthesis sheet. Preserve differences that could affect the decision. Do not replace incompatible requests with an invented average position. A person confirming that a note accurately records their view has confirmed the note, not necessarily the proposed action.
Give the event a bounded description
GRI 2: General Disclosures 2021, Disclosure 2-29, addresses stakeholder categories, identification, engagement purpose and meaningfulness. Its guidance includes access barriers and use of feedback. These points provide narrow context for the event card; the pack is an original working aid, not a GRI form.
Complete the event card before attaching inputs. Record the decision question, information version supplied, actual date and route, and the record’s cut-off. Keep planned arrangements separate from what happened. An invitation log, attendance note and submitted response describe different events, so retain the appropriate evidence for each.
Use group or role codes in this working copy where suitable. Put contact details and any identity lookup in the authorised source system rather than repeating them across sheets. The form does not make coded records anonymous or approve their release. The responsible information owner must decide access, appropriate detail and retention for the real exercise.
The coverage section is a place for the limits of this particular record. If a route was unavailable or a relevant view was not obtained, state the affected question and the next record needed. Do not invent a group’s position from someone else’s attendance. Follow the organisation’s urgent escalation route for an immediate concern; completing this pack should not delay it.
Work through a corrected contribution
All names, dates, roles and records below are fictional. Alder Yard is considering a trial change to delivery-booking hours. Event E01 on 2 September 2026 asks what the trial would need to test. Two nearby residents, one dispatch planner and one carrier coordinator attend. Residents from the east lane have not yet contributed. The meeting is exploratory; no operating change is approved there.
Input I01 version 1 paraphrases the residents as asking to stop all deliveries before 09:00. Their correction C01, received the next day, says their request concerns unloading near the north gate before 09:00, not all deliveries. I01 version 2 retains that narrower account and marks version 1 superseded. The correction does not supply noise measurements or establish a site-wide impact.
Input I02 from the carrier coordinator asks to retain an 08:00 booking option because of the coordinator’s stated routing constraints. That explanation remains an attributed account, not a verified transport study. Issue Q01 links I01 version 2 and I02 version 1. Its summary preserves the different requests instead of saying that participants agreed on later delivery hours.
Decision D01, dated 5 September, authorises preparation of a trial proposal and a separate feasibility review. It does not authorise the trial itself. Action A01 prepares the proposal; A02 seeks the missing east-lane input. At the 10 September cut-off, A01 has produced proposal P02, A02 is still open, and no trial result exists. The file can support that narrow progress statement only.
Record the returned response as its own event
Cabinet Office consultation guidance asks UK government departments to explain received responses and their influence on policy. This is a useful, limited reference for keeping the returned explanation traceable. It does not impose a deadline or statutory consultation process on users of this template.
The feedback sheet records the exact response version, intended group, delivery route, date, dispatch evidence and any receipt or clarification. In the fictional case, response F01 explains D01 and the remaining work. A dispatch log shows it was sent to the attending contacts on 6 September. One resident acknowledges receipt on 7 September; the other recipients’ receipt remains unconfirmed.
Those events allow three distinct statements: F01 was sent to the documented recipients; one recipient acknowledged it; no record establishes general agreement with the proposal. East-lane residents were outside that dispatch list. The record therefore keeps their input action open. Sending a response to some contacts cannot stand in for obtaining every missing view.
If a later response disputes the summary or introduces another condition, link it as a new input and revisit the affected synthesis and decision. Keep the previous decision date intact. The pack’s status fields describe what evidence is present at a cut-off; they are not a satisfaction score or permission to close a grievance.
Check the chain before circulation
Try four checks using the example. First remove C01: I01 version 2 loses its correction evidence. Next use version 1 in Q01: the issue summary again overstates the request. Then relabel the F01 dispatch as agreement: the dispatch log cannot support that claim. Finally mark the trial complete because P02 exists: a proposal is not an authorised or completed trial.
On the blank review sheet, name the version and intended use of the record being released. Check that every selected input points to a retained source, every synthesis identifies the input versions it used, and every decision states what was and was not authorised. Keep the unresolved items visible beside the handover, with an owner and the next evidence needed.
This pack captures engagement records. Use the stakeholder planning guide for the wider design of the exercise and the material-topic collection guide when approved topic decisions become evidence requests. The grievance-data guide addresses aggregate process reporting. None of those steps turns this record into a statutory consultation certificate or a materiality decision.
Sources checked 15 October 2026. GRI reference: Disclosure 2-29 and accompanying guidance.
Cabinet Office reference: Consultation principles, section 9. Contains public sector information licensed under the Open Government Licence v3.0.
Version 1.0. Original Nitium Advisory record sheets, artwork and fictional example. This is an internal documentation aid, not a prescribed format, legal opinion, consultation or consent determination, grievance investigation, GRI conformity claim or independent assurance. No source organisation endorses it.
Comments