Status Reference
Complete reference for booking request statuses
Status Reference
Booking requests use a simple three-state lifecycle. This page provides complete details on each status.
Status Values
| Status | Code | Description |
|---|---|---|
| Pending | PENDING | Request is awaiting review and action |
| Completed | COMPLETED | Request has been approved |
| Cancelled | CANCELLED | Request has been rejected or withdrawn |
PENDING
Definition
The request has been submitted and is waiting for an administrator to review and process it.
Characteristics
| Aspect | Value |
|---|---|
| Terminal | No |
| Editable | Yes (by admin) |
| Can transition to | COMPLETED, CANCELLED |
| Budget state | Reserved (if ON_REQUEST timing) |
Who Can Act
| Actor | Allowed Actions |
|---|---|
| Requester | View, Cancel |
| Admin | View, Edit, Complete, Cancel |
Triggered By
A request enters PENDING status when:
- User submits a booking request (only entry point)
COMPLETED
Definition
The request has been approved by an administrator. The travel can now be booked.
Characteristics
| Aspect | Value |
|---|---|
| Terminal | Yes |
| Editable | No (notes only) |
| Can transition to | None |
| Budget state | Confirmed (moved to spent) |
Who Can Act
| Actor | Allowed Actions |
|---|---|
| Requester | View only |
| Admin | View, Edit notes only |
Triggered By
A request enters COMPLETED status when:
- Admin clicks "Mark Complete" on a PENDING request
Side Effects
When a request is completed:
- Budget reservation is confirmed (pending → spent)
- All items are locked (no edits except notes)
- Policy violations are finalized in logs
- Travel team can proceed with booking
CANCELLED
Definition
The request has been rejected by an administrator or withdrawn by the requester.
Characteristics
| Aspect | Value |
|---|---|
| Terminal | Yes |
| Editable | No (notes only) |
| Can transition to | None |
| Budget state | Released (returned to available) |
Who Can Act
| Actor | Allowed Actions |
|---|---|
| Requester | View only |
| Admin | View, Edit notes only |
Triggered By
A request enters CANCELLED status when:
- Admin clicks "Cancel Request" on a PENDING request
- Requester cancels their own PENDING request
Side Effects
When a request is cancelled:
- Budget reservation is released (returned to available)
- All items are locked (no edits except notes)
- No booking is made
- Request remains for historical reference
Valid Transitions
| From | To | Trigger | Actor |
|---|---|---|---|
| (new) | PENDING | Request submitted | User |
| PENDING | COMPLETED | Mark Complete | Admin |
| PENDING | CANCELLED | Cancel Request | Admin or User |
There are no transitions out of terminal states. COMPLETED and CANCELLED requests cannot be changed.
Invalid Transitions
The following transitions are not allowed and will be rejected by the system:
| From | To | Why Not Allowed |
|---|---|---|
| COMPLETED | PENDING | Terminal state |
| COMPLETED | CANCELLED | Terminal state |
| CANCELLED | PENDING | Terminal state |
| CANCELLED | COMPLETED | Terminal state |
| PENDING | PENDING | No-op |
Status Filtering
When filtering by status in the API:
- Single status:
?status=PENDING - Multiple statuses:
?status=PENDING,COMPLETED