Spreadsheet checks before running Alimony Child Support in Colorado
5 min read
Published April 15, 2026 • By DocketMath Team
What the checker catches
Run this scenario in DocketMath using the Alimony Child Support calculator.
DocketMath’s alimony-child-support spreadsheet checker for Colorado (US-CO) is built to prevent the most common “silent errors” that happen before you run calculations for alimony and child support. Think of it as a preflight checklist: it doesn’t replace court orders or legal advice, but it helps you avoid feeding incorrect or inconsistent numbers into the calculator.
Here are the issues the checker is designed to catch before outputs are produced:
Missing required inputs
- Example: you enter a parenting schedule and one party’s income, but leave the other party’s gross income blank.
- Typical impact: the spreadsheet may calculate incompletely or fall back on unintended defaults.
Inconsistent income fields
- Example: one side is entered as “monthly” while the other is entered as “annual.”
- Typical impact: results can swing dramatically because support calculations scale directly with income.
Negative or impossible values
- Example: a gross income entry of
-500, or a time period of0months. - Typical impact: many spreadsheets will still compute unless you stop them early.
Schedule math mismatches
- Example: parenting time entries that don’t reconcile to the expected total (such as totals that don’t match the year framework you’re assuming).
- Typical impact: child support outputs can be sensitive to parenting-time assumptions.
Wrong units for time
- Example: entering “52” as days-per-year while your sheet interprets it as weeks-per-year (or vice versa).
- Typical impact: parenting time can be accidentally overstated or understated.
Dependents and household consistency issues
- Example: the spreadsheet indicates one number of children, but related cells reference a different number.
- Typical impact: the worksheet may “run,” but outputs won’t match your intent.
Pitfall: Your worksheet might pass a basic formula check yet fail a unit consistency check (annual vs. monthly, days vs. weeks). That’s how you can get results that look plausible but are still wrong.
To keep things practical and actionable, focus on these high-leverage areas in your sheet before using DocketMath:
| Area to verify | Quick self-check | Why it matters for outputs |
|---|---|---|
| Income units | Are both parties entered in the same time basis (monthly or annual)? | Support calculations scale with income |
| Parenting time units | Are you using a consistent approach (days/weeks) and do totals reconcile to the same year assumption? | Parenting time affects the calculation inputs |
| Time period fields | Do dates/time ranges use the same assumptions (e.g., months per year = 12)? | Prevents calculation drift |
| Child count references | Is the child count consistent across all related cells? | Avoids mismatched dependencies |
| Deductions/adjustments (if used in your sheet) | Do adjustment cells exist for every scenario you intend to model? | Prevents partial modeling |
When to run it
Run the checker before you run DocketMath alimony-child-support calculations—not after. The sequencing matters because spreadsheet errors are usually easiest to fix at the input stage, when you can still clearly see what you changed.
A practical workflow for Colorado (US-CO) modeling is:
Assemble your inputs in one place
- Keep everything the checker expects in a single worksheet area (or a consistent cell block).
- Avoid mixing “draft” and “final” entries in the same column.
Run the checker immediately after you complete edits
- Especially after updating:
- gross income numbers
- parenting-time schedule entries
- time unit conversions (days ↔ weeks; annual ↔ monthly)
- child count / dependent-related entries
Lock assumptions before exploring scenarios
- Example: if you test a “higher income” scenario, change only the income cells.
- Don’t also change parenting time units (days vs. weeks, annual vs. monthly) unless that’s truly part of the scenario.
Re-run the checker for every scenario that changes inputs
- Scenario modeling is where errors slip in—especially when comparing outputs generated from different assumptions.
Here’s a simple checklist you can use every time:
DocketMath’s tools are designed to be jurisdiction-aware, but input integrity still matters. The checker helps ensure the spreadsheet is internally coherent before you rely on calculator outputs.
Try the checker
Want to validate your spreadsheet before running alimony + child support in Colorado (US-CO) using DocketMath?
- Start at: /tools/alimony-child-support
A quick “do this in order” approach:
- Confirm the same unit basis for both parties’ income.
- Ensure your parenting-time values reconcile to a single consistent year framework.
- Use the checker to identify missing fields, unit conflicts, and mismatched totals.
- After it passes, run the DocketMath calculations for your selected scenario.
If you want a fast sanity check, test one scenario first:
- Use one income set and one parenting schedule set.
- Confirm the checker passes.
- Then duplicate the scenario rows and adjust only the variables you intend to test.
Warning: If your sheet “passes” but assumptions were entered using different units in different places, the output may still be misleading. The checker exists to prevent that exact problem—so don’t skip it when you start changing units.
(As a reminder: this content is for workflow support, not legal advice. Court outcomes and legal requirements depend on the specific facts of your case.)