Inputs you need for Alimony Child Support in Maryland

Inputs you will need

Run this scenario in DocketMath using the Alimony Child Support calculator.

DocketMath’s Alimony & Child Support calculator for Maryland (US-MD) is designed to take specific facts about the people and finances involved. Before you run /tools/alimony-child-support, gather the items below so you can enter complete numbers and produce a more useful estimate.

A. Basic case identifiers (helps you keep numbers straight)

• ☐ County and/or court location (mainly for your own organization and consistency)
• ☐ Filing date or the date you’re modeling (helpful for timing context)
• ☐ Whether you’re modeling:

  • ☐ monthly support (ongoing amount)
  • ☐ arrears/retroactive planning (if you’re analyzing a specific past period)

B. Parties information

• ☐ Each parent’s full name (for your worksheet and recordkeeping)
• ☐ Number of children covered
• ☐ Children’s situation you plan to model:

  • ☐ ages of children (or birth years)
  • ☐ any special income/needs considerations you want to reflect in your estimate (keep notes on what those are)

C. Income inputs (the calculator’s backbone)

Collect gross income for both parents. The more clearly you separate income sources, the better DocketMath can estimate.

For each parent, gather:

• ☐ Pay frequency (weekly / biweekly / semimonthly / monthly)
• ☐ Employer income (last paystub totals or an annualized figure)
• ☐ Overtime (average you’re using)
• ☐ Bonuses/commissions (average amount and how often they’re paid)
• ☐ Self-employment income (use net figures from your most recent statements/returns)
• ☐ Retirement income (if applicable)
• ☐ Social Security disability or other benefits (only if you intend to include them in your estimate)
• ☐ Unemployment income (if applicable)
• ☐ Other consistent income (e.g., rental/royalties)

Practical tip: If income fluctuates, document the “average window” you want to use:

• ☐ “Use last 3 months average”
• ☐ “Use last 12 months average”
• ☐ “Use latest annual figure”

Pitfall to avoid: Mixing gross and net figures is one of the most common causes of “off” results. Use gross consistently across your entries so your assumptions match the way you’re thinking about the estimate.

D. Health insurance and childcare (if you’re modeling more than income-only)

Depending on what you plan to estimate in DocketMath, consider gathering:

• ☐ Who pays health insurance for the child
• ☐ Monthly premium amounts attributable to child coverage
• ☐ Monthly childcare costs
• ☐ Daycare/after-school or similar recurring expenses you want to include

E. Housing, custody, and parenting-time facts (for child support assumptions)

To model the parenting-time structure you’re analyzing, gather enough scheduling data to describe the arrangement:

• ☐ Custody / parenting arrangement you’re modeling (e.g., shared vs. non-shared)
• ☐ Number of nights per week (or a comparable schedule description)
• ☐ Transportation considerations (only if you intend to model how these costs affect your overall assumptions)

F. Alimony inputs (for spousal support modeling)

If you’re using DocketMath’s workflow that includes alimony alongside child support, gather:

• ☐ Duration of the marriage (years and months)
• ☐ Each spouse’s income (gross and any known variability)
• ☐ Major debts or special financial burdens you want to include in your estimate (keep this simple and itemized)
• ☐ Expected employment changes within the next 6–12 months (if you’re forecasting)

Timing limitations backdrop (Maryland planning context)

Maryland includes a general limitations framework for certain civil actions. The jurisdiction data provided indicates the general/default limitations period is 3 years under Md. Code, Cts. & Jud. Proc. § 5-106.

• General limitations period: 3 years
• 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

Clarity on the rule you have: No claim-type-specific sub-rule was found in the provided jurisdiction notes. That means you should treat 3 years under § 5-106 as the general/default planning baseline, not as a promise that every support-related issue follows the same timeline.

Where to find each input

Turn your existing records into calculator-ready numbers. Below are common places to locate each item in a typical Maryland case file.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

Income

• Pay stubs: Best starting point for gross pay, overtime patterns, and employer-related income context.
• Employer letters or annual earnings statements: Useful when year-to-date figures are incomplete.
• Tax returns and schedules (self-employment): Use the most recent filed return; you can convert to a monthly equivalent for consistency.
• Bank statements: Helpful for verifying consistency with irregular deposits, but don’t replace pay stubs unless you have a documented reason for doing so.

Parenting-time and children

• Proposed or existing custody agreement: Look for dates, schedule rules, and holiday structure.
• Calendar history: If you’re modeling what’s happening, use documented schedules for the last 2–3 months.

Health insurance & childcare

• Health insurance invoices / payroll deductions: Pull the premium amounts attributable to child coverage.
• Childcare receipts/invoices: Gather monthly totals and any recurring add-ons (if you plan to include them).

Alimony-related facts

• Marriage certificate and records: Identify the marriage start date (and any separation date if your worksheet uses it).
• Employment history and expected changes: Any letters or written notes about anticipated job transitions.

Run it

Once you’ve collected your numbers, run DocketMath’s Alimony & Child Support calculator for Maryland (US-MD) at /tools/alimony-child-support.

Enter the inputs in DocketMath and run the Alimony Child Support calculation to generate a clean breakdown: Run the calculator.

1) Enter inputs in a consistent format

Use the same time unit throughout your worksheet so your comparisons are apples-to-apples:

• ☐ weekly income → annualize consistently, or
• ☐ monthly income → convert consistently, or
• ☐ use annual income directly (if DocketMath prompts for it)

2) Align parenting-time assumptions

Pick the schedule you’re modeling and keep it consistent:

• ☐ current arrangement
• ☐ proposed schedule
• ☐ most recent stable period (2–3 months)

Even small changes can move the results:

• More parenting-time nights can shift day-to-day cost allocation.
• Changes to childcare or insurance assumptions can affect the estimated “net effect,” even when income is steady.

3) Observe how outputs change

After running the calculator, do a simple “what drives this?” check:

• Change income by ±5% and rerun to see whether the estimate moves proportionally.
• Update childcare premiums/amounts with your exact monthly figure and rerun.
• Adjust parenting-time nights by a small amount (e.g., 1–2 nights/month) and rerun.

4) Use the tool as an estimate worksheet

Treat the output as a planning baseline:

• Keep a copy of your trusted input set.
• Note which facts you were unsure about so you can refine them before any formal filings.

Primary CTA: /tools/alimony-child-support

Related reading

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