Alimony Child Support rule lens: Maryland

The rule in plain language

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

In Maryland, when alimony or child support issues show up in a legal dispute, the time limit to bring certain legal actions is guided by the state’s general statute of limitations—which is 3 years.

For this “rule lens,” the controlling citation is:

• Maryland default (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

What’s “missing,” and why it matters

This lens is intentionally jurisdiction-aware. But note the scope:

• No claim-type-specific sub-rule was found for this particular lens.
• That means you should treat § 5-106 as the general/default period for understanding the timeline framework here.

If your situation involves a narrower category (a different claim type or a different statutory trigger), a different limitations rule could apply. This article focuses on the baseline general rule rather than mapping every possible support-related claim to its own limitations category.

What “3 years” means practically

If an action falls under Maryland’s general limitations period in § 5-106, a party typically must file within 3 years of the relevant triggering date (often tied to when a claim accrued, depending on how the claim is structured).

After the 3-year window, the matter may face procedural barriers such as dismissal or other limitations on what can be pursued. In practical terms, that affects how much of the “past” can be realistically targeted in a dispute—especially when parties are comparing numbers across time.

Why it matters for calculations

Most people associate alimony and child support calculations with spreadsheets: incomes, deductions, and schedules. Those mechanics absolutely matter. However, the limitations timeline can change what you can pursue (and what arrears history is practically actionable) when you’re building a scenario or preparing a filing.

Below are practical ways the 3-year default limitations lens shows up in calculations and modeling for Maryland (US-MD).

1) “Backward look” may be constrained to a 36-month frame

Even if support obligations existed earlier, a 3-year general limitations window can mean the “effective history” in a dispute looks more like:

• roughly the last 36 months from the relevant filing/reference timeline

So two scenarios can share the same underlying support math, yet differ on what months are emphasized, contested, or treated as actionable based on timeline framing.

2) Date inputs can shift outputs more than people expect

In DocketMath-style workflows (and in real case planning), outputs depend heavily on time anchoring. For example, if your process asks for:

• a support start month (or order effective date),
• a calculation window (how far you want to measure),
• and a reference/filing date,

then limitations framing can reshape what counts.

Rule lens takeaway: if you’re modeling using the general default lens, you’ll often want the “counted” period to align with a 3-year (36-month) baseline under § 5-106.

3) You may need two layers: “support period” vs. “limitations window”

It’s easy to accidentally blend these together.

• Support period layer: the months when payments were due under an order/agreement.
• Limitations layer: whether enforcement actions tied to due amounts are brought within the general 3-year framework under § 5-106.

If you don’t keep the layers consistent, you can end up with a worksheet that looks mathematically correct but is time-framed in a way that doesn’t match the “timeline lens” you’re trying to model.

4) Negotiation posture and documentation improve when you plan around the clock

Even without providing legal advice, it’s helpful to see why parties often structure discussions around timelines:

• what months are highlighted,
• what documents (payment history, order dates, accrual dates) get pulled,
• and what settlement ranges reflect the “most likely” actionable history.

This is where the default 3-year rule can be used as a practical planning baseline—especially when you’re building settlement models, comparing scenarios, or clarifying assumptions between parties.

Use the calculator

Use DocketMath to model alimony and child support scenarios with a Maryland (US-MD) lens.
Primary CTA: /tools/alimony-child-support

Run the Alimony Child Support calculation in DocketMath, then save the output so it can be audited later: Open the calculator.

Step-by-step: make the inputs time-aware (Maryland, US-MD)

1. Open the DocketMath alimony-child-support calculator
   Go to: /tools/alimony-child-support

2. Select jurisdiction

   • Choose Maryland (US-MD) so the tool uses the right jurisdiction lens and formatting.

3. Enter income inputs Typical categories include:

   • gross income or net income (depending on tool design)
   • tax/withholding assumptions (if offered)
   • additional income streams (if supported)

4. Enter child-related inputs Provide what the tool asks for, such as:

   • number of children
   • custody/placement factors (if included)
   • any special circumstances that the calculator supports

5. Set the timeline inputs This is where the 3-year default limitations rule lens becomes operational in your workflow:

   • choose a calculation window anchored to your reference date
   • if you’re modeling general limitations exposure, keep your “counted” window consistent with 36 months and the framework of Md. Code, Cts. & Jud. Proc. § 5-106

How outputs change when you change dates

When you adjust timeline inputs in DocketMath, you’ll typically see shifts like:

Practical checklist for using DocketMath responsibly

Related reading

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