We checked 18 claims in the waiting-time penalty calculator against its data layer, methodology page, automated tests, and the finalized final-paycheck research. All 18 verified; no unsupported, outdated, or unresolved claims remain.
This report covers what a business owner needs to trust before using the tool: which states are modeled, what formula each state uses, when a demand or good-faith issue can change the penalty, why Massachusetts is handled differently, and what the calculator does not try to model.
The tool is intentionally scoped. It models seven high-impact final-paycheck penalty formulas: California, Nevada, Missouri, Minnesota, Connecticut, Massachusetts, and Oregon. That does not mean other states have no deadlines, penalties, attorney-fee rules, liquidated damages, or wage-claim remedies. For non-modeled states, the reader should use the companion research page's full state-by-state table.
Verification result: the checked tool claims are verified for publication. The main caveat is scope: the calculator estimates upper-bound exposure for the modeled formulas only. It does not replace the research table, attorney-fee analysis, federal FLSA liquidated-damages analysis, or state-specific wage-component review.
1 claim
The calculator models seven high-impact final-paycheck penalty formulas, not every state remedy
The tool states that the seven modeled states are examples of high-impact penalty formulas, not the only states with penalties or remedies.
1 claim
Other states can still have final-paycheck deadlines, penalties, attorney-fee rules, liquidated damages, or civil remedies
Faithful to the finalized research's full state table and penalty discussion. This caveat prevents the calculator from implying "not modeled" means "no exposure."
1 claim
The calculator shows upper-bound exposure, not a guaranteed recovery
Naranjo supports the California good-faith qualifier. The methodology now applies cautious upper-bound language to modeled states with willfulness or good-faith concepts.
1 claim
Massachusetts is the strict-liability exception with no good-faith or pre-suit-payment cure
MGL c.149 §150 sets treble damages; Reuter v. City of Methuen supports the no-cure, strict-liability framing used in the tool.
5 claims
California uses daily wage x days late, capped at 30 days
Data layer encodes per-day-of-daily-wage with 30-day cap. Tests verify $200/day x 20 days = $4,000 penalty and cap behavior at 30 days.
Nevada uses the same daily-wage, 30-day cap shape as California
Data layer encodes per-day-of-daily-wage with 30-day cap and avoidance carve-out. Tests verify the cap.
Connecticut uses a flat 2x total recovery model with a good-faith reduction
Data layer encodes flat-multiplier with total multiplier 2 and strictLiability: false. Tests verify $500 late wages = $1,000 total exposure.
Massachusetts uses a flat 3x total recovery model with strict liability
Data layer encodes flat-multiplier, total multiplier 3, strict liability, and no good-faith defense. Tests verify $500 late wages = $1,500 total exposure and $10,000 late wages = $30,000 total exposure.
Oregon uses hourly rate x 8 hours x days late, capped at 30 days
Data layer encodes per-day-eight-hour-cap and 30-day cap. Tests verify the 8-hour daily cap and 30-day cap.
1 claim
California includes an avoidance/refusal-of-tender carve-out and a narrow good-faith defense
§203 carries the avoidance/refusal language. Naranjo supports the narrow good-faith defense to willfulness.
2 claims
Missouri requires written demand before the penalty layer activates and caps the penalty at 60 days
Data layer encodes written-demand and 60-day cap. Tests verify both no-demand zero penalty and written-demand penalty math.
Minnesota's penalty clock starts after employee demand and caps at 15 days of average daily earnings
Data layer encodes on-demand-24h and 15-day cap. Tests verify 10-day and cap scenarios.
1 claim
The input form changes shape by state because the formulas require different inputs
Per-day states need days and wage rate. Flat-multiplier states need the late wage amount. Oregon needs hourly rate because the daily penalty rate is capped at 8 hours.
1 claim
Missing or non-positive inputs return a zero result instead of an invalid calculation
Tests cover missing or zero inputs. Quality check still recommends a clearer empty-state UI, but the math behavior is verified.
1 claim
Missouri without written demand returns no activated penalty layer while keeping the underlying wages owed
The UI correctly avoids showing a misleading penalty number when the statutory written-demand trigger has not occurred.
1 claim
The default California example shows $200/day and 20 days late, producing $4,000 penalty plus $4,000 underlying wages
Matches the article's California penalty math example.
2 claims
The result card does not include attorney's fees
This is a scope limitation, not a source-law dispute. Attorney fees are case-specific and intentionally excluded from the automated calculation.
The calculator does not model federal FLSA §16(b) liquidated-damages stacking
The tool scopes to state-level penalty math. Federal stacking can matter when unpaid wages include overtime or minimum-wage shortfalls, but modeling it honestly would require additional component-level inputs.
1 claim
The tool assumes the user-entered wage amount is the amount the selected state treats as wages
State-specific wage-component questions are intentionally handled in the article/research layer. The calculator's job is to compute the penalty once the wage amount is known.
16 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.