Work Schedules

Work schedules tell Astervis when each operator is supposed to be on the floor, then quietly measure what actually happens — who showed up on time, who was late, who took a long break. You define a shift once, attach it to your operators, and the dashboards take care of the rest. No spreadsheets, no manual roll-call.

This guide is written for a supervisor. By the end you'll know how to build a shift template, assign it, read the time-tracking states, and pull the two reports you'll actually use: time worked and late arrivals.

Schedule templates

A schedule is a weekly template: for each weekday you set a start time, an end time, or mark the day as off. One template can be reused across an entire team, so most call centres need only a handful of them — a standard office shift, a morning shift, an evening shift, and a weekend rota.

A typical office week looks like this:

The late-arrival threshold

The threshold is the grace period after the scheduled start before a login is flagged as late. If a shift starts at 09:00 with a 10-minute threshold, signing in at 09:09 is on time and 09:11 is late. Pick the number that matches how strict you want to be:

Assigning a schedule to operators

A template does nothing until it's attached to people. Assignment happens on the employee record, not on the schedule.

Time tracking

Once an operator has a schedule, Astervis tracks their working time across the day. When they sign in, the login time is recorded and compared against the scheduled start to mark the session on time or late; from there it accumulates effective work time until they sign out.

Tracking states

Every operator's day moves through three states. You'll see these live in the supervisor view.

Breaks

Breaks are operator-driven. From the header the operator pauses work, optionally notes a reason, and resumes when they return. Each pause is logged against the day and excluded from work time, which keeps two questions cleanly separated on the report: how long were they signed in versus how long were they actually working.

Reports

Two reports turn this raw tracking into something you can act on. Both live under the work-schedules area and accept a date range plus filters by position or team.

Time report

Open the schedule report view, choose a date range, and optionally filter by department or position. For each operator over the period you get:

• Scheduled hours — what the template expected.
• Actual hours worked — effective time, breaks already excluded.
• Break time — total paused time.
• Late arrivals — how many days they crossed the threshold.

This is the report to review weekly. It tells you at a glance who is consistently under their scheduled hours and where break time is creeping up.

Late-arrival report

The late-arrival view answers one question — punctuality — and answers it precisely. Pick a date range, filter by employee or position if you only care about one team, and you get every late sign-in with the exact minutes late. The same numbers feed the late-arrival widgets on the dashboard, so the report and the chart always agree.

Handling multiple schedules

Different teams keep different hours, and that's exactly what multiple templates are for. Create one schedule per pattern and assign each operator to the one that fits:

The reports respect each operator's own schedule when judging punctuality, so you can mix morning and evening shifts in a single date range and still get an accurate "late" count — the evening team isn't marked late at 09:00 because their day starts at 14:00.

Timezone

All shift times, sign-ins and reports use the server's configured timezone, set during installation — Asia/Tashkent by default. Times display the same way no matter where a supervisor opens the dashboard from, so 09:00 on the schedule is 09:00 for everyone reading it.