Skip to content
ChronoClockTime intelligence
UTC
--:--:--
UTC
--:--:--

Planning PokerEstimate stories live with your team
Retro BoardLive columns, votes and reveals
Meeting PollVote on times, see the heatmap
Standup TimerRotating speakers, fair airtime
Async StandupYesterday, today and blockers
Mood CheckTeam pulse, hidden until reveal
Lean CoffeeTimeboxed topics your team voted for
Shared TimerOne countdown on every screen
Affinity SizingSize a whole backlog in one pass
Who's NextFair random order for the team
Agenda TimerTimed agenda with a running cost
Team TimezonesWorking-hour bars for the whole team
Sprint CapacityHours and points you can commit
VelocityTrends and Monte Carlo forecasts
Sprint ToolkitSprint dates, points and DoD

Team

Planning poker

Estimate stories together in real time. Create a room, share the link, vote in private and reveal at once. Rooms are ephemeral: no accounts, and everything is wiped after two hours of inactivity.

Start

Create a room and send the link to your team. Whoever opens it joins the same table.

How a round works

One person creates the room and shares the invite link; everyone else opens it and types a name. Put the story or ticket title in the story field, and each person picks a card in private. The table only shows who has voted, not what they voted, so nobody anchors on the first number said out loud. That anchoring is the whole reason planning poker exists: estimates given after hearing someone else's number drift towards it. When the votes are in, hit Reveal, and if the numbers disagree, have the highest and lowest voters explain what they saw before voting again.

Rooms are meant for a session, not for records. The room lives on the server only while people use it and is deleted after two hours of inactivity. Names and votes are never stored beyond that.

Room codes, links and who can get in

Creating a room puts a six-character code in the address bar and nowhere else. The alphabet it is drawn from leaves out I, L, O, zero and one, so a code read aloud over a call or copied off a screen has no ambiguous characters in it. Anyone with the code can type it into the "Have a code?" box and reach the same table, which is worth knowing before you paste an invite link into a channel wider than the team.

Up to fifty people can be in one room; the fifty-first is turned away rather than silently dropped. Your display name, avatar and a random participant id are kept in this browser so that a reload puts you back in your own seat instead of creating a second one. They stay on your device, and clearing site data for ChronoClock removes them.

If the connection drops, the page retries five times with a widening gap before it gives up and shows "connection failed"; reloading starts the attempts again. Someone who closes the tab without a card on the table leaves the seat list, while anyone who has already voted stays visible so the round is not silently short of a vote.

What the reveal actually tells you

Revealing turns three figures over. The average uses only the numeric cards, so a question mark or a T-shirt size is left out of it and a table that voted entirely in T-shirt sizes shows a dash rather than a number. The median uses the same numeric cards and is the more honest summary of the two, because one person's 34 cannot drag it. Agreement reads Yes only when every card on the table is identical, with at least two votes cast; anything else reads Discuss, and a round holding a single card shows a dash until somebody else plays one.

A worked round: the story is "add CSV export to the reports page" and five people vote 3, 5, 5, 8 and 13. The average comes out at 6.8, the median at 5, and Agreement says Discuss. The number to act on is not the average but the gap: the person on 3 had assumed the export already existed elsewhere, and the person on 13 knew the report is paginated. After both explain, the second round lands on 5, 5, 8, 8, 8. The average is still 6.8 and the median has moved to 8, but the spread has collapsed from ten points to three, and that is the part that tells you the team is now estimating the same piece of work.

A reveal is not a commitment. It is a prompt to talk, and the new round button clears every card so the same story can be re-estimated as many times as it needs.

Mistakes that cost a round

Switching the deck mid-round does not clear the cards already played, so a number cast on the Fibonacci deck is still on the table when the T-shirt cards appear. Pick the deck before anyone votes, or press New round straight after changing it.

Reveal, New round, the deck and the story are open to everyone at the table rather than to a moderator. That suits a team of five and goes wrong in a room of thirty, where it pays to say out loud who is driving. Someone who only wants to watch should press Spectate: spectators are excluded from the vote count, so the round no longer waits for them.

Estimating in hours instead of points is the other common slip. The cards are a comparison between stories, not a schedule, and the Fibonacci gaps exist to stop the table arguing about whether something is an 8 or a 9. Turning points into dates is a separate job, and the project estimator below is where it belongs.

Frequently asked questions

Do my teammates need an account?

No. They open the invite link, type a name and they are at the table. Nothing is stored server-side beyond the live room, which expires two hours after the last activity.

What do the cards mean?

The Fibonacci deck expresses that uncertainty grows with size: the gap between 13 and 21 is deliberately wide. The question mark means "I cannot estimate this yet", which is a useful signal, not a cop-out. The T-shirt deck works for rough sizing before a backlog is broken down.

Why hide votes until everyone is done?

Anchoring. Once one person says eight, everyone else's estimate drifts towards eight. Simultaneous reveal keeps each estimate independent, which is where the technique's value comes from.

Who can reveal and reset?

Anyone at the table. Small teams rarely need a dedicated moderator, and it keeps the room simple. Agree on who drives if that bothers you.

Can somebody see my card before the reveal?

No. Until someone presses Reveal, the room only sends out whether each person has voted, not what they voted. The card values are withheld at the source rather than hidden in the page, so opening the browser's developer tools on another seat does not expose them.

Why is the average showing a dash?

Nothing numeric was played. The T-shirt deck has no numbers in it, and a table where everyone picked the question mark has none either, so the average and median have nothing to work from. The Agreement figure still works, because it only compares cards to each other.

I reloaded the page. Did I lose my vote?

No. Your name and a participant id live in this browser, so a reload rejoins the same seat with your card still on the table. Joining from a different browser or a private window creates a second seat, because the id does not travel with you.

How many people fit in a room?

Fifty. Beyond that the room turns new joiners away with a message rather than quietly ignoring them. Spectators count towards the fifty but not towards the vote tally.

Can we keep the room for tomorrow's session?

Not reliably. The room is wiped two hours after the last activity in it, and every action pushes that deadline back. Write down whatever you decided before you close the tab, and create a fresh room next time.

Related tools

How to estimate tasksThe planning fallacy and what corrects itProject estimatorTurn the estimates into a completion dateTask managerTrack the stories as tasks with session estimatesMeeting costWhat the estimation session itself costs

ChronoClock is a free time and productivity toolkit. Personal tasks, focus sessions and plans are saved in this browser. Shared team rooms send content to our server so participants can collaborate. No account is required.

Sun and moon figures are computed astronomically and are approximate.

AboutGuidesTemplatesCountdownsPrivacyTermsContact© 2026 ChronoClock