Staying up-to-date with decisions¶
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.
Reading updates on decision progress is important for progressing decisions, strengthening democratic member control and holding effective meetings. It is expected that members will read updates before the pipeline review meeting, and as requested for decisions that need urgent attention.
Reading regular updates¶
Members MUST:
Read asynchronous updates provided in advance of the fortnightly meeting.
Read any highlighted changes to a decision summary and any specified supporting information.
Note
Example decision update: increasing basic pay
A decision facilitator issues the following update:
We have prepared a budget showing the impact of the proposed pay rise. This information has been added to the decision summary. The full budget is available as optional supporting information.
Members should read the updated decision summary and may choose to read the full budget.
Decision updates: what to expect¶
Updates will 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.