Fleet records are the resources Dispatch uses. Review Fleet, Drivers, Vehicles, and Vehicle Types before assignment work begins.
Prepare resources
Use distinct names, confirm active drivers and vehicles appear in the expected lists, and review the vehicle types and groupings used for assignment. If a resource is unavailable, check its active status and operational settings before creating a duplicate. Preserve records referenced by completed work.
Driver, vehicle, and affiliate profiles show document summaries. Manage those records in Compliance; the profile summaries are read-only. Company documents are also visible in Company Setup.
Check compliance readiness
Open Compliance → Overview. The tiles show Managed subjects, Required records, Current, and Needs attention. Use the Action queue to find missing, expiring, expired, or pending-review records. Select Add for a missing record, or open an existing record to resolve it.
Readiness is calculated from published requirement packs. Each active subject needs a baseline pack; overlays add requirements. Drafts, retired packs, and assignments to inactive subjects do not contribute. A subject without a baseline has unknown readiness. If Central library unavailable appears, use Retry; absent totals during an outage do not mean everything is current.
Define and assign requirements
- Open Compliance → Requirements and select New pack, or open an existing operator pack.
- Enter the name, subject kind, and role. A baseline applies to every active subject of that kind; an overlay adds requirements to its assigned subjects. Subject kind and role cannot be changed after creation.
- Add the required record kinds and warning periods, then select Save draft. Save new changes before publishing: Publish uses the saved draft. A pack must contain requirements before it can be published.
- Select Publish when the requirements are ready to apply. For an overlay, use Assignment to choose all active subjects or named subjects and select Save assignment. A company overlay applies to the company itself.
- Recheck Overview and the resulting action queue. Use Retire pack when an operator pack should stop applying; retired packs are read-only and can be shown with Show retired.
Platform-managed pack details are read-only. Creating a document type in Configuration makes it available for entry; a requirement pack determines whether it is mandatory.
Resolve document actions
In Manage Documents, open the record and choose the action that matches the change:
- Verify & approve accepts a pending submission after review. Reject requires notes explaining what to correct. A submission awaiting review counts toward readiness only after verification.
- Renew document files a new record and keeps the old one for history.
- Edit corrects the record using its original form. Bring to current version checks the answers against the updated form; complete the newly required answers before saving.
In Configuration, applicable driver document types have Requires review when filed from the driver app. This governs driver submissions; records filed by an operator in Backoffice are verified on arrival. After resolving an action, return to Overview and confirm the updated readiness.