Research 2026

Document Expiry Risk: A Sampling Framework for Compliance Files

A sampling framework for testing whether driver and carrier compliance documents are current, verified, and traceable.

Document Expiry Risk: A Sampling Framework for Compliance Files editorial illustration

Published October 22, 2026.

Research question: How can a carrier or brokerage sample compliance files to find expiry risk before a document lapses, without turning the audit into a paperwork sprint?

Method and evidence scope

This paper defines a sampling framework. The unit is a document record for a driver or carrier. Strata are document type and risk tier: identity and authority, medical or safety, insurance, and commercial agreements. Defect rules cover missing, expired, unverified, mismatched, and superseded documents. The framework uses a 90, 60, and 30 day window for expiry risk and reports defects by field and stratum. Public sources describe regulatory context, not a required completeness rate.

Table of contents

Start from the decision the file supports

A compliance file supports a decision: can this driver or carrier be used, and under what conditions? A document that is present but unverified does not support that decision. Define the decision owner and the minimum evidence for each document type. The audit should test the evidence the decision needs, not every field the system can store.

Document states that prevent false comfort

Use states that distinguish presence from acceptance: requested, received, incomplete, verified, expired, superseded, and missing. A file with a current date but no verifier is not verified. A renewal image that has not been checked is received, not accepted. The audit should count each state separately so a team cannot report a clean file on the strength of an upload.

Stratify by document type and risk

Not every document has the same expiry pattern. Medical cards, insurance certificates, authority records, and annual reviews have different cycles. Stratify by type and by risk tier so a small number of high-risk records is not buried under a large number of low-risk ones. Report the population count before sampling.

Defect rules and evidence

Write defect rules before review. Expired means the expiry date is before the audit date. Unverified means no verifier and date are recorded. Mismatched means the legal name, identifier, or effective date conflicts with another document. Superseded means a newer version exists but the file still points to the old one. Each defect should name the evidence location.

Sampling and second review

Use a random sample within each stratum and a second reviewer on a subset. If reviewers disagree, clarify the rule and record the change. A pilot can show whether a field is broadly missing; a precise rate needs a larger sample. Do not audit only the files that are easy to open, because inaccessible files are themselves a defect.

Reporting and remediation

Report the sample size, defect rate per document type, open expiries by window, and the owner of each fix. Pair the audit with a weekly expiry watch so the finding becomes a process, not a one-time cleanup. A repeat audit should use the same rules and show whether the defect pattern changed.

A minimum viable specification

Define the population, strata, sample method, defect rules, and audit date. Report defects by document type and state, open expiries by 90/60/30 day window, and the owner of each fix. Keep the rule version with the report. A repeat audit should reuse the rule so the comparison measures the process, not a new interpretation.

Review cadence and ownership

Run the audit quarterly and after a document rule change. Compliance owns acceptance and exceptions; the assistant owns the sample, indexing, and reminder queue. Record the rule version and the one process change for the next cycle. A clean sample is not a certification; it is evidence that the current control is working for the sampled files.

Limits

The framework tests document state, not the underlying truth of the document. It cannot verify a medical certificate with the issuing clinician or confirm insurance coverage beyond the certificate. It also does not establish that a clean file prevents a regulatory finding. Those questions require the appropriate compliance and legal review.

Sources

  1. FMCSA: Driver Qualification Files
  2. FMCSA: Regulations
  3. NIST Privacy Framework

Frequently Asked Questions

How many files should be sampled?

Enough to support the decision, with the method documented. A pilot of 20 to 30 records can reveal broad gaps.

Should expired documents be counted separately from missing ones?

Yes. They have different causes and different fixes.

What if a document is present but unverified?

Count it as unverified, not current. Presence is not acceptance.

Can the sample be used as a compliance certification?

No. It is an internal risk measure. Regulatory conclusions belong to the qualified compliance owner.