Reference Manual
How to run random selections, manage your driver roster, and read your results in DTSMS Online. Written for company administrators and for drivers who want to understand how a selection works.
Your first selection is free, and no credit card is requested at sign-up, so nothing can charge you automatically. Your first company is created for you using the company name you signed up with, so you land on a working roster rather than an empty account.
If something on the form needs fixing, you're sent back to it with the problem fields marked and everything you typed (except the password) still filled in.
If you run selections for multiple companies under one login, use the company picker at the top of your account. Switching companies changes which roster, selections, and results you're viewing — it doesn't log you out or change your billing.
From your company dashboard, open Roster and click Add Driver. Enter a name and a unique driver ID. If your company uses Social Security Numbers as the driver identifier, you can enter an SSN directly and the system will treat it as the ID.
For larger rosters, use Import CSV instead of entering drivers by hand.
If your file has a Department column (the DOT agency or internal classification a driver belongs to), map it too — this feeds directly into the agency scope options on Running a selection. A Department name that doesn't match an existing entry in the department directory is not auto-created — it's left unassigned and reported in the import summary as a name to review, so a typo doesn't silently split your roster across two departments.
Click Deactivate on any driver row to remove them from future selections. If that driver has a Verified Positive or Verified Negative result already on file, the system asks you to confirm they've actually left the company before the deactivation goes through — an active driver on your roster shouldn't be marked Inactive for any other reason, since it affects your eligible pool for future draws.
A pool (also called a consortium) is a named group of companies whose drivers are combined into one shared roster for selection purposes. This is the standard setup for owner-operators and small fleets who test together to meet DOT random testing rate requirements.
You can belong to more than one pool, and unchecking a company removes it from that pool at any time without affecting its individual roster. Use Delete pool to remove the grouping entirely — the companies themselves are never deleted, only the pool that grouped them.
Every pool has a pool owner, the company that administers it. Only the pool owner can run a pool-wide selection across all member companies. A member company can manage its own drivers and run a selection for itself, but it can't draw across the rest of the pool. On a TPA account the owner is normally your own company — see TPA accounts.
A pooled selection notifies each member company's own DER separately — no company ever sees another member's drivers, even though the draw pulls from the combined roster. See DER notifications. You can also put a pool on an automatic monthly or quarterly schedule instead of running it by hand each time — see Recurring selections.
Every pooled selection you run is kept on the Pool History page — see Pool history. If a member company is leaving a pool you administer, it shows up on Pending pool departures.
Go to Run Selection for a single company, or Run Pool Selection to draw across every company in a pool at once. If your company has departments/agencies set up, choose which one to run against (or All DOT agencies combined, or DOT and Non-DOT together) — otherwise it runs against your whole active roster.
Drug and Alcohol each get their own rate, set the same way: either a fixed number of people or a percentage of the pool. DOT-regulated agencies use a fixed federal rate you can't change — DTSMS Online shows it, but there's nothing to configure. If your scope includes Non-DOT drivers, only that portion is yours to set.
You also choose a Number of alternates and a Selection mode: Separate draws (drug and alcohol are drawn independently, so different people can land in each) or Same person, both (anyone drawn is tested for both).
DTSMS Online draws names using a cryptographically secure random process, not a simple shuffle — the same standard used for lottery-grade randomness. Every eligible driver in the pool at the time of the draw has an equal chance of selection, and the eligible list is saved as a snapshot so the draw can be reconstructed for an audit later.
Selections are for random testing. For Pre-Employment, Post-Accident, Reasonable Suspicion, Return-to-Duty or Follow-Up tests, where you choose who is tested, see Creating a test.
Don't want to run this manually every period? See Recurring selections to set a pool or company on an automatic monthly or quarterly cadence.
Each selection produces a results list showing which drivers were chosen, their driver ID, and the company or pool the draw came from. Each selection has a plain sequential ID (shown as #1, #2, and so on) — it's not formatted to match any legacy DTSMS desktop numbering.
Export any selection to Excel from the results page. The export includes a full multi-sheet workbook — selected drivers, the eligible pool at draw time, and a summary sheet — for your records or an auditor.
If you've been notified that you were selected, it means your name was drawn as part of your employer's random testing program, not because of anything specific about you. Selection is random by design — every eligible driver has the same chance each time. Your employer will tell you where and when to report for testing.
| Term | What it means |
|---|---|
| Eligible pool | Everyone who could have been drawn for that specific selection |
| Selection ID | The unique record number for one draw event, used for audit tracking |
| Testing category | Whether the draw was for drug testing, alcohol testing, or both |
Once a selection has been drawn, each selected driver's actual test outcome gets recorded separately, on the selection's detail page. This doesn't change who was selected — that record stays locked, as described in Running a selection — it adds an outcome to a driver already on that list.
The test date is the collection date on the CCF. It can't be in the future, and it can't be earlier than the date of the selection. (For a test made with Creating a test, the selection date is the date you said the test was ordered.)
A driver who already has a result shows Edit Result instead of Enter Result. Editing a saved negative requires a reason for the change (at least a few words, for example "specimen ID typo"). The old and new values, who changed them, and your reason are kept in the result's change history, shown inside the result form.
If a result becomes part of a legal matter, open it and use Place hold with a reason. A held result can't be edited or deleted. Anyone who can enter results can place a hold. Only the account owner (not a staff login) can remove one, and the owner can still correct a held negative, with the change recorded. Held results show Hold on their badge.
If a selected driver was legitimately not tested (extended leave, no longer employed, no longer in a safety-sensitive position, or another reason), click Excuse beside their name, choose the reason and write a short explanation. The driver shows Excused and the reason. An excusal is not a result and doesn't appear on the MIS report. Anyone who actually was tested gets a result instead, and Excuse is no longer offered once a result exists.
On a random selection, leave Replace with next alternate checked to bring in the next alternate in their place. The replacement appears directly under the excused driver and needs a result like anyone else. Excusals can't be edited or deleted afterwards.
In most selections, the majority of drivers test negative and only a few need individual attention. Rather than clicking through everyone, use Mark Remaining as Negative, which sits under each Drug or Alcohol list on a non-pooled selection (random or created test). You also pick one test date for the whole batch. If everyone in that category already has a result logged, clicking it just tells you there's nothing pending — it won't overwrite anything.
DTSMS Online bills monthly per driver using graduated tiers — drivers past each threshold are billed at a lower rate, not your whole count at the top tier's rate.
| Drivers | Rate |
|---|---|
| 1–25 | $5.00 / driver / month |
| 26–100 | $4.00 / driver / month |
| 101+ | $3.00 / driver / month |
You're redirected back to a confirmation page. Your plan doesn't necessarily flip to Paid the instant checkout finishes — that switch happens when Stripe's webhook confirms the payment, normally near-instant but occasionally a few seconds behind the redirect. If the page still shows "Processing," refresh it or check back from Billing in a moment; nothing's wrong, it just hasn't caught up yet.
Once you're on the paid plan, the Billing page itself doesn't have a control to change your driver count or cancel — that currently goes through the link in your Stripe receipt email, or by contacting support directly.
| Issue | What to try |
|---|---|
| Verification email never arrives | Check spam, then use "resend verification" on the login page rather than creating a second account |
| CSV import skips rows | Check the import summary for flagged rows — usually a missing company name or an unrecognized state value |
| Pool results show blank company names | Refresh the results page; if it persists, contact support with the selection ID |
| Can't switch companies | Confirm you're logged into the account the company was added under, not a separate login |
| "A screening result is required" when saving an alcohol result | Alcohol results require a screening value on every save, and a confirmation value when the result is Positive — this is required, not optional, and the save is blocked until it's filled in |
| "A specimen ID is required" when saving a result | Every result needs the number from the physical CCF, negative results included — see Recording test outcomes |
| "Specimen ID is already on file for [driver]" | That exact specimen ID is already attached to a different driver's result under your account — double-check both entries against the physical CCF for a data-entry mistake |
| A staff login can't see a page or button I expect | Their role doesn't have that permission granted — go to Companies → Roles and check the box for that page/action, or confirm they have a role assigned at all under Companies → Staff |
| "Test date cannot be before the selection date" | The collection date can't be earlier than the selection. For a created test, the selection date is the "date ordered" you entered; see Creating a test |
| DER never received a notification email | Confirm a DER email is saved under Company → Manage Companies — it only applies to selections run after it was saved, see DER notifications |
| DER's confirmation link says "not valid" | The 14-day link has expired — have the DER request a fresh one at resend-der-link.php, see DER notifications |
Support runs through an in-app ticket system rather than email — every response you get back, and every actual fix, is logged directly on the ticket, so you can see the full timeline yourself rather than taking someone's word that it was handled.
Go to Support to see every ticket you've opened for your current company, newest first, with its status and how long it took to get a first response. Click into any ticket to see its full timeline:
| Status | What it means |
|---|---|
| Open | Submitted, not yet reviewed |
| Acknowledged | Reviewed — someone is actively looking into it |
| Resolved | Fixed, with the actual change that fixed it linked directly on the ticket |
| Closed | Wrapped up — no further action expected on either side |
You can add a follow-up comment to your own ticket at any time from its detail page, regardless of its status — no need to open a second ticket for the same issue.
The MIS report is the DOT MIS Data Collection Form, built from your company's actual recorded results rather than filled in by hand. It aggregates a full calendar year of test outcomes into the exact structure the federal form expects — Section III for drug testing, Section IV for alcohol testing — broken out by DOT agency.
Above the drug and alcohol tables, Section II shows your covered-employee count for that agency. When your driver activity log can supply it, this is the average number of covered employees for the year (through today, for the current year), which is the figure the DOT minimum rates are based on. A line under the count shows that average and how many drivers are active today. If the log has nothing for that agency yet, the count is simply the drivers active on your roster today.
The average starts from when your company began in DTSMS Online. Confirm the number against your own payroll records before filing.
Every table lists the six test types from the official form: Pre-Employment, Random, Post-Accident, Reasonable Susp./Cause, Return-to-Duty and Follow-Up, plus a TOTAL row. Random is filled from your random selections. The other five rows are filled from tests you recorded with Creating a test. Each result lands on the row for its test type automatically.
Each agency panel starts with a pace box (it doesn't print and isn't part of the DOT form). It compares the random tests completed this year with the annual minimum rate for that agency, applied to your covered-employee count, and says how many are still short. Only random tests count toward it.
If drivers were selected this year but have no result entered yet, the box also shows Awaiting results counts for drug and alcohol. A shortfall that is just missing data entry isn't the same as tests that never happened, so enter those results first. Excused drivers don't count as awaiting.
If your company runs Non-DOT testing (internal company policy testing that isn't part of a federal program), those results are shown in their own section at the bottom of the report, clearly separated from the DOT compliance numbers above it — Non-DOT results are never mixed into a DOT agency's totals.
Staff logins let other people work in DTSMS Online without sharing your own account credentials. Each staff login is scoped to exactly one company — someone added as staff for one company can never see, switch to, or affect any of your other companies, even if your account manages several. What that person can actually do inside their one company is controlled by a role you assign them.
They log in at the same login page you use, with their own email and password — DTSMS Online recognizes automatically whether a login belongs to an account owner or a staff member.
On Companies → Staff, click Deactivate next to their name. This takes effect immediately — if they're logged in at that moment, their very next click logs them out completely, and they can't log back in until reactivated from the same page.
The audit log shows every add, edit, status change, and selection-lock event for a company's drivers, in plain language rather than raw data — what changed, when, and who did it. It exists so "who deactivated this driver, and why" has a real answer inside the app, not something that requires asking your developer to look at the database.
Each row shows the driver, an action badge — Driver Added, Details Updated, Marked Inactive, Marked Active, or Sealed (Selection) — a short description of the actual change in the Details column, and who did it: either a specific staff member's name, or Account owner if you made the change yourself, logged in directly.
Entries are shown 30 at a time, most recent first, with Prev/Next controls at the bottom. There's currently no search or filter on this page — to find a specific driver's history, page through, or ask your developer to look it up directly if the list is long.
The audit log is scoped to whichever company you're currently viewing — it never shows another company's history, even if your account manages several. For a staff login, access to this page follows the same permission as the roster page itself: if their role can manage drivers for this company, they can see this company's audit log too.
Once a selection runs, results never go to whoever's logged in and clicked "Run Selection" — they go to each company's own Designated Employer Representative (DER), the person your DOT program designates to actually pull a driver for testing. This keeps the person triggering a draw from being the same person who learns who was picked, which is the standard your consortium's TPA arrangement is expected to meet.
Go to Company → Manage Companies. Each company has its own DER Name, DER Email, and DER Phone fields — enter them and click Save DER. This has to be done before a selection runs; setting the DER contact afterward does not retroactively notify anyone for a draw that already happened.
selection_der_notifications log for a skipped_no_der entry against that selection.
Each DER gets one email, scoped to their company only — even for a pooled/consortium selection spanning several companies, a DER only ever sees their own company's drivers, never the rest of the pool. The email lists who was selected for drug testing, who for alcohol, and who's an alternate. For a random selection the instruction is always the same: notify each selected employee and send them to testing only when they're already on-site, never in advance. For a test made with Creating a test, the subject names the test (for example "DOT Post-Accident Test") and the instruction fits that type, such as the time limits for a post-accident test or direct observation for return-to-duty and follow-up tests.
Every DER email includes a link the DER can open to view the same results on a simple web page, without needing to log in to DTSMS Online at all — DERs are not account holders. This link is unique to that one notification and expires automatically 14 days after it's sent.
The DER can request a fresh one themselves at oshaland.com/resend-der-link.php by entering the same email their company has on file. If it matches, a new link is emailed immediately with a fresh 14-day window. This response is the same either way — "if that email is on file, check your inbox" — whether or not it actually matched anything, so the page never reveals which DER emails are valid.
| Term | What it means |
|---|---|
| DER | Designated Employer Representative — the person authorized to pull a driver for testing on behalf of the company |
| Confirmation link | The one-time-issued, expiring link in a DER's email that shows their company's results without requiring login |
| Skipped, no DER | A selection ran, but no notification could be sent because that company has no DER email on file yet |
Rather than remembering to log in and run a selection every month or quarter, a company or pool can be put on a recurring schedule that runs automatically in the background.
The schedule runs itself from that point on — each run advances automatically to the next month or quarter, and produces the exact same kind of selection, results, and DER notification as running one manually. There's no difference in the record it leaves behind; a scheduled draw is audited the same way a manual one is.
A schedule can fail to run — for example, if a pool temporarily has no active drivers. This doesn't silently disappear: it's logged, and skips that period rather than crashing every other company's scheduled selections that same day. If you expected a draw and don't see one, contact support with the pool or company name and the expected date so it can be checked against the schedule's run history.
Federal Drug & Alcohol Clearinghouse rules require a pre-employment query before a driver first performs safety-sensitive duty, and a limited annual query for every driver at least once every 12 months. The Query Schedule keeps track of those due dates for your active roster and stores your records of what's been done — it does not run the queries themselves.
Go to Drivers → Query Schedule. The three tiles at the top summarize your active roster: how many drivers are Overdue, how many are Due within 30 days, and the total number of Active drivers tracked.
Each row shows a driver's CDL number, their last logged query date, when their next one is due, and a status badge. A driver with nothing logged yet shows No date on file instead of a due date — that's expected for a driver who hasn't had a query recorded here, not an error.
| Query type | When to use it | Effect on Next Due |
|---|---|---|
| Pre-employment | Before a driver first performs safety-sensitive duty for your company | Sets Next Due to one year out — this starts the driver's annual cycle |
| Annual | The recurring limited query required at least once every 12 months for every driver | Sets Next Due to one year from the date completed |
| Follow-on (post-notification) | Tied to a driver's return-to-duty / SAP follow-up testing plan, not a fixed annual cycle | Logs the completion but leaves Next Due unchanged |
Pick the query type carefully — Pre-employment and Annual both push Next Due out a year, so logging the wrong one will still show a due date, just possibly the wrong one for that driver's actual cycle. Follow-on is the one exception: it records the query without touching the driver's existing due date.
You don't have to remember to open this page. Once a day, DTSMS Online checks every active driver who has a Next Due date, and emails a reminder about any whose date is within the next 30 days or already past.
The email links back to the Query Schedule page and repeats that DTSMS Online only tracks the deadline — it never submits anything to FMCSA for you.
Query Schedule is scoped to whichever company you're currently viewing, same as the rest of the Drivers section — it never shows another company's due dates, even if your account manages several.
Pool History lists every pooled selection you've run, across all of your pools, newest first. It's the consortium-level audit trail: one record per draw, covering every member company at once.
Each row shows the pool name, the date and time of the draw, its scope (for example a specific DOT agency, or the whole pool roster), the selection number, and counts for drug, alcohol, and alternates. Click a row to expand it.
Use Export Excel on a row for the same multi-sheet workbook described in Reading your results.
If a pool has never been drawn, the page tells you so and links to Run Pool Selection. Staff need the pool-history permission on their role to open it — see Staff & roles.
When a company that belongs to one of your pools moves to a new account, it doesn't drop out of the pool instantly. It's scheduled to leave, and the Pending Departures page (pools/pending-departures.php) lists those companies so the pool's administrator can see it coming and, if needed, keep them in.
| Column | What it means |
|---|---|
| Company Leaving | The member company that has transferred to a new account |
| Pool | Which of your pools it's leaving |
| Requested | When the departure was scheduled |
| Effective | When the company actually leaves the pool, unless you cancel first |
Billing for the departing company has already moved to its new account. This page only affects who is included in your pool's selections.
You can only cancel while the departure is still within its grace period. If the grace period has passed, you'll get an error message instead and the departure stands. With nothing scheduled, the page simply reads "No pending departures."
Not every DOT test is random. Use Create Test to record a Pre-Employment, Post-Accident, Reasonable Suspicion / Cause, Return-to-Duty or Follow-Up test, where you choose exactly who is tested. It works for one employee or several at once. Random tests are still run from Running a selection.
A TPA (third-party administrator) account manages drug and alcohol testing for its client companies. Choose Reseller / TPA when you sign up, or ask us to convert an existing account. TPA rates are $4.00 / $3.00 / $2.00 per driver per month (drivers 1–25 / 26–100 / 101+), unless we agree something different with you. Once your TPA setup is approved, your account gets two extra pages under Company: Client Overview and Client Billing.
On Companies, each client has C/TPA name and C/TPA phone fields. They print on the C/TPA line of that client's MIS report. If you leave them blank and the client belongs to a pool, the pool owner prints there instead, so a TPA's clients are filled in automatically.
You are billed once, on the total active drivers across all your client companies, at your own rates (shown on Billing). The bill follows your roster: a nightly sync updates the number of drivers on your subscription, and Stripe prorates the change.
Client Billing shows what each client contributes so you can invoice them. Each client's amount is its share of your active drivers times your monthly total, so the amounts add up to exactly what you are billed. Choose a month to see past statements (saved from month-end driver counts) and use Download CSV for a spreadsheet. The current month is live.