Working Hours & Out of Office
Pause SLA timers during nights and weekends, route requests to a morning digest, and delegate while reviewers are away.
Overview
By default SLA timers run 24/7 — a 2-hour deadline set at 6 pm Friday expires at 8 pm Friday, not 9 am Monday. Working hours lets you configure the days and times your team is actually at their desks so deadlines pause overnight and on weekends.
Two features work together here:
Working Hours Growth+
Workspace-level setting. SLA timers pause outside your configured hours. Requests submitted after hours are batched into a morning digest sent at the start of the next working day.
Out of Office
Per-user setting. A reviewer can mark themselves as out of office with a return date and delegate incoming requests to a colleague. Available on all plans.
1 — Configure working hours
Go to Settings → General → Working Hours (Growth and Business plans only).
Active Days
Toggle each day of the week. Defaults to Mon–Fri. SLA timers pause entirely on unchecked days.
Start and End Time
Set the daily window in your workspace timezone (configured in General settings). Defaults to 09:00–17:00. SLA timers pause at end time and resume at start time the next working day.
Preview
The form shows a human-readable preview as you configure — e.g. Mon–Fri · 9 am – 5 pm. Save once you're happy with the preview.
Changes apply to new requests only. Existing SLA deadlines are not recalculated.
2 — Per-queue 24/7 override
Some Review Groups must respond around the clock regardless of workspace hours — security incidents, live payment fraud, on-call queues. Mark a group as 24/7 in Settings → Response Times and its SLA timers will always run on wall-clock time.
How it interacts with working hours
3 — Morning digest
When working hours are enabled, requests that arrive overnight are not sent as individual notifications — that would fill up Slack or email while everyone sleeps. Instead, at the start of the first working hour each day, Cheqpoint sends a single digest to all active queue members listing how many requests are waiting and linking directly to the inbox.
Slack
Fires if a Slack bot token or webhook is configured. Includes a count and "Open Inbox" button.The digest only fires when there are pending requests from before the working day started. If the inbox is clear, no digest is sent.
4 — Inbox indicators
When working hours are enabled, two visual indicators appear in the Approval Inbox:
🌙 Off-hours banner
Shown when the current time is outside working hours. Reminds reviewers that notifications are paused and new requests will appear in the morning digest.
🌙 "Submitted outside working hours" label
Shown on individual request cards when the request was submitted during off-hours. Helps reviewers understand why SLA timers show unusual timestamps.
5 — Out of office delegation
Any workspace member with an approver role (Owner, Admin, Reviewer) can mark themselves as out of office from their Profile page.
What to configure
How rerouting works
Auto-expiry
OOO is automatically cleared when the return date passes — no manual action needed. The cron job that runs every 5 minutes checks for expired OOO flags and clears them.
Quick reference
| I want to… | Go to |
|---|---|
| Pause SLA timers outside office hours | Settings → General → Working Hours |
| Mark a queue as always-on (24/7) | Settings → Response Times → Edit group → 24/7 override |
| Set my out-of-office and delegate | Profile → Out of Office |
| See which requests arrived overnight | Approvals Inbox — look for the 🌙 label |
| Change when the morning digest fires | Controlled by your Working Hours start time |
Known limitations
- •No custom public holiday support — bank holidays count as working days unless the day of the week is unchecked.
- •Working hours changes apply to new requests only. Existing SLA deadlines are not recalculated.
- •Delegate chains do not follow more than one hop — if A delegates to B and B is also OOO, the system falls back to the queue, not to B's delegate.