Worked example: Wage Backpay in Tennessee
6 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
Run this scenario in DocketMath using the Wage Backpay calculator.
Below is a worked example of wage backpay calculation in Tennessee (US‑TN) using DocketMath with the general/default backpay period.
Because the jurisdiction data provided identifies no claim-type-specific sub-rule, this example uses the general period only:
- General backpay/general “SOL period” used here: 1 year
- Statute cited: Tennessee Code Annotated § 40-35-111(e)(2)
https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/
What you’ll enter in DocketMath (wage-backpay)
Use these inputs to mirror how the calculator works conceptually. (Exact field names can vary slightly by UI, but the values below are what matter.)
| Input | Example value | Purpose |
|---|---|---|
| Gross hourly rate | $22.00 | Starting pay rate used to compute wages lost |
| Scheduled hours per week | 30 | Converts an hourly rate into weekly backpay |
| Number of weeks paid period covers | (derived) | Limited to the lookback window (here, 1 year) |
| Lookback start anchor | Notice/report/trigger date (example) | Sets the end of the backpay window |
| Lookback window | 1 year (default/general) | Enforces the Tennessee default period |
| Overtime / differentials | None (for simplicity) | Excludes compounding wage complexity |
| Pay frequency | Weekly (for presentation) | Helps interpret the output |
Practical tip: If your wage structure is irregular (overtime varies, commissions exist, hours change), consider running multiple scenarios or using more detailed wage inputs if the tool supports them.
Dates used in this example
- Trigger/anchor date: June 15, 2025
- Backpay lookback window: 1 year back from June 15, 2025
→ covers June 15, 2024 through June 15, 2025 (inclusive/rounding rules are handled by the calculator)
Example wage assumptions
- Hourly rate: $22.00
- Hours per week: 30
- No overtime: $0 additional
- No special wage adjustments: keep it clean for the demonstration
Note: This is a mechanical example of wage-backpay math. Real-world wage recovery can depend on compensation structure (overtime, commissions, fluctuating hours, mitigation/earnings, and fringe benefits). DocketMath focuses on the backpay window and wage arithmetic.
Example run
Here’s what the example calculation looks like when you use DocketMath’s wage-backpay tool with Tennessee (US‑TN) settings and the general/default 1-year lookback.
Run the Wage Backpay calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.
Step 1: Determine the capped period (Tennessee default)
Using the provided jurisdiction rule:
- Default/general period: 1 year
- Cited authority: Tennessee Code Annotated § 40-35-111(e)(2)
https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/
With the anchor date of June 15, 2025, the lookback window begins June 15, 2024.
So the calculator limits the compensable period to up to 52 weeks (accounting for rounding/day-count conventions).
Step 2: Compute weekly wages
- Weekly scheduled wages = hourly rate × hours/week
- $22.00 × 30 = $660.00 per week
Step 3: Multiply by the number of weeks in the backpay window
If the calculator uses a 52-week window for the 1-year period:
- Backpay = $660.00 × 52 = $34,320.00
Step 4: Apply wage-backpay output formatting
A DocketMath wage-backpay run typically presents:
- Total gross backpay
- Period covered (start/end or number of weeks)
- Wage-rate basis (hourly × hours/week)
For this example run, the primary output is:
- Estimated wage backpay (Tennessee default 1-year window): $34,320.00
To try it directly, use the tool here: /tools/wage-backpay
Warning (non-legal advice): Backpay is not always “just gross wages for the whole year.” Many claims involve adjustments such as mitigation (earnings during the period), offsets, or fringe-benefit treatment. This example intentionally excludes those factors to show how the jurisdiction-aware window affects the period counted.
Sensitivity check
Small changes in wage inputs or the dates can shift the result substantially. The purpose of this section is to show how output moves when you adjust assumptions while keeping Tennessee’s default 1-year lookback in place.
To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.
A. Change the hourly rate
Keep hours/week at 30 and keep the anchor date June 15, 2025.
| Hourly rate | Weekly wages | Backpay over ~52 weeks |
|---|---|---|
| $20.00 | $600.00 | $31,200.00 |
| $22.00 (base) | $660.00 | $34,320.00 |
| $25.00 | $750.00 | $39,000.00 |
Takeaway: Every $1.00/hour increase changes weekly wages by $30, and over ~52 weeks that’s about $1,560 in backpay (before any offsets).
B. Change weekly hours
Keep hourly rate at $22.00 and the anchor date unchanged.
| Hours/week | Weekly wages | Backpay over ~52 weeks |
|---|---|---|
| 20 | $440.00 | $22,880.00 |
| 30 (base) | $660.00 | $34,320.00 |
| 40 | $880.00 | $45,760.00 |
Takeaway: Hours/week drives the result linearly. A 10-hour/week change is $220/week, or roughly $11,440 over ~52 weeks.
C. Move the anchor/trigger date (window behavior)
Because the default window is a fixed 1-year lookback, shifting the anchor date typically doesn’t change the number of covered weeks much—it changes which wages apply if your wage rate or schedule changed over time.
Two scenarios to think through:
- Scenario 1: Anchor moved within a period where pay stayed constant
→ result stays close to the base run - Scenario 2: Anchor moved to a time where hours or rate changed
→ result shifts because your wage assumptions for the period likely change
Pitfall: The “1-year” rule sets the time window, but wage amounts still depend on what the employee would have earned during that window. If pay rates increased midstream, a single flat hourly rate can misstate totals.
D. Confirm you are using the correct Tennessee rule (default/general)
This matters for jurisdiction-aware calculations:
- Your jurisdiction data indicates no claim-type-specific sub-rule was found.
- That means DocketMath should use the general/default period: 1 year, tied here to Tennessee Code Annotated § 40-35-111(e)(2):
https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/
If your fact pattern later maps to a more specific rule, the lookback window could differ—changing the computed total.