How to run Settlement Allocator in DocketMath for Rhode Island

Step-by-step

Below is a practical workflow for running Settlement Allocator in DocketMath for Rhode Island (US-RI). This guide focuses on how to set inputs and interpret outputs when applying jurisdiction-aware rules tied to Rhode Island’s general time limit for filing certain post-judgment actions. It does not provide legal advice.

1) Open Settlement Allocator in DocketMath

1. Go to the tool: **/tools/settlement-allocator
2. Confirm the jurisdiction is set to Rhode Island (US-RI). If you see a jurisdiction selector, choose US-RI before entering dates.

2) Identify your “event dates” (the dates that drive allocation)

Settlement Allocator works from the dates you provide. Gather these from your case documents:

• Judgment date (or the triggering date used in the tool’s logic)
• Filing/claim date (the date you’re evaluating against Rhode Island’s time limits)
• Any additional date fields the tool requests (commonly “start,” “as-of,” or “filing” dates)

If you’re unsure which date the tool expects, use the tool’s field labels exactly as written—those labels determine how the calculator interprets your timeline.

3) Enter amounts and party/cost categories

Most settlement allocation workflows depend on two categories of inputs:

• Monetary amounts you want allocated (e.g., settlement total, payments, components)
• Distribution categories available in the tool (often grouped as general components vs. other add-ons)

Tips for clean inputs:

• Enter dollar amounts in the format the tool accepts (whole dollars and/or cents).
• Keep signs positive unless the tool explicitly supports negative numbers/credits.

4) Confirm the Rhode Island default statute period used by the tool

For Rhode Island in this workflow, the General SOL Period applied is:

• General SOL Period: 1 years

The jurisdiction-aware rule here is based on General Laws § 12-12-17 (Rhode Island). Importantly, your provided jurisdiction data notes:

• No claim-type-specific sub-rule was found

So the calculator should treat this as the default/general period rather than switching based on claim type.

Source reference: https://codes.findlaw.com/ri/title-12-criminal-procedure/ri-gen-laws-sect-12-12-17/

5) Run the calculation

1. Double-check every date and every dollar input.
2. Click Calculate (or the tool’s equivalent).
3. Review results in:

   • the allocation breakdown
   • the timeline/eligibility indicators (if shown)

6) Interpret outputs: what changes when dates move

When you rerun with adjusted dates, the output can change in two main places:

• Eligibility/timing outputs: If your evaluated date crosses the 1-year boundary, the tool may shift which portions are treated as time-barred vs. within the allowable window (depending on the tool’s modeling).
• Allocation outputs: Percentages or category splits may also change if the calculator reallocates portions based on which categories are considered affected by the timing rule.

A practical sanity check:

• Change only one date (for example, the filing/claim date) by a few days and rerun.
• If the output doesn’t move, either:

  • your change didn’t cross a threshold, or
  • you may have entered a date into a different field than you intended—so re-check the date field mapping in Step 2.

7) Export or record the results

If DocketMath offers export options (download, copy-to-clipboard, or a results view), use them. Also record:

• the exact input dates used
• the settlement total and any category/component amounts
• the final allocation outputs

This makes it much easier to compare “what-if” scenarios and verify that results are reproducible.

Common pitfalls

Small input mismatches can cause outsized differences in timeline-driven allocators. Watch for these:

• Using the wrong “trigger” date The Rhode Island general period is measured from the tool’s expected starting point. If you plug in a date from a later procedural step, results can flip.

• Assuming claim-type-specific SOL rules apply when none were found Your jurisdiction dataset indicates no claim-type-specific sub-rule was found, so the tool should use the default/general 1-year period tied to General Laws § 12-12-17.

• Entering dates in an unexpected format Common examples include:

  • swapping month/day/year
  • entering day/month in a system expecting month/day
  • missing a year

• Mixing settlement totals and component totals If the tool asks for both a total settlement amount and components, double-counting can happen. Follow the tool’s structure exactly—either enter a total plus components (if supported) or enter components only (if the tool computes totals).

• Relying on outputs without logging inputs Allocation calculators are sensitive to inputs. Without capturing the exact dates and amounts, it’s hard to reproduce results later.

Try it

Here’s a quick, low-risk way to validate your setup before committing to final figures.

1. Go to: **/tools/settlement-allocator
2. Enter:

   • a judgment/trigger date
   • a filing/claim date
   • the settlement amount(s)
3. Run the calculator and note:

   • the allocation breakdown
   • any SOL/timing indicator (e.g., within/beyond)

Then run three versions:

• Run A (baseline): Your current dates
• Run B (boundary test): Move the filing/claim date forward by 30 days
• Run C (boundary test): Move the filing/claim date backward by 30 days

What you’re looking for:

• If Runs A and B land on opposite sides of the 1-year framework, the tool’s timing-sensitive outputs should change.
• If all three runs look identical, revisit Step-by-step—especially the mapping of your “trigger” date (Step 2).

Keep this Rhode Island constraint in mind as you test:

• General SOL Period: 1 years
• Based on General Laws § 12-12-17
• Applied as the general default because no claim-type-specific sub-rule was found in the provided jurisdiction dataset

Related reading

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