What this is
An open count-up race flow for For Time blocks with optional time-cap constraints.
For Time timer workflow
For Time Timer With Race-Format Execution
For Time sessions are about sustained pace under pressure. untraind runs them as open count-up execution with clear round context so you focus on output instead of timer management.
What this unlocks
Done and custom log actions on each open step while round context and elapsed race time stay visible.
Why and when to use it
Use it for benchmark race formats where completion speed matters and transitions must stay clean.
Built for race-style blocks
Instead of generic intervals, untraind treats For Time as a training method with open count-up steps, round sequencing, optional time caps, and in-session logging aligned to race-style pacing.
Open count-up execution is explicit.
For Time blocks show elapsed race time with Done and Custom Log actions on each open step so completion stays fast.
One engine across formats.
For Time, EMOM, AMRAP, Ladder, and Density Zone all share one execution runtime and interaction model.
Open versus timed exercise modes are both supported.
Builder exercises can be open (count-up) or timed (countdown), and tempo or backoff settings still carry into strength-focused steps.
For Time timer FAQ
Can I use this for classic benchmark For Time workouts?
Yes. For Time templates can be configured and executed with clear phase cues and fast set logging.
Does the timer keep running if I switch apps?
Yes. The run flow is designed to keep timing behavior stable during normal app switching.
Does For Time use count-up or countdown timing?
For Time uses count-up execution by default, with optional time caps for race constraints. Timed countdown exercises can still be added where needed.