# Check working time and follow escalation tasks

Read due-time evidence, scheduler delays and task completion in their proper scope.

Source: https://help.smartfact.ai/manuals/refillflow/calendar-and-tasks

Review edition: 25 October 2026

Roles: owner, author, reviewer, stores, supervisor

Due times and escalation tasks depend on the reviewed working calendar and policy. A reminder is follow-up work, not proof that a refill was accepted or completed.

## Prepare the calendar

The owner or author can edit **Working calendar**. Check the site timezone, weekly shifts and dated changes such as closures or special hours. Preview the actual intervals, local and UTC times, offsets and clock changes. Do not assume an overnight shift or daylight-saving boundary behaves like a normal eight-hour day.

Saving creates calendar evidence used by the release. Authors and reviewers should inspect the timing cases in the candidate before **Release rules**. Existing admitted refills keep their recorded calendar and due-time obligation, so a calendar edit is not a way to backdate an overdue cycle.

## Set meaningful escalation

In the release draft, choose supported escalation triggers, delays, stages and permitted targets. Current targets are the stores queue or supervisors. Historical releases may retain an old owner-target label, but those tasks are directed to supervisors; owners do not gain a Tasks workflow.

Use a realistic example at each relevant time boundary and after changed shifts or closures. A proof should expose wrong timing or route behaviour rather than merely establish that a task can exist.

## Work the inbox

Open **Tasks** with stores or supervisor authority. Stores visibility follows current queues. Read the refill reference, container, item, receiving location, stores queue, progress, due time, raised time and stage or reminder number.

Record what you did and mark the task done only after taking that follow-up action. Marking done does not receive material, change the refill target or close a cycle. Other tasks may resolve through acceptance or cycle closure according to their trigger.

## Read late and held alerts honestly

A supervisor sees scheduler alerts. A late task shows when it was actually raised; it was not delivered earlier simply because its due time was earlier. A held scheduler alert can indicate that current permissions or plan could not be confirmed. Refills remain unchanged while reminders wait.

Investigate scheduler or permission problems with the owner and preserve the real timing. Do not mark many tasks done to conceal a delayed run. At handover, distinguish an actioned reminder from an unresolved shortage and from the refill's physical progress.