Worked example: Alimony Child Support in Rhode Island

Example inputs

Below is a worked example of how DocketMath’s Alimony Child Support calculator can be used with Rhode Island (US-RI) jurisdiction-aware rules—using the default general statute-of-limitations period provided for General Laws § 12-12-17.

Scenario (hypothetical)

Assume the following for a Rhode Island family law case:

• Child(ren)

  • Number of children: 2
  • Primary care arrangement: Parent A has the children most of the time
• Income

  • Parent A (income): $80,000/year
  • Parent B (income): $60,000/year
• Parenting-time / adjustment inputs (if your case uses the calculator’s sliders or fields)

  • Shared-time factor selected: moderate shared time
• Support parameters

  • Requested alimony type inside the tool: general alimony field (no claim-type-specific rule found in the jurisdiction data you provided)
  • Arrears lookback flag: enabled (so the calculator applies the jurisdiction general SOL window to arrears-related outputs, where applicable)
• Jurisdiction timing (used for SOL logic inside the tool)

  • Rhode Island general SOL period (provided): 1 year
  • Rhode Island general statute cited by the tool rules: General Laws § 12-12-17

SOL timing rule used in this example (explicit)

Your jurisdiction data says no claim-type-specific sub-rule was found. That means the calculator applies the general/default period as the timeline constraint:

• General SOL Period: 1 year
• Source statute: General Laws § 12-12-17 (cited in the jurisdiction rules)

For reference, the statute is published here:
https://codes.findlaw.com/ri/title-12-criminal-procedure/ri-gen-laws-sect-12-12-17/

Example run

You can run this scenario in DocketMath at:

• Primary CTA: /tools/alimony-child-support

Because your requested calculator is alimony-child-support, the tool typically produces outputs in these categories:

• Estimated child support (monthly)
• Estimated alimony (monthly) if alimony inputs are present/required by the selected approach
• Timeline indicators or arrears window logic (when enabled), using the jurisdiction SOL period

Example inputs entered (as a checklist)

In the tool, you’d set the following inputs (names may vary slightly based on the UI, but the values match the scenario):

What the calculator will output (illustrative structure)

While exact numeric results depend on the tool’s internal formulas and the specific input fields available, a typical output set will look like:

Timeline flag based on the SOL rule

With “arrears lookback enabled” and the jurisdiction SOL period set to 1 year, the calculator will constrain any “eligible lookback” period to:

• 1 year back from the relevant measurement date the tool uses

Because your jurisdiction note says no claim-type-specific sub-rule was found, the calculator treats the general/default period as the governing rule for this run.

Sensitivity check

The fastest way to validate a calculator run is to change one input at a time and observe directional changes. Below are practical sensitivity checks specifically tailored to this Rhode Island example and DocketMath’s structure.

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.

1) Income gap sensitivity (Parent A income vs Parent B income)

Start by changing Parent B income while holding everything else constant.

• Change Parent B from $60,000 → $70,000

  • Expected effect:

    • Child support estimate generally trends down because the income gap narrows.
    • Alimony estimate (if enabled/required by the tool fields) may also trend down, since the relative support need and relative ability to pay commonly become less pronounced.

• Change Parent A from $80,000 → $90,000

  • Expected effect:

    • Child support generally trends up (more capacity on Parent A side).
    • Alimony may trend up if the tool’s logic ties it to relative incomes and support need.

✅ Practical checklist for your next run:

2) Children count sensitivity (1 child vs 2 children)

Try switching:

• Number of children: 2 → 1
  Expected effect:

  • Child support should decrease because the obligation is divided across fewer dependents.

• Number of children: 2 → 3
  Expected effect:

  • Child support should increase.

3) Parenting-time sensitivity (shared time factor)

Adjust the parenting-time factor while holding incomes and children constant:

• Moderate shared time → higher shared time
  Expected effect:

  • Child support may decrease in many guideline frameworks because the time with the children can shift the economic allocation model.

4) SOL window sensitivity (arrears lookback setting)

This is where your jurisdiction note matters.

• If you toggle arrears lookback enabled → disabled:

  • The tool should stop applying the 1-year SOL window logic to arrears/timing-related outputs.
  • Ongoing monthly estimates (child support/alimony) may remain similar, but any “eligible lookback” outputs will change.

• If the calculator has a control for “use default SOL window” vs “other,” keep it on:

  • Default 1-year window from General Laws § 12-12-17

Because no claim-type-specific sub-rule was found in the jurisdiction data, the model should not switch to a different period for a different claim type in this example. The default general rule is the one applied.

Related reading

• Alimony & Child Support Estimator Guide for Alabama
• Alimony & Child Support Estimator Guide for Arizona
• Alimony & Child Support Estimator Guide for Colorado