Common Alimony Child Support mistakes in Colorado
6 min read
Published April 15, 2026 • By DocketMath Team
The top mistakes
Run this scenario in DocketMath using the Alimony Child Support calculator.
Colorado alimony and child support orders can look straightforward on paper, but small errors often create outsized consequences—especially when payments, income, or timelines are off. Below are the most common mistakes people make in Colorado, along with what typically goes wrong when you calculate or draft terms.
Warning: This is practical information, not legal advice. Colorado support and maintenance rules are fact-specific, so treat this as a checklist to reduce avoidable error.
1) Using the wrong income picture (gross vs. net, or missing income)
A frequent error is calculating support using an incomplete or incorrect income base. In Colorado practice, the “income” treatment depends on the type of income and the circumstances, but errors commonly come from:
- relying on paystubs without annualizing variable pay (bonus/commission/overtime),
- forgetting regular side income,
- ignoring documented adjustments (where appropriate and consistently applied),
- using only one party’s income when the analysis requires comparing both parties.
Typical impact in DocketMath: if your input income is too low or too high, the calculator’s recommended range/order terms can shift accordingly—sometimes significantly.
2) Not accounting for parenting-time changes
Child support in Colorado can be sensitive to parenting time, and the schedule details matter. A common error is selecting an oversimplified parenting-time assumption (for example, “50/50” when the actual schedule is week-to-week, holiday-dependent, or changes during the year).
Typical impact in DocketMath: parenting-time inputs can change the outcome because they affect how the guideline worksheet allocates the cost share between households.
3) Mixing up “child support” versus “alimony” obligations
People sometimes treat alimony and child support as if they behave the same way. They don’t.
- Child support is tied to guideline methodology and child-related factors.
- Alimony (maintenance) is tied to the statutory framework and the parties’ circumstances.
Common drafting/implementation mistakes include:
- stating that alimony “replaces” child support without recalculating correctly,
- trying to offset obligations manually instead of using the payment structure the order actually requires,
- entering one obligation into DocketMath while intending to calculate the other.
Typical impact in DocketMath: outputs will not reconcile if you use the calculator for the wrong obligation type or combine them incorrectly.
4) Missing a date or effective-period issue (retroactivity vs. prospective order)
Another common error is forgetting that Colorado orders can operate from a specific effective date and that amounts may change over time when circumstances change.
If one party’s income, employment, or parenting time changes, then the “from” date and “through” date for each set of numbers matter.
Typical impact in DocketMath: if you run only one snapshot, you may understate arrears or misstate how much should have been paid during a specific period.
5) Overlooking tax/withholding mechanics when the order requires specific handling
Even if the amount is correct, operational details can cause problems when the order requires a particular payment method (such as withholding).
Mistakes often look like:
- the payment method in the final draft doesn’t match what the order requires,
- withholding doesn’t start promptly after an income change,
- payment timing doesn’t align with the schedule used in calculations.
Typical impact in DocketMath: the tool helps with calculation logic, but it won’t correct “what was owed when” or fix missing withholding instructions in the final order language.
6) Forgetting about modifications and the “stability” of inputs
People sometimes treat every input as permanent even though certain factors are likely to change—job changes, bonus structures, overtime, or parenting-time schedule adjustments.
A practical error is failing to document:
- how income changed (and when),
- whether the change is temporary vs. ongoing,
- how parenting time is actually being exercised.
Typical impact in DocketMath: projections may be accurate today but become stale quickly; running updated scenarios after key changes can prevent surprise gaps later.
How to avoid them
The fastest way to reduce errors is to build your DocketMath inputs like you’re preparing for review: precise, consistent, and aligned with how Colorado treats parenting time and income in the calculation.
Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.
Step-by-step checklist (use before you finalize any numbers)
- Use annual figures or consistent methods to convert variable pay (bonus/commission/overtime) into an annual baseline.
Include the consistent income streams you intend the order to reflect.
Enter the parenting-time schedule that matches practice, not a rough approximation.
If the schedule changed mid-year, consider separate runs for distinct periods.
Run DocketMath for each obligation type you intend to order.
Avoid “netting” them together unless the order structure clearly does so and the calculations support that approach.
Decide whether your numbers are prospective only, include a retro period, or reflect a change-over window.
Create separate runs when inputs change on a specific date.
If the order requires withholding, ensure the operational terms are reflected in the final draft.
Verify payment frequency matches the entered assumptions.
Inputs that strongly affect DocketMath outputs
Use this quick guide to anticipate how errors change results:
| Input you verify | What goes wrong if wrong | How outputs may change |
|---|---|---|
| Annual income (both parties, where relevant) | Support based on incomplete or incorrect pay | Higher income → higher calculated obligation; lower income → lower |
| Parenting-time schedule | Misallocated parenting share | Parenting-time adjustments can shift the guideline outcome |
| Obligation type separation | Mixing alimony logic with child support logic | Outputs may not align with what you intend to request |
| Effective dates / time windows | Under/overstatement of totals owed | Incorrect period totals or arrears estimates |
| Payment mechanics (timing/withholding) | Correct amount, wrong implementation | Confusion about “what was owed when” |
Scenario-testing: run more than one “what-if”
DocketMath is especially helpful for sensitivity testing:
- Run a baseline scenario using your best-supported inputs.
- Run a second scenario using reasonable alternatives (for example, different annualization of bonus, or a parenting-time schedule change).
- Compare differences to identify which facts matter most before you lock numbers into documents.
Pitfall: Relying on a single snapshot without testing alternative reasonable schedules can lead to an order that doesn’t match the real-world timeline.
Keep a documentation trail for every major input
Colorado disputes often turn on what you can show. To reduce avoidable friction:
- save paystubs and year-to-date summaries,
- keep a record of parenting-time schedule changes,
- note any exceptional income (one-time bonuses, unusual overtime) and how you treated it in the calculation.