In paddock media, per-class delivery is the baseline expectation. Missing a window means missing prime editorial placement, and the photographers who deliver on time keep the better access next round. Speed and accuracy are how reputation gets built in the paddock — but rushing by hand is exactly when class mix-ups and wrong-number tags slip in.
Understanding the problem
Delivery speed in MotoGP is compressed by the multi-class structure: three separate races mean three tagging deadlines, each only a short window apart. International rounds add a second layer — a race in Asia or Australia can fall on a European evening deadline and a US-morning deadline at the same time, so one set of photos has to satisfy several clocks at once.
MotoGP photographers work on tight paddock media cycles. Agencies expect class-specific galleries for each race — MotoGP photos kept separate from Moto2, separate from Moto3. Mixing classes or delivering late means your images get scooped by someone who got the sort right. The hard part isn't only speed; it's keeping three rosters straight under time pressure when fatigue makes manual mistakes more likely.
In this sport specifically
MotoGP's three-class structure creates layered delivery pressure: Moto3 finishes first, then Moto2, then the premier MotoGP race, each with its own delivery window not long after it ends. With short gaps between races and international time zones in play, tagging one class's photos by hand inside a single window is already hard. Doing it three times in sequence, while the next race is underway, is the real bottleneck — and the place where wrong tags creep in.
Where it shows up
Moto3 finishes and its delivery window opens while you're still culling. Moto2 is already on track, so you should be triaging Moto2 shots — but you're not done tagging Moto3 yet. · very common
Overlapping deadlines create workflow chaos. Manual tagging can't parallelize — you can't tag Moto2 while still finishing Moto3 delivery, so the backlog stacks across all three classes.
An international round (Malaysia, Thailand, Australia) means the race ends at one local time but European and US agency deadlines fall at different, earlier wall-clock times for those desks. · common
Time-zone miscalculation is costly. A photographer assumes there's more runway than there is, and a regional deadline has already passed. A slow manual pass per class makes hitting multiple time-zone deadlines effectively impossible.
A red flag or weather delay pushes the schedule, collapsing two or three classes' photos into the same short window — a single large backlog instead of three staggered ones. · occasional
Cascading delays compress all tagging into one window. A by-hand pass through that much material in the time available isn't realistic, so photographers end up choosing which class deadline to miss rather than ship rushed, error-prone tags.
A title-deciding finale where paddock media wants phase-specific galleries (start, opening laps, mid-race, final laps, podium) across all three classes. · occasional
Beyond single-race delivery, media wants timeline-specific galleries. Manual tagging can't segment by phase and class at once, forcing a choice between a complete gallery late or a partial gallery on time.
Traditional approaches, and why they fall short
Manual culling and per-class tagging with staggered delivery windows
Several hours of focused work per class, run sequentially across the evening and the next day — realistically more than fits in a single calendar day for one person · Reasonably accurate while you're fresh; quality drifts on the third class as fatigue sets in and mistakes increase
Time zones and overlapping deadlines make it very hard for one photographer to hit all three windows. You either miss the last class or rush and sacrifice accuracy.
Hire per-class dedicated photographers (one team for Moto3, one for Moto2, one for MotoGP)
Parallelized across three people, but at three people's cost for the weekend · Consistent per class, since each person handles a single roster
Expensive — only viable for major rounds or agency contracts. Solo photographers and smaller outfits can't justify it.
Batch delivery (deliver all three classes at once, post-weekend)
A long consolidation pass after the weekend, all classes together · Comparable to a careful manual pass, since there's no time pressure
Misses every same-day window. Saturday and Sunday delivery deadlines are simply gone. Unusable for agencies and paddock media that expect same-day galleries.
How RaceTagger handles it
RaceTagger reads the rider number off each photo and matches it against the start-list CSV you upload for that class — separate lists for Moto3, Moto2, and MotoGP. Because each class is matched against its own roster, the same number in two classes never gets confused: #23 in Moto3 is matched only against the Moto3 list, #23 in MotoGP only against the MotoGP list. It reads RAW (via the embedded preview) and JPEG, processes in batch, and writes the result back into each photo's metadata (EXIF/XMP/IPTC). When a number is hard to read — spray, extreme lean, motion blur, a low visor — it flags the photo for review instead of guessing.
Key advantage
You stop tagging by hand three times in a row. Queue each class's batch with its own start-list and let RaceTagger detect-and-match while you keep shooting and culling. The slow part — reading every number and looking it up against the roster — is handled in batch, so your time goes to reviewing the handful of flagged reads, not eyeballing every frame.
- Good conditions
- Clear, well-framed fairing numbers in good light are the easy case and match reliably
- Challenging
- Rain, spray, extreme lean angles, and motion blur are harder; more photos get flagged for review rather than auto-matched
- Worst case
- In the toughest conditions (gravel dust, heavy rain roost, poor visibility) low-confidence reads are flagged for you to confirm — the tool surfaces its uncertainty instead of guessing a number
Import each race's batch and load three separate start-lists (Moto3_starters.csv, Moto2_starters.csv, MotoGP_starters.csv). RaceTagger detects and matches per class, writes per-photo EXIF/XMP/IPTC, and can organize the output into per-class folders. Your review time concentrates on the flagged, low-confidence reads. Phase-based galleries (start / mid-race / podium) are organized after tagging by sorting the already-tagged files into folders.
Manual vs OCR vs AI vision
| Metric | Manual | Basic OCR | RaceTagger |
|---|---|---|---|
| Time to delivery-ready galleries across all three classes (culled, tagged, organized) | Several hours per class, run sequentially — hard to fit in one day, and prone to fatigue errors on the third class | Faster than fully manual but needs significant per-class fixing where reads are wrong | Detection-and-match runs in batch per class; your hands-on time concentrates on reviewing flagged reads, not every frame |
| Rider identification on clear shots with visible fairing numbers | Accurate but slow | Struggles with stylized fairing numbering and angles | Reliable on clear, well-framed numbers; matched against the class roster you provide |
| Keeping classes separated (Moto3 vs Moto2 vs MotoGP) | Humans rarely mix classes, but it's slow and tiring to maintain across three rosters | No notion of class — cross-class contamination is possible | Each class is matched only against its own start-list, so the same number in two classes is never confused |
| Rain or low-visibility conditions | Hard and slow; fatigue compounds on the third class | Drops off sharply on spray and blur | Harder reads are flagged for review rather than guessed, so you confirm the uncertain ones instead of trusting a bad auto-tag |
| Cost model for a three-class weekend | Your hours, or a multi-person team for a major round | Compute cost, plus the manual fixing time it creates | Credits — 1 credit per photo analyzed (free monthly allowance, then top up) |
Practical tips
- 1
Queue each race's batch to RaceTagger as soon as the race concludes — don't wait until culling is finished
RaceTagger reads RAW via the embedded preview, so you can hand it the shoot before you've finished your selects. Let the detection-and-match run while you refine the cull. Working the classes in parallel this way is the main time saver versus tagging each one end-to-end by hand.
- 2
Prepare three separate start-list CSVs (one per class) before the weekend, loaded with the current rosters
Dorna publishes official entry lists per class per round. Download all three the night before and format them as CSVs (rider number, rider name, team). Load all three at the start of the weekend so there's no roster re-entry between sessions.
- 3
Set up per-class output folders and delivery paths before the weekend starts
Decide your per-class destinations up front (a MotoGP folder, a Moto2 folder, a Moto3 folder) and let RaceTagger organize output by class. With paths fixed in advance, your upload step is a copy, not a decision made under deadline.
- 4
For rain or low-visibility races, plan for a larger review pass
Wet and low-visibility conditions mean more numbers are hard to read, so RaceTagger flags more photos for review rather than auto-matching them. Budget extra review time for a rain race and less for a clear, dry one — the flagged set is where your attention goes.
- 5
Coordinate with paddock media editors on your delivery sequence
Expectation management prevents 'where is it?' messages. Tell editors the order they'll receive galleries — Moto3 first, then Moto2, then MotoGP — so they can plan around your staggered sequence instead of reading the gap as lateness.
Tag all three MotoGP classes without three back-to-back manual passes
Try it free on a previous MotoGP weekend: upload each race's photos with its own start-list and see per-class detection, matching, and folder organization — with the uncertain reads flagged for you to confirm.
Try it free →Questions photographers ask
If the same number appears in two different classes, does the system tag it correctly?
Yes. Each class is matched against its own start-list. Number #42 in the Moto3 list is only matched against Moto3 photos; #42 in the MotoGP list is handled separately against MotoGP photos. The start-list you upload for each class is the source of truth for who that number belongs to, so a #42 from the MotoGP race is tagged to MotoGP's #42, not Moto3's.
Can the system create phase-based galleries (start, mid-race, podium) on its own?
RaceTagger detects and tags photos per rider; it doesn't segment by race phase for you. To build phase-based galleries, you sort the already-tagged files into folders (start, mid-race, final laps, podium) after tagging is done. The tagging carries the rider identity into the metadata, so the phase sort is a quick organizing step on top of it.
How does it handle international time zones and per-class deadlines?
RaceTagger processes your photos and writes metadata locally; it doesn't manage your agency deadlines. Keep your delivery coordination on a single shared clock with your desks (many agencies standardize on UTC to avoid confusion) and set your own reminders per class. The tool's job is to get each class tagged and sorted fast so the deadline math is the only thing you're tracking.
If a red flag compresses the schedule and several classes' photos arrive at once, can it keep up?
Yes — you can queue each class's batch as the material comes in, each with its own start-list, and RaceTagger works through them in batch. A larger or compressed backlog still goes through the same detect-and-match flow; your review then focuses on the photos it flagged as uncertain rather than on every frame.
What happens to photos where the number can't be read clearly?
Instead of guessing, RaceTagger flags low-confidence reads for review. On a wet or low-visibility race you'll see more flags, which is the point — you confirm the hard ones yourself rather than shipping a confident-but-wrong tag. It also skips frames with no vehicle/number to read, so your review set stays focused on real candidates.
Keep reading