How to run Alimony Child Support in DocketMath for New York

Step-by-step

Below is a practical walkthrough for running Alimony + Child Support calculations in DocketMath for New York (US-NY) using jurisdiction-aware rules. This guide focuses on getting reliable inputs, understanding what the calculator will do with them, and interpreting results so you can iterate quickly.

1) Open the correct tool and set jurisdiction

1. Open the primary calculator: /tools/alimony-child-support
2. Confirm the jurisdiction is set to New York (US-NY).
3. If DocketMath asks you to confirm jurisdiction per calculation, select US-NY before entering any numbers.

Why this matters in DocketMath: jurisdiction selection typically controls rulesets (assumptions, formula components, and verification prompts). Running the wrong jurisdiction can change both the calculation path and outputs.

2) Enter parties’ income inputs (then re-check pay cadence)

Most calculation workflows require some form of:

• Income for the paying party
• Income for the receiving party (or at least enough info to compute comparative need)
• Whether income is monthly or annual
• Any adjustments you plan to model (e.g., variable bonuses, stable overtime)

DocketMath input tips

• Enter numbers using the cadence DocketMath expects (often monthly).
• If income is irregular, start with a conservative baseline and then run a second scenario using a higher estimate—then compare outputs side-by-side.

3) Provide child-related inputs (age and number of children)

For child support components, DocketMath typically needs:

• Number of children
• Each child’s age (or an age range if the interface supports it)
• Any relevant custody-time inputs, if available in the tool

How outputs change

• Support obligations generally scale with the number of children and age-related thresholds.
• If the tool has a custody-time or parenting-time input (even as a percentage), small changes can move outputs noticeably.

4) Add custody / parenting-time parameters (if shown)

If the calculator includes parameters for the parenting-time split, enter them consistently:

• Use the same measurement method across scenarios (e.g., “days per year,” “overnights,” or “percentage”).
• If the tool uses percentages, compute once and reuse the same method.

Practical approach

• Run a “current schedule” scenario.
• Run a “projected schedule” scenario (for example, if parenting time is expected to change as a child ages).

5) Enter alimony-related parameters (if the tool supports both)

For alimony, DocketMath’s alimony child support workflow may prompt you for things like:

• Marriage duration (or separation timeline inputs)
• Whether alimony is modeled as temporary vs continuing (if the UI supports this)
• Proposed term and any phase logic the tool uses
• Relevant income information (already supplied in Step 2)

If the interface includes a model selector:

• Choose the model that matches what you’re trying to compare (e.g., “baseline estimate” vs “term-based projection”).

6) Review scenario settings before you run the calculation

Before pressing Calculate:

• Check whether DocketMath shows a summary panel of your assumptions (often a sidebar or review section).
• Confirm the time basis (monthly vs annual).
• Confirm formatting—especially that no negative values were accidentally entered.

7) Run the calculation, then iterate using a “change one variable” method

Once results appear, iterate with controlled changes:

1. Change one input (like income or number of children).
2. Re-run.
3. Compare outputs side-by-side.

Example iteration workflow

• Scenario A: baseline income inputs
• Scenario B: alternate income estimate (e.g., add/subtract a stable monthly amount)
• Scenario C: different parenting-time split
• Scenario D: updated child ages

This approach helps you identify which inputs drive the biggest differences in DocketMath outputs.

8) Use the results panel to capture key output categories

DocketMath typically separates results into categories such as:

• Child support amount (and potentially adjustments)
• Alimony amount (if modeled)
• Combined monthly obligation
• Intermediate figures the tool uses to build totals

Capture the key numbers you’ll need for next steps:

• Monthly total
• Component totals (child support vs alimony)
• Any recalculation triggers (e.g., “input changed—recompute”)

Common pitfalls

Family-law calculators are sensitive to inputs. These are the most common ways New York calculations can go off-track inside a workflow like DocketMath:

• Mixing annual and monthly income

  • Example: entering $120,000/year as “120” when the tool expects monthly.
  • Fix: convert to the cadence the UI requests and keep it consistent across scenarios.

• Inconsistent child age handling

  • If DocketMath asks for ages individually, don’t approximate by averaging unless the UI explicitly allows it.
  • A one-year difference can affect outputs depending on the tool’s structure.

• Using an incorrect jurisdiction setting

  • Running under a non-NY profile can swap in different assumptions.
  • Always confirm US-NY before calculating.

• Assuming a limitation period rule without verifying the governing provision

  • DocketMath outputs are computational, but timing and enforceability questions depend on statute.
  • Be careful when you connect tool results to enforcement or collections.

• Overgeneralizing statutes

  • You have one general statute reference below, but don’t treat it as claim-type-specific.
  • The jurisdiction data you provided indicates only a general/default period.

New York limitations reference you can use alongside your workflow (general/default only)

You provided the following jurisdiction data for New York:

• General SOL Period: 5 years
• Cited statute: N.Y. Crim. Proc. Law § 30.10(2)(c)
  Source: https://www.nysenate.gov/legislation/laws/CPL/30.10

How to interpret this in a DocketMath context

• Treat the 5-year general/default period as a timing reference only.
• Do not assume it applies to every sub-type of enforcement or filing question without matching the relevant legal provision for that specific issue.

Try it

Ready to run your first New York scenario in DocketMath?

1. Open the tool: **/tools/alimony-child-support
2. Set jurisdiction to **New York (US-NY)
3. Enter:

   • Income (paying party, receiving party if requested)
   • Number of children and ages
   • Parenting-time split (if prompted)
   • Alimony parameters (if prompted)
4. Click Calculate
5. Then run two quick iterations:

   • Iteration 1: adjust paying-party income by a realistic alternate estimate (for example, add/subtract a stable monthly amount)
   • Iteration 2: adjust parenting-time split (if available) by a small step and observe the combined total change

What to look for in the outputs

• Is the combined monthly obligation more sensitive to income or custody time?
• Does the tool surface intermediate figures you can sanity-check (so you can spot entry errors quickly)?
• Are any components unexpectedly zero or missing? If so, revisit whether a required input was left blank.

If you want, tell me what fields your DocketMath screen shows for US-NY (income cadence, custody model, and which alimony inputs are present), and I can help you map your numbers into the exact input order.

Related reading

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