Tracking a high council vote without asking twelve men twice

August 28, 2026 · Stakesauce

Somewhere in your stake right now there is an item waiting on the high council, and the honest answer to “where does the vote stand?” is someone would have to ask around. Not because anyone is careless — because a vote spread across twelve calendars has no natural home. It lives in a council meeting's minutes, a text thread, and memory.

The three states that matter

The classic tracking mistake is treating a councilor's vote as yes-or-no. There are three states, and the difference is the whole game: approves, does not approve, and hasn't answered yet. Collapse the last two and you can't tell an objection from a busy week — which means you either advance something you shouldn't, or you sit on something that was ready days ago.

What good tracking looks like

• Each councilor's answer is recorded individually, so the question “who hasn't answered?” has an instant answer — and only those men get the follow-up.
• The stake decides its threshold — unanimity, or a count the stake presidency sets — and the item advances the moment the threshold is met.
• An objection holds the item no matter what the count says, until the objector withdraws it or the presidency resolves it. An objection that gets outvoted silently is a council that stops raising objections.
• When the vote opens, all twelve are notified at once — nobody finds out at next month's meeting that they were the missing vote.

This is precisely how Stakesauce runs high council votes: twelve named rows, three states, a per-stake threshold, and objections that hold. The presidency sees the count in real time; the councilors see one clear ask in their inbox. Nobody asks twelve men twice.