Scheduling: Employee portal
Objective. View the employee-side experience of a published schedule - shifts, acknowledgment, requests and swaps - and read acknowledgment as 'seen and accepted', not as adherence.
This screen answers: what does the employee see, acknowledge and transact? The key read is that the portal shows the published version and that acknowledgment confirms the schedule was seen and accepted, not that it will be adhered to on the day.
See it in the demo
What this screen answers
A Sales or CSM person opens the portal to answer: how do employees see their published schedule, confirm it, and raise requests, swaps or open-shift claims? It is the employee half of a clean publication process and a fairness and adoption driver.
The task
View the employee-side view of a published schedule for the team: the shifts an employee sees, the acknowledgment action, and the request / swap / open-shift options routed back to the manager. Confirm that only published versions appear, so employees are never acting on a draft.
How to read it
The portal shows the published version to employees. Acknowledgment confirms the schedule was seen and accepted - not that it will be adhered to; whether people actually work the plan is measured in Real-Time Adherence, not here. A request raised in the portal is demand for change routed back to approvals, not an executed change. The misread to avoid: reading high acknowledgment as proof of adherence or coverage.
Honest limits
The portal reflects what is published and acknowledged; it does not prove the day ran to plan. Confirm with product which portal actions (swap, bid, request), notification channels and acknowledgment rules apply for a customer; the demo uses seeded personas and data.
Interpretation check
Acknowledgment in the portal means the schedule was seen and accepted, not adhered to - what actually happens on the day is measured in RTA, not here.
In the field
A distributed team confirming shifts through the portal: acknowledgment gives the manager a clean record of who has seen the week, while the CSM is clear that adherence is still an RTA question.
Practical task
On the demo portal, view a published schedule as an employee and write one line distinguishing what acknowledgment proves (seen/accepted) from what it does not (adherence).
Self-check
90% of employees have acknowledged the schedule. Does that mean 90% adherence?
No. Acknowledgment is seen-and-accepted. Adherence - whether they actually work the plan - is a separate measure in Real-Time Adherence.
An employee raises a swap in the portal. Is the schedule now changed?
No. It is demand for change routed back to the manager's approvals. The live schedule changes only when the swap is approved and published.
What version should an employee ever see in the portal?
Only a published version. Employees acting on a draft is exactly the confusion a clean publication process prevents.
Verified vs demo. Screen is live in the demo at /#/portal; exact controls, labels and figures are SME-validation-pending.