Skip to content
DQid

Carrier workspace

Your driver files. Your next action.

See what needs review, open the driver file and manage the checklist behind your DOT driver-qualification work.

Managing driver files?

Create carrier account

Sending your documents?

14-day free trial. Starts when you create an account in the app.

Carrier admin in a red polo using a tablet beside a white pickup in a fleet yardCarrier workspace
Mexican-American driver in a mustard jacket sending a file from his phone beside a white cargo van in warm daylightDriver submission

Start with the driver, then the file.

The workspace brings driver records, checklist items and document states into the same review flow.

  • Driver records

    Open a driver’s record to follow their assigned checklist and submissions.

  • Checklist templates

    A default template is read-only. Duplicate it before customising the required items.

  • Document details

    Keep the source document beside its dates, version and recorded review state.

Northline Freight Co.

Driver-file overview
Drivers
24
Under review
6
Reviewed items
80%

Mateo Salazar

Driver file · Checklist

80%Checklist compliance
Application formUnder review
Default checklistRead-only

Workspace overview

An overview points to a specific item.

A dashboard number is a starting point. Open the underlying checklist item before making a review decision.

  1. Checklist item

    Application form

    Awaiting driver submission

    Find the missing submission

    A checklist item without a submission still needs a document from the driver.

    Not submitted
  2. Document comparison

    Source file

    Version
    Latest submission
    Review
    Carrier checks details

    Compare the source

    A submission waits Under Review while the carrier checks the document and its details.

    Under review
  3. Item review

    Verification recorded

    The item’s state is updated after review.

    Record the decision

    The carrier records verification for the individual item. A file-level score is a separate summary.

    Compliant

Move from a file state to a clear action.

The driver sends the requested record. The carrier checks it. Both can follow what the file still needs.

Next in the review queue

Mateo Salazar

Driver file · Checklist

80%Checklist compliance
Application formUnder review

Compare the document

Open its source and recorded details before making the review decision.

  • Send the requested document

    Open the assigned item in the app and upload, scan or fill its form.

  • Review and verify

    Compare the submission with its metadata before recording verification.

  • Keep the checklist current

    Confirm the carrier’s required items and the people who may manage them. Permission scope depends on the confirmed account setup.

Try the controls. See what changes.

Choose a permission to try Admin and Reviewer access, or open Template builder to change the checklist. Changes stay on this page; nothing is saved to an account.

Workspace controls

Changes stay on this page

Permissions and checklist

Select the control you want to explore.

Template builder

A duplicate checklist you can customise. Include or remove an item to recalculate the weighted score.

Commercial driver license

Weight 50

Compliant

Medical certificate

Weight 30

Compliant

Application form

Weight 20

Under review
Compliance score80%80 reviewed weight / 100 included weight. Removing an item changes the summary; it does not verify a document.
A Mexican-American driver and a carrier admin reviewing a tablet at a depot gate beside a white van

A number becomes a file you can review.

Start with the fleet overview, then open the driver card to see the checklist behind the summary.

Compliance percentage and profile completion describe different things. Neither replaces checking the individual documents.

Does a high score finish the review?

No. The carrier still checks the underlying documents. A score summarises the illustrated checklist; it does not guarantee audit readiness.

Ask the workspace. Approve the next step.

Ask across your driver files in plain language, review the matches, then approve the follow-up. Confirmed capabilities only; available connections and permissions are awaiting product confirmation.

Ask across the driver files

Find drivers whose medical cards expire this month. Review the matches in the workspace, then approve the follow-up requests.

Keep MCP access specific

Connect carrier tools through MCP with confirmed capabilities only. Permissions follow the roles you set in the workspace.

Setup, access and limits

Decide the boundaries before you begin.

Set the checklist and confirm who should work with personal driver documents.

  • Confirm each role’s access

    Admin and Reviewer are the roles shown here. Exact permission names, defaults and available controls await confirmation.

  • Treat the score as a summary

    Item weights and review states are awaiting confirmation. Production scoring, exemptions and template behaviour need confirmation.

  • Keep verification with people

    A submitted document, completed profile or dashboard total does not establish compliance. The carrier checks and records the review.

Before you set up your workspace.

What can a carrier admin act on?
Open driver records, follow checklist submissions and review documents. The carrier can duplicate a read-only default checklist to customise it.
Are these the account’s actual permission defaults?
No. This is an interactive access illustration. Confirm the exact roles, defaults and permission scope before assigning access in your account.
How does the score change?
It divides the weight of included, carrier-reviewed items by the total included weight. Removing an unreviewed item raises this score without reviewing a document. An empty selection has no score. These weights are awaiting confirmation.
Can I change a default template?
The default is read-only. Duplicate it to create a checklist you can customise for your carrier.

Open the workspace behind your files.

Create your carrier account and start with your team’s driver-file work.