Give each segment an identity
Synthetic request LV5 has morning segment M09:00–11:00 and afternoon P14:00–16:00 on the same day. Supplied decision approves M and leaves P pending. Local administration applies confirmed unavailability for M only and retains P as a request, without deciding entitlement or staffing.
| Segment | Supplied decision | Availability effect |
|---|---|---|
| M09–11 | Approved | Confirmed unavailable |
| P14–16 | Pending | No confirmed change |
Apply the supplied segment decisions
- Read LV5 segment IDs
- Match decisions by segment
- Apply M only
- Keep P pending visibly
Approval for M cannot be stretched to P just because both share LV5.
How many hours of confirmed unavailability are added?
Show the worked answer
Two hours, M09:00–11:00. The two-hour P request remains pending and contributes no confirmed change.
Publish only confirmed changes
| Case | Action or result | Evidence boundary |
|---|---|---|
| Mark wholeLV5 approved | Reject | P still pending |
| Store segment outcomes | Accept | M approved/P pending |
A later P decision must name P and its revision. Do not rewrite M’s earlier approval when updating the other segment.