Automatic drafts and the Sunday briefing

Nothing runs unless you asked for it

Every job below is off by default and has to be switched on. A product that creates shifts in your account uninvited is a surprise, not a feature.

Two more rules hold across all of them: a job never touches a published week, and a job never publishes. Their output is always a draft waiting for a human. Each also runs as a real manager in your organization — the most senior active one — rather than as a system superuser, so every permission and plan check that applies to a person applies to the job.

Sunday draft of next week

Switch on auto-draft and you arrive Monday with next week already seeded and only the decisions that need you left to make.

The seed is continuity-based: it copies your most recent week that actually has shifts, looking back up to four weeks. It is deliberately not an AI run — for the overwhelming majority of rotas, "the same as last week" is what drafting next week means, it costs nothing, and it is completely predictable. Use the assistant for the weeks where it is not.

It refuses to overwrite: a target week that already has shifts is left alone and treated as handled. Afterwards it runs a compliance check over what it created, so the notification you get on Monday names the problems rather than just announcing a draft.

If a schedule already has a recurring template, that takes precedence — the two never both populate the same week.

Template recurrence

Enabled per template rather than per organization, and covered in full in Schedule templates. It runs an hour before auto-draft, so a schedule with a recurring template gets its fixed layout and auto-draft steps aside.

The weekly manager briefing

A Sunday-afternoon digest of what your managers should know before the week starts. It arrives three ways: email, the in-app bell, and — if you configure one — a webhook into your team's Slack or Microsoft Teams channel.

It is read-only by construction. The only operation it performs is a read, so a bug in it can send a wrong email but cannot alter a schedule.

The Slack or Teams post fires once per organization, since it lands in a shared channel, and it ignores individual mute preferences — those govern your own inbox, not the team's channel. Muting the briefing silences your email and your bell.

The briefing draws on the analytics surface, so it needs Pro. See Insights and analytics.

When each one runs

Times are UTC and not configurable today. If you need a different cadence, the API lets you run the equivalent operations on your own schedule.