Providing updates on decision progress¶
Warning
Much of the Decision Pipeline documentation can be considered as guidance or as a framework for visualising how decision-making happens.
The sections on providing and engaging with updates are much more prescriptive. The agreement that transparency will be reciprocated with timely engagement is an implicit principle of collective management and is built into the design of the decision pipeline.
Sending regular and timely updates on decision progress is important for building awareness, strengthening democratic member control and holding effective meetings.
Sending regular updates¶
Decision facilitators MUST:
Send an update on a decision in advance of every fortnightly team meeting if relevant progress or change needs to be reported, or if requested to do so.
How to provide an update on a decision¶
Update the decision summary and relevant fields in the decision ticket with relevant information.
Add an update to the relevant decision ticket that describes the changes, including pointers to any supporting information. Be explicit if members are expected to read the supporting information.
Make sure that the ticket is assigned to Members.
When to send an update¶
Timetable¶
Updates should be sent according to the pipeline review timetable:
Activity |
Time |
|---|---|
Provide updates |
By 10am Thursday before fortnightly meeting. |
Read updates |
By 10am Friday of the fortnightly meeting. |
Pipeline Review |
10.30am Friday approx, depending on agenda. |
Triggers that require a decision update¶
A regular update MUST be issued for a decision if:
The status of the decision has changed.
The substance of the decision has changed.
The planned decision type, event or schedule has changed.
The decision facilitator or team has changed.
There has been material progress on or change to any aspect of the decision summary or supporting information.
An update has been requested by a member.
A regular update should highlight any relevant changes to the decision ticket and decision summary, which members are expected to read. A regular update may also highlight any supporting information that members are required to read.