People and organizations

Build the week as shifts. Publish it once.

A roster is not a stack of meetings. Group people into wards, crews or departments, build the week as shifts, publish it to calendars and inboxes at once, and account for what it cost.

Get started free
Saturday, nobody onSaturday, covered

How it works

  1. Group people, then build the week

    Teams inside the organization — wards, crews, departments — each with its own rota. Bring the people in from a spreadsheet rather than typing a hundred of them.

  2. Publish it once

    Shifts go to calendars and inboxes together. Everyone gets their own week rather than a photograph of everybody's.

  3. Account for it

    Hours, cost and mileage tracked against the shifts and grouped by category.

A shift is not a meeting

Coverage is who is on, not who is meeting whom. The schedule is built in the shape of the work rather than in the shape of a calendar invite.

Teams, and the person who runs each one

Hand one team's week to whoever runs it — schedule edits for their team only, without money, publishing, or admin.

Twenty-five people is an afternoon; a hundred is a project

People, roles, emails and rates come in from a CSV, with a template to start from.

Hours the way a grant report wants them

Tracked time by category, so the report is a query rather than a reconstruction.

Needs a second person, so it starts on Team. Compare the plans

Next

Get started free

Everything Hotline does · See pricing →

Teams and coverage — build the week as shifts | Hotline · Hotline