The Overtime List: Why Saying No Still Moves You

You got the call at 5:40 in the morning and said no. Reasonable. You had slept four hours and you were back on that night anyway.

Six weeks later you are wondering why the good overtime keeps landing on someone else, and why your name came up on a forced shift ahead of two people with less service than you.

Nothing went wrong. The list did what it was written to do. In a lot of contracts, the call you turned down was added to your total exactly as if you had worked it.

That is the part almost nobody is told on day one: on a round-the-clock roster, extra work is usually not distributed by who answers fastest or who wants it most. It comes off an ordered list, and the number that orders the list is not always a record of hours you were paid for. Here is where that number is actually written down.

Federal law has nothing to say about who gets asked

It is worth being clear about how little the law does here, because people spend a lot of energy arguing the wrong point.

The Fair Labor Standards Act governs what you get paid once hours pass a threshold. It does not govern who gets offered the hours. The regulation says so almost in passing: "Since there is no absolute limitation in the Act (apart from the child labor provisions and regulations thereunder) on the number of hours that an employee may work in any workweek, he may work as many hours a week as he and his employer see fit, so long as the required overtime compensation is paid him for hours worked in excess of the maximum workweek prescribed by section 7(a)" (29 CFR § 778.102).

The same section adds that nothing in the Act relieves an employer of "any obligation he may have assumed by contract" to limit overtime hours or pay premium rates.

Read those two sentences together and you have the whole map. Federal law sets a floor on pay. Everything about distribution — the order, the list, the charging, the forcing — lives in your contract or your department's policy. Which means it is written down somewhere, in ordinary language, and it is usually public.

So let us read some.

The running total is of hours offered, not hours worked

The clearest version of this is in the Andover, Massachusetts fire contract with IAFF Local 1658. Overtime there runs on a "draft system" with a master list, and Section 9.3(b) sets the order plainly: "Overtime shall be offered initially on a seniority rotation basis. As the list progresses, overtime shall be offered first to the Firefighter with the lowest number of cumulative hours on the master list, except where an EMT is required" (Article 9, § 9.3, 2023–2026 agreement).

Lowest cumulative hours goes first. Simple enough — until you read the next paragraph, which defines what "cumulative hours" means:

"As each firefighter is offered overtime, they shall be charged on the master list for the full number of overtime hours offered, whether worked or not."

Whether worked or not. You picked up the phone, you said no, and a full tour's worth of hours went onto your total anyway. Your total is not a record of what you earned. It is a record of what you were asked.

That sounds harsh read cold, and it is worth understanding why a union would agree to it. If refusals were free, the person who never answers the phone would sit at the bottom of the list forever and be offered everything, first, in perpetuity. Charging the refusal is what makes the rotation actually rotate. The clause exists to protect the people who do pick up.

It also comes with limits, and the limits are where the practical knowledge is. The same subsection continues: "However, firefighters will not be charged for more than one refusal per shift." And a refusal only counts against you if it is a genuine refusal — the contract carves out a long list of situations that do not count, including being "on approved or scheduled to work an approved special leave, attending an approved EMT class, outside detail, sick leave with doctors note, disability leave, vacation, personal or allowed leave or any approved instructional class during that overtime period."

There is one more piece worth knowing, in Section 9.3(g): "All units shall begin a clean draft master list for all bargaining unit members January 1st of each year." The total resets annually. Where you sit in November and where you sit in January are two different facts.

And new arrivals do not start at zero. Under 9.3(f), after their first thirty days a recruit "will assume high hours of the unit and then fall into the draft rotation" — the same rule applies to anyone transferring in under 9.3(i). Starting at zero would mean being offered everything on your first week. Starting at high hours means being offered nothing until the list comes around.

The same word, "the list," can mean two opposite orders

A few towns over, the Upton, Massachusetts fire agreement runs a completely different architecture, and it is a good illustration of why you cannot generalize from one department to another.

Upton has two lists, ordered in opposite directions.

The voluntary one, for open shifts, runs "starting with the most senior to the least senior." You go to the top by waiting, and the contract spells out the movement: if you are not available your name "shall go to the bottom of the list" — but if the reason is one of a defined set (already on a shift, town-approved leave, department-approved outside training, or missing the qualification the shift needs), then "their name shall be skipped and shall remain at the top of the list for the next available open shift" (Article VIII, § 6).

The forced one, in Section 11, runs the other way: "a list of Bargaining Unit Members starting with the least senior to the most senior," and the person at the top gets forced. Same protections for the same defined absences.

So in Upton, seniority pulls you toward the voluntary work and pushes you away from the forced work, and both effects are produced by the word "list." If you moved here from Andover and assumed the list worked the way your old list worked, you would be wrong twice.

Section 7 adds something I have not seen elsewhere and that is worth borrowing as a question wherever you are: how long you get to answer, and what happens if you do not, is keyed to the notice period.

That is a well-built clause. A missed call at 3am costs you nothing; a shift posted a week out that you ignore costs you your place. Whether your own agreement makes that distinction is a real question to ask, because a department that treats every unanswered call the same way is quietly penalizing people for sleeping.

In nursing, volunteering can buy you off the forced list

The same machinery shows up far outside the fire service, doing a slightly different job.

The Washington State agreement covering DSHS and DOH nurses with SEIU Healthcare 1199NW puts mandatory overtime on an inverse-seniority rotation: "When overtime is required, it will be assigned to nurses on duty in inverse order of seniority, provided the nurses have the skills and abilities required of the position" (Article 6, § 6.4(A)).

Refusing is possible, once, and it does not get you out of the rotation: "A nurse can refuse to work a required overtime one (1) time per rotation. The nurse will remain on the list and will be required to work the next required overtime assignment."

The cycle ends only when it has run all the way through — "The inverse order will be re-established when the list has been exhausted, i.e., the nurse with the greatest seniority has worked his or her required overtime."

And then the sentence that changes how you would actually plan a month:

"A nurse who volunteers to work an overtime shift will have his or her name removed from the required overtime rotation for that cycle."

Under that clause, picking up a shift you choose is not only extra pay. It is insurance against a shift you do not choose, at a time you do not pick, on a day you may already have plans for. A volunteered Tuesday and a mandated Friday are not interchangeable, and the contract prices that difference for you.

Whether your agreement contains anything like it is worth knowing before the next cycle rather than after.

Being skipped almost never pays

Here is the part that surprised me most, because it turned up independently in two contracts that have nothing to do with each other.

If the employer runs the list wrong and passes over someone who should have been called, what does the person get?

In East Grand Rapids, Michigan, the police agreement rotates call-in overtime down an established callback list — and you are only on that list if you opted in, "provided that the employee has indicated that they want the overtime opportunity by placing their name on the overtime roster for their classification." When the order is not followed, the contract says: "the remedy of the affected employee and the Union shall be limited to placement of the affected employee at the top of the overtime opportunity list" (Section 9.2, 2020–2023 agreement with POLC).

The Washington nursing agreement reaches the same place in different words: "If a nurse was not offered overtime for which he or she was qualified, the nurse will be offered the next available overtime opportunity for which he or she is qualified. Under no circumstances shall a nurse be compensated for overtime that was not worked" (§ 6.4(B)).

Two different states, two different professions, two different unions, one answer: the remedy for a scheduling error is a place in line, not money. Which tells you something about what the list actually is. It is not an administrative record of a process. It is the thing itself — the asset being distributed. Losing your position is the injury, and restoring your position is the whole repair.

That is also why the grievance most people want to file ("they owed me that shift") tends to go nowhere, and the one that works ("put me back where I was") tends to succeed.

And it is not only shift work in the emergency services

If you work somewhere without a fire hall or a nursing station, the same clause shape is still probably above you.

Ohio University's agreement with AFSCME Local 1699 rotates scheduled overtime among qualified employees and then says: "An employee who is offered but refuses an overtime assignment shall be credited as if the employee had worked the overtime for purposes of equalization." It goes further than the fire contracts on one point — being unavailable is treated the same as refusing: "An employee who is not available for overtime (on temporary assignment outside the segment/department, on temporary assignment outside the Bargaining Unit, or on leave for more than two (2) weeks) will be charged on the overtime equalization list as if the employee was asked but refused overtime" (Article 11).

For emergency overtime, it is blunter still: "Employees who refuse or are not available for emergency overtime (i.e., not present or unable to be reached by telephone) shall be charged with overtime as if they worked the overtime."

Read that against Andover's carve-outs and you can see the whole range in one glance. Andover protects you while you are on approved leave. Ohio University charges you for a long leave as though you had said no. Same mechanism, opposite treatment of the same situation, and the difference is not a legal question — it is just what two sets of people agreed to.

The four questions worth asking once

None of this needs to be re-derived every time the phone rings. It is four facts, they are written down, and they do not change often.

1. What is my position on the list actually measured by? Hours worked, hours offered, or seniority. These produce completely different months, and only one of them can be checked against your paystub.
2. What is charged to me when I say no, and what is exempt? Look specifically for approved leave, sick leave, training, and already being on duty. Look also for a cap like Andover's "not more than one refusal per shift."
3. When does the list reset, and where do I land after a transfer? An annual clean list and "assume high hours on transfer" are both common, and both mean your position is not a permanent property of you.
4. Does the voluntary list interact with the forced list? In some agreements they are entirely separate. In others, as in Washington, volunteering removes you from the forced rotation for that cycle — which turns a shift you pick into protection against one you do not.

If you can answer those four for your own workplace, you know more about how your next three months will actually be shaped than any single month's schedule will tell you.

And if the answer to any of them is "nobody could tell me," that is worth noticing too. A list that nobody can describe is a list nobody is checking.

US framing throughout. Every clause quoted above is from one specific agreement and applies only to the people covered by it — these mechanisms vary enormously between departments, and the point of the article is that variation, not a rule you can carry from one to another. Read your own agreement, or ask your steward for the article that covers overtime distribution.

Related reading: Mandatory overtime, explained · Call-back pay and minimum hours · Shift bidding: seniority and bid cycles · The relief factor: why "fully staffed" is short