Vehicle Requests Guide
Understand request lifecycle states and how to submit high-quality requests in FleetWise.
What a Vehicle Request Represents
A vehicle request captures demand for testing or engineering usage in a structured way. Good request quality directly improves allocation outcomes.
Purpose & Context
Request purpose and project context.
Time Window
Required time window and duration.
Essential Requirements
Must-have requirements for matching. Shown as
Essential
in the UI.
Preferred Requirements
Nice-to-have requirements to improve ranking. Shown as
Preferred
in the UI.
Lifecycle Overview
1. Preparation (Draft)
The request is drafted with initial requirements but not yet submitted.
2. Submission (Submitted / Pending Approval)
The request is submitted and enters the queue for coordinator review or automated processing.
3. Review (In Review / Tentative Allocation)
Coordinators evaluate the request against available vehicles and may tentatively assign options.
4. Fulfillment (Allocated / Partially Allocated)
The request is fulfilled with an allocation.
5. Resolution (Completed / Withdrawn / Rejected)
The request lifecycle concludes.
Request States
Each state is shown in the UI with a colored badge. Use this reference to understand what each means:
| Badge | Meaning |
|---|---|
| Draft | Initial working state before submission |
| Submitted | Request is submitted and queued for processing |
| Pending Approval | Waiting for approval decision |
| In Review | Coordinator review and matching in progress |
| Tentative Allocation | Potential assignment exists but not final |
| Partially Allocated | Only part of requested coverage is currently satisfied |
| Allocated | Full requested coverage is currently assigned |
| Withdrawn | Requestor removed the request |
| Rejected | Request was declined |
| Completed | Request lifecycle ended successfully |
| Deleted | Draft was removed |
Best Practices for Requestors
- Provide complete essential requirements before submission.
- Use preferred requirements to help ranking, not block matching.
- Keep date windows realistic and aligned with test readiness.
- Withdraw stale requests to keep coordinator queues clean.
- Track status changes and respond to clarifications quickly.