How a request becomes a rostered shift
A request asks agencies to cover one shift. An agency replies with a proposal naming one of its own officers and an hourly rate. You confirm one proposal, that confirmation is recorded as an assignment, and the roster cell the request came from then reads as filled and names the officer.
What are the stages?
- Request — one site, one date, one start and end time, for exactly one officer. Asking for more is refused outright: Quantity must be exactly 1. To request multiple officers, create separate requests. Two guards on one night is two requests. A request can also list the licences its officer must hold — every one of them, each valid on the shift date. With none ticked, the role's own licence is checked, if the role needs one.
- Share — a request reaches an agency only once it has been shared with that agency, either by picking agencies as you raise it or by sharing it afterwards. An agency's Requests screen lists the requests shared with its agency and nothing else.
- Proposal — the agency puts an officer forward at an hourly rate. It can only propose its own officers, and only officers who have already accepted their login invite. An officer who lacks a required licence, or whose licence ends before the shift, is refused at this point, and again at confirmation or when the agency swaps the officer. A request can hold several proposals: one per officer put forward, across every agency it was shared with.
- Assignment — an Admin, Manager or Control user confirms one proposal (see Review proposals and confirm officers). That proposal becomes Selected, the assignment records which officer and which agency, and the request stops accepting confirmations.
- Roster — the cell now reads as filled and shows the officer's name. Once the officer books on in the phone app the shift moves to In Progress, and to Completed on book-off, with the position the app sent (with the current version of the app) kept for the shift's map. A roster manager marking the shift In progress or Completed books the officer on and off at the scheduled times.
Confirming also copies the shift into the officer's own roster, which is what puts it in their portal — the portal reads that roster, not the assignment. If the agency has not rostered that officer, the assignment still stands but the shift never reaches them.
What do the request statuses mean?
| Status | What it means |
|---|---|
| Open | Raised, and no agency has put an officer forward yet. Every new request starts here. |
| Proposed | At least one live proposal exists. The first proposal moves the request from Open to Proposed, and withdrawing the last one moves it back to Open. |
| Confirmed | As many officers are assigned as the request asked for. Because a request always asks for one, that means one confirmed proposal. |
| Cancelled | The organisation cancelled it with a reason the agency is told — see Create and manage requests — or the agency fill was taken off the shift, or the roster shift behind it was cancelled. A cancelled request can no longer be edited. |

So a request does not go straight from Open to Confirmed. It passes through Proposed for as long as offers are on the table and none has been confirmed.
Older data may contain a Partially Filled status, but the platform no longer produces it and existing rows were migrated to Open. The value still exists in the database because Postgres cannot cleanly drop one.
Where do I see each stage?
Requests and their proposals live on the Requests screen, which organisations and agencies both have. The agency sees the same requests under Available Requests, with a Propose action on the ones still open, a Proposal Sent badge and BID PENDING on any it has answered and is waiting on, and WON on any where its officer was confirmed.

The roster says the same thing on the cell the request was raised from: Awaiting agency while the request is Open, the agency's name with Proposed once an officer has been put forward, and the officer and agency once one is confirmed. The request form's slot picker uses the same words, so the picker and the roster cannot describe one slot two different ways.

Cancelling the roster shift ends the link: restoring it later gives an ordinary open seat, not agency cover. Once the officer has started the shift, you can no longer cancel it, mark it no-show or give it to an employee from the roster. Giving the shift to one of your own employees while the request is still open cancels the request and tells the agencies, because only one way of filling a shift runs at a time.
Where the shift lands depends on what it was raised against. A request raised from a pattern seat produces a shift carrying that pattern, so it sits in that pattern's row. A request raised through New ad-hoc slot produces a shift carrying no pattern at all, so on Week + Patterns it drops into the single row beneath the pattern rows, labelled Ad-hoc with Unscheduled — no pattern under it.
Related
Last updated 2026-11-17