Place a vehicle into maintenance
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Block the asset from dispatch while work is carried out.
Where to goAdmin Area → Courier & Logistics → Vehicles → Open vehicle
What this guide helps you do
Block the asset from dispatch while work is carried out. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Follow these steps
- Check active assignments.
- Move affected work through the supported reassignment/cancellation process.
- Set Availability to maintenance.
- Save.
- After authorised release, update evidence/dates and set the correct state.
Fields and options
This action uses the values already stored on the selected source record. Review that record before continuing.
Rules and limits
- Dispatch requires an available vehicle and will reject maintenance vehicles.
Check it worked
- The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action.
Security, audit and operational checks
- Use the exact record and least-privilege role before changing any state.
- Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed.
- Use protected document and image routes rather than exposing server filesystem paths.
- Keep customer, driver, provider, financial and credential data within the authorised workflow.
- For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process.
Do not bypass the code flowDo not force database values, invent a status, mark a job completed without signed POD evidence, or expose encrypted credentials to make a screen appear successful.
Related guides
Was this guide useful?Your response is stored only in this browser.