Interactive example · fictional data
One absence. Two staffing alternatives.
Compare coverage, availability, recorded qualification, room and budget before proposing a change.
Conceptual demonstration. It does not represent a customer case or prove available features.
Objective Prepare an alternative to cover a shift while making conflicts visible.
Team Coordinator · Professional A · Professional B · Site team
Explore the scenario. No action reaches a real system.
- 01Compare
- 02Propose
- 03Consult
- 04Confirm
- 05Publish
- 06Verify
| Schedule | Morning | Afternoon |
|---|---|---|
| North · proposal | Regular team | No option |
| South site | Regular team | Professional A already assigned |
| Professional B | Unassigned | Availability to be confirmed |
| Room S2 | Available | Available in the records |
Q1: A and B listed · Fictional cap: R$ 600 · A: R$ 450 · B: R$ 550. Q1 is an illustrative marker, not a clinical qualification.
What we know now · v1
Shift without coverage. Compare the options.
Example inputs, parameters and limits
Inputs
- Uncovered Tuesday afternoon shift
- Stated availability
- Recorded qualification Q1
- Room S2 and illustrative budget
Fictional parameters
- Q1 is only a fictional marker, not a medical qualification
- Illustrative cap: R$ 600 per reassignment
- A: R$ 450, already assigned at the same time
- B: R$ 550, availability to be confirmed
Exploration history
Choices and handoffs will appear here, only in this session.
What NebulaOS supports in this example
Supports context, integrations and controls at the points defined by the deployment. Confirmation comes from the destination system.
- NebulaWorks Brings together the work, owners, pending items and process artifacts.
- Starya / FDE Investigate recurring coverage gaps and response times for proposals.
Features, rules and integrations must be confirmed for each deployment.
Related guide: How to organize operational monitoring