DQ Checklist Requirements

An overview of DQ checklist requirements and how to complete them

 

Table of Content 
DQ Checklist Requirements
How the Checklist Helps You Keep Track
Dealing with Incomplete Requirements
Requirement Errors & Completing Requirements
List of DQ Checklist Requirements
Reporting Feedback

DQ Checklist Requirements

DQ Checklist requirements can be in two states: complete or incomplete. Think of these as whether the requirement is fulfilled or not. To track this, there's a behind-the-scenes method in the code, but you don't need to worry about that part.

How the Checklist Helps you Keep Track: 

The checklist determines if a  requirement is complete based on the documents attached to an application. Each requirement looks for specific types of documents and uses them to gather needed information.

Complete requirements are shown with green check marks on the DQ Checklist Summary page, while incomplete requirements are displayed with a red number indicating the issues.

Dealing with Incomplete Requirements:

To address incomplete requirements, simply click on them. This will show you details on how to complete the requirement. For example, with the "Annual MVR Review," it will tell you that you need to provide a document with the type "MVR Review."

This way, it's easier to understand how DQ Checklist requirements work and what to do when you come across incomplete ones.

Requirement Errors & Completing Requirements

To make sure you're always working with the most accurate information, we regularly examine all the requirements for any mistakes. If any errors are found, the system marks those requirements as incomplete. You'll spot this because there's a little warning symbol next to the requirement's name, a count of how many issues there are next to each requirement on the Summary page, and a Complete counter below the checklist header.

How to Get More Details About Errors:

If you're curious about the errors and want to know more, just click on the name of the requirement. This will give you extra info about what needs to be fixed to complete that particular requirement.



This process is all about keeping your checklist accurate and making sure you have the most reliable information when you need it.

 

List of DQ Checklist Requirements

We've listed each requirement in the DQ Checklist, along with what you need to do to finish it.

Driver Application
Pre-Employment MVR Inquiry
Safety Records Request
Medical Examination
Certified Medical Examiner Requirement
Road Test
Drug and Alcohol
Annual MVR Inquiry
Annual MVR Review
Safety Records Correction
LCV Certificate
Skill Performance Certificate
Multiple Employer Drivers

1. Driver Application

• What's needed:  Application
• How to Complete: Supply a  driver's application. This can include signed DriverReach applications or manually uploaded Application documents.
• Document Rules: Only one document of this type is required.
  
  

2. Pre-Employment MVR Inquiry

• What's needed: MVR with an MVR Type of Pre-employment
• How to Complete: Supply a document of type MVR with an MVR Type of Pre-employment. Check the verification box.

• Document Rules:
  • Requires a Report Date,
  • Next Review Date,
  • Document must indicate MVR Type of Pre-employment
  • Only one document of this type is required

3. Safety Records Request

What's needed:  Verification of Employment (VOE) document
How to Complete:

1.) First, you'll need to supply a verification document. This requirement will recognize three types of verification documents: 

• Documents that are automatically generated when a VOE is complete or purchased
• Documents that are manually attached to the Verification Results section of a verification request.
  
  
• VOE documents that you upload manually (either via the checklist requirement or documents tabs.) 
  
  
  
  

2. Finish the Verifications milestone. You can do this either automatically through the system or by marking the milestone as complete yourself from the applicant's profile.



Document rules: 

• You only need one type of this document
• Verification documents that are automatically created or attached will show as a "Verification document" type. You can't manually upload this type.
• Verification documents will only be visible under this requirement if their end date is within the three years before the application's creation date. However, manually uploaded VOE documents are always an exception, as their end dates are not collected during the upload process, so they will always appear under this requirement.

 

4. Medical Examination

• What's needed: DOT Physical 

• How to Complete: Supply a document of type DOT Physical. Verify the most recent medical examiner's certificate.
• Document Rules: Each document supplied requires a Report Date and expiration Date, and it should cover specific years based on employment history. Must have a current non-expired DOT Physical.

5. Certified Medical Examiner Requirement

What's needed:  National Registry Verification document 
How to complete:  Supply the above document
Document Rules:

• Each document must have a "Report Date."
• You should have one "National Registry Verification" document for every two years of work in the past three years.

Important Points: The National Registry Verification must be up-to-date (not expired), and this rule only applies to applications in the "hired" stage. The Report Date helps check when the document expires, and at least one National Registry Verification should be dated within two years of the current date.

6. Road Test

What's Needed: Provide either a Road Test document or a CDL (Commercial Driver's License).

How to Complete:
Use any Road Test document uploaded via the applicant's Onboarding & Orientation page.

Document Rules:
You only need one document, and it can be either a "Road Test" or a "CDL."

7. Drug and Alcohol

What's Needed: You can provide either a Drug Screen document or a Drug Screen Exception.

How to Complete:

You can use any Drug Screen document uploaded via the applicant's Onboarding & Orientation page.

Document Rules

You only need one document, and it can be either a Drug Screen or a Drug Screen Exception.

• A Drug Screen Exception requires no additional information 
• A Drug Screen requires: 
  • Result type
  • Where it was ordered
  • Where it was verified
  • The variety type
  • The result 

8. Annual MVR Inquiry

What's Needed: You need to provide a document of type "MVR" with an MVR Type of "Annual."
Important Note: This requirement can be overridden.

How to Complete:

• This requirement is automatically marked as complete until one year after an applicant's hire date.
• You can provide an "MVR" document.

How It Works:

• When you manually upload documents using the requirement's uploader, the MVR type is automatically set to "Annual."
• When uploading documents via the applicant's DQ File or Documents tabs, you must choose the "Annual MVR" type.

• This requirement will recognize documents generated as a result of background check orders from specific providers (Asurint, DriveriQ, Foley, and HireRight). If these orders contain an MVR or Motor Vehicle Record, it will be tagged with an MVR label and appear under this requirement. Removing the MVR label will unlink it from this requirement, but the document will still be accessible in the applicant's Documents tab.
• You can edit these documents and change the MVR Type to "pre-employment" to move them to the "Pre Employment MVR Inquiry" requirement.
• There's a checkbox for you to confirm that all required MVRs have been returned and reviewed.

Document Rules:

• Each document must have a "Report Date."
• Each document must have a "Next Review Date."
• Documents must have an "MVR Type" of "Annual."
• You need an MVR document for every year of employment in the last three years.

Override Option:

If your company has enrolled in Continuous License Monitoring, you can override this requirement by checking the box for "Continuous License Monitoring" in the company's Compliance Configuration settings.

9. Annual MVR Review

What's Needed: You must provide a document of type MVR Review.
Important Note: This requirement can be overridden.

How to Complete:

• Provide a document of type MVR Review

Document Rules:

• Each document must have a "Report Date."
• You need an "MVR Review" document for every year of employment.
• The "Report Date" is used to determine if you've covered every year of employment.

Override Option:

If your company has enrolled in Continuous License Monitoring, you can override this requirement by checking the box for "Continuous License Monitoring" in the company's Compliance Configuration settings.

10. Safety Records Correction

What's Needed: Provide a document of type Rebuttal. 


Override Options:

You can override this requirement for all applications in your company account by unchecking the box for "Driver Correction or Rebuttal" in your company's Compliance Configuration settings.

You can also override this requirement on a per-application basis by checking the box labeled "I will not be providing a document" under the Safety Records Correction requirement.

Document Rules: If it applies to the application, only one document of this type is required.

11. LCV Certificate

What's Needed: An LCV Driver Training Certificate or LCV Certificate of Grandfathering
How to Complete: Provide the above documents 
Document Rules: If it's applicable to the application, only one document of either type is required

 

12. Skill Performance Certificate

What's needed: A Skill Performance Evaluation
How to Complete: Simply upload the above document 
Document Rules:  If applicable to the application, only one document of this type is needed

 

13. Multiple Employer Drivers

What's needed:  N/A
How to Complete: Currently, this requirement is always marked as complete.
Document Rules: N/A

 

 

Reporting Feedback

If you come across anything that's missing, not working as expected, or if you have suggestions to improve the DQ Checklist beta test, we encourage you to report it. Your feedback is invaluable in helping us fine-tune the product.

How to Report Issues:

To report any issues or provide feedback, please send an email to help@driverreach.com. Our dedicated team will swiftly review your report, investigate the matter, and escalate it to our engineering team as necessary. Throughout the process, our team will keep you updated on the progress and any resolutions.

 

Known Errors and Hurdles:

Occasionally, you may encounter known errors or face certain challenges during the beta test. Rest assured, we're actively working to address these issues and appreciate your patience and understanding.

 

Example of a Good Bug Report/Product Request:

To help you get started, here's an example of what constitutes a good bug report or product improvement request: