A timer alert can fire at exactly the moment your attention is deepest somewhere else. Persistent acknowledgement keeps that selected timer event visible until you respond, instead of allowing the prompt to clear on its own.
The alert competes with the task already in front of you
A timer often reaches its selected point when the current task still has all of your attention. The paragraph is nearly finished, the call is still active or the design problem has just become clear. A single sound can enter that moment briefly and then disappear.
You may genuinely intend to respond, but the task already on screen still holds the stronger cue. If the alert disappears immediately, the work can simply continue.
Persistent means keeping the same prompt active
The principle is simple: keep the same due prompt active until there is a response. The on-screen message remains visible. If a sound or male or female voice alert is selected, it can continue subject to browser permission and device settings.
It is to stop the selected timer transition clearing without a response in the interface.
One response pattern across four different timer events
The work or break timer reached its selected endpoint.
The next selected water reminder became due.
The selected movement cadence reached its endpoint.
A scheduled Learn Sprint is ready, or an active stage has reached its endpoint.
Acknowledgement has a precise meaning
Pressing Acknowledge records that the active prompt received a response. It clears that prompt and allows the timer to continue into its next state.
It does not prove that water was drunk, movement happened, a break was taken, learning occurred or focused work was completed. The acknowledgement records the screen response, not what happened away from the screen.
Acknowledgement and Capture have different jobs
Persistent acknowledgement belongs to the four timers. It deals with a selected event that has become due: a Focus transition, Hydrate reminder, Move prompt or Learn Sprint stage.
UP Capture deals with something different: an unscheduled note, idea, question, reflection or to-do that appears while you are working. It gives that interruption somewhere to wait without turning it into another acknowledged timer event.
Focus, Hydrate, Move and Learn use acknowledgement when a selected timer event reaches its endpoint.
An interruption can wait until you are ready.
Capture stores the thought. Decide, plan and act later rather than treating it as the next task.
Control still matters
A prompt that waits must remain configurable. Choose timings that suit the task, use pause and reset controls deliberately, select the alert treatment you want, and decide whether browser notifications are allowed.
Persistent acknowledgement should be noticeable, not punitive. If a timing repeatedly interrupts at the wrong moment, change the routine rather than treating alert fatigue as something to tolerate.
See due, active and acknowledged states in the full product behaviour.
The Persistent Acknowledgement page shows how a timer event remains active until it receives a response, and where that behaviour stops. UP Capture remains separate for unscheduled notes, ideas, questions and to-dos.