Now onboarding design partners

Workforce scheduling as flexible as your workforce.

scheduleBru is the operations engine for high-stakes, shift-based teams — configured to fit any world. Roster, approve, and run from one staged, auditable workspace.

No deployment to reconfigure Audit-grade staged saves Reporting built in
Schedule Timecard Reports Requests
Save Changes
Day Week Month Unsaved schedule changes
NameWatchJob Mon 28Tue 29Wed 30Thu 01Fri 02Sat 03Sun 04
Smith, JamesBlueFF/L DDNN
Williams, SarahBlueFF ALALDD
Johnson, MarkRedEO ABSDDNN
Evans, ClaireGreenFF/L DDNN
Brown, LisaWhiteEO NNDD
On shift (Day): 3 On shift (Night): 2 Annual Leave: 2 Absent: 1
Staff request · auto-gated
SWSarah W.Approved
CEClaire E.Approved
Annual leave balance
142.5 hrs

Built for operations where a shift simply can't go unfilled.

Emergency Services Manufacturing EMS Healthcare Utilities Public Safety Transit
The platform

One workspace for the whole operation.

Every surface is profile-driven and database-configured — so the system speaks your organization's language, not ours.

Core workspace

Schedule grid

A profile-driven rostering grid with multi-segment shifts and a staged save model. See coverage, conflicts, and skills at a glance — commit changes only when they're right.

Hours & pay

Timecard & balances

Balance events, policies, and adjustments tracked to the hour. Accruals and leave roll up automatically, with a full audit trail behind every change.

Insight

Reports

Database-profile-driven tabular views with layered filters. Build the report once, save the profile, and let planners slice coverage, overtime, and compliance on demand.

Workflow

Staff requests

Multi-step request workflows with automated gating. Swaps, leave, and overtime route themselves through the right approvals — and stop when policy says stop.

Admin

Config Over Code

Reshape stations, watches, jobs, and rules from database values — no deployment, no developer. Administrators own the system, not a backlog ticket.

Comms

Email engine

Trigger-based draft generation and send management. The right message goes out the moment a shift changes — reviewed, queued, and logged before it ever leaves.

config > code

Your terminology. Your rules.
Zero deployments.

Most platforms make you bend to their model. scheduleBru bends to yours. Words like Station, Watch, and Job are database values — change them, and the whole system follows.

Rename Watch → Crew, Station → Depot — instantly, everywhere
Define shift types, skills, and gating rules without a release
Build report and schedule profiles that planners reuse
system_setup · config object
// terminology and rules live in the DB
{
  "label_watch":   "Crew",
  "label_station": "Depot",
  "shift_types": ["D", "N", "DS", "NS"],
  "gating": {
    "min_skill":     "FF/L",
    "max_overtime":  48,
    "auto_approve":  true
  }
}
// no deploy. no ticket. live on save.
How it works

From model to operation in three moves.

Model your world

Set your stations, watches, jobs, and rules in System Setup. The platform adopts your language and your gating logic before anyone touches a roster.

Build the roster

Plan in the schedule grid with staged saves. Test changes against coverage and skills, then commit a clean, auditable version when it's ready.

Run operations

Requests route themselves, timecards and balances stay current, and the email engine keeps everyone informed — all from one workspace.

Get started

Bring scheduleBru to your operation.

Join the waitlist for early access, or talk to us about a configuration built around how your teams actually run.

Almost there — check your inbox to confirm your spot on the waitlist.
Something went wrong. Please try again, or email us directly.

No spam. Personnel and roster management, nothing else.

Need it sooner? Request a demo →