Worked example: Damages Allocation in Massachusetts
6 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
Run this scenario in DocketMath using the Damages Allocation calculator.
This worked example walks through damages allocation in Massachusetts using DocketMath (tool: /tools/damages-allocation). It’s a practical walkthrough of how to structure inputs and how the output shifts when key assumptions change—especially around Massachusetts’ general statute of limitations (SOL).
Jurisdiction rules used (Massachusetts, US-MA):
- General SOL period: 6 years
- General statute citation: Mass. Gen. Laws ch. 277, § 63
- No claim-type-specific sub-rule was found: For this example, the calculator uses the general/default SOL period of 6 years (not a shorter/longer window for a specific claim type).
Note: This walkthrough is about modeling and allocation mechanics, not advising you on whether a particular Massachusetts claim is timely. SOL analysis can turn on detailed facts and issue-specific doctrines.
Scenario (used for the calculation)
Assume a plaintiff is seeking damages for a claim covering a continuous course of conduct. For simplicity, the “damages allocation” model assumes you have:
- a total damages amount (pre-allocation),
- a damages accrual window (when damages began and ended for modeling purposes),
- and an evaluation date (the date the demand/filing is treated as relevant for SOL cutoffs in the model).
Inputs you’d enter in DocketMath /tools/damages-allocation
Use these example values:
| Input (calculator field) | Example value | What it represents |
|---|---|---|
| Jurisdiction | US-MA | Massachusetts rules |
| Total claimed damages | $240,000 | Amount before SOL/time slicing |
| Accrual start date | 2018-01-15 | First date damages are treated as beginning to accrue (modeled) |
| Accrual end date | 2023-12-31 | Last date damages are treated as accruing (modeled) |
| Case evaluation date | 2024-06-01 | Date used to “look back” for SOL cutoffs in the model |
| SOL period (years) | 6 | Default/general period: Mass. Gen. Laws ch. 277, § 63 |
| Allocation method | SOL-based time window | Allocate damages into “within SOL” vs “outside SOL” buckets |
Checkbox-style checklist for clean inputs:
Example run
Now run the calculation using the inputs above.
Run the Damages Allocation 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: Apply Massachusetts’ general SOL lookback
Massachusetts’ general SOL period is 6 years under Mass. Gen. Laws ch. 277, § 63.
With an evaluation date of 2024-06-01, the SOL lookback window begins:
- Evaluation date: 2024-06-01
- Lookback: 6 years
- Window start (modeled): 2018-06-01
So, in this example:
- Damages accrual after 2018-06-01 are treated as potentially within SOL (subject to facts/doctrines not modeled here).
- Damages accrual before 2018-06-01 are treated as outside SOL for allocation purposes.
Warning: A SOL cutoff can be affected by specific accrual rules, tolling, and discovery concepts. DocketMath’s time slicing is a workbench model using the provided dates, not a substitute for jurisdiction-specific litigation analysis.
Step 2: Compare the accrual window to the SOL window
Accrual window used for modeling:
- Start: 2018-01-15
- End: 2023-12-31
SOL window used for allocation:
- Start: 2018-06-01
- End: 2024-06-01 (but damages only run through 2023-12-31 in this scenario)
Therefore:
- Portion outside SOL: from 2018-01-15 to 2018-05-31
- Portion within SOL: from 2018-06-01 to 2023-12-31
Step 3: Allocate the total damages by the modeled time share
Assume the tool allocates proportionally by time within the accrual window (a common simplifying method for allocation examples). Under that approach:
- Outside-SOL segment length ≈ 137 days (Jan 15–May 31, modeled)
- Total accrual window length ≈ 2,211 days (2018-01-15 through 2023-12-31, modeled)
- Within-SOL share ≈ (2,211 - 137) / 2,211 ≈ 93.8%
- Outside-SOL share ≈ 6.2%
Apply shares to $240,000:
- Within-SOL allocated damages: $240,000 × 93.8% ≈ $225,120
- Outside-SOL allocated damages: $240,000 × 6.2% ≈ $14,880
Example output (what you’d expect to see from DocketMath)
Depending on the calculator’s exact day-count convention, your figures may differ by a small rounding amount, but the structure should be consistent:
| Bucket | Modeled time basis | Allocated amount (approx.) |
|---|---|---|
| Within SOL | 2018-06-01 → 2023-12-31 | $225,120 |
| Outside SOL | 2018-01-15 → 2018-05-31 | $14,880 |
| Total claimed | full accrual window | $240,000 |
What the output is telling you (allocation-level interpretation)
If the model slices your damages into SOL-eligible and SOL-barred periods, you can use that split to:
- frame settlement ranges,
- summarize “time-bar exposure” quantitatively,
- and run “what-if” scenarios by shifting dates.
Sensitivity check
A reliable damages allocation model should show how sensitive the result is to date assumptions. Here are three targeted sensitivity checks you can run quickly in DocketMath /tools/damages-allocation.
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.
Sensitivity 1: Move the evaluation date 90 days later
Change only:
- Case evaluation date: from 2024-06-01 → 2024-09-01
- SOL window start shifts from 2018-06-01 → 2018-09-01
Impact you should expect: a larger “outside SOL” portion shrinks into SOL, because the lookback window starts later.
- Outside-SOL share decreases
- Within-SOL allocated damages increase
Sensitivity 2: Move accrual start date earlier by 60 days
Change only:
- Accrual start date: from 2018-01-15 → 2017-11-16
Impact you should expect: more time falls before the SOL start (2018-06-01), increasing the outside-SOL slice.
- Outside-SOL allocated damages increase
- Within-SOL allocated damages decrease
Sensitivity 3: Shorten the accrual end date by 6 months
Change only:
- Accrual end date: from 2023-12-31 → 2023-06-30
Impact you should expect: the within-SOL time window becomes smaller in absolute terms, but since the SOL start doesn’t move, the proportional effect depends on how much of the remaining time is within SOL.
- Within-SOL allocated damages decrease in dollars
- Outside-SOL allocated damages may become relatively smaller or similar proportionally
Use this checklist to keep comparisons consistent:
Pitfall: If you accidentally switch from “general/default SOL” to a claim-type-specific rule (even implicitly), the 6-year baseline could change and the allocation percentages will no longer be comparable across runs.