The Decision Lifecycle

Every decision in Decisio follows a structured lifecycle from initial identification through final resolution. This page explains each stage and the transitions between them.

Overview

Workspace → Project → Issue → Motion → Mechanism → Submission → Resolution

Each entity in this chain has a specific purpose:

Entity	Purpose
Workspace	Organization-level container
Project	Groups related issues
Issue	Frames the decision needed
Motion	Proposes a specific resolution
Mechanism	Defines how to decide
Submission	Records participant input
Resolution	Immutable outcome record

Stage 1: Issue Creation

An issue is created when a question or topic requires a formal decision.

Issue Statuses

Status	Description
Draft	Being prepared, not yet open for motions
Open	Active and accepting motions and votes
Resolved	Decision has been recorded
Closed	No longer active
Archived	Moved to long-term storage

Creating an Issue

When creating an issue, you specify:

• Title: A clear statement of what needs to be decided

• Description: Background context and relevant information

• Exhibit permissions: Who can add supporting materials

• Motion permissions: Who can propose motions

• Default mechanism settings: Pre-configured voting rules

An issue in draft status allows you to prepare everything before opening it for discussion.

Opening an Issue

Moving an issue from draft to open signals that it is ready for participant input. At this point:

• Participants can be invited

• Motions can be proposed (based on permissions)

• Discussion can begin

An issue in "Open" status, ready to accept motions and participant input

Stage 2: Motion Proposal

A motion is a specific proposal to resolve an issue. Each issue can have multiple motions, allowing participants to consider different approaches.

Motion Statuses

Status	Description
Draft	Being prepared by the proposer
Proposed	Submitted but awaiting a second (if required)
Seconded	Received a second, ready to open voting
Open	Active and accepting submissions
Resolved	Voting complete, outcome determined
Withdrawn	Removed by the proposer

Motion Workflow

Draft → Proposed → [Seconded] → Open → Resolved
                                     ↘ Withdrawn

1. Draft to Proposed: The proposer submits the motion for consideration

2. Proposed to Seconded: Another participant seconds the motion (if seconding is required)

3. Seconded/Proposed to Open: An administrator opens voting

4. Open to Resolved: Voting completes and outcome is determined

A motion can be withdrawn at any point before it is resolved.

Motion Outcomes

When a motion is resolved, it receives one of these outcomes:

Outcome	Description
Passed	The motion was approved
Failed	The motion was rejected
Withdrawn	The proposer withdrew the motion

Stage 3: Mechanism Configuration

Every motion has an associated mechanism that defines how the decision will be made.

Resolution Types

Type	Description
Vote	Participants submit votes that are tallied
Consensus	All participants must agree
Chair Decides	A designated chair makes the final call

Vote Configuration

When using vote-based resolution, you configure:

Threshold: What percentage is required to pass?

• Majority: More than 50%

• Supermajority: Typically 66% or 75%

• Unanimous: 100% agreement required

Quorum: What minimum participation is required?

• Count: A specific number of participants (e.g., 5 votes minimum)

• Percentage: A fraction of eligible participants (e.g., 75% must vote)

Seconding

Some governance frameworks require motions to be "seconded" by another participant before voting can proceed. This prevents frivolous proposals and ensures at least two people support discussing the motion.

When seconding is enabled:

1. The proposer submits the motion (status: Proposed)

2. Another participant seconds it (status: Seconded)

3. An administrator can then open voting (status: Open)

Stage 4: Participant Submissions

Submissions are the responses participants provide to a motion.

Submission Process

1. A participant receives an invitation to participate (via email)

2. They access the issue using their unique invite link

3. They review the issue context, exhibits, and motion details

4. They submit their choice and optional justification

Submission Choices

For vote-based mechanisms, standard choices are:

• Aye (in favor)

• Nay (against)

• Abstain (decline to vote)

For consensus-based mechanisms:

• Agree

• Disagree

For chair-decides mechanisms:

• The designated chair records the decision directly

Submission Visibility

Decisio uses transparent voting:

• Before submitting: You can see who has voted but not how

• After submitting: You can see how others voted

This encourages independent thinking while maintaining accountability.

Changing Submissions

Participants can change their submission while the motion remains open. The most recent submission is what counts when the motion is resolved.

Voting in progress on a motion, showing vote options and current tally

Stage 5: Resolution

A resolution is the formal, immutable record of a decision.

Creating a Resolution

When an administrator creates a resolution, they:

1. Specify which motions are included and their outcomes

2. Write a summary of the decision

3. Optionally link relevant exhibits as supporting documentation

Resolution Properties

Property	Description
Summary	Human-readable description of what was decided
Motions	The motions included with their outcomes
Exhibits	Supporting documents attached to the resolution
Recorded by	The administrator who created the resolution
Created at	Timestamp of when it was recorded

Resolution details showing the outcome, summary, and associated motions

Resolution Immutability

Once created, a resolution cannot be edited or deleted. This immutability is fundamental to decision governance:

• The record accurately reflects what was decided at that time

• Audit trails remain intact

• Legal and compliance requirements are satisfied

Superseding Resolutions

If circumstances change or an error is discovered, you do not edit the original resolution. Instead, you create a new resolution that supersedes the previous one. The superseding resolution:

• Links to the original resolution

• Explains why it replaces the previous decision

• Becomes the new authoritative record

The original resolution remains in the system with a "superseded" status, preserving the complete decision history.

A resolved issue showing the final outcome and resolution record

Complete Lifecycle Example

Here is how a typical decision flows through Decisio:

1. Issue Created (Draft): "Should we implement a remote work policy?"

2. Issue Opened: Participants invited, discussion begins

3. Exhibits Added: Policy draft documents, survey results

4. Motion Proposed: "Adopt the proposed remote work policy effective March 1"

5. Motion Seconded: Another participant formally supports the motion

6. Voting Opened: Administrator opens the motion for submissions

7. Submissions Collected: Participants vote aye/nay/abstain

8. Motion Resolved: Voting closes, motion passed 7-2

9. Resolution Created: "Board approved remote work policy per Motion A, effective March 1, 2024"

10. Issue Resolved: Decision is complete and documented

Related

• Understanding Decision Governance - Why this matters

• Roles and Permissions - Who can do what at each stage

• Glossary - Detailed definitions of all terms