01
Intake
Capture the condition, affected driver record, source, triggering evidence, date, and initial context.
BOF VAULT / Exceptions & Disputes / LEVEL 2 DOMAIN
Exceptions & Disputes
The administrative domain that keeps incomplete, conflicting, disputed, or aging conditions visible until the driver's record has an owned path to resolution.
An exception is an administrative condition, not an error message
Exceptions & Disputes controls what prevents a driver's record from being treated as complete, current, verified, or accepted for a particular process.
A missing medical-card page, conflicting credential date, disputed employment record, rejected evidence item, or unresolved ownership question can interrupt a driver's professional record. The important question is not merely whether the system shows an error. It is whether the condition is classified, routed, owned, aged, corrected, and historically explainable.
The Vault keeps the driver at the center of that work. BOF can preserve the condition and route administrative follow-up, while the driver supplies clarification or replacement evidence and an employer applies its own qualification decision. The exception remains part of the portable record rather than disappearing inside one employer's file cabinet.
The mechanics of an owned exception
A useful exception record says what is wrong, what it affects, who must act, what evidence is needed, and what happened next.
02
Classification
Distinguish missing, conflicting, disputed, expired, rejected, incomplete, or otherwise unresolved conditions.
03
Routing
Direct the next action to the driver, reviewer, verifier, employer contact, or designated administrator.
04
Aging
Keep due dates, follow-up attempts, elapsed time, and current status visible while the condition remains open.
05
Resolution
Record the corrective evidence, decision, owner, outcome, and historical reason the condition changed.
Visibility to resolution
The exception lifecycle prevents a condition from being lost between an alert and an undocumented closure.
01
Detect
A missing, conflicting, disputed, expired, or rejected condition enters the administrative view.
02
Classify
The condition receives a meaningful type, severity, affected record, and process context.
03
Route
The next action moves to the actor who can provide evidence, review the dispute, or make the applicable decision.
04
Own
A named owner, due date, and follow-up expectation remain attached to the open condition.
05
Investigate
Records, evidence, prior history, and involved people are compared without assuming the first submission is correct.
06
Correct
The driver or responsible actor supplies a replacement, clarification, or other corrective material.
07
Decide
An authorized reviewer or employer process records the applicable outcome and its limits.
08
Preserve
The original condition, action path, resolution, and any remaining limitation stay in history.
Three exception and dispute workflows
Each workflow shows how an exception becomes accountable work rather than a dead-end warning.
Workflow 01
Conflicting credential dates
Starting condition: A current credential and a supporting record show different issue or expiration dates.
Record involved: Both documents, their sources, driver association, date fields, and the conflict classification.
Actors: The driver provides clarification; BOF routes and records the condition; a reviewer assesses evidence; an employer owns its qualification decision.
Exception: Neither source can establish which date is authoritative or a replacement record is delayed.
Ownership and resolution: The clarification owner remains visible with follow-up and aging; resolution requires accepted evidence or an explicitly qualified status.
Historical consequence: The conflict, evidence considered, decision, and reason for the final date remain attached to the record.
Workflow 02
Disputed employment record
Starting condition: A driver disputes an employment-related document or its association with the professional record.
Record involved: The disputed document, driver's statement, source context, related credential, and review status.
Actors: The driver raises the dispute; BOF records it; an authorized reviewer investigates; a former or prospective employer may provide context without owning the Vault.
Exception: The parties provide inconsistent accounts or the original source cannot be obtained.
Ownership and resolution: The dispute stays assigned for review and cannot be silently marked resolved because a new document was uploaded.
Historical consequence: The dispute, evidence, outcome, and any limitation on use remain available to explain later status.
Workflow 03
Aging incomplete follow-up
Starting condition: A required document page or supporting evidence is missing after an initial request.
Record involved: The open exception, requested item, owner, request dates, follow-up attempts, and readiness impact.
Actors: The driver supplies the missing item; BOF tracks the request; the reviewer confirms completeness; the employer considers the qualified result.
Exception: The owner does not respond, the evidence remains incomplete, or the deadline passes.
Ownership and resolution: Aging remains visible and can be escalated or re-routed; closure requires documented evidence or a recorded decision to retain the limitation.
Historical consequence: The request and aging trail show why the record was not ready and what ultimately changed its condition.
Exceptions and accountability
The broken path still needs an owner
Disputed and unresolved conditions require visibility, ownership, action, resolution, and history in that order and often more than once.
Missing information is not the same as conflicting information. A disputed record is not the same as rejected evidence. Each condition gets its own classification, evidence request, owner, and next action so the driver and management can understand what is actually blocking progress.
Aging is part of accountability. If a request is unanswered, a review is pending, or a dispute cannot be resolved, the Vault preserves the elapsed condition and the follow-up path rather than presenting an unexplained green status.
Resolution means the corrective evidence or decision is recorded with scope and history. If the condition remains unresolved, the driver record can remain incomplete or not ready for the relevant employer process.
Exceptions follow the driver's record across employers
A condition does not vanish because the driver changes carriers, operating environments, or returns to a prior employer.
The Vault preserves the exception, its evidence, owner, aging, resolution, and historical status as the driver moves from Employer A to Employer B to Employer C. A new employer can receive appropriate current context without inheriting another employer's decision or becoming owner of the portable record.
When a driver returns to a prior employer, the record can show what was previously disputed, what changed during the intervening period, and which condition is current now. Continuity makes a resolved exception distinguishable from a deleted one.
An unresolved exception changes professional readiness
Management needs the administrative condition, the operational consequence, the required action, and the preserved history together.
Administrative condition
A disputed credential remains open after the requested source evidence was not supplied.
Professional / employment consequence
The driver may not have an accepted or complete record for the next qualification process.
Management action
Keep the dispute assigned and aging, request corrective evidence, and record the eventual resolution or limitation.
Exceptions & Disputes — Future Level 3 subjects
These are deeper workflow subjects beneath this Level 2 domain. They are visible architectural gateways only; no Level 3 routes exist in this batch.
01
Exception Intake
How missing, conflicting, disputed, rejected, expired, or incomplete conditions enter the administrative record.
Future Level 3 subject
02
Exception Routing
How the next action moves to the actor who can supply, review, decide, or resolve the condition.
Future Level 3 subject
03
Dispute Review
How conflicting accounts and evidence are examined with scope, ownership, and reviewer history.
Future Level 3 subject
04
Dispute Resolution
How corrective evidence, decisions, limitations, and outcomes change the exception status.
Future Level 3 subject
05
Exception Aging
How elapsed time, due dates, escalations, and unresolved responsibility remain visible.
Future Level 3 subject
BOF Vault next step
Turn unresolved conditions into accountable work
The BOF Vault assessment helps identify where exceptions, disputes, aging, ownership, and resolution are falling out of the driver's record.