Pit-wall stopwatch for timing up to four riders at once.
Something broken, something confusing, or something you wish it did? Write to us. A real person reads it.
If you are reporting a problem, telling us your iPhone model, your iOS version, and what you were doing when it happened will usually get you a useful answer first time.
Getting started
The user manual (PDF) covers what the app does, how to run a session, what to do when a session goes wrong, and how to get lap times off the phone.
The short version: the app opens on a session that is already armed. Press START, then tap a rider's tile each time they cross the line. That is the whole input.
Then set an alert, because nothing warns you until you do. See the first question below.
Common questions
No warning fired before my rider came round
Almost always, the alert is simply switched off. Alerts belong to each rider rather than to the session, and both of them start at 0, which means off. A new rider is silent until you say otherwise.
Open Roster, tap the rider, and under ALERTS set a DUE Alert: how many seconds before their predicted crossing you want the phone to buzz. Fifteen is a reasonable place to start. LATE Alert is the other half, the seconds past that crossing before the tile flags them overdue.
If the alert is set and still nothing fires, it has nothing to predict from yet. It works off the rider's target lap, and after that off the laps they actually run, so a rider with neither gives it nothing to work with and it stays quiet rather than guessing. Set a target lap, or run one lap and it takes over from there.
One rider should not be buzzing
Each rider carries their own Buzz and Sound switches, on the same ALERTS row in the Roster. Turning Buzz off silences that rider and nobody else.
Sound starts off for everyone. A pit wall is a place where a noise nobody asked for is a liability, so it stays opt-in, one rider at a time.
The LAPS line shows a dash instead of a number
Laps-remaining needs the rider's OUTLAP Offset: how much longer their lap out of the pits or off the grid runs than a normal one. Without it the figure would be wrong by however long that first lap took, so the app shows a dash rather than a number it cannot stand behind.
Set it on the rider in the Roster and the line fills in.
I tapped the wrong rider
You have a few seconds to fix it. Straight after a lap is recorded the tile offers UNDO, and the other riders offer to take the lap instead. If it belonged to one of them, hand it over rather than undoing and re-timing.
Miss the window and the lap stays. It can still be read back later in Review, and the session record is not damaged by one misattributed lap.
The sector tree is one bar and will not split
Sectors stay locked at one until the rider has a target lap set. There is nothing to divide before then: a sector tree is a division of a known lap time.
Set the target lap first, then choose the number of sectors and enter your measured splits.
Are the sector times measured?
No, and this is worth being clear about. The app's only input is your tap at start/finish; it cannot see the circuit. The sector tree divides the rider's reference lap and shows where they should be if they are on their usual pace.
It is a prediction, not a measurement. It is useful for spotting a rider who is off their pace, not for analysing where they gained or lost time.
The app closed in the middle of a session
Reopen it. Sessions are anchored to wall-clock times rather than to a running counter, so the app reconstructs where every rider was and picks the session back up with the right elapsed times.
A red flag in progress survives too: if the session was halted when the app went away, it comes back halted, and the time it spent closed is excluded exactly as if you had been watching.
A rider came in and I want to stop just them
Use the pause control on that rider's tile. It takes them out of timing without touching anyone else, and they stay stopped through a relaunch.
If they are coming back out, use the pit stop instead. That pauses their lap, times the stop, and keeps the slow in-lap out of their pace so it does not spoil every prediction that follows.
How do I get lap times off the phone?
From a finished session (either the debrief right after the flag, or any session in Review), switch the control cap to PDF and hold it for three seconds. You get a printable report with per-rider lap tables, the fastest lap marked, pit stops noted and an event log.
It goes straight to the standard iOS share sheet, so you can AirDrop it to a rider, mail it, print it, or save it to Files.
On a weekend where you know you want all of them, turn on Sessions → AUTOSAVE PDF → Save to Files. Every session that timed a lap is then filed as the flag falls, into Files → On My iPhone → MotoChronPRO, named by date, track and type, so the whole weekend sorts itself and goes out in one go. Review puts a document mark on every session that has a report, so the end-of-day check is spotting the one without it.
Where did my finished session go?
Into Review. Every finished session is kept there and can be filtered by rider, track and date. Open one and it comes back on the same tiles it was run on. Swipe a rider's tile to scrub back through their laps one at a time.
Does it need an internet connection?
No. The app makes no network connections at all, which means it works the same in a paddock with no signal as it does anywhere else. There is no account and nothing to sign in to.
Is my data backed up anywhere?
Not by us: there is no cloud service behind the app, by design. Your sessions live on your iPhone.
They are included in an iPhone backup, so restoring a backup restores them. Deleting the app deletes them, and we cannot recover them. If a session matters, export the PDF before you delete anything.
Does it run on iPad?
No. MotoChronPRO is an iPhone app. The grid is laid out for a phone held in portrait on a pit wall, and it has not been designed or checked on an iPad, so we do not advertise a device we cannot stand behind.
Does it score a race?
No. Race mode runs a session to a lap count and shows laps remaining, but the app times riders; it does not produce finishing order, gaps, or positions.
Requirements
iPhone running iOS 17 or later. Designed and checked for portrait use on iPhone 15 and newer. The screen stays awake on its own while a session is running, so it will not lock on you mid-stint.
A word on what this is. MotoChronPRO is a hand-operated stopwatch with a prediction on top. Every lap it knows about comes from someone tapping a tile, so it is exactly as accurate as the person holding the phone. It is not a transponder system and is not intended for official timing.
Privacy
The app collects nothing. No account, no network calls, no analytics, no tracking. See the privacy policy for the detail.
Suggestions
Feature requests are welcome and get read. The app is built from what crews actually do on a pit wall, so if it is missing something you need on a race weekend, that is worth an email.