Lion Timing PhotoFinish

Buyer Questions

PrecisionReliabilityControlIntegration questionsSupport planningBackup workflowsReview workflowRace-day workflow PrecisionReliabilityControlIntegration questionsSupport planningBackup workflowsReview workflowRace-day workflow
Product
Buyer Comparison Guide
Start here The comparison method Buyer tools Professional systems map Buyer criteria matrix Academy comparison guide Alternative research
FinishLynx alternativeALGE OPTIc alternativeALGE vs FinishLynxTimeTronics Argus alternative
Pricing About Us Support Academy Book a demo
Back to Academy

Buyer Questions

The right questions make photo finish easier to understand and safer to buy.

If you are new to photo finish, you do not need to start with technical language. Start with practical questions about your event: where the camera goes, who operates it, how recording works, and what evidence is saved.

Buyer questions from real race-day workflows

Race-day complexity usually lives in a few predictable places: camera adjustment before recording, the selected meeting or heat, how recording is started, how images are evaluated, how participant information appears, how display boards receive data, and what happens when a start or arrival is missed. Those topics become the buyer questions below.

  1. Can we align it without guessing? The operator should have a live alignment view or a clear software reference that shows the actual finish-line scan position, not just a camera picture that looks roughly correct.
  2. Can we recover from common mistakes? Ask what happens if the operator forgets to arm the race, presses the wrong key, starts recording late, or gets multiple start impulses.
  3. Can we separate capture from evaluation? Some workflows use one computer for both recording and review; others support a separate evaluation station. If officials need fast results while another race is being recorded, this matters.
  4. Can we manage participant data? Ask how lanes, bibs, heats, participant lists, transponder mappings, and result lists are imported, edited, or exported.
  5. Can we prove the decision later? Ask whether the original recorded image remains available after zooming, cropping, exporting, printing, or publishing the result image.
  6. Can the system talk to the rest of the event? Ask about start impulse devices, photocells, scoreboards, wind measurement, timing consoles, APIs, and transponder systems only if those devices are part of the event plan.

The buyer should leave the demo knowing not just that the system works, but how it behaves when the event is imperfect.

Race-day scenario: wrong race active or evidence export needed

If the wrong race is active, the operator needs a clear way to attach the captured evidence to the correct event. If officials ask for evidence after a close finish, the export should be easy to create while the original recording remains available.

Demo questions checklist

BeforeShow setup from zero

Ask to see mounting, alignment, focus, event setup, and trigger checks.

DuringShow a messy moment

Ask what happens if the wrong race is active or recording starts late.

AfterShow the evidence path

Ask to reopen the race, review the image, export evidence, and explain the result.

What to ask before buying photo finish

  • What is required for our first event, and what can wait until later?
  • Who will train the operator, and what should they practice before race day?
  • How does the workflow protect evidence if a trigger or race selection is wrong?
  • What files or images can officials receive after a disputed finish?

Where does the camera go?

The camera should be placed where it can see the official finish line clearly, usually square to the line and high enough to avoid blocked views. The answer should include mounting, distance, lens choice, cable route, protection from athletes or public, and how the position changes for track, road, cycling, or horse racing.

How do we know it is aligned to the official line?

The operator should verify alignment in the software before the event. A good workflow uses the live image, finish-line markers, a test pass, and a visible reference so the reviewed image corresponds to the official line, not a painted line nearby or a camera angle that looks correct from the side.

What lighting is needed for readable evidence?

The finish line needs even, stable light on the part of the body, wheel, nose, or vehicle being judged. Ask whether the system can handle shade, night races, indoor light flicker, backlight, rain, and low sun. The practical answer should say when extra lighting is needed and where it should be placed.

How does recording start and stop?

The operator should be able to arm recording before finishers arrive, then capture the finish window without panic. A strong system supports operator control and planned workflows, and it makes clear what happens if the operator starts early, starts late, or needs to keep recording through multiple finishers.

What triggers the recording?

Triggers can be operator-controlled, connected to start or finish hardware, or part of an event workflow. The important question is not only how triggering works when everything is perfect, but what backup exists if a trigger is missed, delayed, disconnected, or pressed at the wrong time.

What original evidence is saved?

The system should preserve the source finish-line recording, not only a screenshot or final result image. Ask whether the original evidence, timing information, review image, export, and relevant metadata can be kept together so the result can be checked later.

How do officials review the finish?

The software should let the operator zoom, scroll through time, read the finish line, and compare each participant’s rule-defined finish point. For example, running may use the torso, cycling may use a wheel or defined bike point, and horse racing may use the nose.

Can the result be checked later?

A good workflow keeps enough evidence to reopen the race, explain the decision, and export a clear image for officials, organizers, or disputes. The buyer should ask what is stored, where it is stored, and whether exports are linked back to the original evidence.

What support is available on race day?

Ask who helps with first setup, training, software questions, and urgent race-day problems. The answer should name the support channel, expected response, what is included in the package, and whether someone can guide the team through the first real event.

First buyer shortcut

Ask to see one full race flow.

The demonstration should start with camera placement and alignment, then show recording, trigger behavior, finish review, result export, backup recovery, and how the original evidence is saved. If that flow is clear, the system is much easier to trust before race day.

Sources used

These questions come from topics covered in public timing-system documentation: installation, camera alignment, power, recording, triggers, judging, participant lists, export, and integrations.