Spreadsheet checks before running Alimony Child Support in Maryland
5 min read
Published April 15, 2026 • By DocketMath Team
What the checker catches
When you’re calculating alimony and child support in Maryland, the biggest avoidable problems are often not the math—they’re the dates, timeline alignment, and input consistency that decide what period the numbers are supposed to cover. DocketMath’s alimony-child-support checker (jurisdiction-aware for US-MD) is built to help you catch those spreadsheet issues before you rely on the output.
Here are the main spreadsheet checks it’s designed to surface:
Missing or inconsistent dates
- Examples: an incorrect filing date, an arrears start date that’s earlier than the operative order date, or multiple conflicting “effective” dates inside the same workbook.
- Why it matters: support calculations are date-sensitive—small date mismatches can produce large changes in arrears totals.
**Statute of limitations exposure (general rule)
- The checker uses Maryland’s general/default 3-year period under Md. Code, Cts. & Jud. Proc. § 5-106.
- Important clarification: Based on the information available for this brief, no claim-type-specific sub-rule was identified. So the checker applies the general rule conservatively rather than attempting to classify each claim type.
- Practical effect: if your worksheet models an arrears period that extends beyond what the general 3-year baseline would cover, the checker flags the risk so you can adjust the period you’re modeling.
Order vs. arrears alignment
- A common spreadsheet error is using an arrears window that isn’t properly anchored to the operative timeline (for example, the order effective date or any relevant modification-related date you’re using).
- Practical effect: the checker helps you confirm the arrears window is consistent with the dates you entered, reducing the chance you’re calculating for the wrong timeframe.
Unit mismatches and transcription errors
- Spreadsheet failures often come from input formats rather than formulas, such as:
- weekly vs. biweekly vs. monthly income fields,
- mixing gross and net income values,
- duplicate income lines, or
- leaving an income source as 0 when it should be included.
- Practical effect: the checker encourages you to normalize input frequency and confirm income is represented the way the worksheet expects.
Inadvertent “stale” inputs
- Support calculations usually depend on multiple dates and income lookbacks. A sheet can be “updated” but still contain older dates (for example, older income start dates) that don’t match the period you think you’re calculating.
- Practical effect: the checker helps you verify that your current date range and your worksheet’s underlying assumptions agree.
**Jurisdiction-code guardrails (US-MD)
- If a workbook is accidentally set up as if it were for another state—or uses the wrong configuration—the output can look reasonable while being jurisdiction-incompatible.
- Practical effect: DocketMath’s jurisdiction-aware rules are intended to catch those configuration inconsistencies.
Pitfall to watch: A spreadsheet can be internally consistent and still unusable if the arrears window (or the effective start date you used) falls outside the 3-year general limitations baseline described by Md. Code, Cts. & Jud. Proc. § 5-106.
Maryland timing rule the checker is built around
For the limitations baseline, Maryland uses a 3-year general statute of limitations under Md. Code, Cts. & Jud. Proc. § 5-106 (general/default period).
Because no claim-type-specific limitations sub-rule was identified for this brief, the checker intentionally uses the general rule rather than trying to tailor limitations by claim category.
Gentle note: This tool helps with spreadsheet validation and input consistency. It doesn’t replace reviewing your actual documents and dates with a qualified professional.
When to run it
Run the checker anywhere you’re using a spreadsheet to produce “final” numbers or you’re working through multiple revisions. The ideal approach is to treat the checker like a preflight step before you export, share, or rely on the result.
A practical cadence:
Before you compute a first draft
- Set your key timeline fields (order effective date / relevant period start / relevant period end) and confirm the income frequency inputs first.
- Then run the checker to catch timeline and input issues early.
After every meaningful edit
- If you change any date, add or remove an income source, adjust income frequency (weekly/biweekly/monthly), or modify the arrears window—rerun the checker immediately.
Right before exporting or filing anything
- Use it as a final “release gate” to reduce the chance you’re working from a period mismatch or a stale set of assumptions.
Quick self-check list:
Try the checker
Ready to validate your spreadsheet inputs with Maryland-aware checks? Start with DocketMath’s alimony-child-support tool:
- Primary CTA: /tools/alimony-child-support
If you already have spreadsheet outputs, you can still use DocketMath to “preflight” your assumptions by comparing:
- your worksheet’s date range choices to the limitations baseline (the 3-year general rule under Md. Code, Cts. & Jud. Proc. § 5-106), and
- your income frequency and date alignment to the tool’s jurisdiction-aware expectations for US-MD.
A simple run sequence you can follow:
- Enter your key dates (operative start/end for the period you’re modeling)
- Normalize income to the expected frequency format
- Run alimony-child-support in DocketMath
- Re-run the checker after any date or income edits
Warning: Use the checker to improve input quality and reduce avoidable date/timeline/limitations errors. It does not provide legal advice and cannot confirm the correctness of case-specific outcomes.