Abstract background illustration for How to calculate Alimony Child Support in Maryland

How to calculate Alimony Child Support in Maryland

7 min read

Published June 4, 2026 • By DocketMath Team

Partially verified

older_than_packet

Quick takeaways

  • Maryland child support is calculated under the Maryland child support guidelines in Md. Code, Fam. Law § 12-204, using an “income shares” approach that produces a monthly support amount for children.
  • Maryland alimony is not computed with a single fixed formula. Instead, courts consider statutory alimony factors in Md. Code, Fam. Law § 11-106 to make an award that is fair and equitable.
  • DocketMath helps you run a side-by-side planning workflow:
    • child support via the § 12-204 guidelines, and
    • alimony via § 11-106 factor inputs—so you can see how changes in income, parenting time, and related expenses can affect outcomes.
  • For alimony duration, DocketMath uses the general/default period approach when no claim-type-specific sub-rule is available. In plain terms: you’re using the standard period logic rather than a special-case rule.
  • Primary CTA: run the calculator here: /tools/alimony-child-support.

Note: This guide explains how to calculate using DocketMath and Maryland statute concepts. It’s informational only and not legal advice.

Inputs you need

Before you start in DocketMath, gather the numbers that drive both the child support guideline calculation and the alimony factor analysis.

A. Child support inputs (Maryland guideline calculation)

You’ll typically need:

  • Combined monthly household income components
    • Gross income by parent (e.g., wages, business income, and other applicable income sources)
    • Any documented adjustments/treatment items required for guideline modeling in your inputs workflow
  • Number of children
  • Health insurance cost (if applicable in your worksheet)
  • Childcare cost (if applicable)
  • Parental time / custody arrangement
    • Parenting time split can affect the guideline calculation because it changes how shared care is modeled.
  • Support base adjustments (if your situation requires them in the tool’s input flow)
    • For example, certain mandatory deductions or related components where guideline treatment applies.

Statutory anchor: Maryland authorizes the guideline system for determining child support amounts under Md. Code, Fam. Law § 12-204.
Source: https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gfl&section=12-204

B. Alimony planning inputs (factor-based determination)

Alimony in Maryland is factor-based, so you’ll need information that maps to the statutory factors (rather than expecting one “equation” to compute it automatically). Common inputs include:

  • Who is seeking alimony and who would be paying
  • Ability to be self-supporting
  • Income, earning capacity, and employment-related evidence
  • Reasonable expenses and other financial needs/circumstances relevant to fairness
  • Other case-specific circumstances the statute directs the court to consider

Statutory anchor for factors: Md. Code, Fam. Law § 11-106 (including § 11-106(b), which lists factors the court must consider).

C. Time period logic (default/general approach)

Because the jurisdiction note indicates no claim-type-specific sub-rule was found, DocketMath uses the general/default period logic for the alimony duration output.

What to take away: if your case falls into a special procedural or claim scenario that would trigger a different duration framework, a default period model may not mirror how a court would handle that period. Treat the output as planning-focused rather than case-definitive.

How the calculation works

DocketMath runs two different types of reasoning in one workflow—child support (guidelines) and alimony (factors). That matters because the same input change (like income) may affect each side differently.

1) Child support: calculated under Md. Code, Fam. Law § 12-204

Maryland’s child support guideline framework in Md. Code, Fam. Law § 12-204 is designed to produce a presumptive monthly obligation based on:

  • parents’ incomes,
  • the number of children,
  • and relevant child-related cost/time-sharing inputs you enter.

In DocketMath terms, you typically:

  • enter monthly income for each parent,
  • enter children count,
  • enter parenting time/custody split,
  • and enter health insurance and childcare if applicable.

Then DocketMath calculates a monthly child support figure based on the Maryland guideline structure embedded in the jurisdiction-aware tool rules.

How changes typically move the number

  • Higher paying-parent income → often increases guideline obligation.
  • More parenting time for the paying parent (properly reflected in the model) → often reduces obligation in many guideline systems.
  • More child-related mandatory expenses (health insurance/childcare when included) → can increase the overall monthly support need in the model.

Practical tip: small input differences (especially custody/time split) can change outputs, so verify the time modeling before trusting the result.

2) Alimony: factor-based, centered on Md. Code, Fam. Law § 11-106(b)

Unlike child support, Maryland alimony is not driven by a single, fixed math formula. Instead, the court considers “all the factors necessary for a fair and equitable award” and weighs the statutory factors in Md. Code, Fam. Law § 11-106.

The statute text highlights, among other things, that the court must consider the ability of the party seeking alimony to be wholly or partly self-supporting (see Md. Code, Fam. Law § 11-106(b)(1)).

In DocketMath:

  • you enter factual variables that align with relevant factors (e.g., self-support ability and other fairness inputs),
  • then the tool produces an alimony planning output that applies its jurisdiction-aware amount/period approach.

Important caution: because Maryland alimony is discretionary and evidence-driven, two cases with similar incomes can still produce different outcomes depending on evidence about needs, self-support capacity, and fairness circumstances. A calculator helps organize assumptions—it can’t replace judicial discretion.

Duration note (default/general period)

  • DocketMath uses the general/default period approach because no claim-type-specific sub-rule was found in the provided jurisdiction data.

3) Putting them together (planning the combined picture)

When you run /tools/alimony-child-support, DocketMath provides a combined planning view so you can compare:

  • child support that is guideline-anchored under § 12-204, and
  • alimony that is factor-anchored under § 11-106, especially § 11-106(b) for factor considerations.

Why the results may “move” differently

  • Child support often moves more predictably with income and modeled parenting time/cost inputs.
  • Alimony can change based on how the factor inputs evaluate fairness—particularly self-support ability and other case circumstances—before the tool applies its period logic.

Common pitfalls

  • Treating alimony like a strict formula

    • Child support is guideline-based under § 12-204.
    • Alimony is factor-based under § 11-106(b).
    • Expecting a “plug-and-chug” result for alimony can lead to overconfidence in the output.
  • Entering incomplete or inconsistent income

    • If income is missing, double-counted, or not consistently monthly, the § 12-204 guideline side and the § 11-106 factor side can both be skewed.
    • Double-check that inputs represent the same time basis (typically monthly).
  • Incorrect custody/time split modeling

    • Parenting time/custody inputs can materially affect guideline calculations under the § 12-204 framework.
    • Even small reporting mistakes can create seemingly “wrong” results.
  • Assuming the alimony period is claim-type specific

    • The guidance notes that no claim-type-specific sub-rule was found.
    • DocketMath therefore uses the general/default period logic. If a special claim scenario applies to your case, the modeled duration may not reflect how a court would treat the period.

Pitfall to watch: adjusting only one side (like changing income without updating custody or child expense inputs) can make the result seem inconsistent when the real issue is mismatched inputs.

Sources and references

Next steps

  1. Run the DocketMath combined workflow here: /tools/alimony-child-support.
  2. Start with baseline numbers you can document:
    • monthly income for each parent,
    • number of children,
    • parenting time split you want modeled,
    • health insurance and childcare costs (if applicable).
  3. Perform a “what changes the result” review:
    • adjust income in small increments (for example, 5–10%) and compare child support and alimony outputs,
    • adjust the custody/time split to see sensitivity on the child support side,
    • update alimony-relevant factor inputs tied to fairness and self-support ability under § 11-106(b).
  4. Record your assumptions so you can compare scenarios consistently.

Related reading