On-call rotation that takes the fight out of it.
A seniority queue that runs itself, on the record, on every phone in your unit.
A seniority queue that runs itself, on the record, on every phone in your unit.
Everyone sees the queue. Everyone sees who's next. The rotation is the rule, not the rumor.
Drag the staff list into the order your unit has agreed on. Holidays get their own rules in the same setup. The app enforces it from there.
When a call shift posts, every eligible staff member gets the same push at the same moment. No one gets a head start.
First eligible person to tap accept gets it. Seniority order resolves any ties. Pass and it rolls down the queue.
Every accepted shift waits on one tap from the manager. Approve, deny, or ask. Each action stamps the audit log with timestamp and actor.
The queue rebalances after every pick. Everyone sees who's next, anytime they look. No one moves up the line in private.
Picks, approvals, overrides, swaps. All recorded with timestamp and actor. Six months later, the answer is on the record.
Antonimar Mello, RN
I'm an RN on Long Island. The rotation fight on my unit wouldn't end and management was taking the heat for what should have been a math problem.
I built the queue we wished we already had.
Hospital legal and HR ask three questions. We answer all three before they ask. Every staff member sees the queue. Every action is on record. No one moves up the line in private.
| Timestamp | Actor | Action | Target |
|---|---|---|---|
| 05-16 09:31 | manager_a | approve | shift_a8c3 |
| 05-16 09:24 | staff_4 | accept | shift_a8c3 |
| 05-16 09:24 | staff_3 | pass | shift_a8c3 |
| 05-15 14:02 | manager_a | override | queue_RN · reason: clinical |
| 05-15 13:58 | manager_a | post | shift_a8c3 |
| 05-14 11:30 | director_1 | queue.set | queue_RN · v23 |
Pick, accept, pass, override, approve, swap. Nothing happens off-system.
Append-only by Postgres design. A retroactive change leaves its own row in the log.
Staff, managers, and directors see the same log. No private back-channel.
Every unit's data lives behind row-level security. Cross-unit visibility is impossible at the database layer.
Shifts, schedules, queue positions. No patient information. BAA template ready on request.
TLS, HSTS, append-only audit log. Your data is yours, exportable anytime.
Pilot scope is yours: one unit, your staff, your seniority order.
Two minutes to create the account. Set seniority order, roles, and holiday rules. Send invite links to staff.
Each invite link takes a minute. Once your roster is in, you're live.
Daily use. Audit log fills up. Real data.
Go or no-go. Full data export either way.
Closing the wrong-fit doors up front saves everyone a meeting.
OnCallRank is the unit-level call scheduling layer. We sit next to your workforce platform, not inside it.
This only matters when there's a queue to manage.
We're not certified yet. We're a fit for unit-level pilots and smaller hospitals while we build there.
OnCallRank uses no AI for the rotation. The director's seniority order is the rule. The app enforces it.
OnCallRank doesn't store PHI. Shifts, queue positions, and manager actions only. We sign a BAA if your hospital requires one for any vendor regardless of PHI scope.
No. Time, attendance, payroll, and accruals stay in your existing workforce platform. OnCallRank handles unit-level call scheduling. We sit next to the platform, never inside it.
Each round has a configurable time window — once a turn opens, the staff member has that window to claim or pass. If they don’t act, the manager can override and advance the queue. Every override is logged with timestamp and actor.
You get a full export of every action ever taken on your unit. PDF and CSV. We delete our copy on your timeline.
Yes. Each unit is a separate tenant with its own queue, manager set, staff list, and rules. They share an organization but don't see each other's data.
AF Mello Solutions Inc, an S-Corp registered in New York. Trademark and copyright registered. Your data is yours and exports cleanly into a spreadsheet your team can keep running with.
Yes. Book the call and we walk through the manager and staff flows on a sandbox unit before any commitment.