We checked 12 claims in this quick read against the refreshed retro-pay research, the companion article, federal wage-hour regulations, and state wage-payment sources. All 12 verified; no unsupported, outdated, or unresolved claims remain.
This quick read intentionally does less than the article. It teaches one idea: a rate-change correction is not always just the missing hourly difference because overtime can require a second calculation. The quick read keeps liquidated-damages and Massachusetts-law statements scoped while preserving the practical urgency.
Ship verdict: the quick read can ship under this fact-check.
1 claim
Retro pay is not always just the missing hourly difference
The statement is scoped with "not always" because straight-time-only corrections can be exactly the rate difference.
3 claims
If the affected period had overtime, the employer may owe a second calculation
§778.303 supports the additional half-time recompute for overtime hours in the retroactive period.
If an employee worked overtime during the affected period, the old overtime rate was wrong too
A retroactive increase changes the regular rate for the period, which changes the overtime premium for overtime hours in that period.
Missed overtime recompute creates unpaid overtime, not just an ordinary payroll adjustment
The quick read avoids saying the amount always doubles. It correctly says the omitted half-time premium is unpaid overtime.
6 claims
Paying the missing rate difference is enough only when the affected period had no overtime
The extra half-time layer applies to overtime hours. If the correction period had only straight-time hours, the rate difference covers the wage correction.
Employers should pull affected workweeks, not just total hours
Overtime is calculated by workweek, so retro-pay overtime recomputation should identify the affected workweeks.
Employers should keep the calculation, payment date, and source records together
Federal recordkeeping rules require payroll and supplementary wage computation records; the quick read translates that into a practical file-keeping instruction.
Corrections involving separated employees, Massachusetts, California, bonuses, commissions, or multiple employees can pick up state penalties or a bigger overtime calculation
The listed triggers correspond to verified layers in the research: final-pay timing, California §203/§226, Massachusetts §150/Reuter, bonus allocation, and multi-employee exposure.
Correcting the upstream rate, effective date, bonus setup, or time rule before the next payroll run is better than only issuing a check
The claim is operational, not statutory. It follows from preventing the same verified payroll error from recurring.
The cheapest correction is usually the one caught quickly, paid fully, and documented clearly
The quick read uses "usually" because some state penalty frameworks remain strict. Speed, full payment, and documentation still improve the employer's posture and reduce preventable exposure.
2 claims
A $20 to $22 raise over 180 hours with 20 overtime hours produces a $360 straight-time correction, $20 overtime correction, and $380 total
$2 x 180 = $360. 0.5 x $2 x 20 = $20. Total = $380.
Paying only $360 in that example leaves the employee $20 short
The unpaid amount is the omitted overtime half-time recompute.
10 unique sources cited across the report — click to audit any claim directly against its evidence.
Every claim above links to the source we used. Open any source to compare the wording here with the underlying rule, guidance, court opinion, or product behavior.
If a source has changed or a claim looks wrong, tell us. We would rather correct the page than leave a stale answer online. See how we fact-check.
Clockspot helps small businesses track employee time and keep payroll-ready records. Used in all 50 states since 2007, we focus on getting time and pay right — including the wage-and-hour rules that shape both.
We build Clockspot for the same reason we publish these reports: time records should be understandable, reviewable, and tied to the rules that affect payroll. See how Clockspot works.