Worked example: Wage Backpay in Kentucky
5 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
This worked example shows how DocketMath can calculate wage backpay in Kentucky (US-KY) using jurisdiction-aware rules. It’s a practical walkthrough of inputs, what DocketMath outputs, and how changing one assumption affects the result.
Because Kentucky’s wage-backpay timing is tied (in this scenario) to Kentucky’s general statute of limitations, there’s no claim-type-specific sub-rule applied. DocketMath uses the default period: 5 years under KRS 500.020.
Note: This example uses the general/default SOL only. If your situation involves a different limitation rule triggered by the specific legal theory or claim type, the time window could change.
Scenario (assumptions for the example)
Assume you’re modeling a wage backpay claim for an employee whose wages were underpaid. The employer’s conduct occurred repeatedly over time.
We’ll use these numbers:
- Jurisdiction: Kentucky (US-KY)
- Statute of limitations period used by DocketMath: 5 years (per KRS 500.020)
- Date backpay period begins (alleged underpayment starts): March 1, 2020
- Date backpay period ends (last day of underpayment): August 31, 2021
- Demand / filing date (used to “look back”): September 15, 2024
- Weekly hours: 40 hours/week
- Underpayment rate (per hour): $6.00/hour
- Total workweeks impacted during the period: computed by the date range (not manually guessed)
Checkbox: What DocketMath uses
- Kentucky default SOL window: 5 years from the demand/filing date (per KRS 500.020)
- Only the months/weeks that fall inside the SOL window count for backpay
- Backpay is calculated as: (hours in included time window) × (underpayment per hour)
Example run
Now let’s run the math exactly the way DocketMath would structure it: first determine the SOL “lookback” window, then compute wages owed for the overlap between (a) the alleged backpay period and (b) the SOL window.
1) Determine the SOL lookback window (Kentucky default)
- Demand/filer date: September 15, 2024
- General SOL period: 5 years (Kentucky KRS 500.020)
- Lookback start date: September 15, 2019
So DocketMath will only include underpayment occurring on or after September 15, 2019.
2) Identify the overlap with the alleged underpayment period
Alleged underpayment runs:
- Start: March 1, 2020
- End: August 31, 2021
Because March 1, 2020 is after September 15, 2019, the entire alleged period (March 1, 2020 through August 31, 2021) falls inside the 5-year window.
In other words, for this scenario, there is no time-based trimming.
3) Compute included work time
- Weekly hours: 40
- Underpayment rate: $6.00/hour
- Workweeks included: DocketMath determines the number of weeks between the start and end dates and multiplies by weekly hours.
For a date-range example like this, you’ll typically see DocketMath calculate based on calendar weeks covered by the period. Using the period March 1, 2020 → August 31, 2021, the covered time is approximately 87 weeks (the tool handles the exact week mapping).
4) Compute total backpay
Backpay formula used by the wage-backpay calculator:
- Total backpay = (weeks included) × (weekly hours) × (underpayment per hour)
- Total backpay = 87 × 40 × $6.00
- Total backpay = 87 × $240
- Total backpay = $20,880
Example output (what you’d expect DocketMath to show)
| Item | Value |
|---|---|
| Jurisdiction | Kentucky (US-KY) |
| SOL rule applied | General/default 5 years under KRS 500.020 |
| Lookback start | 09/15/2019 |
| Alleged underpayment start | 03/01/2020 |
| Alleged underpayment end | 08/31/2021 |
| Weeks included | ~87 |
| Hourly underpayment | $6.00/hour |
| Total wage backpay (included time) | $20,880 |
Sensitivity check
The headline result—$20,880—depends heavily on the time window included under KRS 500.020 and on the hourly underpayment rate. Below are two sensitivity checks showing how DocketMath output changes when inputs shift.
Pitfall: Many backpay disputes turn on how much of the period is legally recoverable, not on whether the math for hours and rates is straightforward.
Sensitivity 1: Move the filing/demand date later by 2 years
Change only:
- Demand/filer date: September 15, 2026 (instead of 2024)
New lookback start:
- 09/15/2021 (5 years before 09/15/2026)
But your alleged underpayment ends 08/31/2021, which is just before 09/15/2021.
Result: the overlap becomes minimal or potentially zero depending on exact week mapping in DocketMath.
Expected change in backpay:
- If the overlap is 0 weeks, DocketMath returns $0.
- If there’s a small overlap (e.g., a partial week logic), the number may be small.
This is a clear illustration of why SOL (KRS 500.020) matters in wage backpay computations.
Sensitivity 2: Keep dates the same, increase underpayment per hour
Return to the original dates (demand: 09/15/2024, period: 03/01/2020–08/31/2021). Change only:
- Underpayment rate: from $6.00/hour to $7.50/hour
Using the same included weeks (~87) and the same weekly hours (40):
- Total backpay = 87 × 40 × $7.50
- Total backpay = 87 × $300
- Total backpay = $26,100
So, moving from $6.00/hour to $7.50/hour increases backpay by:
- $26,100 − $20,880 = $5,220
Sensitivity summary (what moves the needle)
| Change | What it affects | Likely impact on backpay |
|---|---|---|
| Demand date later | SOL lookback overlap (KRS 500.020) | Can drop to $0 if the entire period falls outside the 5-year window |
| Underpayment rate higher | Dollar value per hour | Linear increase: higher $/hour increases total backpay proportionally |
| Weekly hours higher | Total hours in the included window | Linear increase: more hours means more owed wages |