How seniority call-outs work under a collective agreement

This is an explainer, not legal advice. Agreements differ, and yours governs. What follows is the shape most of them share, drawn from the agreements common in this sector and from interviews with the managers and frontline workers who administer them.

What a seniority call-out is

When a scheduled worker cannot come in, the shift has to be offered to someone else. A collective agreement usually says two things about how: who is eligible to be offered it, and in what order the eligible people are asked. The order is almost always seniority, sometimes within a classification, sometimes within a site. The rule exists so the same open shift is not quietly handed to whoever the manager likes, and so the record can show it wasn't.

Agreements in this sector (BCGEU and HEU community social services agreements in BC, CUPE and OPSEU agreements in Ontario, and the local agreements that copy them) differ in the details. The shape is the same.

The order: eligible first, then senior

The order has two steps, and the first one is the part people forget.

1. Who is eligible. Usually casuals and relief staff in the right classification, sometimes part-time staff below their line, sometimes anyone at the site. Eligibility can also drop someone out. They may already be at the overtime threshold, they may not have had the minimum rest since their last shift, or the shift may need a certification they do not hold.
2. Then, among the eligible, by seniority. Highest seniority is offered the shift first. The next person is offered it only if the first declines or does not answer within the time the agreement allows.

The interviews we ran with managers in BC in June 2026 found that step one is done well and step two is done loosely:

That is not a character flaw. A manager calling nine people one at a time, with a house to open at seven, will call the people who usually say yes. The rule and the morning are in conflict, and the morning wins.

The wait between calls, and why it is the rule most often skipped

Many agreements say how long a worker has to answer before the offer moves on: ten or fifteen minutes is common. The point is fairness. Without a wait, a senior worker who is in the shower when the phone rings has lost the shift before she can call back, and the record says she "did not respond".

Skipping the wait is the single most common way a call-out becomes a grievance. It is also the easiest thing to fix, because it is a timer, not a judgement.

What counts as a refusal

Agreements usually distinguish three things, and the record has to as well:

• Declined. The worker was reached and said no. Some agreements count refusals toward a limit; most do not, for casuals.
• No answer. The worker was not reached within the wait. This is not a refusal. It should be logged as an offer made and not answered.
• Not offered. The worker was skipped, on purpose or by mistake. If they were eligible and senior, this is the one that costs money.

The difference matters because a grievance is rarely about who worked the shift. It is about whether the person who should have been offered it first was offered it at all.

The record a steward will ask for

When a call-out is challenged, the steward asks four questions. Who was offered the shift? In what order? At what time? What did each person answer? A schedule that shows who ended up working is not an answer to any of them.

In the agencies we interviewed the record was a manager's own list, updated the next day from memory, or a spreadsheet that lived on one laptop:

A defensible record is written at the moment each offer goes out and each answer comes back, by something that does not get tired. That is the whole argument for doing this with software, and it is a better argument than speed.