Resources · Documentation
Call-assignment grievances: the documentation that settles them
By Antonimar Mello, BSN, RN, a working perioperative nurse on Long Island and the founder of OnCallRank. This article is about record-keeping practice, not legal or labor-relations advice. Published July 6, 2026.
A call-assignment grievance almost always turns on one factual question: who was offered the shift, in what order, and when. The manager who can answer that from a record made at the time wins the meeting quickly and fairly. The manager reconstructing it from memory and text threads is negotiating, whatever the contract says.
Why call assignments are grievance magnets in union units
In a union-represented unit, seniority is not a management preference, it is contract language, so a call assignment that looks out of order is not a gripe: it is a potential contract violation with a formal process attached.
That changes the stakes of ordinary scheduling sloppiness. In a non-union unit, a skipped turn costs the manager an awkward conversation. In a union unit, the same skipped turn can become a written grievance, a steward meeting, and a remedy discussion. None of that requires anyone to be acting in bad faith. It just requires the assignment record to be thinner than the contract language, and in most units it is: the contract specifies seniority order with precision, while the actual assignments live in group texts and a spreadsheet that gets overwritten weekly.
The question a grievance actually asks
Strip the framing away and nearly every call-assignment grievance reduces to a sequence question: what was the rotation order that day, who was offered the shift before it was awarded, and what did each person say.
That means the useful record is not a summary ("J. worked 3 call shifts in June") but a sequence: offer, response, award, each with a time. Summaries invite arguments about what they left out. Sequences settle them.
The record set that answers it
Five items, captured when they happen, answer nearly any assignment dispute: the rotation order in force, the offer and who could see it, each response with its time, the award and who made it, and any trade or give-away afterward.
| Record | What it answers in a dispute |
|---|---|
| The rotation order in force that day | Was the grievant actually next? |
| The offer, and who it was visible to | Did everyone get the same chance to claim it? |
| Each response, timestamped | Did the grievant request it, decline it, or stay silent? |
| The award: who, by whom, when | Did the decision follow the published rule? |
| Any later trade or give-away | Who actually worked it? (The rotation itself never moves on a trade; the record just shows who covered.) |
Notice what is not on the list: justifications written after the fact. A note explaining a decision three weeks later reads as advocacy. The same facts recorded the day they happened read as evidence.
Why texts and spreadsheets fail exactly here
Group texts and spreadsheets fail as grievance records for the same two reasons: they are incomplete by accident and editable by design.
- A text thread shows who answered, never who was asked. If the offer went out by voice to two people first, the thread cannot prove it, and the gap belongs to the manager.
- A spreadsheet's current state is not its history. Anyone disputing an entry can reasonably ask when it was written, and a file that can be edited silently cannot answer.
- Both scatter across personal phones and shared drives, so assembling the sequence for one contested shift means archaeology across weeks of messages.
Transparency prevents more grievances than it wins
The strongest use of the record is before any dispute: when staff can see the rotation, the offers, and the awards themselves, most challenges never get filed, because the answer is already visible.
Grievances thrive on information asymmetry. When the assignment history is open to the unit, a nurse who suspects they were skipped checks the record in thirty seconds and either finds the mistake (which the manager should want found) or finds the answer. Either outcome beats a formal process. Stewards benefit the same way: a visible, complete record lets them tell a member "this one was clean" with confidence, which protects the process for the disputes that are real.
Where software fits
A scheduling tool carries its weight in a grievance context when the record writes itself: every offer, response, award, and trade logged with timestamp and actor, in a history that cannot be quietly edited, visible to the people it governs.
That describes OnCallRank's history by design, because its founder is a working perioperative RN who lived the paper version of this problem from the staff side: open call shifts are offered to the whole unit on their phones, every request and award is logged with the time and the person who acted, a give-away changes who works the shift without ever moving the rotation, and nothing in the history can be deleted. The product holds no patient data at all, only names and shift records, so no PHI concern attaches to adopting it. If a defensible record is the thing your unit is missing, the trial is free for three weeks, no card: start your free trial, or book a 15-minute call.
More from the resource library: all articles · How to keep an on-call rotation fair when seniority rules collide