Non-DOT Workplace Testing

Non-DOT workplace drug testing records, organized in one secure workspace.

Non-DOT records, organized.

TestLedger™ Documentation Platform offers HR and compliance teams a customer-controlled record for each non-DOT testing event, with supporting files, timestamped reference states, and export-ready documentation when requested.

A secure workspace for each testing event, with supporting files, reference states, and export-ready documentation.

Customer-controlled Customer-retained Export on request
Non-DOT workplace drug testing documentation REC-2026-0094

Reference state recorded

Recorded May 8, 2026 · 8:03 AM UTC
Files Result CryptoSeal
One record per test
Each test event is documented in its own customer-controlled record.
CryptoSeal™ Engine
A SHA-256 reference state is recorded when the customer completes the record.
Supporting files stay attached
PDFs, images, video and text files remain linked to the record.

Customer-controlled. Customer-retained. TestLedger does not evaluate test results, determine compliance, or make employment decisions.

Why we built TestLedger

Watch the 2-minute overview.

A short explanation of how TestLedger keeps non-DOT testing records organized, supported, and export-ready.

How TestLedger works

One workflow. One completed record.

TestLedger helps HR teams capture the testing documentation workflow as it happens, keep supporting materials attached, and complete a record that can be checked later against its recorded reference state.

01 Recorded
Capture the event

Authorization, consent, collection details, results, and follow-up notes are entered into one structured workflow.

02 Attached
Attach supporting files

PDFs, images, short video clips, and customer-provided reference materials stay connected to the same record where enabled.

03 Completed
Complete with CryptoSeal™ Engine

At completion, TestLedger records a timestamped reference state and SHA-256 fingerprint for supported export comparison.

04 Compared
Recheck later

When documentation is requested, a supported export can be compared against the state recorded at completion.

TestLedger does not evaluate test results, determine compliance, or make employment decisions.

See workflow
Why This Matters

Documentation gets harder to trust when records are scattered.

When non-DOT workplace drug testing documentation is revisited, HR teams need more than a file search. They need a clear chronology, attached materials, and a way to check whether a supported export still matches the state recorded at completion.

Why document early

Early documentation reduces the scramble later. TestLedger helps teams record the workflow as it happens, complete the record, and preserve a reference state for supported export comparison.

Scattered files slow the response.

Paper forms, inbox attachments, spreadsheets, and shared folders can force teams to rebuild the record after the request arrives.

Chronology matters later.

Late assembly can leave teams sorting out what was entered, when it was captured, and which supporting materials belonged with the record.

Exports need a reference point.

Without a recorded reference state, it is harder to show whether a supported export still matches the completed record.

4.4% / 5.6%

Quest Diagnostics reported 2024 combined U.S. workforce urine drug positivity of 4.4% and general U.S. workforce urine drug positivity of 5.6%. Quest data reflect its reported workforce testing dataset and should not be treated as a prediction for any employer, industry, jurisdiction, or individual matter.

Platform essentials

One record. Supporting files. Export-ready documentation.

TestLedger gives HR and compliance teams a customer-controlled workspace for each non-DOT workplace drug testing record, with attached materials and supported export comparison when needed.

How the record works

Each completed record can organize the key tabs in one place: Authorization, Donor, Consent, Collection, Result, Customer THC Context, Follow-Up, Record Labels, Files, and CryptoSeal.

Authorization Donor Consent Collection Result Customer THC Context Follow-Up Record Labels Files CryptoSeal
What CryptoSeal supports

At completion, TestLedger records a timestamped reference state and SHA-256 fingerprint for supported completed records. Later, a supported export can be compared against that recorded state.

Important boundaries

TestLedger does not evaluate test results, determine compliance, provide legal or medical advice, certify testing procedures, or make employment decisions. Customers control what they enter and how records are used.

Workflow

Collect. Document. Complete. Check.

Turn customer-entered documentation for workplace drug testing events into completed records designed for documentation-sensitive workflows. TestLedger tracks completion status, timestamp consistency, and change detection without validating the underlying record content.

  • Every finalized record receives a SHA-256 state recorded at completion
  • Designed to limit identifier exposure in supported comparison workflows
  • Structured for consistent documentation handling across locations
  • Export timing depends on record volume, file size, configuration, and system conditions
CryptoSeal™ Engine SHA-256 Reference State CryptoSeal Record Check
CryptoSeal™ Engine
Record completion and record check workflow
01
Collect samples and data
02
Document structured records
03
Timestamped reference state saved
04
Compare supported export
One record. Everything inside.

One organized record with every key step in view.

TestLedger offers HR teams a cleaner way to see the chronology, supporting materials, completion status, and CryptoSeal™ reference state without rebuilding the file by hand.

TestLedger™ Documentation Platform
TestLedger™ Documentation Platform
Completed non-DOT workplace drug testing record
Reference state saved
Record TL-2026-0094
One organized workspace for chronology, supporting materials, completion status, and later supported export checks.
10 / 10 Tabs Recorded
✓
AuthorizationEmployer, reason, test date
✓
DonorCustomer-assigned donor code
✓
ConsentOutcome and timestamp
✓
CollectionSpecimen-handling references
✓
ResultRecorded result context
✓
Customer THC ContextCustomer-entered THC context
✓
Follow-UpCustomer-recorded actions
✓
Record LabelsLabels and custodian references
✓
FilesSupporting files attached
✓
CryptoSealReference state recorded
CryptoSeal™ Engine
A reference point for later comparison.
At completion, TestLedger records a timestamped reference state so a supported export can be checked later without reconstructing the file trail.
StatusReady
TimestampRecorded
Fingerprintd4e8b2c7...
Compare Export
Comparison applies to supported exports and completed record reference data.
STANDBY
Source
Processed
0 / 10
Authorization
Donor
Consent
Collection
Result
Customer THC Context
Follow-Up
Record Labels
Files
CryptoSeal
Reference state
CryptoSeal™ Engine
Reference-State and Consistency Workflow
REFERENCE-STATE PACKAGE RECORDED
CRYPTOSEAL ENGINESHA-256 | HMAC | AES-256-GCMv1.1.0
CryptoSeal Record Check Portal
When a record is shared for internal handling, audit preparation, or authorized external review, the receiving party can compare a supported export against the state recorded at completion.
Compare Export
www.testledger.io/check

When records are requested, what can HR assemble?

Two common documentation moments show the difference between a scattered file trail and a completed TestLedger record with attached materials and a recorded reference state.

Scenario 01

A record request after a testing event

HR needs to assemble authorization, consent, collection references, results, follow-up notes, and supporting files for one non-DOT workplace drug testing event.

Before TestLedger
  • Consent record stored separately
  • Collection details not linked to the result
  • Supporting file buried in email
  • No completed-record reference state
Later Documentation Note
"The team had to reconstruct the documentation path before it could compare the assembled file set."
With TestLedger
  • Consent timestamp recorded in the platform
  • Collection references linked to the same record
  • Supporting materials attached where enabled
  • Supported export checked against the recorded reference state
Comparison Note
In this illustrative example, the supported export matched the recorded reference state 92 days after record completion.
The completed record showed when the documented workflow was recorded, and the supported exported copy matched the recorded reference state during later comparison.
92days later, export matched recorded state
Scenario 02

A multi-site documentation review

A distributed employer needs to assemble records from multiple locations for internal review, audit preparation, or an authorized external request.

Before TestLedger
  • Site-by-site formats vary
  • Some fields are partial or missing
  • Records live in spreadsheets, paper files, or email
  • No consistent export structure
Documentation Note
"Four sites, four formats, and no consistent completed record for later review."
With TestLedger
  • Records exported in a consistent supported structure
  • Completion timestamps and record references included
  • Supporting materials stay connected where enabled
  • Export checks available for supported completed records
Standardization Note
Records from every location were exported in the same supported structure with timestamped fields and comparable completed-record exports.
The team can assemble one cleaner export set instead of reconciling site-by-site documentation by hand.
158example records, one supported export structure

Illustrative examples only. TestLedger does not certify testing programs, determine legal sufficiency, validate the underlying testing event, or make employment decisions. Outcomes depend on customer configuration, policies, applicable law, reviewer requirements, and counsel guidance.

Before and after TestLedger

From scattered files to one completed record.

When documentation is requested, HR needs a clear way to see what was recorded, what was attached, and whether a supported export still matches the state recorded at completion.

Scattered documentation
The record has to be reconstructed.
Consent, collection references, results, notes, and files may live across folders, email, spreadsheets, provider portals, and local handoff details.
4+ sources to check before review can begin
Consent timestamp Find
Collector details Confirm
Result document Match
Supporting files Gather
The review starts with searching, reconciling, and rebuilding.
Before
After
TestLedger workflow
Open one completed record.
TestLedger organizes workflow steps, timestamps, recorded actions, and supported files in a customer-controlled completed record.
Completed record packet
Workplace testing event
Completion reference saved
Workflow steps together Authorization, donor, consent, collection, result, follow-up, and completion status in one organized record.
Supporting files attached Supported PDFs, images, video, and TXT files remain connected to the same record where enabled.
Timeline and status preserved Recorded timestamps and completion details stay in one place for later handling.
Export comparison ready A supported export can be checked later against the recorded reference state.
HR can prepare a cleaner package for internal review, privacy, retention, legal-hold, disclosure, and counsel decisions without rebuilding the file first.

Plans for customer-controlled non-DOT documentation.

Start with Essentials for routine donor-coded records. Choose Professional when your program needs expanded context, identity-linked workflows where enabled, multiple locations, and higher monthly volume.

Essentials
$299 /month

For routine non-DOT workplace drug testing programs that need one organized record per donor-coded test event.

Best for
  • Routine donor-coded records
  • Smaller teams and lower monthly volume
  • Authorization, consent, collection, and result documentation in one workflow
Includes
  • CryptoSeal Record Check Portal for supported export checks
  • Search, reporting, and completed-record history
  • Supporting-file workflows after paid activation and required setup, where enabled
  • Up to 10 users
  • Up to 500 completed records/month
  • 1 TB included storage
Start Essentials Trial

When Professional fits

Professional is for teams that need more than a routine donor-coded record workflow.

Identity-linked workflows Document identity-linked donor records where enabled and appropriate for the customer program.
Expanded event context Add observer, policy, reasonable-suspicion, post-accident, and specimen-handling reference fields.
THC context Use dedicated customer-entered THC context workflows where applicable.
Follow-up activity Record customer-managed follow-up context in the same completed-record workflow.
Multiple locations Support larger operating teams with expanded administration and location management.
Higher capacity Increase monthly completed-record volume, users, and included storage.
Capacity Essentials Professional
Monthly price $299 $599
Users Up to 10 Up to 25
Completed records/month Up to 500 Up to 2,500
Included storage 1 TB 5 TB

Professional adds expanded context workflows, plus up to 5x monthly record capacity and 5x included storage compared with Essentials.

Taxes, add-ons, overages, implementation services, and professional services are not included unless stated in the applicable order form.

Trial and production notes

No credit card is required to start a trial. Trial accounts use fictitious sample records only and do not support PHI/ePHI, SSNs, biometric identifiers, identity-linked production data, BAA execution, production record completion, supporting-file upload, or production CryptoSeal Record Check exports. Trial accounts do not automatically convert to paid subscriptions.

Trial records, sample exports, sample completion events, and preview workflows are for evaluation only and must not be used for real employees, applicants, donors, customers, disputes, audits, employment decisions, production recordkeeping, lab reports, identity documents, photos, videos, or other production data.

Production PHI/ePHI-capable, identity-linked, and supporting-file workflows require paid activation and required agreement setup, including BAA execution where applicable or required.

TestLedger is a customer-controlled documentation platform provider and does not act as a laboratory, collector, MRO, C/TPA, employer decision-maker, insurer, auditor, counsel, compliance authority, or regulatory authority. TestLedger does not determine whether a testing program, notice, consent, collection process, laboratory result, MRO review, THC-related action, accommodation process, employment decision, retention practice, disclosure, or use of records is lawful, complete, accurate, admissible, or sufficient.

Answers for evaluating TestLedger.

A focused look at the workflow, record checks, trial limits, security posture, and customer responsibilities.

Start Your Trial.

Begin a 14-day evaluation with no credit card required. Explore the complete workflow in a preview-only environment.

Trial workspaces are for fictitious sample records only. Do not enter PHI/ePHI, SSNs, biometric identifiers, real employee, applicant, or donor records, lab reports, identity documents, photos, videos, or other production data during trial.

Contact TestLedger for product, account, billing, trial access, subscription setup, or BAA availability support. Do not send PHI or ePHI through ordinary support, email, contact forms, chat, or billing support. TestLedger does not provide legal, medical, compliance, employment, or testing advice.