How to run Settlement Allocator in DocketMath for Ohio

Step-by-step

You can run Settlement Allocator in DocketMath for Ohio (US-OH) by entering your settlement’s allocation inputs and using Ohio’s jurisdiction-aware rules framework under Ohio Civ. R. 23. This guide is designed to be practical and actionable—and it explains how the outputs change when you adjust key fields.

1) Open the tool and select Ohio

1. Go to the primary CTA: /tools/settlement-allocator
2. Confirm you’re using:

   • Calculator: settlement-allocator
   • Jurisdiction: US-OH (Ohio)

If DocketMath includes a jurisdiction selector, choose Ohio before entering your numbers. This ensures the allocator applies Ohio Civ. R. 23–based configuration for the run.

2) Gather the inputs DocketMath requires

Before you type anything into the allocator, pull the “allocation” details from your settlement materials—especially the portions commonly labeled as an allocation formula, plan of distribution, schedule of payments, or distribution methodology.

In Ohio class-action settings, Ohio Civ. R. 23 governs class-action procedure, and it provides the procedural framework that commonly informs distribution settings in tools like DocketMath.

In DocketMath, the Settlement Allocator typically needs inputs along these lines:

• Settlement total / pool to allocate (gross or net, depending on what your plan states)
• Distribution basis (what drives the allocation: weights, units, claim value, etc.)
• Per-line item quantities (for each claimant/member/entity row)
• Eligibility and adjustments (for example: caps, exclusions, offsets/reserves, if your plan uses them)
• Any timing/period fields the tool requests (when those affect the distribution logic)

Practical tip: If you aren’t sure which field corresponds to your plan, use the settlement’s own wording as your mapping guide. DocketMath is performing a calculation based on your inputs—it should not be expected to rewrite the settlement terms.

3) Enter each party/member/claim line item

Add the rows (line items) for each person/entity that will receive an allocation.

For each row:

• Enter the identifier required by the tool (name/ID)
• Enter the measurable allocation basis your plan uses (e.g., weight, units, or claim value)
• Enter any row-level adjustments tied to your plan (e.g., eligibility constraints, caps/floors, or other criteria)

After you populate the table, DocketMath will normalize and allocate from the pool using the Ohio configuration you selected.

4) Check Ohio jurisdiction-aware settings (Rule 23 context)

Ohio’s Civ. R. 23 addresses class actions and the procedural structure for class relief. In DocketMath, the “jurisdiction-aware” portion primarily affects how the allocator applies its configured logic for Ohio (US-OH)—including the default/general period behavior when no claim-type-specific rule is available.

Because the tool setup for Ohio is based on the general/default period, you should:

• Expect the allocator to apply that baseline timing approach across supported categories
• Reflect category-specific timing or category differences (if your settlement plan has them) through the inputs you provide (weights, eligible periods, or other differentiators), rather than assuming the tool can infer claim-category–specific timing automatically

If DocketMath provides a summary panel for the run, use it to confirm which defaults were activated for US-OH.

5) Run the allocation

Click Calculate (or the equivalent action button).

Then review:

• Whether total allocated matches the settlement pool per the tool’s reconciliation rules
• The per-line allocation amounts
• Any rounding behavior (allocators often distribute remainder pennies/cents in a deterministic way to keep totals equal)

If the results aren’t what you expect, adjust the allocation basis inputs (weights/units/claim value, eligibility, caps, reserves) rather than forcing totals by changing the pool—unless your settlement plan explicitly defines a different pool to allocate.

6) Validate outputs against your settlement plan

Before exporting or finalizing, validate that the run matches your settlement’s intended allocation mechanics. Use this checklist:

• Settlement pool used equals the “gross settlement amount,” or the “net settlement pool,” if your plan already deducts fees/costs
• Eligibility/exclusions are implemented correctly (included rows vs. excluded rows)
• Allocation weights/units match the plan’s measurement method
• Any caps, offsets, minimums, or reserves are entered in the correct row-level fields
• Totals reconcile to the penny (or within the tool’s stated rounding rule)
• The allocator is using the default/general period logic for Ohio (not claim-type-specific timing), consistent with the availability noted above

7) Export or save results

After the allocator runs, export or save your allocation results (table/ledger). Many case workflows require:

• A distribution summary for the file
• A per-member allocation ledger for review
• A record of the inputs used so results are reproducible later

Keep the exported output alongside your settlement documentation so reviewers can trace how each figure was produced.

Common pitfalls

Even when settlement allocation math seems straightforward, Ohio-focused distribution workflows often break due to mismatched inputs, pool confusion, or incorrect assumptions about timing/category logic. Watch for these issues:

• Expecting claim-type-specific timing when the tool only applies the general/default period

  • Since a claim-type-specific sub-rule was not found, DocketMath applies general/default period logic for Ohio.
  • If your settlement plan differentiates timing by category, capture those differences via the inputs you enter (such as eligible periods or category-specific weight basis), not by expecting the tool to infer claim-type-specific timing automatically.

• Incorrect allocation base

  • Common input mistakes include:

    • Entering percentages where the tool expects weights
    • Entering a net-after-fees figure into a field the tool treats as gross (or vice versa)
    • Entering units like days into a field intended for a dollar or damages basis (or the opposite)

• Forgetting deductions/reserves

  • If your plan includes a reserve (e.g., administrative costs, holdbacks, or unclaimed-fund rules), ensure you use the allocator’s deduction/reserve fields as intended.
  • Otherwise, the totals may not reconcile to your plan’s intended net amount.

• Eligibility represented inconsistently

  • If certain members are excluded, avoid adding them with zero values unless your plan/tool instructions explicitly allow that approach.
  • In many workflows, the cleaner and safer method is to exclude rows entirely unless the allocator requires placeholders.

• Rounding surprises

  • Allocators commonly preserve total equality by using deterministic rounding rules.
  • It’s normal to see small per-row differences (like a few cents) as long as totals reconcile exactly to the configured pool.

Try it

Ready to run a quick Ohio allocation test in DocketMath? Follow this minimal workflow:

1. Select US-OH (Ohio).
2. Enter a simplified dataset:

   • 1–2 settlement pool values (you can start with one)
   • 3–5 line items with distinct weights/units (so allocation differences are visible)
3. Click Calculate.
4. Verify:

   • The sum of allocations equals the settlement pool per the tool’s rules
   • Higher-weight rows receive more
   • Any rounding differences are small and consistent with the tool’s behavior

To stress-test your configuration:

• Increase one line item’s weight by 10% and rerun; confirm that the allocation shifts in the expected direction.
• Adjust a reserve/deduction value (if available) and rerun; confirm the total allocated changes accordingly.
• If the tool exposes period-related fields, toggle them to ensure the allocator updates using the default/general period logic for Ohio (not claim-type-specific timing).

When the test behavior matches your expectations, replace the test inputs with your real settlement inputs and export the final allocation ledger.

Related reading

• How to calculate Settlement Allocator in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Settlement Allocator in Philippines — Worked example with real statute citations
• Inputs you need for Settlement Allocator in Philippines — Input checklist with sourcing guidance

Ohio rule reference used in this guide: Ohio Civ. R. 23 (as reflected in the Ohio Supreme Court’s Civil Procedure rules compilation): https://www.supremecourt.ohio.gov/docs/LegalResources/Rules/civil/CivilProcedure.pdf