A Partial BIB Number Should Not Be Guessed: How Exception Review Protects Race Photo Data
When only part of a participant number is visible, forcing a complete BIB can introduce avoidable errors. A structured exception-review process keeps uncertain references visible without turning assumptions into data.
Race photography often produces images where a participant number is only partly visible.
A runner may turn sideways. Another participant may block part of the BIB. Clothing may fold over one digit. Motion blur may make one number uncertain.
If the visible information does not support a confident participant reference under the project's rules, the better workflow is to preserve the uncertainty rather than invent the missing digit.
What Does a Partial BIB Look Like?
Imagine an image where the participant reference appears as:
Illustrative Visible Reference
The third digit is not clearly supported by the source image.
It may be tempting to assume that the number is 1284, especially if that seems plausible.
But if the image only supports 12?4, entering a complete number creates information that did not actually come from the visible source.
Guessing Converts Uncertainty Into False Certainty
The core problem with guessing is not simply that a processor might choose the wrong digit.
The larger issue is that the final record may look confident even though the source was uncertain.
Guess the Missing Digit
Partial source information is converted into a complete participant reference without a clear basis.
UNCERTAINTY HIDDENRoute for Exception Review
The visible portion is preserved and the record remains clearly marked for additional review.
UNCERTAINTY VISIBLEException Review Is a Control, Not a Failure
An exception queue should not be viewed as evidence that processing has gone wrong.
In many race-photo workflows, exceptions are an expected part of dealing with real-world imagery.
A controlled process distinguishes between:
- clear participant references
- partial participant references
- unreadable references
- multiple possible references
- conflicting supplied data
- missing source information
The important point is that each condition has an agreed path.
Partial BIB Exception Workflow
For a broader processing model, see our Race Photo Processing Workflow .
Why BIB Numbers Become Partially Visible
Partial BIB numbers can occur for many ordinary reasons.
Body Position
The participant is turned at an angle, hiding part of the number.
Another Participant
A nearby runner or rider blocks one or more digits.
Folded BIB
Clothing movement or folds obscure part of the participant reference.
Blur
Fast movement makes one or more digits difficult to distinguish.
Mud or Water
Obstacle and endurance events can physically cover portions of the BIB.
Image Crop
Part of the participant number falls outside the visible image area.
The Visible Portion Can Still Be Useful
A partial reference does not necessarily mean the image has no usable data.
The visible characters can still be recorded where the client's workflow supports partial-reference handling.
For example:
- visible reference: 12?4
- status: Review Required
- source image: preserved
- event reference: retained
- exception reason: partial BIB
This preserves what is known without pretending that the missing information is also known.
Supporting Reference Data Should Follow Defined Rules
Some projects may provide additional event data that can be used during exception review.
If so, the workflow should define:
- which reference sources are allowed
- how they may be used
- what counts as sufficient support
- when the record must remain unresolved
- how the final status should be documented
The existence of a possible match does not automatically mean the image should be assigned to that participant.
The processing rule should determine whether the supporting information is enough to resolve the exception.
Multiple Participants Can Make Partial BIBs Even Harder
Consider an image containing:
- BIB 1284 — fully visible
- BIB 2417 — fully visible
- BIB 30?6 — partially visible
The first two references may be routine. The third may require exception handling.
One image can therefore contain both completed and review-required participant references.
This is why tagging rules and exception rules need to work together.
See our guide on Multiple BIB Numbers in One Race Photo for the multi-participant side of this workflow.
Photo Indexing Should Preserve Exception Status
When partial references are stored in a race-photo index, the status should remain visible.
A structured record may include:
- image ID
- visible BIB portion
- event
- photo zone
- exception type
- review status
- final participant reference if resolved
This helps prevent unresolved data from appearing identical to fully validated data.
Learn more about structured image records through our Race Photo Indexing Services .
Partial BIB Handling Matters Even More in Larger Batches
In a larger event image workload, even a small number of guessed references can create repeated data-quality problems.
A better model keeps the decision rule simple:
Not clear enough under the agreed rule → Route for review.
This is easier to scale than asking each processor to decide independently how much uncertainty is acceptable.
For larger event workloads, see our Bulk Race Photo Processing Services .
Obstacle and Mud Events Need Strong Exception Handling
Obstacle races and mud runs are a useful example because participant references may be affected by:
- mud
- water
- obstacle structures
- body position
- crowded frames
- movement
In these conditions, forcing every image into a complete BIB record would hide the reality of the source material.
A review-aware workflow is therefore especially useful.
See Obstacle Course & Mud Run Photo Tagging for more on this event type.
Final Review Should Confirm How the Exception Was Resolved
The final check should not only ask whether the BIB field contains a value.
It should also confirm whether that value has a clear processing basis.
The Core Principle: Preserve Uncertainty Until There Is a Basis to Resolve It
A controlled workflow does not turn a partial BIB into a complete BIB simply because a complete value is convenient.
Good race-photo data processing does not require every record to look complete.
It requires every record to represent the source as accurately as the agreed workflow allows.
When a BIB is partial, preserve what is visible, document the exception and follow the defined review path.
Partial BIB & Exception Review FAQs
If the visible source and agreed project rules do not provide a clear basis for the missing digit, the record should remain partial or move into the exception-review workflow.
Where the client workflow supports partial references, the visible digits can be preserved together with an appropriate review or exception status.
Common causes include body position, another participant, folded clothing, motion blur, mud, water, equipment, obstacles or image framing.
If supporting data is supplied and the project rules explicitly allow it, it can form part of the review process. The resolution should still follow the agreed criteria.
Separate statuses preserve visibility into which records are complete, uncertain, unresolved or still awaiting review.
Need a Clear Exception Workflow for Race Photo Data?
Share your visible-BIB rules, exception categories, supporting reference data, review requirements, output format and approximate image workload to discuss how the processing workflow can be structured.