FMCSA Annual MIS Report Drug Testing: Employer Guide

Preparing an FMCSA annual MIS report for drug testing can feel like a once-a-year paperwork exercise, but the underlying work starts with accurate records collected throughout the year. The Management Information System (MIS) report summarizes a motor carrier employer’s DOT drug and alcohol testing program data. Employers should know what the report covers, how to respond if FMCSA requests it, and why the report is not a substitute for other compliance duties.

Talk with a compliance specialist

What Is an FMCSA Annual MIS Report?

MIS means Management Information System. For DOT-regulated employers, an MIS report is a calendar-year summary of drug and alcohol testing program information. It is a standardized way to report program-level data, such as the number of covered employees and testing activity and results, rather than a list of individual drivers’ names or a substitute for each employee’s test record.

FMCSA’s reporting framework is part of the DOT drug and alcohol testing rules. Employers must prepare and retain annual summaries of their program results and provide a report when the agency requests one under the applicable rules. In other words, an employer should not assume that every carrier files the same form on the same date every year. The specific submission obligation, format, and deadline depend on the applicable rule and the agency’s notice or instructions. See the Federal Register discussion of DOT MIS reporting procedures and 49 CFR Part 40.

The report gives the agency a summary of testing-program activity. It does not replace a written testing policy, individual records, required notices, or documentation of a specific test. Employers that need a broader overview of testing-program responsibilities can review Patriot’s guide to DOT drug testing programs.

Who Needs to Prepare or Submit an MIS Report?

Employers subject to FMCSA’s drug and alcohol testing rules should be prepared to create and maintain the annual summary required by the regulations. Submission is a separate question. FMCSA may direct an employer to submit MIS information, and employers need to follow the agency’s request rather than rely on assumptions based on another carrier’s experience or a prior year’s process.

Do not confuse a requirement to prepare and retain a summary with an automatic annual filing obligation for every employer. Read the current FMCSA communication carefully. It should identify the reporting period, the requested data, the filing method, and the due date or other response instructions. If the employer receives a notice, make sure it reaches the designated employer representative (DER), compliance lead, and any third party administrator (TPA) responsible for program records.

Responsibility remains with the employer even when a TPA, consortium, laboratory, or collection network helps gather data or administer testing. A service provider can support data compilation and quality checks, but the employer should confirm that the reporting population and information are complete and that the report is submitted as instructed. Learn how TPA and consortium support can fit into program administration.

Coverage can be complicated when an organization has multiple operating divisions, locations, or related legal entities. First identify the employer entity covered by the FMCSA program and the safety-sensitive employee population associated with it. Then reconcile that group against the company’s driver roster, payroll or HR records, and program enrollment information. When the scope is unclear, ask the agency or a qualified compliance resource before combining or separating records.

A practical way to define scope is to write down the employer name and identifiers used for the DOT program, the relevant operating units, and the reporting year before anyone starts exporting data. Then note which records belong to another DOT agency or a non-DOT testing program. A parent company may share a payroll system across subsidiaries, but shared software does not by itself mean the entities belong in one report. Keep the scope note with the working papers so that reviewers can see the logic behind the population and repeat the same process next year.

What Information Is Included?

The MIS report summarizes information about a testing program over a calendar year. The exact fields and format depend on the current reporting instructions and form. In general, the employer should be ready to validate the employee population, the types of required tests conducted, and the results or outcomes reported for the relevant categories. Test events may arise from pre-employment, random, post-accident, reasonable-suspicion, return-to-duty, and follow-up requirements, as applicable to the program.

Do not treat a summary as permission to disclose more personally identifiable information than the form requires. Use the fields requested, protect individual records, and transmit the report using the designated method. When preparing the supporting detail, keep employee-level documents separate from the aggregate totals and restrict access to people with a business or legal need to handle them.

This table is a planning aid, not a substitute for the current MIS form or instructions. Report counts according to the definitions on the applicable form. For example, a company should not assume that every collection, canceled test, or administrative correction belongs in the same category. Confirm how the form treats each situation, and document the decision when a record needs interpretation.

Think of the report as a controlled roll-up, not a fresh count made by searching email at filing time. Source information might come from a TPA report, laboratory or breath alcohol testing records, the employer’s roster, and documents about events that required follow-up. Each source has a different purpose and may use its own labels. Map those labels to the MIS form only after confirming what the event represents and whether it falls within the reporting period.

For example, if a provider export shows a test marked “pending” near year-end, do not automatically treat it as a final result or leave it out without review. Check the underlying record and applicable instructions, record the resolution, and make sure the final count matches the prescribed category. If a single event appears in two systems, trace it by the identifiers available to the authorized reviewer and resolve whether it is a true duplicate rather than counting both rows.

How Should Employers Prepare the Report?

A careful process reduces last-minute searches and makes totals easier to defend. The following steps work well whether a report is requested by FMCSA or the employer is preparing its annual summary for recordkeeping.

1. Confirm the reporting obligation. Identify the rule, agency request, reporting year, and due date. Save the notice and the current form or instructions. If there is no request to submit, still complete the required annual summary and retain it as directed by the regulations.
2. Assign an accountable owner. Name the person who will coordinate data, review totals, approve the report, and retain proof of filing. Include a backup contact so a staff change or absence does not interrupt a response.
3. Define the reporting population. Determine which employer entity and covered employees belong in the report. Reconcile the applicable driver list with program enrollment, employment changes, and records maintained by the TPA or consortium.
4. Collect source records. Request year-specific reports from each relevant service provider and retrieve the employer’s own records. Use consistent reporting dates and confirm that every record belongs to the correct employer and reporting period.
5. Reconcile totals by category. Compare the MIS categories with the source data. Investigate discrepancies, duplicate records, missing results, and items that appear in one system but not another. Keep a short note of how each material difference was resolved.
6. Review the form before submission. Check the reporting period, employer identifiers, contact information, required fields, totals, and certifications. A second reviewer can catch transposed digits or a category that was left blank.
7. Submit and preserve evidence. Follow the submission channel and deadline provided by FMCSA. Retain the final report, any confirmation or receipt, the source summaries, and notes supporting corrections or unusual entries.

Build this process into the annual compliance calendar instead of starting when a deadline approaches. A month-end or quarter-end reconciliation can expose gaps while the related records are still easy to locate. Employers using several locations or providers can designate one central owner and use a standard data request that specifies the employer, reporting year, cutoff date, and categories needed.

Make the data request specific enough that each contributor returns comparable information. Include the legal employer or program name, calendar-year start and end dates, the response deadline for the internal collection, and the categories or fields needed. Ask providers to identify the date the report was generated and whether it is final or preliminary. If the provider cannot supply a requested field, record that limitation and find the appropriate source rather than silently substituting a different measure.

Use a reconciliation log to move from raw exports to approved totals. A simple log can list the category, source value, MIS value, difference, question raised, resolution, reviewer, and date. For instance, when the employer roster includes a driver who is absent from a consortium report, the owner can check enrollment dates and program status, then document whether the person belongs in the reporting scope. The log need not repeat sensitive test details; it should show the reasoning and point to restricted supporting records.

Before the final review, freeze a dated copy of each source file and mark the version used to prepare the report. This prevents a later export from being confused with the original data set. Have a second reviewer compare the entered totals back to the reconciled worksheet, not just reread the form. Check arithmetic, reporting year, units, employer identifiers, and required attestations. If the submission portal provides a receipt or confirmation, save it alongside the final report and note the date and person who submitted it.

What Timing and Recordkeeping Issues Matter?

The reporting year for an annual summary is a calendar year, but that does not mean an employer should invent a universal filing date. If FMCSA sends a report request, follow the deadline and directions in that notice. If the current regulations or a formal agency instruction establish a time period, use that authority. When the due date is unclear, promptly ask the issuing agency rather than waiting until the presumed deadline has passed.

Keep the final MIS report together with the records needed to support its numbers. This may include employer rosters, provider summaries, reconciliation notes, copies of applicable instructions, and proof of submission. The underlying retention periods differ by record type; do not assume that one period applies to every test, annual summary, or report. The Department of Transportation’s DOT recordkeeping requirements chart is a useful starting point, but employers should verify the current requirements that apply to their program and agency.

Access controls matter because the source data may include sensitive employee information. Store records in a secure system, limit access to authorized personnel, and use a consistent naming convention that makes the reporting year and employer entity clear. If a vendor prepares a summary, make sure the employer can retrieve the report and its supporting records after a contract or account change.

For multi-state or multi-division operations, define who owns data quality at each site and who resolves conflicting records. A local office may know that a test was canceled or repeated, while the central compliance team sees only a consolidated export. A basic exception log can record the employee identifier, event date, discrepancy, person who reviewed it, and final disposition without putting unnecessary sensitive detail into the MIS file.

Retention planning should include the supporting trail, not just the submitted form. Keep a record of which source exports were used, who reviewed the totals, what changed during reconciliation, and how a requested correction was handled. Preserve that material in the appropriate restricted location and apply the relevant retention schedule to each record category. When people or vendors change roles, verify that the employer still has access to historical records and knows who can retrieve them.

A useful annual closeout sequence is to confirm that all sites have sent their files, reconcile late-arriving items, complete the summary, document review, and then place the report and supporting material in the designated records system. If the report is requested before the normal closeout is complete, identify what is missing immediately and follow the request’s instructions. Do not let an internal process delay cause the employer to miss the agency’s stated response date.

How Is MIS Reporting Different From Clearinghouse Duties?

MIS reporting and the FMCSA Drug and Alcohol Clearinghouse are related to drug and alcohol program compliance, but they are not the same process. The MIS report is an annual summary of program information, prepared and retained and submitted when required by the agency. Clearinghouse obligations involve a separate electronic database and specific employer duties concerning queries and reporting of certain violations. Completing one process does not automatically satisfy the other.

Likewise, MIS reporting does not replace individual testing procedures under Part 40 or employer obligations under FMCSA’s testing rules. A report with correct totals cannot fix a missed test, incomplete chain-of-custody documentation, an overdue Clearinghouse action, or a gap in a written policy. Keep a separate compliance calendar for the distinct tasks, owners, and records. Employers managing broader DOT obligations can review the information on DOT and non-DOT compliance support and FMCSA drug testing requirements.

Separating the workflows also helps teams avoid using the wrong record or deadline. A Clearinghouse task may involve an individual driver and an electronic query or report, while MIS preparation compiles program-level information for a particular reporting year. Give each obligation its own calendar entry and evidence folder. When the same person owns both, use distinct checklists so completion of one item is not mistaken for completion of the other.

What Common MIS Reporting Errors Should Employers Avoid?

• Assuming everyone files automatically each year. Distinguish the annual summary and recordkeeping requirement from a specific submission request. Respond to the actual notice and current instructions.
• Using the wrong reporting period. A prior-year export or a rolling 12-month report may not match the calendar-year reporting period. Confirm the dates before calculating totals.
• Mixing employers or programs. Data from different legal entities, DOT agencies, or non-DOT programs can distort the report. Set the reporting scope before merging records.
• Counting the wrong event or outcome. A canceled, incomplete, or corrected event may require special handling under the form’s definitions. Do not classify it based only on a shorthand label in a vendor export.
• Trusting one data source without reconciliation. A provider’s summary is useful, but compare it with employer rosters and any other relevant records. Follow up on unexplained differences.
• Leaving no audit trail. If totals change during review, preserve the source version, final version, and a concise explanation of the correction. Otherwise, the employer may be unable to explain how it reached the submitted figures.
• Waiting until the due date to locate records. A departed employee, expired vendor login, or missing site file can slow preparation. Gather records throughout the year and confirm access before the reporting period closes.
• Treating submission as the end of compliance. Maintain the separate testing, policy, Clearinghouse, and retention processes that apply to the employer.

For an employer that discovers a discrepancy after submission, the practical first step is to document what was found and when. Compare the submitted figure with its source records, identify whether the error affects a reportable field, and follow any correction process described by FMCSA. Do not silently replace a filed report or assume that a material error is harmless. Retain the original and corrected versions and a record of any communication with the agency.

Several process failures often lead to these errors. A request sent only to one employee may be missed during an absence, so keep a backup contact and route agency correspondence to the responsible compliance function. A provider file may use a cutoff date different from the employer’s, so record the date range on every export before combining data. A spreadsheet may also preserve old filters or formulas; use a controlled working copy and have a second reviewer check the totals against the source, especially after sorting, copying, or removing duplicate rows.

When a variance appears, resist the urge to force the numbers to match by editing a source record without support. First determine whether the sources cover the same entity, period, event type, and status. Then contact the data owner who can explain the discrepancy, retain the response, and make only corrections supported by the record and reporting instructions. If the meaning remains uncertain, seek clarification from the agency or an appropriate compliance professional and document the question and guidance received.

Frequently Asked Questions

Does every FMCSA-regulated employer submit an MIS report every year?

Do not assume that all employers have the same annual filing obligation. Employers should prepare and retain the required annual summary and submit a report when directed under the applicable rules or agency instructions. Follow the current request and verify the filing requirement for your situation.

What period does the report cover?

The annual summary concerns testing-program information for a calendar year. Check the form or agency notice for the exact reporting dates and instructions, particularly if you are working on a requested submission.

Can a TPA or consortium submit the report for an employer?

A TPA or consortium may help collect records, administer the program, or assist with preparation. The employer should still confirm the scope, accuracy, submission instructions, and proof of filing. Clarify who performs each task in writing so that a shared responsibility does not become an unowned one.

Is the MIS report the same as a Clearinghouse report?

No. MIS reporting is a program-level summary. Clearinghouse query and violation-reporting duties are separate obligations with their own requirements. Keep separate procedures and records for each.

How long should an employer keep MIS and supporting records?

Retention depends on the type of record and the applicable regulation. Consult current DOT and FMCSA requirements rather than applying one retention period to every document. The DOT recordkeeping chart linked above can help identify the relevant categories.

Request help reviewing your reporting process

A reliable MIS report begins with a clear reporting scope, reconciled records, and a documented review—not a last-minute search for totals. Keep the annual summary, any requested submission, and the supporting records organized so your team can respond accurately when FMCSA asks.