Set up the fleet context
Use the company, vehicle category, explicit units and current Driver assignment. Capacity and membership remain scoped; an invitation or old assignment does not bypass access.
Explore mixed fleetsHow it works
Set up the correct context, record explicit facts and keep later work and decisions connected. Each step retains its own permission and meaning.

Use the company, vehicle category, explicit units and current Driver assignment. Capacity and membership remain scoped; an invitation or old assignment does not bypass access.
Explore mixed fleetsUse the versioned template, answer explicitly and keep required evidence. A local draft is not a committed server receipt; retry the original operation after connection loss.
Explore checks and receiptsKeep manager assessment, maintenance instructions, work completions and evidence connected. Later review does not rewrite the original facts or automatically release an asset.
Explore work and reviewSeparate facts and authority
Current tenant, role, resource and membership checks apply throughout. Driver, manager, independent workflow reviewer and competent release authority are not interchangeable.
Competent Return to Service remains disabled pending its separate accepted policy. This local preview has no real sending, charging or operational release.
Read the workflow guideExplicit answers and a server-confirmed receipt.
Keep reported facts separate from a manager assessment.
Work, evidence, costs and independent workflow review.
Separate authorisation and blocker checks; unavailable in this local review.
Local sign-in opens synthetic workspaces. Public signup, trial activation, production storage/identity, real devices and launch remain separate acceptance gates.
Open local sign inA connected record of fleet work
Follow a check from an explicit observation to a server receipt, a retained work record and an authorised report.