Why attorney fee calculations results differ in Maine
5 min read
Published April 15, 2026 • By DocketMath Team
The top 5 reasons results differ
Run this scenario in DocketMath using the Attorney Fee calculator.
If you’re using DocketMath’s attorney-fee calculator in Maine (US-ME) and two runs don’t match, the mismatch is usually traceable to one of a handful of input/assumption changes. Maine also has a general/default statute of limitations (SOL) period, so if your fee model embeds a timing assumption, it can ripple into the result.
Under Title 17-A, § 8, Maine’s general/default SOL period is 0.5 years. This is the default/general period for this diagnostic. No claim-type-specific sub-rule was identified for the diagnostic you’re using—so treat 0.5 years as the reference timing anchor unless you have a separate, specific basis to deviate.
Source: https://legislature.maine.gov/statutes/17-a/title17-asec8.html?utm_source=openai
Here are the top 5 causes we see when attorney-fee calculations don’t line up:
Different assumed filing/trigger date
- Many calculators convert a start date into an elapsed-time factor (or into a recoverable window).
- Shift the “trigger” by even 30–90 days, and outputs can move.
Different statute-of-limitations window
- If one workflow effectively applies Maine’s general/default SOL of 0.5 years and another workflow uses a different window (or an unstated alternative), fee eligibility/timing math can diverge.
- For this diagnostic, the key reference point is Maine’s general/default timing anchor in Title 17-A, § 8 (0.5 years).
**Mis-keyed billing inputs (rates, hours, or reductions)
- Small data-entry differences can compound after multipliers, caps, or discounts.
- Example: $275 vs $285/hour or 12.0 vs 12.5 hours.
Different treatment of costs vs fees
- Some runs include costs inside “attorney fees,” while others keep them separate.
- Even if fee-only amounts are identical, totals won’t match if one run adds costs and the other doesn’t (or if “cost inclusion” is toggled).
Fee multipliers or jurisdiction-specific settings
- If DocketMath is using a multiplier, enhancement percentage, or “type of agreement” setting, the same raw billing numbers can generate different totals.
- These settings are commonly the hidden “one different field” that causes mismatches.
Pitfall: Even when two parties agree on “the hours and the rate,” inconsistent handling of timing (SOL window) or components (fees vs costs) is a common reason the totals don’t match.
How to isolate the variable
Use this “single-change” diagnostic approach in DocketMath to find the exact input that creates the divergence.
- Freeze the jurisdiction and tool settings so both runs use the same rule set.
- Compare one input at a time (dates, rates, amounts) and re-run after each change.
- Review the breakdown to see which segment or assumption drives the difference.
Step-by-step checklist
What to verify against Maine’s default timing
Because this diagnostic uses Maine’s general/default SOL period of 0.5 years under Title 17-A, § 8, check whether one run is effectively using:
- 0.5 years from your selected start/trigger date, or
- a different length driven by a different assumption.
Quick sanity method:
- If Run A and Run B differ only in the “trigger date,” compare whether the calculator recalculates elapsed time-based eligibility using a 0.5-year window.
- If the output jump suggests a different window, confirm the run is not using an alternative SOL setting.
| Variable you changed | Expected effect pattern | What mismatch usually means |
|---|---|---|
| Trigger/filing date | Output changes with elapsed time | One run recalculated a recoverable window differently |
| SOL window setting | Step-change in eligibility/timing-based portion | One run used a different SOL anchor than 17-A, § 8 (0.5 years) |
| Hours or rate | Nearly linear change in fee-only subtotal | A number was entered differently (not a “math interpretation” issue) |
| Costs included | Fee total changes (or fee vs total split changes) | Components were combined differently |
| Multiplier | Non-linear change | Enhancement/cap setting differs between runs |
Gentle reminder: this is a calculator diagnostic workflow, not legal advice. If your situation depends on a specific claim type or a disputed timeline, you’ll want your inputs/assumptions to match the factual record you’re modeling.
Next steps
Once you identify the variable that flips the result:
- Pinpoint the exact DocketMath field(s) that differ between Run A and Run B (e.g., “trigger date,” “include costs,” or “SOL window”).
- Re-run a single standardized scenario:
- Fix trigger date
- Fix hours and hourly rates
- Fix multiplier/enhancement and cost-inclusion settings
- Ensure SOL logic is aligned to Maine’s general/default 0.5-year period under Title 17-A, § 8
- Create a reproducible inputs snapshot for comparisons (a short “inputs manifest” of key numbers and selected settings), so the same scenario can be rerun later.
Related reading
- Worked example: attorney fee calculations in Vermont — Worked example with real statute citations