Platform · Scheduling
Turn the schedule into the start of the operation.
A schedule should not end at a calendar. Phibian connects planned work to the people, time, activity and operational evidence that follow it.
The operational problem
The plan and the day stop agreeing by mid-morning.
A schedule is published, and then the real day begins. Someone calls out. A visit runs long. A site changes. Within a couple of hours the published plan and the actual operation have quietly diverged, and the only people who know are the ones improvising in the middle of it.
Because scheduling usually lives in its own tool, that divergence is invisible until something downstream breaks — an unstaffed shift, an unexplained gap in a timesheet, a service that was planned and never delivered. The schedule was never wrong; it was just never connected to what happened next.
How Phibian handles it
Plan clearly. Connect plan to execution. Understand coverage.
Scheduled work in Phibian is not a separate artefact. It is the reference point that field activity, exceptions and approvals resolve against, which is what makes coverage a fact rather than a guess.
Plan clearly
Give teams a reliable view of upcoming work, by person, program and location — one place both a supervisor and a worker can trust.
Connect plan to execution
Scheduled work is compared against what was actually observed, so the difference between intent and reality is visible while the day is still running.
Understand coverage
Approved time off sits beside scheduled work, so staffing conditions that need attention surface without cross-referencing two systems.
Exceptions rather than reports
When planned work has no matching activity, that becomes a ranked item for review — not a discrepancy discovered at period close.
Scoped to the right supervisors
Schedule visibility follows the same permission model as everything else, scopeable to a program or a location.
One definition of the work
Because scheduling shares the workforce directory, a person is the same person across the schedule, the field record and the approval.
In the product
One model, two surfaces.
What the worker records is what the supervisor reviews. There is no second entry, and no reconciliation step between the two.
In Admin
Supervisors work from coverage and exceptions rather than from a wall calendar: what is scheduled, who is off, and where the plan and the day have stopped matching.
- Scheduled work by person, program and location
- Approved time off visible against coverage
- Planned work with no matching activity, surfaced as an exception
- Every entry opens into the underlying operational record
For the Worker
The worker gets the part of the schedule that concerns them — today, in order, with the context needed to start.
- Today’s assignments on one screen
- What is next, and where
- Request time off and see its state
- No hunting through an organization-wide calendar
How it connects
Nothing here is a standalone product.
The value is not the capability on its own — it is what happens when this record is continuous with the rest of the operation.
Workforce defines who can be scheduled
Assignments, roles and program scope come from the shared directory rather than from a scheduling-only list of names.
Field activity closes the loop
Clock-ins and check-ins are matched against scheduled work, which is what makes “did this happen?” answerable today.
Time and approvals inherit the context
Hours arrive at the weekly approval already associated with the work they belong to.
Attention ranks what changed
Coverage problems and unmatched work become operational items, not a report someone has to remember to run.
Keep exploring
Workforce
The directory, assignments and approval cycle scheduling resolves against.
Explore WorkforceField
What happens when the plan meets the real world, and how it is recorded.
Explore FieldDistributed workforce
The solution view for coordinating people across locations and systems.
Explore Distributed workforce