Antonimar Mello, BSN, RN - OnCallRank founder

Antonimar Mello, BSN, RN · Founder, OnCallRank

About the founder

The nurse who built OnCallRank.

I am Antonimar Mello, a perioperative registered nurse on Long Island. I built OnCallRank because the argument over who gets the next call shift is not a medical problem, and it should never have been a memory problem either.

Who is behind OnCallRank

Antonimar Mello, BSN, RN. I am a perioperative registered nurse on Long Island and I still practice. That is not a credential bolted onto a software company after the fact. It is the reason the software exists at all.

I have never been the person who hands out call shifts. Only managers do that, and that is how it should be. My seat was the other one. The text goes out, the fastest phone wins, and if you are scrubbed in when it lands, the shift is gone by the time you pull your gloves off. Ask any nurse who takes call and you will hear a version of the same story.

Why OnCallRank exists

Most call fights are not really about one shift. They are about not being able to see the rule.

When the rotation lives in a spreadsheet, on a whiteboard, or in one manager's head, nobody else can check whether their turn came and went. People fill that gap with guesses, and the guess is almost always "why him again." The manager is left defending a decision with nothing written down to defend it with, which is a hard place to stand anywhere and harder in a union shop, where seniority is contractual and a disagreement can turn into a formal grievance.

So I built the rotation I wished was already there. A director sets the unit's seniority order once. When a call shift opens, the same notification reaches every eligible person at once. Staff claim with one tap, seniority settles the tie, a manager approves, and the whole sequence lands in a permanent history with a timestamp and a name attached. Six months later, "whose turn was it" has an answer anyone on the unit can pull up and read for themselves.

Nothing in that loop is decided by AI. The order your unit agreed on is the rule. The app's entire job is to enforce it without an opinion.

What the product believes

OnCallRank facilitates. It does not police.

An awarded call shift belongs to the person holding it. If they want to hand it to a specific coworker, including the one who always says yes, that is theirs to decide and the app treats it as ordinary. If they would rather post it back open and let the rotation choose among whoever wants it, that works too. Either way, giving a shift away changes who works it, never whose turn it was. Rotation credit stays with the person originally awarded, so covering for a colleague never costs you your place in line.

The choosing was never the broken part. The record was, and so was the manager's approval. Those are the two gaps the software fills, and it stays out of the rest.

The same restraint draws the edges of the product. OnCallRank is the unit-level scheduling layer, so time and attendance, payroll, and accruals stay in whatever platform already runs them. It collects an email address and a password. Nothing clinical passes through it.

Will OnCallRank still be here in five years?

People ask, and they are right to.

The company is AF Mello Solutions Inc, an S-Corp registered in New York. The OnCallRank trademark is filed, with registration pending. Your unit's data is your unit's data: every action ever recorded exports to PDF and CSV, into a spreadsheet your team could pick up and keep running with tomorrow.

I built OnCallRank, it has been in production since April 2026, and I am still the one running it. And whatever the future holds, nothing about your rotation is locked inside my software: you can hold the entire record in your own hands the day you ask for it.

Rather hear it from me directly?

Fifteen minutes on the phone, or a free three-week pilot on one unit. Either one starts here.