Features/Planner

01 · Anchor

The surface your chief planner stares at all day.

Daily, weekly, monthly, and year views. Conflict checks on every save. Drafts for what's still being figured out so today's calendar stays calm while tomorrow's gets worked out.

BASESuiteBasic planner in BASE · Drafts in Suite

A · The headline view

The week is the unit theatres think in.

Five-day calendar grid by default; flip to six- or seven-day if your house works Sundays. Every event carries its production, work type, room, and roster. Click an empty slot to schedule. Drag an event to move it.

Built for how chief planners actually plan

Conflict detection runs at save time, not on a background job. The system says "this won't work because Ola is already in the Foyer at 14:00" the moment you try to schedule it, while you still have the production calendar open.

  • Day · Week · Month · Year views, navigable with hotkeys
  • Per-event metadata: production, work type, room, attendees, notes
  • Filter by production, work type, room, or person
  • Sticky header so you always see the period you're scoping
Week 27 · 2026-07-06 → 07-10Saved 2s ago
·
Mon 06
Tue 07
Wed 08
Thu 09
Fri 10
10
Hamlet · 1.3 read
Hamlet · 2.1
Crew meeting
Hamlet · tech
Hamlet · run
13
Hamlet · lights
Hamlet · lights
Hamlet · sound
Hamlet · run
19
⚠ Hamlet · preview
Hamlet · perf

B · Live conflict checks

The system tells you it won't work before you publish it.

A conflict is anything that breaks the rules you've configured. Person double-booked. Room double-booked. Work-type rest-time violated. Vacation policy breached. Each conflict is named, blamed on the right entity, and resolvable from the same view.

Conflict surface · live2 conflicts
Person double-booked
Ola Nordmann is in Hamlet · tech (Thu 09 · 13:00–17:00) AND Macbeth · read (Thu 09 · 14:00–15:30). Resolve by removing from one assignment.
Room double-booked
Foyer is reserved for Hamlet · preview (Thu 09 · 19:00–22:00) AND House photo call (Thu 09 · 20:00–20:30). Move one or change the room.

Named, not generic

The conflict banner tells you exactly which person, room, or rule is in trouble. There's no "scheduling conflict detected" — there's "Ola is in two rooms at the same time, here's both, click to fix."

  • Configurable rules per work type (max hours, rest periods, day-off rules)
  • Per-person availability windows + vacation balances respected
  • Conflicts surface in the planner AND in the production's own roster view
  • Live during draft editing; nothing publishes if a conflict is unresolved

C · Drafts Suite

Plans that aren't real yet.

Drafts are sandbox planners. You build them next to the live schedule. You publish when ready and runorder fans out the notifications to everyone affected, with a diff against what each person had before.

The publish flow

Drafts get their own surface, their own conflict checks, their own notification preview. Approve the draft, runorder writes it into the live calendar and emails the people affected with a clear before-and-after. Reject the draft, nothing changes.

  • Per-draft access controls — only some people see the draft
  • Approval workflow — N approvers, configurable threshold
  • Diff against live schedule on the notification
  • Conflict preview before publish, so nothing breaks the live calendar
Drafts · active3 drafts
Season 2026-27 — Q1 rehearsals
42 events · 18 people · awaiting approval (2 of 3)
DraftMaria S.
Hamlet — week 32 reshuffle
8 events moved · 1 person affected
PublishLars H.
Macbeth — full season
126 events · 31 people · drafting
DraftMaria S.

D · Integrations & notifications

It plays nicely with what your team already uses.

The calendar people use every day is their own. Apple Calendar. Google Calendar. Outlook. runorder writes to those via iCal feeds and Google Calendar OAuth. Notifications go out via email and webhooks the moment a change is published.

Integrations · active4 active
Google Calendar42 subscribed
iCal feed18 tokens
Email notifyon publish
Webhook out3 endpoints

People keep their tools

Stagehands won't open a new app to check tomorrow's call time. They check their phone calendar. runorder makes sure what's on their phone matches what's on the plan — and updates it within minutes when something moves.

  • iCal feeds per person, per production, per room, per group
  • Google Calendar OAuth push sync (basic, in BASE)
  • Email notifications on publish + reminder + change
  • Webhook out for in-house automation, Slack, Teams

Want to see your week in runorder?

30-minute discovery call over Teams. We'll size a fit and walk you through how your current scheduling would land in runorder.

Request a conversation →

Or read about the rest.

Productions, People, Timesheets, Admin & access, and the Suite extras. Each gets the same depth as this page.

All features →