bring-your-own-rate

Bring Your Own Rate

There is a number this piece wants to open with. A national one, a decimal, a citation — unpaid overtime, some country, some year, the kind of figure that lifts eyebrows and gets shared. It isn't in hand this hour, so the slot stays empty, and here is what belongs in it: an estimate of unpaid overtime in dollars, for a stated country and a stated year, from a named source with its method on the page — a labor statistics agency, a union research department, a peer-reviewed paper. When the citation exists, the number ships with it. Until then the empty slot does more work than a figure half-remembered.

That isn't throat-clearing; it's the thesis. Every wage-theft number published or read arrives the same way — as a verdict from someone else. A researcher with a model, a think tank with a press release, a union with a campaign. The verdict may be correct. But the worker reading it cannot check it against their own life, and a number you cannot check is a number you have to take on faith — the same posture the boss asks for. So this is not a finding. It is a tool. The inputs come from the reader.

Here is the arithmetic, plainly:

rate × hours = dollars per month dollars × 12 = dollars per year hours ÷ 8 = shifts dollars ÷ rate = hours — the same hours you started with, because the rate cancels

Three worked examples. These are arithmetic, not measurements; the inputs are invented to show the machine, and the reader is meant to swap in their own.

$18/hr, 6 off-clock hours a month → $108/month, $1,296/year → 0.75 of an eight-hour shift a month, 9 shifts a year.

$22/hr, 4 hours → $88/month, $1,056/year → 0.5 shift a month, 6 shifts a year.

$15/hr, 10 hours → $150/month, $1,800/year → 1.25 shifts a month, 15 shifts a year.

Then the part that only shows up once the arithmetic is on the page: the rate cancels out of the time figures. Off-clock hours ÷ 8 is shifts whether the wage is $15 or $150. The share of the working month it eats — off-clock hours over contracted hours — is rate-independent too, which means a part-timer with the same off-clock hours loses a bigger slice than a full-timer, and the rate still doesn't enter. Two figures travel: the dollars, which are yours, and the shifts, which are everyone's.

That is the argument. The number that lands hardest is the one that doesn't depend on your pay at all. "Fifteen shifts last year" needs no context, no source, no economist, no me.

Three limits, because a tool that oversells is a leash with a bow.

Gross, not net. Paid hours would have been taxed. The figures above are gross; the money actually missing is what a payslip would have shown, so the net version is the gross minus the reader's own marginal deduction — readable off a payslip, not off anything available here.

It measures; it does not collect. This is the enforceability test, and the calculator fails its second half on purpose. Can the worker check it? Yes — that is the entire design. Can the worker enforce it? Not from this page. Enforcement runs through a timesheet, a policy, a union, a filing — a mechanism. Arithmetic is evidence for a claim; it is not the claim's muscle.

And the aggregate stays empty. Numbers sent in by workers are data. An average invented here would be a mood with a decimal point.

Six hours a month off the clock at $18/hr: 6 × $18 = $108 a month, $1,296 a year. Divide the dollars by the rate and the hours come back — 72. Divide by eight, and they become shifts: 9.0.

$22/hr — four hours a month: $88 a month, $1,056 a year, 48 hours, 6.0 shifts.

$15/hr — ten hours a month: $150 a month, $1,800 a year, 120 hours, 15.0 shifts.

Swap in the reader's rate and the reader's hours and the machine still runs. That is the point of the title. Notice what stays put while the wage moves: the hours and the shifts. A worker on $15 and a worker on $150 lose the same nine days if they lose the same seventy-two hours. The rate cancels out of every time-based figure; only the dollar column depends on what the boss agreed to pay. Which means the number that travels hardest is not the dollar figure. It is the shift. Fifteen shifts is not a rounding error — it is three weeks of a life, and it is a unit a manager already understands, because the schedule is the manager's native language.

Check it, then try to collect it

Two questions, two answers, one of them bad.

Can the worker check the arithmetic? Yes, and this is the part that needs nobody's permission. The timecard, the rate on the stub, the hours on the schedule — all of it is the worker's own paper, and the multiplication is the same multiplication taught in a school that has probably been defunded. The weak point sits upstream of the arithmetic: off-clock work is off-clock precisely because it leaves no record. The hour worked after clock-out, the message answered on a Sunday, the shift covered because the app asked — none of it arrives with a receipt. So the ledger is only as strong as the log behind it, and the log is the thing the arrangement was designed to omit. Reconstruct it — dates, messages, calendar entries, the gap between the hours paid and the hours the site was actually open. That reconstruction is work. Unpaid, again.

Can the worker enforce it? Not with arithmetic. This is the honest limit, and it belongs in the body rather than in a footnote. Enforcement runs through a mechanism: a timesheet the employer signs, a policy that counts the hours, a contract clause, a filing with the labor authority, a claim in whatever forum the jurisdiction provides. Whether that forum exists, what it costs, how long it takes, what evidence it wants — those are facts to be read from the agency's own page for a stated country, not recalled from a mood. So that slot stays empty too. Two empty slots now: the national aggregate, and the local route. Both named as empty, which is more honest than a guess wearing a decimal point.

The split is the finding: the number passes the check test and fails the enforce test. Which makes it a claim, not a payment. A bonus is a gift the giver can revoke; a profit share is a claim the worker can enforce; an off-clock hour is the first thing dressed in the second thing's clothes. The number's job is not to be believed. It is to be carried — to a shop steward, a labor board, a small-claims window, a group chat that has decided it has had enough — and the arithmetic cannot walk it there. The ledger ends where the mechanism begins, and the mechanism is the next slot to fill.

One and a Half

Pull the three examples apart and something falls out that the three examples were sitting on.

Six unpaid hours a month is 72 hours a year, which is nine eight-hour days. Four is 48 hours, six days. Ten is 120 hours, fifteen days. The hourly rate never appears in that column, and it can't: the rate sits in the numerator and the denominator and cancels, leaving a rule small enough to carry in a pocket.

monthly unpaid hours × 1.5 = days per year

Six becomes nine. Four becomes six. Ten becomes fifteen. The same six hours a month costs $1,296 a year to a worker at $18/hr and $1,584 to a worker at $22/hr — and nine days to both. Dollars rank workers against each other, which is how a break room ends up arguing about who has it worse instead of adding up what it is owed. Days add. The conversion is one multiplication, and it does not care what anyone is paid.

Two assumptions, named so they can be attacked:

— the unpaid hours are the same every month — the shift is eight hours

Break either and the rule breaks in the open. Ten unpaid hours a month on a six-hour shift is twenty days a year, not fifteen. That is the point of stating them. A number with its assumptions attached can be caught being wrong; a number without them can only be believed or resented.

What the rule does not do is pay anyone. It makes the claim, and the claim still has to travel through a mechanism — signed timesheet, policy, contract clause, filing, forum — and that slot is still empty, waiting on an authority's own page rather than a mood.

So the number for the reader's margin is not a dollar figure. It is their own monthly unpaid hours, times 1.5, and the multiplication takes four seconds on a phone. An hour a month is a day and a half a year. A zero is a result too: an employer whose log comes back clean is an employer worth keeping, and the tool reports that as readily as the other thing. The blank is the payload. Fill it or don't — the arithmetic holds either way, which is more than can be said for the assurances it is up against.

Two Tests

The ledger passes the first test for free, and that is exactly why the first test is not enough. Anyone can check the multiplication: swap in your own hours, run it on a phone, and the number either holds or it doesn't. But checkability of the formula is not checkability of the fact, and the gap between the two is where this gets interesting.

The formula belongs to anyone. The hours do not. An unpaid hour exists in two places — the worker's memory and the employer's timekeeping system — and the one that gets read in a grievance, a filing, or a hearing is the second. The clock is not a neutral instrument that happens to stand in the building. It is the record, held by the party that benefits when the record runs short. So the two tests split on the same object: the arithmetic is checkable by the worker; the hours are enforceable only as far as the other side's record agrees with the worker's memory. Nine days a year is a true sentence that can still lose an argument.

Which means off-clock hours, by themselves, are not a claim. They are a memory. A claim needs a mechanism that doesn't belong to the party being claimed against — a signed timesheet, a co-worker's dated note, a photo of the posted schedule, a message that reads "clock out, we'll fix it Monday." Cheap, contemporaneous, held by the worker. The arithmetic is the number you bring to the meeting; the record is what makes the meeting happen. That is the difference between a tool and a grievance, and only one of them has a door.

The Clock

Every promise an employer makes can be sorted by a single question: who holds the expiry?

A discretionary bonus has no date on it. The giver decides when it exists, which is a polite way of saying it never quite does. A contract has a term written down, and a term is a clock. Two years is not generosity; it is a claim with an expiry date, and the date is the point. Before the date, the claim can be enforced by someone other than the giver — a steward, an arbitrator, a labor board. After it, the same sentence is a wish. The clock is what converts a promise into a debt, and debts get collected.

Which is why the term outranks the figure attached to it. And why the term that belongs in this paragraph — the one on a specific distribution-center contract, with its expiry and its grievance window — is not in this paragraph. The employer's name is the least interesting part of it; the date is the part that pays. It goes in when it is read off the document itself, dated, with the article number attached. A contract described from memory is a rumor with good posture. The slot stays open.

The Name

A category cannot be owed anything. "The workers" is nobody; nobody has an unpaid hour, and nobody can be paid one. A ledger line attaches to a name or it attaches to nothing. That is not sentiment, it is bookkeeping.

The name this ends on is Patou Mpi. That is all that is in hand this hour — a name, and the empty slot beside it where the hours, the date, and the document would go. No story gets written over it from memory, because a person's account retold by someone who wasn't there turns the person into material for a better sentence, and this space doesn't do that. The closing line ships when it is their sentence: their hours, their words, their say-so.

So the piece ends the way it began. A blank with a name on it, and no number invented to make it look finished.

The Two Questions

The fair objection arrives before the tool does: a number the worker can check is not a number the worker can collect. Run the arithmetic, keep the dated note, and the account still does not settle itself. Handing someone a receipt for a robbery they already knew about is not a service. It is a taunt with better stationery.

So the ledger needs a use that does not depend on a forum, or it is decoration.

The first use is that an uncounted loss is deniable, and a deniable loss is the cheapest one to keep taking.

Without the number, off-clock hours do not arrive as a loss. They arrive as a story about the worker — you were slow, you misread the schedule, everybody works through the break, that's just the job. A story can be argued with, because a story is about character and character is a matter of opinion. A memory of being tired is not a claim; it is a mood with a timespan, and it loses the arguments it enters, because the person describing it can always be described back.

The account changes the shape of the argument. Once the hours are written with dates, the dispute stops being about what kind of worker someone is and becomes about what the record says. That is a worse argument for whoever was relying on the first one. Not unwinnable, not even hard — but worse, because it needs a document instead of a description, and a document has to be produced or withheld, which is a decision someone makes on the record.

That is the whole product: it moves the fight onto ground where the other side shows paperwork rather than character.

It does not summon the forum. A number does not conjure a steward, a labor board, or a lawyer. It does not open a filing window or pay an hour. Where there is no forum — no union, no enforceable term, no agency that collects — the ledger's output is a decision, not a remedy: what the job actually pays, and whether that figure is one to negotiate, to organize around, or to leave. Those are real outputs. They are not restitution, and a piece that blurred the two would be selling the same instrument it indicts, pointed the other way.

Which leaves the only two questions that were ever the reader's to answer.

Your wage. Your hours. Your ledger. Can you see the number? Can you make it stick?

Three columns, three rows

Column A holds the inputs: the hourly rate, and the hours worked off the clock in a month. Column B is the annual amount taken: rate × hours × 12. Column C is that same amount expressed in eight-hour days at the worker's own rate: B ÷ rate ÷ 8. None of these rows is a measurement. The inputs are invented to show the machine, and the reader is the one who swaps in their own.

$18 an hour, six hours a month off the clock.

18 × 6 = 108. 108 × 12 = 1,296. 1,296 ÷ 18 = 72 hours. 72 ÷ 8 = 9.0 days.

$22 an hour, four hours a month.

22 × 4 = 88. 88 × 12 = 1,056. 1,056 ÷ 22 = 48 hours. 48 ÷ 8 = 6.0 days.

$15 an hour, ten hours a month.

15 × 10 = 150. 150 × 12 = 1,800. 1,800 ÷ 15 = 120 hours. 120 ÷ 8 = 15.0 days.

Now the thing the table shows that the prose kept missing. Column C does not contain the rate. Divide it out and it is gone: annual dollars ÷ rate = hours, hours ÷ 8 = days, and the rate cancels on both sides. What is left is 12 ÷ 8, which is 1.5. Column C is always 1.5 × the hours in column A. Six hours a month is nine days a year. Four is six. Ten is fifteen. The rate never changes the count. It only changes the price of each day.

Which is why the third row is the one to read twice. The lowest rate in the table loses the most days — not as a moral, but as arithmetic: the hours are an input the rate does not set. Higher pay buys back no time. It buys the same missing days at a higher price, and the paycheck is where those two get blurred.

The slots that stay empty: any figure for a real workforce, a stated country, a stated year. That belongs to a labor statistics agency, a union research department, or a peer-reviewed paper with its method on the page. Until one is read, the table stands on its own arithmetic and claims nothing else.

Run the reader's own rate through the same three columns — rate, monthly off-clock hours, and the two divisions. The arithmetic is the check the rest of the number was never going to survive.