01
Current state
Represent what is true now: current, expired, pending review, superseded, incomplete, or ready for an authorized use.
BOF VAULT / Continuity & History / LEVEL 2 DOMAIN
Continuity & History
The administrative domain that explains what happened to the driver's record, when it happened, why it changed, and what remains current now.
Current state is not the whole record
Continuity & History controls the chain between the record that exists today and the events, replacements, status changes, and employment transitions that produced it.
Simply storing the newest credential is insufficient. A current document may have replaced an expired certificate, corrected an inconsistent record, followed a verification question, or arrived after an employer transition. Without the historical chain, a reviewer sees a file but not the explanation behind its current state.
The driver can move from Employer A to Employer B to Employer C while the professional record remains connected to the driver. The Vault preserves enough history to show what existed, what changed, when it changed, why it changed, what replaced it, what verification occurred, and what remains relevant.
The mechanics of continuity
History is useful when each event explains a meaningful change in the record rather than becoming an unstructured activity log.
02
Historical event
Preserve an upload, replacement, review, verification, status change, employer transition, or correction with its timing.
03
Relationship
Connect a new document or status to the prior record it replaces, updates, clarifies, or leaves unresolved.
04
Reason
Capture why the record changed, including renewal, correction, expiration, employer handoff, or verification outcome.
05
Accountability
Keep the actor, next action, decision context, and follow-up visible across time and organizational boundaries.
From event to coherent history
The continuity lifecycle separates the current answer from the events that make that answer explainable.
01
Existing record
Start with the current professional document, status, and known relationships.
02
Change event
Record the upload, replacement, expiration, review, correction, or employment transition.
03
Comparison
Relate the changed item to what existed before and identify what is different.
04
Reason
Preserve why the change occurred and who supplied or recorded the information.
05
Status update
Update current state without deleting the historical state that came before it.
06
Verification history
Connect review or verification activity to the version and evidence considered at that time.
07
Continuity check
Confirm the record remains associated with the driver through employer or fleet transition.
08
Management view
Show current condition, aging, open action, and the history needed to interpret them.
Three continuity workflows
These workflows show why continuity is an administrative control, not a decorative audit trail.
Workflow 01
Credential replacement
Starting condition: A driver submits a renewed credential after the prior credential is approaching expiration.
Record involved: The new document, prior version, effective and expiration dates, source, and replacement relationship.
Actors: The driver submits; BOF records the transition; a reviewer or authorized verifier may assess the new evidence.
Exception: The new document has a date conflict or the prior version cannot be matched confidently.
Ownership and resolution: The driver supplies clarification or corrected evidence; the reviewer records the outcome; BOF preserves the open question until closure.
Historical consequence: The prior credential remains historical, and the reason the new record became current is visible.
Workflow 02
Employer transition
Starting condition: The driver leaves Employer A and begins a qualification process with Employer B.
Record involved: The driver's existing documents, current statuses, prior review context, and the event marking the employer transition.
Actors: The driver carries the record; Employer B requests appropriate documentation; BOF maintains relationships without transferring ownership.
Exception: Employer B requires evidence not present or disputes whether a prior record is current.
Ownership and resolution: The driver provides missing material; Employer B owns its qualification decision; BOF records the request and resulting status context.
Historical consequence: The record shows continuity across A to B instead of presenting B as a new identity or empty file.
Workflow 03
Historical verification question
Starting condition: A reviewer questions why a document was previously accepted or why a status changed.
Record involved: The document version, evidence considered, prior review, reviewer identity, decision status, and subsequent correction.
Actors: The reviewer investigates; the driver may provide context; an employer uses the result for its own process.
Exception: Supporting evidence is incomplete or a prior decision cannot be reconstructed from the available record.
Ownership and resolution: The unresolved question is assigned for follow-up and cannot be represented as settled merely because a newer file exists.
Historical consequence: The verification change and its reason remain attached to the affected version and current state.
Exceptions and accountability
An unresolved historical question stays visible
Continuity breaks when an old condition is overwritten instead of resolved. The Vault preserves uncertainty until an accountable action changes it.
An expired, superseded, inconsistent, or disputed record can affect the meaning of the current file. The right response is to relate the condition to its owner, evidence, next action, and due follow-up rather than deleting the old state.
A status change is not automatically a resolution. A reviewer may need to explain a decision, the driver may need to replace documentation, or an employer may need to apply its own policy. Each actor's responsibility remains distinct and historically visible.
If the condition remains unresolved, management sees both the current limitation and the aging history. The record does not imply readiness simply because activity has occurred.
The record survives changes in employment
Continuity means the driver's professional record remains coherent while employers, fleets, reviewers, and qualification contexts change.
The Vault connects Employer A, Employer B, and Employer C as contexts around the same driver-centered record. It does not make every employer a permanent owner of the Vault, and it does not copy one employer's operating file into the driver's professional record.
Current state answers what is true now. Historical record answers how that state came to be. Both are necessary when a credential expires, a document is replaced, verification changes, or a later employer needs to understand prior context.
A missing history changes the meaning of readiness
Management must be able to distinguish a resolved replacement from an unexplained disappearance of the prior record.
Administrative condition
A current credential exists, but its prior version and replacement reason are absent.
Professional / employment consequence
A prospective employer may face uncertainty about continuity, timing, or whether the current record addresses the earlier condition.
Management action
Reconstruct the event chain, assign clarification, and keep the current state qualified until the history is understood.
Continuity & History — Future Level 3 subjects
These are the deeper workflow subjects beneath this Level 2 domain. They are visible architectural gateways, not active links.
01
Continuity Documentation
The documents and relationships that keep the driver's record connected across employment and credential changes.
Future Level 3 subject
02
Continuity Events
The structured events that explain uploads, replacements, expirations, reviews, transitions, and corrections.
Future Level 3 subject
03
Continuity Audit
The history of actors, decisions, access context, changes, and unresolved conditions.
Future Level 3 subject
04
Continuity Chain
The relationship between what existed, what changed, what replaced it, and what is current.
Future Level 3 subject
05
Continuity Archive
The durable historical context retained when a record is no longer current but still explains the professional story.
Future Level 3 subject
BOF Vault next step
Keep the driver's record coherent through change
The BOF Vault assessment helps identify where current status is disconnected from the history required to trust and explain it.