ScrubGrid

Everything a group needs to run its schedule

ScrubGrid covers the whole life of a schedule: setting up a group, building each month, and every change after it is published.

Build the schedule from settings

A group's way of working is entered on a few setup pages. The application follows what is entered there. It has no built-in assumptions about any specialty or hospital.

Shifts

Each job the group must fill is a shift, with the days and hours it runs: a weeknight, a weekend held whole, a 12-hour day, or a week whose nights may be shared out.

Roster and eligibility

Everyone on the roster has a short code and a color of their own. Eligibility says who may hold each shift.

Rules

Rest before and after a shift, spacing between shifts, days in a row, weekends off, the night before time off, paired people, a last resort. Each rule is marked Must or Prefer.

Special days

Your organization keeps one holiday calendar. Each group chooses how it schedules each holiday: as an ordinary day, kept with one person, joined to the weekend, or earning a day off.

Fairness and goals

Choose what is counted, how far back the count looks, and what the schedule should favor when two goals pull against each other.

An assistant for the typing

Describe a shift or a rule in your own words and the assistant fills in the form. You read it, correct it, and apply it. Nothing is saved before that.

Generate builds the draft, and shows its work

Press Generate and an optimizer builds the month, weighing every shift, every rule, the approved time off and the holidays together. The result says what it could not do: which shifts were left open and why, and where one goal gave way to another.

  • A Must rule is never broken. The shift is left open instead.
  • A Prefer rule is kept where possible
  • Change a rule or a cell by hand, and generate again

Run it after you publish

Draft, published, locked

A schedule is in one of three states, and the state decides what may still change. Earlier versions of a published schedule stay on record and can be opened to read.

Requests and approvals

A provider opens their own shift and asks for coverage, from anyone who can take it or from a colleague they name, or proposes a trade. A colleague can take an open shift, or ask to work one. Each request goes to the people who decide, in one list called Approvals.

  • One request can cover one shift, chosen shifts, or every shift that day
  • An approved request changes the published schedule
  • Everyone affected is told, on the bell in the application and by email

Time off that the schedule respects

Your organization names its own kinds of time off and gives each a color. A request is approved or denied, and Generate never puts a person on a shift while they are away. The month board shows who is off on each day, and how many.

  • An allowance for each kind, and each person's balance
  • Unused days that may carry over to the next year
  • One time-off calendar for the person, wherever they work

What each provider has

A provider signs in and lands on My Home. There is no menu to learn: the page is their own work, and nothing else.

My Home

The next 14 days, requests that are waiting, time off and balances, on one page.

My schedule

The published shifts at every place the person works, a month at a time.

My call

Their own weekday, weekend and holiday call beside the group's average.

Add to your calendar

A private link puts their shifts in the calendar on their phone and keeps them current. Replace the link and the old one stops working at once.

Email

When a schedule is published or changed, when a request is decided, and the day before they are on call.

Text alerts

Optional. Each person turns them on for their own number, proves the number with a one-time code, and can stop them by replying STOP.

One organization, many groups

An organization is drawn as a tree: a department, its divisions, each hospital. Every roster, rule and schedule belongs to one place on the tree. A provider who works at two hospitals is still one person, and a rule can say what one person may hold at once across different schedules.

Reports with a Why?

Each person's weekday, weekend and holiday call, their share and their fair share. Every row has a Why? button that explains the number.

Activity

Every change to the organization's setup, newest first, with who made it. Each schedule keeps its own history as well.

A PDF for everyone else

Any schedule downloads as a PDF. When a schedule is published, the PDF is emailed to the group's schedulers.

Light and dark

Each person chooses a light or dark theme, a text size, and less motion if they prefer it.

A role for each kind of person

Member
A person on the roster. Sees their own schedule, and asks for time off and cover.
Chief
As a member, with a read-only view of everyone's schedules, the numbers, balances and the record of changes. Changes nothing.
Scheduler
Builds and runs the schedule: setup, generate, edit, publish, lock, and requests. Cannot give anyone access.
Administrator
Everything a scheduler does, with accounts and access, employment dates and allowances.
Organization owner
Everything, across the organization, with the tree itself, the organization's clock and the review of who has access.
Executive
View only. Published schedules and everyone's numbers. Sees who is away by name and date, never why.
On-call desk
For operators, the operating room desk or a transfer center. Sees who is on call, and nothing else.
Viewer
Sees published schedules, and nothing else.

Block

Operating room block time

For surgical departments, a second track schedules block time: which surgeon holds which operating room on each weekday. It uses the same roster and the same time-off calendar as call, so a surgeon on vacation is away from both.

  • Rooms, and the weekdays each one runs
  • Who owns a room, week by week
  • Block counts kept even, with make-up blocks after time off
  • Open rooms that colleagues can ask for
  • A fairness report for block time, with a Why? on every row
  • Counts of cases only. No patient information is recorded.

See it with your own group's rules

Tell us about your group and we will show you its schedule being built.