Skip to main content

Timers

A question can carry a time limit. When it does, answers stop being accepted when the limit passes - on the server, not just on screen.

Setting a time limit​

Select a question in Build and set Time limit in its properties: whole seconds from 1 to 3600, or empty for none. A question without one is untimed.

To time every new question the same way, set Default time per question in the activity's Settings. It fills in the limit on questions you add from then on; questions already in the activity keep theirs.

How the clock works​

  • The clock starts when the question opens for answers. Someone who joins late gets the time that is left, not a fresh full limit. Reopening voting restarts it.
  • The server decides. A late answer is refused with "Time is up for this question". A short grace period, which is never shown, absorbs the round trip from a phone, so somebody who tapped Submit at 29.9 seconds is counted.
  • Every screen shows the same deadline. Phones and the presenter's screen count down to a deadline the server sends, corrected for each device's clock, so a phone whose clock is a minute out still finishes with the room. A phone disables the question when it reaches zero.
  • Screen readers hear the countdown at ten seconds, five seconds and zero, not every second.

More time​

Participants can press I need more time while a timed question is open, unless you switch the button off in the activity's Settings. You see only a count in the presenter view's footer - "2 people have asked for more time" - never who asked, and Murmle does not record who asked either. Participants do not have to explain or disclose anything to the room.

While a timed question is open, the presenter controls include Give more time, which adds 30 seconds, and Remove the limit, which makes the question untimed for the rest of its time on screen. Both apply only to the current question.