Worked example: Wage Backpay in Florida

Example inputs

Below is a worked example of wage backpay calculations in Florida using DocketMath. This example is written to show how the jurisdiction-aware statute settings change the math—not to provide legal advice.

Here is a simple illustration for Florida. These values are for demonstration only and should be replaced with your actual inputs.

• Principal or amount: $100,000
• Rate or cap: 10%
• Start date: 2025-01-15
• End/as-of date: 2025-09-30

Scenario

• Employment start date: January 10, 2021
• Employment end date: September 20, 2023
• Backpay period sought: from the earliest allowable date up to the end date
• Pay frequency: biweekly (assumed 26 pay periods per year in typical payroll practice)
• Gross wages per pay period: $1,600
• Pay raises during the lookback: none in this example
• Liquidated damages / interest: excluded (DocketMath here focuses on wage backpay principal)

Florida lookback period used by DocketMath

DocketMath applies a general/default statute of limitations (SOL) window for the relevant claim type, because no claim-type-specific sub-rule was found.

• General SOL period: 4 years
• Florida statute setting: Florida Statute § 775.15(2)(d) (general period referenced by this calculator configuration)

Source: https://www.flsenate.gov/Laws/Statutes/2004/775.15?utm_source=openai

Clear default note: This example uses the general 4-year default because the “claim-type-specific sub-rule” flag is not present. If your situation involves a different claim category, the allowable lookback window could change.

What DocketMath needs from you

In DocketMath’s /tools/wage-backpay workflow, you typically supply inputs like:

• The clock start date (or another event date in your workflow that starts the SOL clock)
• The end date (or last date wages were unpaid)
• Your wage rate (fixed or time-sliced if wages changed)
• Pay cadence (weekly/biweekly/monthly)

For this worked example, the key decision is how far back the calculator lets you recover under the Florida 4-year default window.

Example run

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 SOL start boundary (Florida default: 4 years)

To illustrate the SOL-aware behavior, assume the relevant “clock start” date is the employment end date in this simplified example:

• Clock start (effective): September 20, 2023
• General SOL period: 4 years
• Earliest recoverable date: September 20, 2019

This means DocketMath would cap any recovery to the window:

• Backpay period allowed by SOL: September 20, 2019 → September 20, 2023

Because the person in our scenario only worked from January 10, 2021 onward, the actual payable period within the SOL becomes:

• Actual payable period used in the math: January 10, 2021 → September 20, 2023

Step 2: Convert dates into pay periods

Now convert the included dates into pay periods using the selected cadence.

• Cadence: biweekly
• Gross wages per pay period: $1,600

To keep the math transparent (and consistent with a worked-example approach), we’ll use approximate biweekly counting that aligns with a typical payroll cadence:

• 2021 (Jan 10 onward): ~24 pay periods
• 2022: 26 pay periods
• 2023 (Jan 1 through Sep 20): ~18 pay periods

Total estimated pay periods:

• 24 + 26 + 18 = 68 pay periods

Step 3: Multiply pay periods by gross wages

With the payable period determined and the pay periods counted:

• Backpay (principal) = 68 pay periods × $1,600
• Backpay = $108,800

Step 4: Show how the Florida SOL rule affects the result

If someone attempted to include wages unpaid earlier than September 20, 2019, DocketMath would exclude those amounts due to the 4-year default SOL window set using Florida Statute § 775.15(2)(d).

Even though employment began later (January 10, 2021), the SOL rule still matters because it establishes an “earliest allowable date” boundary for the calculator’s lookback.

Result (principal wage backpay)

• Wage backpay (principal only): $108,800

For running this exact scenario in DocketMath, start at: ** /tools/wage-backpay

Sensitivity check

You can learn a lot by changing one input while keeping everything else constant. Below are three sensitivity checks showing how the total changes.

Sensitivity 1: Change gross wages per pay period

Keep the dates (and therefore the 68 pay periods) the same, and change the wage per pay period.

Takeaway: Backpay moves linearly with wages per pay period. A $150 increase adds:

• $150 × 68 = $10,200

Sensitivity 2: Change the end date (affects pay-period count)

Assume the last unpaid wage date shifts forward by about two weeks.

• New end date: October 4, 2023
• Approximate change: +1 biweekly pay period

Then:

• Baseline: 68 pay periods → $108,800
• New: 69 pay periods → $110,400

Takeaway: Under biweekly assumptions, each additional complete pay period adds about:

• $1,600 in this scenario.

Sensitivity 3: Move the clock start date earlier

In real disputes, the clock start might be tied to an event date earlier than the employment end date. If the clock start moves earlier but the employment timeline is still fully inside the SOL window, the result may not change.

Example shift:

• Clock start changes from September 20, 2023 to June 15, 2023
• With a 4-year SOL, the earliest allowable date becomes June 15, 2019
• In our scenario, employment still runs from January 10, 2021 to September 20, 2023

Because the payable period still lies entirely within the allowable lookback, the counted portion is unchanged.

Takeaway: SOL changes matter most when wage loss begins before the 4-year cutoff. If the employment (and wage loss) is already within the cutoff, moving the clock start earlier may not affect the total.

Confirming the jurisdiction rule is the default

In this Florida setup, DocketMath uses:

• General SOL period: 4 years
• Statutory basis in this configuration: Florida Statute § 775.15(2)(d)
• No claim-type-specific sub-rule found: therefore the default window applies

That “default applies” behavior is why this worked example produces a single consistent lookback boundary.

Related reading

• Wage & Backpay Calculator Guide for Alabama
• Wage & Backpay Calculator Guide for Arizona
• Wage & Backpay Calculator Guide for Colorado