How to run Settlement Allocator in DocketMath for Ohio

Step-by-step

Run this scenario in DocketMath using the Settlement Allocator calculator.

This guide walks you through running Settlement Allocator in DocketMath for Ohio (US-OH). You’ll set the tool to use Ohio jurisdiction-aware rules for the general statute of limitations (SOL) period, then interpret the output so you can allocate settlement amounts with a consistent timeline.

1) Open the Settlement Allocator tool

Start from the primary call-to-action:

• /tools/settlement-allocator

If you’re navigating from inside DocketMath, find the Settlement Allocator calculator and open it for a new run.

2) Select the jurisdiction: Ohio (US-OH)

In the tool’s jurisdiction selector:

• Choose Ohio — US-OH

This matters because DocketMath uses Ohio’s SOL structure to drive date-based calculations used by Settlement Allocator (for example, how far back an obligation could be considered under the selected default SOL logic).

3) Use the default SOL logic (Ohio general period)

For Ohio, configure Settlement Allocator to use the general/default SOL period associated with Ohio Rev. Code § 2901.13.

Per the jurisdiction notes for this page:

• General SOL Period: 0.5 years
• No claim-type-specific sub-rule was found, so this guide uses the general/default period as the governing time window for the tool run.

Statutory reference used for this setup:

• Ohio Rev. Code § 2901.13 (general SOL period reference)
  Source (authenticated PDF): https://codes.ohio.gov/assets/laws/revised-code/authenticated/29/2901.13/7-16-2015/2901.13-7-16-2015.pdf

4) Enter the timeline inputs required by Settlement Allocator

Settlement Allocator typically needs (at minimum) the timeline inputs you want the allocation to be based on. While the exact field names can vary, you’ll generally see inputs such as:

• Relevant event date (often: incident date, accrual/start date, or another “start of clock” date—use the one your workflow standardizes)
• Evaluation/cutoff date (often: settlement date or the date you measure back from)
• Settlement amount to allocate
• Any additional case-specific modifiers the calculator asks for (for example, categories that affect allocation weights)

Practical tip: use consistent date meaning across runs. If one run uses incident date and another uses filing/accrual date, the elapsed time may cross the SOL window and the output will change.

5) Understand how the Ohio default SOL affects outputs

Because the general SOL period is 0.5 years, DocketMath’s Ohio default SOL logic effectively creates an SOL lookback window that is approximately six months.

Practical implications:

• If your cutoff/settlement date is close to the relevant event date, more time falls within the effective SOL window → the allocation will tend to weight more of the settlement to the “within SOL” portion (depending on how the tool structures its categories/buckets).
• If the event date is farther back than ~6 months, more of the period falls outside the effective SOL window → the “outside SOL” portion may be reduced or handled differently by the allocator’s weighting logic.

A quick sanity-check you can do before finalizing:

• Compute (Cutoff date − Event date) in months
• Compare it to **0.5 years (~6 months)

6) Run the calculation and review the allocation breakdown

After you submit:

• Review the allocation breakdown (categories, time buckets, and/or weighted components—whatever Settlement Allocator displays for your run).
• Confirm the tool shows the correct jurisdiction setting: Ohio (US-OH).
• If the tool includes an “assumptions,” “calculation basis,” or similar panel, verify it explicitly reflects the general/default SOL period of 0.5 years (not a claim-type-specific period).

This step is important because even when inputs are entered correctly, users can sometimes miss the SOL basis actually driving the output.

7) Iterate: adjust dates to see how the output changes

To make sure the SOL-driven window is behaving as expected, run a couple of controlled variations:

• Keep the settlement amount and any other non-date inputs constant
• Change only one date—typically the relevant event date or the cutoff/settlement date
• Observe how the allocation shifts when elapsed time moves above or below ~6 months

If the tool is using the expected SOL window, you should usually see meaningful shifts when the time difference crosses the rough 6‑month boundary.

Checklist before you finalize

Common pitfalls

Here are the most common reasons people get unexpected results when running Settlement Allocator for Ohio:

1. Accidentally switching away from Ohio

   • If the jurisdiction selector is left on another state, the allocator may apply a different SOL framework, producing a different allocation timeline.

2. Assuming claim-type-specific SOL logic is being used

   • This Ohio setup relies on the general/default SOL period because no claim-type-specific sub-rule was found for this configuration.
   • If you try to model a specific claim type, the calculator may not apply that logic unless the tool has an explicit rule/option for it.

3. Using inconsistent meaning for the “event date”

   • One run might use incident date; another might use filing/accrual date.
   • That change can push the elapsed time across the 0.5-year (~6-month) boundary and materially change the allocation.

4. Not confirming which SOL window the tool actually used

   • Look for a summary panel or “calculation basis” section and confirm it references the general/default 0.5 years logic.
   • Don’t rely only on the field selections—you want to confirm the runtime basis.

5. Treating output precision as real-world certainty

   • Settlement Allocator outputs are best treated as model-based allocations tied to the dates and SOL framework you selected.
   • They are a calculation aid, not a determination of legal outcomes.

Pitfall to watch: If your event-to-cutoff time crosses the ~6‑month mark, you should generally expect allocation outputs to change materially. Don’t assume small date differences are “noise.”

Try it

Use this quick workflow to validate your setup:

1. Open /tools/settlement-allocator
2. Select **Ohio (US-OH)
3. Enter a sample run with:

   • Settlement amount: any number (you can replace later)
   • Relevant event date and cutoff date set to produce about 5 months elapsed
4. Run and note the allocation breakdown
5. Run again, changing only the cutoff date so elapsed time becomes about 8 months
6. Compare results

What you should see:

• With ~5 months elapsed (within the 0.5-year default), the allocation should reflect a larger share associated with the “within SOL window.”
• With ~8 months elapsed (outside the 0.5-year default), the allocation should reflect reduced or rebalanced weighting based on the calculator’s SOL-driven logic.

If outputs don’t shift when you cross the rough 6‑month boundary, double-check:

• Ohio jurisdiction selection (US-OH)
• That the tool is actually using the general/default 0.5-year period
• That you entered dates into the correct fields (especially the relevant event date vs. cutoff date)

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado