Time and Activity: Schedules and policies
Objective. Understand that schedules, shift, break and overtime policies set the baseline that attendance, available hours and overtime flags are measured against - enough to validate correctness and escalate deep setup.
This screen answers 'what schedule and policy is each person measured against?' It is the configuration that defines scheduled time, breaks and overtime rules - the yardstick behind attendance and overtime numbers.
See it in the demo
What this screen answers
A CSM opens this to answer 'is the baseline correct before we trust any attendance or overtime number?' Sales needs awareness that these are configurable. Attendance is presence against a schedule, overtime is time beyond a policy, and available hours net out breaks - so if the schedule or policy here is wrong, every downstream figure is wrong in the same direction without looking wrong.
The task (validate, do not re-engineer)
Confirm, at a high level, that the right schedule, shift pattern, break rule and overtime policy are assigned to the right people and time zone. The highest-value CSM check is coverage: is anyone on a default or missing schedule, which would silently distort their attendance and overtime. Deep policy design, rotations and precedence are specialist work - capture requirements and escalate rather than tuning them live in front of a customer.
How to read it
The misread is trusting an attendance percentage or an overtime flag without checking the baseline behind it. An attendance number is only as correct as the schedule it is measured against, and an overtime flag only means 'beyond policy' if the policy is right. A wrong shift assignment can make a punctual employee look late, or hide genuine overtime. Always confirm the schedule and policy are current and correctly assigned before reading, especially across time zones where the same clock time means different things.
Honest limits
This is an admin screen; exact policy options, rotation handling and integration with any external scheduling or HR system must be confirmed with product. It defines the yardstick, not behaviour - a correct schedule does not make attendance good, it just makes the measurement trustworthy. Note that detailed workforce scheduling itself lives in the Scheduling application; this screen is the measurement baseline, not a full rostering tool.
Interpretation check
An attendance percentage or overtime flag is only as correct as the schedule and policy it is measured against. A wrong or missing schedule distorts every downstream number without looking wrong.
Practical task
In the demo, note how you would check schedule and policy assignment for a team (coverage, time zone, overtime policy) and write the one baseline risk you would confirm before trusting its attendance numbers.
Self-check
Attendance looks poor for one employee. What baseline check comes before any conversation?
Whether the correct schedule, shift and time zone are assigned. A wrong shift makes a punctual person look late. Validate the baseline first.
Why is a missing or default schedule the highest-value thing to catch?
It silently distorts attendance, available hours and overtime for that person in a consistent direction, so the numbers look plausible but are wrong.
An overtime flag fires. What does it actually mean?
Time beyond the configured policy - nothing more. If the policy is wrong, the flag is wrong. Confirm the policy before acting.
A customer wants a complex rotation built. What is the CSM move?
Validate the requirement and escalate deep setup to a specialist. Detailed rostering also belongs to the Scheduling application, not this baseline screen.
Verified vs demo. Screen is live in the demo at /#/policies; exact controls and figures are SME-validation-pending.