A disputed drug test costs $125,000 to defend. Make sure your records aren't the reason you lose.

No. TestLedger does not conduct laboratory testing, perform MRO review, or provide clinical interpretation of results. It provides documentation infrastructure only. The platform records and seals the documentation surrounding a test; it does not perform, evaluate, or certify the test itself.

No. TestLedger is designed for non-DOT employer drug testing programs. If your organization conducts DOT-regulated testing under 49 CFR Part 40, the Federal CCF remains the required legal document of record. TestLedger may be used as supplemental documentation alongside the CCF, but it does not replace it.

A typical Basic record can be completed and sealed in a few minutes. Professional records with full chain-of-custody documentation, THC jurisdictional context, and evidence attachments take longer depending on the complexity of the testing event, but the structured form with dropdowns, checkboxes, and standardized fields is significantly faster than assembling the same documentation on paper. Once sealed, the record is cryptographically locked.

When a record is sealed, TestLedger computes a SHA-256 cryptographic hash over the complete record content, timestamp, and operator identity. If any data in the record is changed after sealing, the hash will no longer match, making the modification detectable. This is the same hashing standard used in banking, digital signatures, and blockchain technology.

Yes. TestLedger is vendor-neutral and works with any drug test kit from any manufacturer, any certified laboratory, and any third-party collection site. Your HR or compliance team enters results received from these providers into the platform. TestLedger does not require integration with lab systems, API connections, or changes to your existing testing workflow.

Sealed records are preserved in an append-only structure within the platform. They cannot be modified or deleted, even by account administrators. If a correction is required, a superseding record is created that references the original, maintaining continuity of documentation.

Verification confirms that a record has not been altered since it was sealed. When your organization exports a sealed record and provides it to an authorized party, that party can upload the file to the TestLedger verification interface. The system recalculates the cryptographic hash and confirms whether the record matches its sealed version. No record content is stored or exposed by the verification process; it requires possession of the exported file, which remains under your organization's control.

TestLedger is designed with PHI-aware architecture. Personally identifiable fields such as donor name and date of birth are available only in the Professional tier and are excluded from the cryptographic record hash for HIPAA isolation. Evidence uploads require a non-PHI attestation or an executed Business Associate Agreement. The platform displays warnings against entering PHI in free-text fields unless a BAA is in place. Organizations are responsible for determining whether their testing program involves PHI under HIPAA and for ensuring appropriate agreements are executed before submitting protected data.

Yes. The Professional plan supports up to 10 users across multiple locations with role-based access controls and an administrative dashboard. Every location uses the same standardized form and sealing workflow, eliminating the documentation inconsistencies that arise when different sites use different paper forms or spreadsheet templates.

Your HR team, compliance officer, or designated employer representative. TestLedger is not a lab system. It is the employer's documentation layer. When your organization receives test results from a laboratory, collection site, instant test kit, or MRO review, the designated person enters the complete testing event into TestLedger's structured form, including authorization, donor identification, consent, collection details, results, employment action, and any supporting evidence.

Yes. Records are controlled entirely by your organization. Sealed records are not publicly accessible, searchable, or visible to other TestLedger users. The verification portal operates on a possession-based model: only someone who already has the exported record file can verify its integrity. No record content is exposed during verification. Professional plan data is stored in isolated, encrypted S3 infrastructure. If your testing program involves PHI under HIPAA, PHI fields are blocked by default and can only be activated after executing a Business Associate Agreement.

When a test result flags THC, TestLedger prompts the operator to document four additional fields: the employee's primary work state, the THC legal status in that state at the time of testing, whether the position is classified as safety-sensitive, and the source of that classification. These fields are sealed into the record alongside the test result, providing documented evidence that the employer considered the jurisdictional legal framework before making an employment decision. This is increasingly critical in states with recreational or medical marijuana protections for employees.

No. Admissibility is determined by applicable law, evidentiary standards, and the specific circumstances of each case. TestLedger provides tamper-evident documentation architecture designed to support record integrity, which is substantially stronger than paper forms, spreadsheets, or unverifiable digital records. The platform does not provide legal, regulatory, or compliance advice.

You get full access to the platform with no credit card required. During the trial, records are stored locally in your browser and you can seal up to 10 records to evaluate the complete workflow. When you subscribe, both plans store sealed records in cloud infrastructure. The Professional plan enforces cloud-only storage with no client-side record persistence, which is required for workflows that may involve Protected Health Information. Both plans support JSON record export and independent verification.