Spreadsheet checks before running Alimony Child Support in California

What the checker catches

Before you run DocketMath’s Alimony Child Support calculator for California (US-CA), a spreadsheet-style preflight check can prevent common downstream mistakes—especially around whether you’re even in the right time window to calculate or claim amounts.

This spreadsheet checker focuses on timeline and data integrity issues that frequently break calculations.

1) Wrong assumptions about the statute of limitations (SOL)

California uses a default/general SOL period of 2 years for the claim-type referenced in your workflow, grounded in CCP §335.1. Under your jurisdiction data, no claim-type-specific sub-rule was found, so the checker treats the 2-year period as the general/default.

Why that matters in a spreadsheet: your sheet needs a clean mapping from event date(s) to a “lookback” boundary that reflects:

• Start date for the relevant period you’re testing
• Trigger date (often the date a payment obligation arises or an event occurs in your dataset)
• Current date (or “as of” date you’re calculating to)

If those columns are inconsistent, the calculator output may look plausible while being based on amounts you shouldn’t include in a SOL-sensitive workflow.

2) Date format errors that quietly skew results

Spreadsheet failures commonly come from:

• Mixed formats (e.g., 01/02/24 interpreted as Jan 2 vs Feb 1)
• “Text dates” that don’t behave like real dates
• Rows sorted alphabetically instead of chronologically

The checker flags these by validating that:

• Each date field is a true date value (not text)
• Your dataset sorts by date in a consistent direction (ascending or descending)
• No blank dates exist in rows that feed calculation inputs

3) Amount mismatches that propagate into the running totals

Even when dates are correct, totals can drift if your spreadsheet stores values inconsistently. Common causes include:

• Income figures stored as monthly in one table and annual in another
• Payment amounts stored in different formats (e.g., "$1,200" vs 1200 with commas)
• Rounding differences (whole dollars vs two-decimal cents)

DocketMath can only calculate what your sheet provides. The checker ensures the spreadsheet’s “source of truth” is consistent so that results change predictably when you adjust inputs.

4) Jurisdiction mismatch inside multi-state spreadsheets

If you reused a template from another state, you may accidentally:

• Use the wrong SOL window
• Use an input schedule that assumes a different jurisdictional rule set

For US-CA workflows, the checker enforces that California-specific settings are selected before running alimony-child-support calculations.

When to run it

Run the spreadsheet checker at three points—not only once. This keeps “silent errors” from surviving into your final numbers.

Run the checker before importing a spreadsheet into the Alimony Child Support workflow. It is especially helpful when you have multiple entries or when a teammate provided the inputs.

1) Before you enter any “final” numbers

Do a first pass as soon as you structure the sheet:

• Add and normalize your date columns
• Lock down your units (monthly vs annual)
• Confirm jurisdiction is set to US-CA

This prevents rebuilding after you discover a formatting or timeline issue.

2) After you import or paste data

If you paste from bank statements, court documents, or another spreadsheet:

• Run the checker immediately
• Fix any rows where dates become text
• Verify any currency conversions and unit consistency

Spreadsheet imports are where most “invisible” corruption happens.

3) Just before you export results or share outputs

When you’re ready to generate a report or run a second iteration:

• Re-check the SOL lookback boundary logic (default 2-year window, CCP §335.1)
• Confirm the “as of” date you used in the sheet matches what DocketMath will use

Try the checker

Use DocketMath to turn spreadsheet readiness into a repeatable workflow. The goal is simple: confirm your inputs won’t produce misleading totals before you calculate.

Upload the spreadsheet, review the warnings, and then run the calculation once the inputs are clean: Try the checker.

Step-by-step workflow (practical)

1. Open the tool: DocketMath Alimony Child Support
2. Select jurisdiction: **California (US-CA)
3. In your spreadsheet, ensure you have these minimum columns (names can vary, but the meaning should match):

   • Event/Trigger Date (the date your dataset uses to anchor the SOL logic)
   • As-of Date (or confirm a consistent “today” date)
   • Payment Period (monthly/weekly label if applicable)
   • Amount (numeric, consistent units)
   • Income or Support Inputs (whatever your worksheet provides)

What to look for in the checker output

Use this checklist to identify issues quickly:

Spreadsheet readiness checklist

How output changes when you fix inputs

When you correct common issues, you’ll typically see:

• Lower totals after removing rows that fall outside the 2-year lookback boundary tied to CCP §335.1
• Different per-period averages after unit normalization (annual vs monthly)
• Fewer calculation anomalies (less “spiky” output) after rounding and date alignment fixes

A typical “before vs after” scenario

• Before: mixed date formats cause some rows to appear earlier than they are
• After: normalized dates push those rows outside the SOL lookback
• Result: totals decrease, and per-period calculations become stable

Run it now

Start with this primary call to action:

• Run DocketMath: Alimony Child Support

Gentle note: This is a data-validation workflow, not legal advice. For questions about your specific situation or legal deadlines, consider consulting a qualified professional.

Related reading

• Alimony & Child Support Estimator Guide for Alabama
• Alimony & Child Support Estimator Guide for Arizona
• Alimony & Child Support Estimator Guide for Colorado