There is no standardised way of providing members with proposals or supporting information. The following information is offered as guidance. The Decision Pipeline includes a regular {ref}`update process<updating_products_processes_and_activities>` through which individual products, processes and activities may be updated or identified for improvements.
A decision summary will vary depending on the complexity and impact of the decision. Small decisions may require only a paragraph or so of text. Larger decisions may require a paper for members, with supporting information in various formats.
A decision summary may require some or all of the components listed below.
:header-rows: 1
:widths: 1 3
* - Component
- Description
* - Proposal text
- The text of a decision that Members will vote on, as currently understood by the decision team.
* - Drivers or rationale
- A summary of why a particular decision is needed. Describing this in terms of [organisational drivers](https://patterns.sociocracy30.org/describe-organizational-drivers.html) can be a useful technique.
* - Outcomes and benefits
- What is expected to result from the decision.
* - Supporting information
- Information that allows Members to make an informed decision. This may vary in format depending on the nature of the decision, e.g. a budget, an appendix of technical options, a report of market conditions.
* - Outputs
- A high-level summary of outputs or products, i.e. authorisation of projects with deliverables.
* - Budget
- An outline budget for a decision with cost or capacity implications.
* - Deadlines
- Any internal or external deadlines for the decision.
* - Dependencies
- Any internal or external dependencies that have been identified.