Diagnose The Actual Layer
Employee Is Marked Unscheduled
Compare the schedule, selected timeframe, job transfer, and punch date.
What this usually means
Compare the schedule, selected timeframe, job transfer, and punch date.
First checks
- Confirm a schedule exists on the exact date and time.
- Check whether the schedule was published and effective.
- Compare scheduled job/location with the worked transfer.
- Review schedule edits made after the punch.
- Validate exception rule tolerances and schedule source.
Evidence to capture before escalating
- Employee or manager ID; do not send sensitive information in open channels.
- Exact date, timeframe, page, tile, or workflow.
- Expected result versus actual result.
- Screenshot of the message and relevant audit or configuration evidence.
- Whether the issue affects one user, one location, or the full organization.
Avoid
Do not make broad production configuration changes until the issue is reproduced with a controlled test. Fix the smallest confirmed layer first.
Need A Configuration-Specific Answer?
Book an FREE Consult to find a personalized solution that works for your organization.
Book A Free Consult