Skip to main content

Applications for the autumn mentorship cohort are open until 30 September. Apply now

Template

Voting Window & Decision Journal

A dated journal that runs from the moment an action appears to the moment your rationale is published, so the reasoning behind a vote survives the vote.

Type
Template
Difficulty
foundational
Time
25 min
Version
v1.0.0
Updated
8/9/2026
governance actionsprocesstransparency

What this helps you do

A vote is a single event. The reasoning behind it is a process that runs for days or weeks, and most of it is lost unless it is written down as it happens.

This journal holds the working record for one governance action: the voting window and its deadlines, when research started, what you currently lean towards and how confident you are, which questions remain open, and finally the decision, the date, and the link to the published rationale. It records movement over time, including the times you changed your mind, which is the part readers find most credible.

When to use this

  • An action has opened and you want a dated record from first read to published rationale.
  • You are working several actions at once and need to see which deadlines are closest.
  • You expect to change your mind and want the change visible rather than hidden.

When NOT to use this

  • The vote has already closed and you are reconstructing reasoning from memory. Write a short note instead and mark it as retrospective.
  • You want a public commentary thread. This is a working record; publish the rationale separately.

What you'll need

  • The action identifier and the submission date
  • The voting deadline or expiry epoch, read from chain or a governance explorer
  • Your intake brief or first-read notes
  • Any outstanding questions already sent to the proposer

Estimated completion time

25 minutes

Working time for one governance action, assuming the inputs listed here are already to hand.

How to use it

  1. 1Open the journal on first read, not on the day you vote. The value is in the interval.
  2. 2Record the voting window from chain: submission, deadline or expiry epoch, and any procedural date in between.
  3. 3Set your own research cut-off before the deadline, and leave room to draft the rationale.
  4. 4Write today's leaning in one sentence and a confidence level. Low confidence early is normal and worth recording.
  5. 5Log outstanding questions with who was asked and when. Mark each answered, unanswered, or refused.
  6. 6Add a dated entry whenever your leaning or confidence moves, and write the specific evidence that moved it.
  7. 7At decision time record the final decision, the date, and the link to the published rationale.
  8. 8Close the journal with what you would monitor after the vote, which becomes the input to a monitoring plan.

The tool

Full template - v1.0.0

Action and window

  • Action title and identifier
  • Action type
  • Submitter
  • Submission date
  • Voting deadline or expiry epoch
  • Where you read the deadline, with a link
  • Research started on
  • Your research cut-off
  • Rationale drafting date
  • Other important deadlines: proposer response, community call, committee milestone

Position over time

  • Dated entry: current leaning in one sentence
  • Confidence: low, moderate, or high
  • What would change your mind
  • Evidence that moved you since the previous entry
  • Whether the movement came from new evidence or from a new reading of existing evidence

Outstanding questions

  • Question
  • Who it was addressed to
  • Date asked
  • Answered, unanswered, or refused
  • Date answered
  • What the answer changed

Decision

  • Final decision
  • Decision date
  • Confidence at decision
  • Main reasons, in order of weight
  • Considerations you rejected and why
  • Published rationale link
  • Disclosures made alongside the vote
  • What you will monitor afterwards
Fictional Example

Invented for illustration. It does not describe a real governance action, proposal, or organisation.

Fictional journal: Stake Pool Tooling Grant

  • Window: submitted day 0, expiry epoch ends day 21, research cut-off set at day 14
  • Day 2 entry: leaning undecided, confidence low. Budget lacks day rates.
  • Day 6 entry: leaning against, confidence low. Two of three referees are affiliated with the submitter.
  • Day 11 entry: leaning undecided, confidence moderate. Proposer published day rates and replaced one referee. Movement came from new evidence.
  • Outstanding question: who owns the tooling licence after the grant ends? Asked day 3, answered day 10, licence confirmed open source.
  • Decision: abstain, recorded day 15. Main reason: delivery plan credible, ownership resolved, but no baseline exists for the stated adoption target.
  • Rationale published day 15 with a link to this journal summary.
  • Monitoring: first adoption report due at month 3.

How to interpret the result

  • A journal with a single entry made on voting day is a decision without a process. That is worth noticing about your own practice.
  • Confidence that never moves usually means the research was not capable of changing the answer. Check whether your questions were falsifiable.
  • Refused questions are evidence. A pattern of refusal from a proposer belongs in the rationale, stated as fact rather than as motive.

Limitations

  • The journal records your reasoning, not its correctness. A well-documented decision can still turn out wrong.
  • Deadlines and epoch boundaries must be read from chain. Any date copied from a summary can be stale.
  • This is a private working record until you choose to publish. Do not include anything you would not stand behind in public.

Sources and methodology

Downloads

  • Markdown export: the complete tool, including metadata, instructions, the template, limitations, sources and version history.

No other file formats are published for this resource. We list a format only when the file exists.

Version and governance

Current version
v1.0.0
Published
Not recorded
Last updated
8/9/2026
Next scheduled review
2/9/2027
Licence
CC BY 4.0
Editorial status
Not yet externally reviewed

No named reviewer is shown because no external review has been completed. Attribution appears only once a verified reviewer has signed off.

Changelog

  • v1.0.0 (2026-08-09) - First published edition.