> ## Documentation Index > Fetch the complete documentation index at: https://docs.time2.bike/llms.txt > Use this file to discover all available pages before exploring further. # Combined finish > One chute for every race in the event — with blind capture for when riders arrive faster than you can type. Normally the timing screen is scoped to one race at a time. **Combined finish** turns that off: one screen, one chute, every rider in the event. Use it when several categories share a finish line and sorting riders into races at the moment they cross is unrealistic. > !!-IMAGE-NEEDED-!! — Combined finish: the wave board on top, the plate box, and the combined finish feed below with overall and per-race places. ## Turning it on The button below the rider lists. On a multi-race event this section leads with the question outright — *Timing 5 races — how?* The other option is **One race at a time**, which is the default. Save. > !!-IMAGE-NEEDED-!! — Timer setup → How I am timing, with both finish-style options. ## Dual slalom races are unaffected An event can mix the two. Combined finish covers your ordinary races; any dual slalom race keeps its own two-lane screen and is reached from the race tabs, which stay on screen for exactly that reason. Those races are also kept out of the combined wave board and finish feed — they're bracket-scored, so they don't belong in a shared chute. **Finish style showing as locked?** That only happens on a timer originally set up for dual slalom, before per-race formats existed. The whole dialog is also unavailable after you finalize, or for volunteers whose timing link doesn't include admin. **Getting back to per-race.** The combined screen replaces the standard one, so the **Timer setup** button on the timing screen goes with it. Reach the panel from **More actions → Timer setup** and switch back to *One race at a time*. ## What changes | | Per-race (default) | Combined | | --------------- | -------------------------------------- | ----------------------------------------------------------- | | Race tabs | Pick one, everything scopes to it | Gone — everything at once | | Start controls | START/PAUSE/STOP for the selected race | A **start board**: waves to release, plus every race's gun | | Typing a bib | Resolves within the selected race | Resolves across the whole event | | The finish list | That race only | Every rider, with overall place and place within their race | Scoring stays per race. This changes how you *capture*, not how anyone is placed. ## Which races come through your chute The selector collapses — it's a set-up decision, and it starts closed so the screen leads with the chute rather than its own configuration. By default every race in the event resolves on your screen. If your chute only takes some of them — juniors finish on the field, the road race finishes on the hill — tick just those at the top of the screen. It's **per device**, like your recording point, so two operators covering different chutes each narrow their own screen without affecting the other. Bibs from races you haven't selected won't resolve, which is the point: a rider who was never coming past you can't be recorded by you. Races are **grouped by discipline**, with a one-tap *all* / *none* per group. That matters because a category name isn't unique — a weekend routinely has a Cat A downhill, a Cat A mass start, and a Cat A dual, and picking between three identical chips is guesswork. For the same reason, every place this screen names a race shows the discipline with it — the resolve preview, the finish feed, the start-time dialogs, and the prompt that asks which race a shared bib belongs to. > !!-IMAGE-NEEDED-!! — The "Races through my chute" selector with two of four races selected. ## Where you're standing A shared chute isn't only a finish line. The same crew works a shared start/finish on a criterium, and a marshal on a multi-race course stands at one split with every category coming past. So this screen has the same **This device is timing the…** control as the per-race one — start line, any timing point, the finish, or both ends at once. **Whatever you select is what an entry records.** Type a bib or tap a rider and it does that job: | Where you are | An entry records | | ------------------ | ------------------------------------------------------------------------ | | **Finish line** | A finish | | **Start line** | Checks that rider onto the course | | **A timing point** | A split at that point, in that rider's own race | | **Both ends** | Resolved per rider — not out yet checks them in, on course finishes them | Checking a rider in **starts the race gun if nobody has**, and releases their wave if they're in one — otherwise they'd be on course with no clock to be timed against, and their splits would record as nothing. It says so when it does, so you can correct the gun if the field went earlier. Finishing and recording splits don't auto-start anything: firing the gun at the moment somebody finishes would hand the whole field a time of about zero. Those tell you the race hasn't started and point you at the race guns. The submit button changes with it — **CHECK IN**, **SPLIT**, **FINISH**, or **OUT / IN** — and so does the race sheet, so nothing ever claims to finish a rider who hasn't started. **Timing points are matched by name across races.** Each race owns its own points, so "Halfway" is a separate record in every category — you pick the name once and each rider's split lands on their own race's point. A race with no point of that name says so rather than recording something else. ## Three ways to record | Way | When | | ------------------ | --------------------------------------------------------------------------------------------------------------------------------- | | **Bib box** | You can read the number. Resolves across every selected race and confirms the rider, their race, and their wave before committing | | **Race sheet** | The number is unreadable or caked in mud. Search the field and tap that rider's row | | **Stamp the time** | The chute is moving faster than you can read numbers. Stamps the moment with no bib — add it afterwards | Stamping is a finish-line tool, so it's hidden at a start line or a timing point where a bib-less crossing wouldn't mean anything. ## Blind capture The feature that makes a busy chute survivable. Riders arrive faster than you can read numbers, so **stamp the crossing without a bib**. Press the capture button each time someone crosses; you get a timestamped slot with no rider attached. Afterwards — minutes later, or after the race — work through the queue of unassigned times and attach a bib to each. The **time never moves**; you're only saying who it belonged to. This is what you fall back to when the chute gets away from you. Better a complete set of accurate times you attach names to later than a partial set of times with names on them. ## Typing a bib across races The plate box searches every race at once. When it finds someone, it shows their name, their race, and their wave so you can confirm before committing. If two riders in different races share a bib number, it asks which one you mean rather than guessing. Duplicate bib numbers across races cost you time at the finish line. If you're planning to use combined finish, assign one number per rider across the whole event on the **Bibs** page rather than restarting numbering per race. ## The race sheet Every rider, one row each, a column per timing point — the shape a timing crew already reads on paper. ``` Pl Bib Rider Race Halfway Summit Time 112 Dana Ruiz Cat A · XC 12:04 15:40 18:32 418 Sam Okafor Cat B · XC 12:51 19:07 1 427 Jane Smith Cat A · XC 11:58 15:02 31:44 2 203 Alex Bright Cat A · XC 12:10 15:22 32:06 ``` * **Split columns run left to right in course order** — the order you listed the points in during setup. A row therefore reads as that rider's progress round the course. * **A blank cell is a point that rider hasn't reached.** Deliberately blank rather than a dash — a column of times with holes in it is exactly what you're scanning for. * Riders still out are tinted and show a **running time** in the Time column. * Finished riders show their finishing time and place, and `N in race` next to their name. * **Search by name or bib**, and filter to Out / In / Not started, one race, or everything. * The header row stays put while you scroll. ### Rows stay put The sheet is in **bib order and stays in bib order**. Nothing reshuffles while you're using it. This matters because tapping a row is how you record a rider whose bib you can't read. A sheet that re-sorts itself as times land is a sheet where the row under your finger changes between looking and tapping — you reach for #114 and record \#237, and neither rider finds out until results are published. **Progress order** is still available from the sort control, and the option says what it does — *rows move*. It's the right choice when you're watching the race rather than recording it: riders still out sort first, furthest round first, then finishers in placing order, so the top of the sheet is the road and the bottom is the result. Switch back to bib order before you start tapping rows. ### Every pass, not just one Where a rider crosses the same point more than once — every lap of a criterium past the same marshal — the cell lists **each pass**, numbered by lap: ``` Pl Bib Rider Race Halfway Lap Lap times 112 Dana Ruiz Cat A · Crit 1 4:02 3/8 1 8:10 2 12:15 2 8:04 3 20:19 3 8:09 ``` A single-pass point still shows as one plain number, so an ordinary race's sheet reads exactly as it always did. This is the point of the sheet in a lap race: a rider who lost two minutes on lap four is obvious in a column of lap times and invisible in a single summary number. ### Tap a row to record The sheet is also how you record somebody whose bib you can't read. Tapping a row does whatever your recording point does — checks them in, records their split, records a lap, or finishes them. The **recording-point buttons sit in the sheet header too**, so a marshal working down the sheet can see and change what their taps do without scrolling back to the bib box. It's the same setting in both places — change it in one and the other follows. Rows that can't be actioned (a rider already finished, when you're at the finish) simply aren't tappable. ### Correcting one rider Every rider with a recorded time carries a **⋮** button at the end of their row. **Right-click** the row does the same thing, and on a tablet so does a **long-press**. It opens the same corrections sheet the per-race screen uses: | | | | --------------------- | ---------------------------------------------------------- | | **Set a manual time** | Type the finishing time from the backup watch | | **Edit splits** | Fix, add, or remove a time at any timing point — see below | | **Void a lap** | Remove one lap with a reason — mechanical, crash, penalty | | **DNF / DNS / DSQ** | One tap, no confirm — UNDO has it if you misfire | | **Delete the result** | Puts them back to not-recorded | Riders with no time recorded at all have no menu — there's nothing yet to correct. Record them first, then fix the time. #### Editing splits **Edit splits** gives you one field per timing point, and in a lap race **one field per point per lap** — so you can correct the rider's lap-3 time at Halfway without touching lap 1 and lap 2. | To | Do | | ------------------------ | -------------------------------------------------------------------- | | Fix a time | Type over it | | Remove a crossing | Clear the field, or press the bin on that row | | Add one a marshal missed | Press the point's **+** button — it adds the next lap for that point | It warns, without blocking you, if the times you've entered don't increase down the course — the usual sign of a lap or a point typed into the wrong row. ### Lap races If any race in your chute is in [lap mode](/timing/formats/laps-and-primes) or is a relay, the sheet grows a **Lap** column (`3/5`) and a **Lap times** column listing every lap, and a crossing recorded for one of those riders is a **lap**, not a finish. Riders are finished on the lap that hits the target, and the confirmation says that's what happened. Riders in ordinary races on the same screen are unaffected — what a crossing means is read from the rider's race, not from a control you have to remember to flip. ### Riders who missed a timing point Tick **Every rider must pass here** on a point in [setup](/timing/screen/recording-points), and a rider who gets past it without a time there is flagged: the cell turns amber, their name picks up a **missed** badge naming the points, and a **Missed a point** filter appears in the header. They're only flagged once they've demonstrably gone past — they finished, or they have a time at a *later* point. Nobody is flagged for a point they simply haven't reached yet. **This never changes a result.** Their finish stands and their place stands. A blank cell is far more often an unstaffed post or a missed number than a rider cutting the course, so treat it as a prompt to go and check the post. If you look into it and conclude they did cut the course, DQ them yourself — [corrections](/timing/screen/corrections). ## Rearranging the screen Nobody uses all six panels at once. The person working the chute wants the bib box and the sheet; whoever is releasing waves wants the start board at the top and doesn't care about the RFID importer. **Panels**, at the top right, lists every panel with arrows to move it and a switch to hide it: | Panel | | | ----------------------- | ----------------------------------- | | Races through my chute | Which races resolve on this device | | Bib entry & capture | The number box and the stamp button | | Times waiting for a bib | The blind-capture queue | | RFID timing pad | CSV import | | Start board | Waves and race guns | | Race sheet | Every rider | **Per device**, like everything else on this screen that describes how one person works — moving yours doesn't move anyone else's. **Reset** puts them back. The Panels button itself never moves or hides, so you can always get back even if you switch everything off. ## RFID The RFID watcher is on this screen too — a chip-timed shared chute is the commonest place to be running a pad. It follows your chute selection: only the races you've ticked are offered as targets, and only their riders are matched against incoming reads. → [Timing with an RFID pad](/timing/hardware/rfid) ## Waves fit naturally here Combined finish and [waves](/timing/screen/waves) are usually used together: the wave board releases each group in turn, and net time keeps everyone comparable even though they didn't start at the same moment. The start board also lists **every race's gun** underneath the waves, whether or not that race uses them. The gun is what gun time is measured from, and for any rider who isn't in a wave it's what their net time is measured from too — so each race row says how many riders are timed from it. Both rows carry the same clock button: press it to set a start that already happened. See [forgetting to start](/timing/screen/corrections). ## Next Releasing start groups and how net time works. Assigning one number per rider across the event.