Read supplied availability and request
Fictional S14 has confirmed availability Monday 09:00–17:00. Request LV1 asks to be unavailable 13:00–15:00 but is pending under the organisation’s supplied decision process. No approval exists. Local administration shows the pending request beside confirmed availability and does not rewrite it yet. No leave entitlement or pay rule is supplied.
| Record | Interval | State |
|---|---|---|
| Confirmed availability | 09:00–17:00 | Unchanged |
| LV1 | 13:00–15:00 | Pending |
Keep the decision state separate
- Match LV1 to S14
- Retain supplied availability
- Display pending interval separately
- Route LV1 to named decision process
A request marked pending cannot be inferred approved from a calendar note.
How many confirmed availability revisions result from LV1 now?
Show the worked answer
Zero. The request is recorded, but no authorised availability change is evidenced.
Route the unresolved request
| Case | Action or result | Evidence boundary |
|---|---|---|
| Subtract pending two hours | Do not alter confirmed record | Approval absent |
| Show LV1 pending | Supported | Preserves request without inventing decision |
Any planning affected by LV1 should expose the unresolved request rather than claim a final absence decision. Actual staffing allocation remains a separate task.