You Worked It. The Roster Says Someone Else Did.
Somebody texts you at nine at night. Can you take my Thursday? You say yes, because that is what people in this job do, and because you will need the same favour in three weeks.
Thursday comes. You work it. Twelve hours, or twenty-four, or whatever your unit runs. Two weeks later the paycheck arrives and there is nothing on it for that day.
You look at the roster. Thursday is still in your coworker's name. Nobody ever moved it.
This is not a rare disaster. It is the ordinary result of a very ordinary gap: the schedule and the time record are two separate systems, and the handshake only ever lands in one of them — sometimes in neither.
The swap lives in three places, and they don't talk to each other
Walk through what actually happened on that Thursday.
- The agreement. A text message between two people. Real, but it exists only on two phones.
- The roster. The published schedule your unit is staffed from. This is a plan, not a record of anything. It says who was supposed to be there.
- The time record. Punches, a signed timesheet, an exception log. This is what payroll reads.
A properly processed swap updates all three. An informal one updates the first, and then everyone assumes the rest follows. It usually does — right up until it doesn't, and by then the shift is two weeks in the past and the only person who remembers it clearly is you.
The question worth asking is not "did we agree?" It is "which of those three did the agreement actually reach, and who put it there?"
For public agencies, "approved" is part of the definition
If you work for a fire department, a police agency, a public EMS service, or another public employer, federal law has a specific box for shift trades — and the approval is not a formality bolted onto the side of it. It is one of the conditions.
Under 29 CFR § 553.31(a), two individuals employed by the same public agency may agree, "solely at their option and with the approval of the public agency, to substitute for one another during scheduled work hours" in performance of work "in the same capacity." When that happens, "each employee will be credited as if he or she had worked his or her normal work schedule for that shift" (29 CFR § 553.31).
Read that credit rule closely, because it cuts both ways.
- Swap approved: you get credited with your own normal schedule. So does your coworker. The hours you actually worked on their shift are excluded from your overtime calculation. Clean.
- Swap never approved: it is not a substitution under the rule at all. It is just you, working hours, on a day the agency has you down as off.
The second case is not automatically worse for you — in some situations it is better, because those hours are now ordinary hours worked and may push you into overtime. But it is unpredictable, and it depends entirely on a record nobody made.
Hours you worked count, even if nobody scheduled them
Here is the part most people never get told, and it is the most useful thing on this page.
Whether hours count is not decided by whether they were on the schedule. Under 29 CFR § 785.11: "Work not requested but suffered or permitted is work time." The regulation's own example is an employee who voluntarily keeps working after the shift ends. What matters is that "the employer knows or has reason to believe that he is continuing to work" (29 CFR § 785.11).
§ 785.12 extends the same rule to work done off the premises: "If the employer knows or has reason to believe that the work is being performed, he must count the time as hours worked" (29 CFR § 785.12).
And § 785.13 puts the responsibility somewhere specific: "In all such cases it is the duty of the management to exercise its control and see that the work is not performed if it does not want it to be performed." The regulation continues: "It cannot sit back and accept the benefits without compensating for them. The mere promulgation of a rule against such work is not enough. Management has the power to enforce the rule and must make every effort to do so" (29 CFR § 785.13).
Put those three together and the shape is clear. You standing in the building, doing the job, for twelve hours, in front of a supervisor, is not erased by the fact that a scheduling entry was never made. The scheduling entry was never the thing that made it work.
Keeping the record is the employer's job, not yours
This is the second half, and it is the half that changes how the conversation goes.
29 CFR § 516.2(a) requires employers covered by minimum wage or overtime provisions to keep, among other items, "hours worked each workday and total hours worked each workweek" — and for employees on a section 7(k) work period, which covers most fire and police personnel, "the starting time and length of each employee's work period" (29 CFR § 516.2).
That is not a best practice. It is an obligation, and it sits with the employer.
So when the answer to "can you fix my pay?" is "we can't change hours without proof" — the missing record is, in the first place, the employer's missing record.
What happens when the record isn't there
The Supreme Court answered this in 1946, in Anderson v. Mt. Clemens Pottery Co., and the rule has framed unpaid-hours cases ever since.
Where an employer's records are inadequate, the Court held that "an employee has carried out his burden if he proves that he has in fact performed work for which he was improperly compensated and if he produces sufficient evidence to show the amount and extent of that work as a matter of just and reasonable inference."
Then: "The burden then shifts to the employer to come forward with evidence of the precise amount of work performed or with evidence to negative the reasonableness of the inference to be drawn from the employee's evidence." And a court "may then award damages to the employee, even though the result be only approximate" (Anderson v. Mt. Clemens Pottery Co., 328 U.S. 680 (1946)).
The principle underneath it: an employer does not get the benefit of its own failure to keep records.
This is not a promise that you will be paid, and it is not legal advice — it is a description of how the burden is arranged. But it is worth knowing, because the informal version of this conversation runs on exactly the opposite assumption: that a missing record is your problem to solve alone, and that without a perfect one you have nothing.
The practical part
None of the above helps you at the moment the text arrives. These do.
Before you say yes
- Ask where the swap gets entered, and who enters it. Not "did you tell them" — where does it go, and who types it. If the honest answer is "we just tell the officer on duty," that is a plan, not a record.
- Ask who approves it. On a public agency, approval is part of what makes it a substitution at all.
- Ask when it has to be in by. Most systems have a cutoff relative to the pay period, not relative to the shift.
On the day
- Punch in and out under your own name if there is any way to do it. A time punch is a record even when the roster is wrong, and it is the single most useful thing you can leave behind.
- If you cannot punch, send one short message that day to whoever runs the schedule: date, hours, whose shift, that you worked it. One line, in writing, on the day. That message is your contemporaneous note, and it is worth more than a perfect memory a month later.
If it has already happened
- Write down what you have while it is fresh — the original text, who saw you there, when you arrived and left.
- Raise it as a timekeeping correction, not as a dispute with your coworker. Payroll can fix a record. It cannot referee a favour.
- Keep the ask specific: which day, which hours, which pay period.
The one-line version: a swap is not an agreement between two people, it is an entry in a system — and until someone makes the entry, the only person carrying the shift is the one who showed up for it.
This article explains general federal wage rules in plain language. It is not legal advice, and state law, your contract, and your agency's own policies can change the answer. If real money is missing from a check, your union representative or your state labour agency is the right next call.
Sources: 29 CFR § 553.31 · 29 CFR § 785.11 · 29 CFR § 785.12 · 29 CFR § 785.13 · 29 CFR § 516.2 · Anderson v. Mt. Clemens Pottery Co., 328 U.S. 680 (1946)