Most meetings end with someone asking "Are we all agreed?" and interpreting silence as consensus. That is not consensus. It is the absence of objection, and the two are very different things. People stay quiet for all sorts of reasons: they do not want to slow things down, they feel outnumbered, or they assume their concern is not important enough to raise.
A structured consensus check gives every person in the room a clear, low-friction way to signal their actual level of support. It surfaces hidden disagreements before they become downstream problems, and it gives the facilitator concrete data about where the group stands.
This tool supports three voting methods: Fist of Five, Thumbs, and a Confidence Scale. You can run quick checks on a shared screen during any meeting. Everything runs in your browser. Nothing is stored or sent to a server.
The most widely used consensus check in agile and facilitation circles. Each participant holds up fingers to indicate their support level. Best for proposals where you need nuanced feedback, not just yes or no.
The simplest and fastest method. Use this when you need a quick temperature check and the decision is relatively straightforward. Thumbs up means support, sideways means reservations or need for discussion, and down means opposition. Best for time-pressured situations or when the group is large.
A finer-grained approach for when you need to measure confidence levels precisely. Useful for technical decisions, risk assessments, or any situation where you want to quantify the group's overall confidence in a proposal. The wider scale helps distinguish between "slightly unsure" and "deeply uncertain."
The numbers matter, but the pattern matters more. Here is what to look for when interpreting consensus check results.
The group is aligned and ready to move forward. If there are any low votes, they are outliers worth a quick check but unlikely to block progress.
The group can proceed, but there are meaningful reservations. The facilitator should ask anyone who voted below 3 to share their concerns. Often a small adjustment to the proposal resolves the gap.
The group is not aligned. Pushing forward without addressing the objections will create problems later. Open the floor for discussion, identify the root disagreements, and consider revising the proposal before voting again.
Watch out for votes that cluster at both ends (e.g. several 5s and several 1s). Even if the average looks acceptable, a bimodal pattern signals a fundamental disagreement in the group that averaging will hide. These situations need facilitated discussion, not a second vote.
If everyone votes 2 or 3, the proposal has lukewarm support at best. The group might be settling rather than genuinely agreeing. Ask whether there is a better option nobody has raised yet.