About
Why this exists
Because the person who builds a department's schedule is usually a clinician doing it in the evenings, unpaid, and because the result is a schedule whose fairness nobody else can verify.
Both halves of that are solvable with software and mostly have not been. The market is full of tools that publish a schedule somebody else built, which leaves the hard part — building it, and defending it — exactly where it was.
What the product is
A scheduling system that generates the schedule from the rules a department already works by, distributes the undesirable slots evenly over a window you choose, shows everyone the counts it used, and handles the swaps, leave and open shifts that follow.
Features describes each part.
What it refuses to do
It does not hold patient data. It schedules staff. See security.
It does not hold financial data. No card details, no pay rates. Payment details live with the payment processor.
It does not ship a list of job titles. Every attempt to define the professions and hierarchies that exist in healthcare is wrong somewhere. A site administrator defines the categories their department actually uses.
It does not claim certifications it does not hold. The security page lists what we do not have, by name.
It does not claim to deliver compliance. Software can build a schedule against the limits you configure and report the counts. Whether those limits match your accrediting body's current requirements, and whether what was worked matches what was scheduled, are not things a scheduling tool can know. See the duty-hours guide.
What this page does not have
No founding anecdote, no team photographs, no customer logos and no testimonial quotes — because the product is not yet generally available and the honest version of all four is an empty space.
When there are customers willing to be named, they will be named here. Until then, the pages that are worth reading are the ones about the work: the guides.
Getting in touch
Contact us. A real person reads it.