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.

OnCallRank staff home screen showing two open call shifts and a draft turn

Everyone sees the queue. Everyone sees who's next. The rotation is the rule, not the rumor.

How it works

Six steps. Set up once. The app does the rest.

Admin panel showing the seniority order list with drag handles for each staff position
01

Director sets the queue.

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.

02

A shift opens. Notification goes to everyone.

When a call shift posts, every eligible staff member gets the same push at the same moment. No one gets a head start.

Lock screen showing an OnCallRank push notification for a new RN call shift
Staff home screen with an open call shift card and a green Request This Shift button
03

Staff claims it, one tap.

First eligible person to tap accept gets it. Seniority order resolves any ties. Pass and it rolls down the queue.

04

Manager approves.

Every accepted shift waits on one tap from the manager. Approve, deny, or ask. Each action stamps the audit log with timestamp and actor.

Manager view of an open shift with requested-by list and an Award to Nurse button
Staff rotation view showing the queue with who is next up
05

Rotation moves to the next person.

The queue rebalances after every pick. Everyone sees who's next, anytime they look. No one moves up the line in private.

06

Every action lives in the history.

Picks, approvals, overrides, swaps. All recorded with timestamp and actor. Six months later, the answer is on the record.

History tab showing past call assignments with timestamps
Antonimar Mello, RN — OnCallRank founder

Antonimar Mello, RN

Built by a nurse, on the floor

I built OnCallRank because the paper tracking never worked.

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.

Audit

Every action. Every timestamp. Every rule.

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.

audit_log · append-only
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
6 of 1,247 entries · last 7 days read-only export: PDF · CSV
1

Logged with timestamp and actor.

Pick, accept, pass, override, approve, swap. Nothing happens off-system.

2

No deletions, ever.

Append-only by Postgres design. A retroactive change leaves its own row in the log.

3

Override requires a reason.

The bypassed person picks first next time. Queue rebalances automatically.

Security

Built for IT review.

Tenant isolation, by Postgres design.

Every unit's data lives behind row-level security. Cross-unit visibility is impossible at the database layer.

No PHI. Ever.

Shifts, schedules, queue positions. No patient information. BAA template ready on request.

Hardened hosting and full data export.

TLS, HSTS, append-only audit log. Your data is yours, exportable anytime.

Pilot

Three weeks. No cost. No commitment.

Pilot scope is yours: one unit, your staff, your seniority order.

01

Manager signs up and configures the unit.

Two minutes to create the account. Set seniority order, roles, and holiday rules. Send invite links to staff.

02

Staff joins.

Each invite link takes a minute. Once your roster is in, you're live.

03

Three weeks live.

Daily use. Audit log fills up. Real data.

04

Post-pilot decision.

Go or no-go. Full data export either way.

Honest

Who this is NOT for.

Closing the wrong-fit doors up front saves everyone a meeting.

×

Hospitals looking to replace UKG, Workday, or Epic scheduling.

OnCallRank handles the on-call rotation specifically. Master schedule stays where it is.

×

Units with no on-call coverage requirement.

This only matters when there's a queue to manage.

×

Health systems that require SOC 2 Type 2 certification for any vendor contract.

We're not certified yet. We're a fit for unit-level pilots and smaller hospitals while we build there.

×

Anyone looking for an AI-powered scheduling oracle.

OnCallRank uses no AI for the rotation. The director's seniority order is the rule. The app enforces it.

FAQ

Real questions we get.

Are you HIPAA compliant? +

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.

Does this replace UKG, Workday, or Epic scheduling? +

No. OnCallRank handles the on-call rotation specifically. Your master schedule stays where it is. We sit next to it.

How do you handle override scenarios? +

Managers can override any pick. The override is logged with reason required. The queue rebalances on the next opening so the bypassed person picks first next time.

What happens to data if we cancel? +

You get a full export of every action ever taken on your unit. PDF and CSV. We delete our copy on your timeline.

Can multiple units in the same hospital each have their own rotation? +

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.

Who's behind this, and what if you disappear? +

AF Mello Solutions Inc, an S-Corp registered in New York. Trademark filed (USPTO 99748772). Copyright registered (Reg # 1-15158973441). Your data is yours and exports cleanly into a spreadsheet your team can keep running with.

Can we see a demo before the pilot? +

Yes. Book the call and we walk through the manager and staff flows on a sandbox unit before any commitment.

Ready to end the fight?

Book the call. 15 minutes. The demo is the pitch.