How to run Settlement Allocator in DocketMath for Arkansas

Step-by-step

This guide walks you through running Settlement Allocator in DocketMath for Arkansas (US-AR) using jurisdiction-aware rules tied to Ark. R. Civ. P. 23 (Class Actions).

1) Open the tool from the primary CTA

Start at: Settlement Allocator

Before you enter anything, gather the items you’ll need:

• The settlement pool amount (the funds to allocate)
• The class/participant list (who receives allocation shares)
• The allocation basis you want to use (e.g., documented metrics such as days, units, dates, or other case-plan measures)
• Any weights, caps, or exclusions you intend the allocator to reflect

2) Set jurisdiction to Arkansas (US-AR)

Inside the tool, set jurisdiction to Arkansas (US-AR).

DocketMath uses this setting to align the workflow with Ark. R. Civ. P. 23, which is the governing rule for class actions. In practice, that primarily affects how the tool frames the allocation as part of a class-style settlement model (rather than a one-off individual split).

3) Enter the settlement pool

In the settlement allocator input panel, provide:

• Settlement amount (the total fund you want allocated)
• If applicable, amount already reserved for approved deductions (administration, fees, taxes, etc.)

How outputs change: if you increase the pool, participants’ allocations increase proportionally unless you use caps/weights/exclusions that redistribute the remainder.

Quick checklist:

• Decide whether your settlement amount input is gross or net after known deductions, and enter values consistently.
• If you reserved deductions, enter them in the deduction/reserve fields so the tool computes the available pool correctly.

4) Add participants and their allocation basis

Next, add participant rows (names/IDs) and the input values that define each participant’s allocation basis, such as:

• Counts (e.g., number of qualifying items)
• Numeric measures (e.g., days employed, units purchased)
• Any precomputed weight values your plan uses

How outputs change: participants with larger basis/weights receive larger shares. A proportional model typically follows:

• Participant share ≈ (Participant basis / Sum of all bases) × Available settlement pool

5) Apply Arkansas Rule 23 constraints at the workflow level

Because Ark. R. Civ. P. 23 is the general governing framework for class actions (and not broken into claim-type-specific periods here), use the same allocation approach across your Arkansas participants unless your documented plan explicitly overrides it outside the allocator.

Practical implication: ensure your dataset reflects the class membership logic you’re using under a Rule 23 class setup. (This is not legal advice—just a workflow reminder.)

6) Run the allocation calculation

Click Calculate (or the tool’s equivalent).

Review:

• Allocation amount per participant
• Total allocated (should reconcile to the available pool, subject to rounding)
• Summary metrics (sum of bases, implied percentages, and how any remainder/rounding is handled)

Sanity checks:

• Total allocated ≈ available settlement pool (within rounding tolerance)
• The participant with the largest basis has the largest allocation
• Excluded participants receive 0 allocation if the tool’s model supports exclusions and you used it correctly

7) Export results for review and iteration

Export or copy the results (CSV/PDF depending on your tool options).

Then iterate:

• If totals don’t reconcile, re-check reserved deductions fields and basis totals.
• If allocations look “off,” verify basis numbers and ensure no participant entered as 0 basis unintentionally.
• If you rely on weights/caps/exclusions, confirm those fields are populated as intended across all rows.

8) Document inputs for traceability (recommended)

DocketMath results depend on your inputs. Record:

• Settlement pool amount (and whether gross vs. net)
• The basis definition used per participant
• Any weights/caps/exclusions applied
• Jurisdiction setting (US-AR)
• The fact you used the Ark. R. Civ. P. 23 general/default class-action framework with no claim-type-specific sub-rule driving separate periods for Arkansas

This helps you reproduce the run later with the same dataset and assumptions.

Common pitfalls

These are common issues when running Settlement Allocator in DocketMath for Arkansas (US-AR) under Ark. R. Civ. P. 23:

• Selecting the wrong jurisdiction mode

  • Running another jurisdiction can change how the workflow applies class-style assumptions.
  • Fix: confirm US-AR is selected before calculating.

• Double-counting deductions

  • Example: entering a gross settlement amount while also reserving deductions in both places can reduce the available pool twice.
  • Fix: choose gross vs. net treatment and enter deduction/reserve values consistently.

• Expecting claim-type-specific allocator periods in Arkansas

  • Arkansas guidance here uses the general/default framework from Ark. R. Civ. P. 23.
  • Fix: since no claim-type-specific sub-rule was found, use one consistent basis approach across participants for Arkansas runs unless you have a separate, documented plan that governs otherwise.

• Basis totals don’t reconcile

  • A single typo can materially shift proportional shares.
  • Fix: quickly review the largest and smallest basis rows, then confirm the basis sum matches your expectation.

• Exclusions not handled explicitly

  • If someone shouldn’t receive allocation, they must be entered in a way the tool recognizes (e.g., using exclusion flags/fields, if supported).
  • Fix: use DocketMath’s exclusion capability rather than leaving blank fields.

• Rounding surprises

  • Totals often reconcile within rounding tolerance, but displayed per-participant values can differ slightly by formatting.
  • Fix: treat rounding as a final presentation step unless your plan specifies a particular remainder/cents approach.

Try it

Ready to run your first Arkansas allocation?

1. Open the tool: Settlement Allocator
2. Select Arkansas (US-AR)
3. Enter:

   • Settlement amount
   • Any reserved deductions/reserves (if applicable)
   • Participant rows with allocation basis/weights (and exclusions if relevant)
4. Click Calculate
5. Review:

   • Total allocated vs. available pool
   • Largest basis participant vs. largest allocation
6. Export the results and compare totals with your working spreadsheet (if you have one)

To reduce risk on your first pass:

• Run with a small subset (e.g., 5–10 participants)
• Verify proportionality and totals
• Then run the full dataset

Related reading

• How to calculate Settlement Allocator in Ohio — Full how-to guide with jurisdiction-specific rules
• 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