How to run Alimony Child Support in DocketMath for Maryland

Step-by-step

This guide walks you through running Alimony + Child Support calculations in DocketMath for Maryland (US-MD) using the alimony-child-support calculator and jurisdiction-aware settings. It’s designed to help you produce calculation outputs you can discuss with a legal professional—without providing legal advice.

1) Open the right DocketMath calculator

1. Go to the primary calculator here: **/tools/alimony-child-support
2. Confirm the jurisdiction is set to Maryland (US-MD).

   • If DocketMath prompts you for jurisdiction selection, choose Maryland so the tool applies Maryland-specific assumptions and time-related defaults.

2) Enter the parties’ baseline information

In the calculator inputs, populate the sections for:

• Parent/Party A financial details (e.g., income fields requested by the calculator)
• Parent/Party B financial details
• Household / child details (number of children, and any child-specific fields the tool asks for)

How outputs change:

• Child-support-related outputs generally move with combined incomes and the number of children.
• Alimony outputs generally move with income differentials and any alimony-duration or eligibility inputs DocketMath requests.

3) Add the timeline facts the tool asks for

DocketMath’s alimony/child support calculations often require dates such as:

• Effective date / start date for the calculation period (depending on the tool UI)
• Whether you’re running the calculation for a single month, a range, or a scenario tied to time

Set these carefully because they affect:

• The number of months being calculated
• The total payable over the displayed period (monthly amount × months, where applicable)

4) Use Maryland’s default limitations framework (general rule)

Maryland has a general statute of limitations period of 3 years for many civil actions, including time-based recovery limits that can affect how far back certain claims may run.

• General SOL Period: 3 years
• General Statute: Md. Code, Cts. & Jud. Proc. § 5-106
• Source: https://codes.findlaw.com/md/courts-and-judicial-proceedings/md-code-cts-and-jud-pro-sect-5-106/?utm_source=openai

Important clarity for this guide:
In this content, the “3 years” figure is treated as the general/default period, because no claim-type-specific sub-rule was found for the specific topics addressed here. That means:

• If you’re evaluating “how far back” obligations or related amounts could be pursued, DocketMath can help you model payment amounts, but the court’s and claim’s specific limitations analysis may still differ based on the exact legal basis.

5) Select scenario options inside DocketMath

Depending on the DocketMath UI, you may see toggles or inputs such as:

• Whether to include alimony
• Whether to include child support
• Which calculation perspective you want (monthly vs. period totals)

Choose the combinations that match your scenario:

• Child-support-only estimate: disable alimony
• Alimony + child support combined view: enable both

How outputs change:

• Enabling both often changes how DocketMath presents results (for example, separate lines for each obligation category plus a combined figure).
• Switching between monthly and period totals usually changes the aggregation—not the underlying monthly computation assumptions.

6) Review the calculation outputs carefully

After you run the calculator:

• Look for monthly results for each obligation type (as shown in the tool)
• Check totals over the selected date range
• Validate that the tool used the inputs you intended (especially children count and dates)

A practical checklist for review:

7) Export or save your results for discussion

If DocketMath provides export, download, or a shareable summary:

• Save the calculation so you can compare scenarios (e.g., changing income or child count)
• Keep a note of the exact date range and input assumptions used

This helps you quickly answer “what changed?” questions when you run multiple versions.

Common pitfalls

Even with good inputs, a few recurring issues can cause results to be misleading. Here are common ones when running alimony + child support in Maryland via DocketMath.

If one party’s income is entered as monthly while the other is entered as annual (or vice versa), the outputs can change dramatically.

• Double-check each income field’s label in the calculator.
• Use consistent time basis with what the tool requests.

Pitfall 2: Miscounting children or missing child-specific fields

Child-support outputs typically depend heavily on:

• Number of children
• Any tool-specific child details (if requested)

If you entered “2” children but the case involves “3,” the monthly figure will not reflect the scenario you mean to model.

Pitfall 3: Date range mismatch

If you select a date range from January to June but intended March to July, totals will change even if the monthly number seems similar.

• Confirm the tool’s computed number of months.
• If your scenario is meant to start on a specific month, align the start date precisely.

Pitfall 4: Treating the 3-year default as universal

This guide uses 3 years under Md. Code, Cts. & Jud. Proc. § 5-106 as a general/default framing.

That’s a helpful lens for time-based questions, but it isn’t a substitute for claim-specific legal analysis.

Try it

Run a quick sanity check scenario in DocketMath for Maryland (US-MD):

• Go to **/tools/alimony-child-support
• Enter:

  • A small number of months for your date range (for example, 3–6 months) so you can quickly verify outputs
  • Your best-available income estimates
  • Your correct child count

Then run two versions:

• Version A: alimony enabled + child support enabled
• Version B: alimony disabled + child support enabled

Compare the results:

• Does the child-support component stay consistent between versions B and A?
• Does the difference between A and B match the alimony portion shown by the tool?

You can also test sensitivity:

• Change Party A’s income slightly and re-run.
• Observe how the tool’s monthly outputs move.

If small input changes create massive output swings, re-check:

• time basis (monthly vs. annual)
• date range length
• child count and any child-related inputs

Once the numbers behave plausibly, expand to your intended date range and scenario set.

Related reading

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