Spreadsheet checks before running Alimony Child Support in Maine
5 min read
Published April 15, 2026 • By DocketMath Team
What the checker catches
Running an alimony or child support calculation in Maine is usually more error-prone in spreadsheets than in the law itself—because the spreadsheet tends to “accept” bad inputs silently. DocketMath’s alimony-child-support spreadsheet checker is designed to catch issues before you run the math, using Maine-aware defaults.
Here are the most common problems the checker targets:
- Missing or blank required inputs
- Examples: one parent’s income left blank, child count omitted, or the start date not provided.
- Date logic mistakes
- Checks for inconsistent timelines (for example, a filing date earlier than the relevant event date).
- Sign errors and improbable values
- Flags negative numbers in fields that should never be negative (gross income, monthly income, support duration).
- Also catches values that are orders of magnitude off (for example, income entered as annual when the sheet expects monthly).
- Jurisdiction-specific time-window mismatch
- Applies a general/default limitations period check using Maine’s general statute of limitations.
- Maine’s general SOL period referenced here is 0.5 years, tied to 17-A M.R.S. § 8 (general/default period).
- No claim-type-specific sub-rule was found for the scenario you’re running in this checker, so the checker treats the 0.5-year period as the general/default period rather than attempting to apply a more specialized limitation.
- Inconsistent units
- The checker looks for mismatched units (annual vs. monthly) and warns when the values don’t align with the calculator’s expected format.
Pitfall: A spreadsheet can compute “perfectly” even when the numbers are entered in the wrong period (annual vs. monthly). That can produce outputs that look credible but are mathematically consistent with the wrong assumptions. The checker focuses on preventing that silent failure.
To keep it practical, the checker’s job is to align your inputs with what the alimony-child-support calculator is expecting and to surface timing issues early—especially those tied to Maine’s general limitations period referenced above.
Quick overview: what gets checked (and why it matters)
| Check | What it prevents | Typical symptom in results |
|---|---|---|
| Blank/required fields | “Half-filled” calculations | Output shows zeros or NaNs; missing components |
| Date ordering | Timeline contradictions | Effective dates don’t make sense; outputs jump |
| Negative/improbable numeric values | Invalid arithmetic | Large swings that don’t match reality |
| Unit mismatch | Overstated/understated amounts | Monthly result looks off by ~12x or similar |
| Maine SOL window (general/default) | Running stale or non-comparable scenarios | You may compare outcomes across timeframes that shouldn’t be treated the same |
When to run it
Use the checker before you start generating scenarios or exporting numbers for sharing. A clean workflow saves time because you’ll correct data once—rather than rerunning multiple versions.
Run DocketMath’s spreadsheet checker at these points:
- Before the first calculation
- As soon as you’ve entered the minimum required inputs, run the checker to catch blank fields, unit mismatches, and date logic errors.
- After every spreadsheet “refactor”
- If you copy/paste columns, change the format of dates, or switch from monthly to annual values, run it again.
- When you add or edit dates
- Any change to filing date, event date, or effective date can affect timing checks.
- Because this checklist references Maine’s general/default limitations period (0.5 years) under 17-A M.R.S. § 8, date edits can shift whether two scenarios are comparable in the way your spreadsheet assumes.
- When you produce a “shareable” output
- If you’re going to send numbers to someone else, run the checker as a final QA pass so the output doesn’t rely on hidden spreadsheet assumptions.
A useful habit: treat the checker like you’d treat a spellcheck in a legal draft—small data issues are easier to fix early than after you’ve built a narrative around the numbers.
Warning: This post uses general/default limitations context based on 17-A M.R.S. § 8 and a 0.5-year general SOL period. The checker does not claim a claim-type-specific limitations rule for every possible situation. Use the checker to detect spreadsheet errors and timing inconsistencies, not to guarantee a legal conclusion about eligibility.
Try the checker
If you want a fast, low-friction way to validate your spreadsheet inputs in Maine, start with DocketMath’s alimony-child-support tool.
- Then follow this order:
- Enter incomes and child details using the units the tool expects (match the calculator’s input design—don’t rely on what “sounds right”).
- Add dates carefully and keep them internally consistent.
- Run the spreadsheet checker step (or the tool’s built-in validation, if integrated).
- Fix flagged items and rerun until warnings clear.
- Generate scenarios only after the inputs pass the checks.
What to watch while you test (input → output behavior)
Use these mini-checkpoints to confirm the tool is reading your spreadsheet correctly:
- Change one unit at a time
- If you switch an income field from annual to monthly, your computed amounts should change in the expected direction (often roughly a 12x relationship, depending on the tool’s design).
- Adjust dates by a small amount
- If you move a date forward by a few weeks, your outputs may shift, but the change should be coherent—not discontinuous—unless your dates cross a boundary the calculator uses.
- Try a deliberate bad value once
- Enter a negative number in a field the tool expects to be positive.
- The checker should stop you or flag the issue rather than letting you compute a misleading result.
If you’re building multiple versions of a spreadsheet (for example, “baseline,” “low-income,” “high-income”), run the checker for each version after you edit—spreadsheet errors love to travel with copy/paste.