Inputs you need for Alimony Child Support in Massachusetts
6 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
DocketMath’s alimony-child-support calculator for Massachusetts (US-MA) helps you collect the key numbers that drive both child support and alimony calculations. Before you run anything, assemble the inputs below so the tool can calculate from the same set of facts.
Note: This is about data collection and calculator inputs, not legal advice. Court outcomes depend on case-specific facts and judicial discretion.
A. Parties and case context (minimum identifiers)
- ☐ Who pays / who receives (payer and payee)
- ☐ Number of children for the child support portion
- ☐ Child ages (or birthdates) for each child
- ☐ Parenting time split (commonly: who has more time and approximate overnights per year, if you track it)
B. Income information for both parents (child support + alimony rely on earnings)
For each parent, gather:
- ☐ Gross employment income (paystubs or last full year W-2s)
- ☐ Self-employment income, if applicable
- ☐ Business income summary (or the last 1–2 years of tax returns)
- ☐ Bonuses, commissions, overtime (if they’re regular)
- ☐ Other taxable income (e.g., rental income, interest/dividends—only what applies to your situation)
- ☐ Health insurance premium for the parent paying support (if you plan to include it where applicable)
- ☐ Work-related deductions you can substantiate (the calculator may ask for specific entries rather than broad assumptions)
C. DocketMath income adjustments you may need to provide
Depending on what you enter, DocketMath may request specific earnings details such as:
- ☐ Pre-tax versus post-tax pay amounts
- ☐ Monthly income (often the easiest way to stay consistent)
- ☐ Annualized income when income varies (e.g., seasonal work)
If you don’t have clean monthly figures, compute a reasonable average using the last tax year and/or the most recent pay period—then keep your method consistent across both parents so the comparison is fair inside the calculator.
D. Alimony-specific inputs (so the calculator doesn’t guess)
For alimony, gather:
- ☐ Length of marriage (in years and months)
- ☐ Current ages of both spouses
- ☐ Employment status (employed, unemployed, underemployed)
- ☐ Any documented income limits or earning capacity constraints you plan to reflect in numbers you enter (e.g., ability to work, training plans)
E. Expense inputs (often critical for alimony, sometimes for child support)
The calculator may ask for:
- ☐ Health insurance costs for dependents
- ☐ Large ongoing obligations you can express as monthly amounts (for example, additional household expenses tied to the children or existing support obligations)
Warning: Avoid “category shopping” (randomly adding expenses to force a desired outcome). Use what you can document or at least reconcile to credible records.
F. Timing-related context (helps you interpret results)
Even though the tool focuses on math, you’ll likely want to track the timing of payments:
- ☐ Order effective date you’re modeling (or the date you expect to start)
- ☐ Whether amounts are hypothetical (planning) versus tied to an existing order
Where to find each input
Use these sources to assemble the numbers DocketMath needs. Keeping your source consistent reduces mismatches later.
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 sources
- Paychecks / paystubs
- Best for: hourly wage, overtime, regular deductions, current monthly earnings
- W-2s and/or 1099s
- Best for: confirming annual employment income and contractor/self-employment income
- Last filed tax return
- Best for: averaging fluctuating income, verifying total taxable income, and capturing non-wage income
Parenting time and child details
- Birth certificates / child records
- Best for: child birthdates and ages
- Shared calendar / parenting plan
- Best for: actual overnights and schedule regularity
Marriage and spouse details (alimony)
- Marriage certificate
- Best for: marriage date (start date)
- Birthdates
- Best for: spouse ages used in duration/qualification inputs
Insurance and obligations
- Insurance premium statements
- Best for: health insurance monthly premium amounts
- Court orders or proof of existing payments (if any)
- Best for: ongoing obligations you may need to enter accurately
One practical workflow (about 60 minutes)
- ☐ Export last 12 months of pay data (or use the latest full year + latest paystub)
- ☐ List income sources for each parent and compute a monthly average
- ☐ Collect child ages and estimate parenting time consistently
- ☐ Enter marriage length and spouse ages
- ☐ Add insurance premiums and any recurring obligations you plan to include
Run it
When you’re ready, run DocketMath’s calculator here: /tools/alimony-child-support.
- Select Massachusetts (US-MA) within the tool (jurisdiction-aware rules apply).
- Enter the inputs in the same units the tool requests (commonly monthly amounts).
- Review the output sections:
- Child support estimate (primarily driven by both parents’ incomes, children count/ages, and parenting time inputs)
- Alimony estimate (driven by marriage length, ages, and the income-related entries you provide)
- If results look unexpectedly high or low, use the tool output to spot which inputs dominate:
- Changing monthly gross income for either parent typically moves support amounts the most.
- Adjusting parenting time often materially affects child support calculations.
- Updating marriage duration and spouse ages has a large impact on alimony modeling.
Statute of limitations context (general information)
Massachusetts provides a 6-year general statute of limitations under Mass. Gen. Laws ch. 277, § 63. The rule above is the general/default period; based on the provided overview, no claim-type-specific sub-rule was identified. Limitations analysis can depend on procedural posture and the specific type of enforcement or filing—so treat this as timeline context, not a promise about any particular deadline in your case.
Pitfall: If the tool expects monthly income and you enter annual income (or vice versa), results can distort dramatically. If you see unusually high or low outputs, confirm unit conversion first.
Quick sensitivity checklist (what to test)
Use the tool to sanity-check your model with small, controlled updates:
- ☐ If you’re unsure about income consistency, run once using conservative monthly averages and once using recent higher/lower pay
- ☐ If parenting time inputs are estimates, try a “most likely” schedule and a “more conservative” schedule
- ☐ Confirm insurance premiums are entered as monthly figures