Reaction Time Training Plan
A useful plan is short daily drills with the same start cue, logged times, and rest—not long sessions that add fatigue noise.
Who this is for
This plan is for browser practice at a desk or on a phone. You use the same lights-out cue each day, write down one clean time, and stop while the attempts are still sharp. It suits someone who wants a week they can actually finish, not a pile of tips.
It is not a gym program, a strength plan, or medical advice. You do not need a wheel, pedals, or any other gear. A laptop trackpad, a mouse, or a phone thumb is enough if you keep that choice the same for all seven days.
Rules of the drill
Wait until the lights go out, then tap once. An early tap is a false start. It does not count as a time, and it does not go in the log. The point of the warm-up reps is to feel the wait. The point of the timed reps is one honest start, not a guess that happens to be early.
Compare days only when the setup matches. Same device, same hand, and a similar time of day. A faster number on a different phone is not automatically a better start.
How a start is timed is covered in how this tool measures a start. Why a different screen or touch delay can move the number is covered in device latency and reaction time.
7-day plan
Keep each day short. Warm-up reps are uncounted: use them to settle your hands and to practice waiting. Timed reps are the only ones you may log. If a day lists eight reps, eight is the ceiling, not a quota you must reach after you are already jumping the lights.
Any millisecond figure in the Example only column is an example of how a log note can look. It is not a promise, and it is not a score you must hit.
| Day | Warm-up | Timed reps | Rest | Example only |
|---|---|---|---|---|
| 1 | 3 uncounted | 5 | 15–20 seconds between reps | About 280 ms on a phone |
| 2 | 3 uncounted | 6 | A full breath after any false start | Close to day 1 |
| 3 | 2 uncounted | 4 | Stop after the fourth rep | Do not chase a number |
| 4 | 3 uncounted | 6 | Log clean starts only | Within about 20 ms of day 1 |
| 5 | 3 uncounted | 8 | End early if you jump twice in a row | Skip the number if you jumped |
| 6 | 2 uncounted | 4 | Longer pauses; recovery day | Do not compare with day 5 |
| 7 | 3 uncounted | 5 | Log the best clean start of the week | Often still 200–300 ms in a browser |
How to log progress
After the timed reps, write one number: the best clean start of that day. Leave every false start out of the log. On day 1, also write the device name so a later session on another phone is not treated as the same series.
A useful week is seven of those lines, not a spreadsheet of every tap. If you miss a day, leave the line blank and continue. Do not stack two days of reps into one sitting to catch up.
When to stop
End the session when you feel tired, when you start guessing the lights, or when you jump more often than you wait. Extra reps after that mostly add fatigue noise, and the log gets harder to read. Stopping early still counts as doing the day.
If your hand feels rushed before you finish the listed reps, stop there. The plan is a ceiling. It is not a reason to keep tapping through a sloppy set.
Related
- How to improve reaction time — Sleep, focus, and practice habits that sit beside this week.
- What is a good reaction time — How to read a millisecond score without treating one attempt as a verdict.
- Guides — The rest of the ReactionF1 library.
Gear is optional. A wheel is not required for this week. If you want a stable desk setup later, see the beginner racing wheel notes.
