Attorney fee calculations in Florida

Quick takeaways

• Florida attorney-fee estimation in DocketMath focuses on the statutory framework in Fla. Stat. § 57.105 (frivolous claims), along with the cap and tier logic the tool uses to translate your inputs into an estimated fee range.
• DocketMath includes lodestar multiplier guardrails: a default multiplier of 1 and a maximum multiplier of 2.5.
• If you’re estimating using the tool’s contingency-fee tier caps, then the claim type and the outcome amount you enter matter a lot—switching claim-type overrides (for example, medical malpractice vs. workers’ compensation) can change the estimated maximum.
• You can run multiple scenarios quickly in DocketMath—such as comparing:

  • contingency-fee vs. lodestar-style assumptions
  • different claim-type overrides included in the tool’s verified settings

Inputs you need

Before you open DocketMath → attorney-fee, gather the facts and numbers you plan to model. The tool can’t compute what you don’t enter—so your output is only as useful as your inputs.

Core inputs (typical for fee modeling)

Check you have:

• Attorney-fee approach you want to simulate

  • contingency-fee style using the tool’s tiered caps, or
  • lodestar-style using multipliers
• Claim type (so the tool can use the correct override structure, where applicable)
• Relevant outcome dollar amount (used to place the estimate into the correct tier thresholds)
• Base lodestar hours and rate (only if you’re modeling a lodestar-style scenario)

Claim-type-specific inputs (use what matches your case)

DocketMath’s verified settings include these contingency-fee override tier structures:

• Medical malpractice contingency-fee override tiers

  • Tier 0: max_percentage 30% and up_to_amount 250,000
  • Tier 1: max_percentage 10% (with the verified schedule structure included in the tool)
• Workers’ compensation contingency-fee override tiers

  • Tier 0: max_percentage 20% and up_to_amount 5,000
  • Tier 1: max_percentage 15% and up_to_amount 10,000
  • Tier 2: max_percentage 10% (with the verified schedule structure included in the tool)

General contingency-fee cap tiers available in the tool

In addition to claim-type overrides, DocketMath also includes a general tiered schedule (verified):

Hard maximum settings (used to bound results)

These verified settings act like guardrails on estimates:

• max_fee_percent: 33.33
• sub_rules.0.max_fee_percent: 30
• lodestar_multiplier_cap.default_multiplier: 1
• lodestar_multiplier_cap.max_multiplier: 2.5

In plain terms: even if the raw tier math would suggest a higher figure, the tool’s verified maximum constraints should prevent the estimate from exceeding those caps.

How the calculation works

Below is a practical mental model for using DocketMath’s attorney-fee calculator in Florida.

Step 1: Pick the framework that matches your modeling goal

In DocketMath, the “shape” of the calculation depends on whether you’re estimating:

• Contingency-fee style

  • The tool uses a tier schedule of percentages (and where provided, up-to amounts) tied to your relevant outcome amount.
  • If the claim type matches a verified override, DocketMath uses that override tier structure rather than the general tier schedule.

• Lodestar-style

  • The tool forms a base lodestar number from your hours and rate inputs.
  • It then applies a multiplier bounded by:

    • default multiplier (1)
    • maximum multiplier (2.5)

Step 2: Apply the tier logic (contingency-fee modeling)

When your estimate is based on the verified contingency-fee tiers:

• Identify the tier in which your relevant outcome amount falls.
• Apply the max_percentage for that tier.
• If the modeled outcome spans tier boundaries, the tool reflects those boundaries according to the verified schedule logic it includes.

Small example (method-only illustration)

If you select the workers’ compensation override and your outcome amount corresponds to an early tier range, then the tool applies:

• Tier 0: 20% up to $5,000
• Tier 1: 15% up to $10,000
• Remaining amounts: then follow the verified Tier 2 (10%) logic

The important takeaway is not the specific arithmetic (your exact inputs determine that), but that claim-type overrides can change the percentage schedule.

Step 3: Enforce the cap guardrails

After DocketMath applies tier or multiplier arithmetic, it bounds results using the verified maximum constraints, including:

• max_fee_percent 33.33
• sub_rules.0.max_fee_percent 30
• lodestar multiplier caps (default 1, max 2.5)

So, outputs tend to be:

• sensitive to tier selection inputs (claim type and outcome amount), and
• limited by verified ceiling settings that prevent runaway results.

Step 4: Treat each run as a scenario

DocketMath outputs are best read as scenario estimates. To understand what drives the number most:

• Change only one input and re-run:

  • Increase the outcome amount → may shift tiers → estimate changes
  • Switch claim type override → tier schedule changes → estimate changes
  • Adjust lodestar multiplier → estimate changes (within verified bounds)

Comparing scenarios helps you spot which assumptions are doing the most work.

Common pitfalls

1) Mistaking an estimate for entitlement

DocketMath produces an estimate based on your modeling inputs and verified cap/tier settings. It does not decide whether you’re legally entitled to fees in your case.

2) Selecting the wrong tier schedule (claim type)

The largest estimate swings typically come from using the wrong schedule:

• Medical malpractice override uses 30% up to 250,000, then 10% (per verified tiers)
• Workers’ compensation override uses 20% up to 5,000, 15% up to 10,000, then 10%

If your claim-type selection doesn’t match the override tier set you intend to model, the output won’t reflect that scenario.

3) Forgetting the percent ceilings

Even if the tier math would produce a higher result, verified maximum settings can cap your estimate:

• 33.33% overall maximum
• 30% sub-rule maximum
• lodestar multiplier bounds (default 1, max 2.5)

4) Not anchoring your model to the right “outcome amount”

If you don’t clearly define the amount the tier schedule should be calculated against, the tool can’t correctly place you into the appropriate tiers.

Use this checklist:

• Do I know the outcome amount the tier schedule should be based on?
• Is that amount consistent across scenarios?
• When I change one variable, did I keep the claim-type selection consistent?

Sources and references

• Fla. Stat. § 57.105 (Frivolous claims) — https://www.flsenate.gov/Laws/Statutes/2023/57.105
• Fla. Const. art. I, § 26 — https://www.flsenate.gov/Laws/Constitution#A1S26

Next steps

1. Open DocketMath’s calculator: /tools/attorney-fee
2. Run at least two scenarios:

   • Scenario A: use the general tier schedule
   • Scenario B: use the appropriate claim-type override (medical malpractice or workers’ compensation), if applicable
3. If you run lodestar-style scenarios:

   • keep hours and rate the same
   • adjust only the multiplier, staying within the tool’s verified max 2.5
4. Compare outputs and note which change moved the estimate most (claim type, outcome amount, tier selection, or multiplier). That tells you what to verify next in your underlying case file.

Related reading

• Attorney fee calculations in United States (Federal) — Full how-to guide with jurisdiction-specific rules
• Why attorney fee calculations results differ in United States (Federal) — Troubleshooting when results differ
• Attorney fee calculations reference snapshot for United States (Federal) — Rule summary with authoritative citations