Spreadsheet checks before running Alimony Child Support in Georgia

What the checker catches

Before you calculate alimony and child support in Georgia, you can reduce avoidable mistakes by running a jurisdiction-aware pre-check in DocketMath. The goal isn’t to decide the case outcome—it’s to catch “plausible but wrong” spreadsheet errors that often slip through when dates, units, and worksheet logic aren’t consistent.

Below are the most common items this kind of checker is designed to spot, using Georgia’s baseline timing framework.

• Missed or incorrect time-window assumptions

  • Georgia’s general SOL (statute of limitations) baseline is 1 year for the timing framework described here.
  • This baseline is from O.C.G.A. § 17-3-1.
  • Important: this is the general/default period. The brief note indicates no claim-type-specific sub-rule was found for the inputs covered by this checker. That means the checker intentionally applies the general baseline rather than assuming a specialized SOL track.

• Date fields that break calculations

  • Empty dates (for example, a blank “date of filing” or “effective date”)
  • Incorrect date formats (e.g., MM/DD vs. DD/MM depending on how your sheet is set up)
  • Start date after end date, which can invert your date range and distort totals or eligibility windows

• Mismatch between worksheet logic and jurisdiction-aware inputs

  • If your spreadsheet uses a different “starting event” than the DocketMath workflow expects (for example, one sheet starts from filing while another starts from separation), the computed numbers may not align.
  • The checker looks for inconsistencies in how your worksheet is “wired” relative to the US-GA jurisdiction context.

• Data entry errors that change results dramatically

  • Negative or zero values for income/expense fields that the calculator expects to be positive (or left blank)
  • Stray characters from copy/paste (like commas, currency symbols, or extra spaces) that can cause values to be read incorrectly
  • Rounding inconsistencies, such as one tab rounding to whole dollars while another uses cents (small differences can compound across multiple months)

• Unit and frequency problems

  • Mixing weekly and monthly income without converting to a consistent basis
  • Treating annual income as if it were monthly (or vice versa)
  • Forgetting to align payment frequency with how totals are aggregated in the worksheet (weekly vs. biweekly vs. monthly)

Pitfall to watch: even if income numbers are correct, a single wrong date can cause the SOL-based logic to evaluate the wrong period. That can change the feasibility window your spreadsheet is modeling—sometimes without obvious “red flags” in the amounts themselves.

If your spreadsheet uses multiple tabs (imports → cleaning → calculation → summary), the checker’s value is even higher: it helps you verify the plumbing before you trust the outputs.

When to run it

Run the checker at three practical moments: before calculation, after input changes, and right before sharing. That keeps your workflow from “locking in” spreadsheet errors.

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) Right before you run Alimony + Child Support calculations

Use the checker once your worksheet has the core inputs in place but before you generate final results. This is usually the fastest time to fix issues, because you haven’t exported or relied on the outputs yet.

2) After any input update that affects dates or timing

Re-run the checker whenever you change anything that could affect the modeled time window, including:

• a filing date / effective date
• a separation date
• any child-related milestone date used in the model
• any date range that defines “how long” a component applies

Because Georgia’s general SOL baseline is 1 year under O.C.G.A. § 17-3-1, date edits can be high-impact.

3) Before you share results with clients, partners, or your own review team

If anyone else will review your worksheet (or if you’ll use the numbers in a workflow where formatting matters), run the checker to reduce the chance that formatting, units, or hidden spreadsheet logic produces different interpretations.

A simple workflow that works well:

• ✅ Run checker → fix flagged issues
• ✅ Generate results in DocketMath
• ✅ Export/paste results into your spreadsheet (if needed)
• ✅ Run checker again if you changed any dates or frequencies during export/import

Try the checker

If you want a fast, jurisdiction-aware preflight for US-GA calculations, start in DocketMath here:

• Primary CTA: Run Alimony + Child Support — Georgia

As you test it, treat the checker like a spreadsheet “unit test.” Your goal is to eliminate structural problems first, then focus on substantive numbers.

Recommended input checklist (Georgia / US-GA)

Tick through these before trusting outputs:

How outputs change when the checker flags issues

When the checker finds a mismatch, you typically see noticeable changes after you correct it:

If you don’t get any flags but the outcomes look surprising, check frequency alignment and date range definitions first. Those are the most common drivers of “looks right, is wrong” spreadsheet behavior.

Quick reference: Georgia SOL baseline used here

• General SOL period: 1 year
• Statute: O.C.G.A. § 17-3-1
• Context note: This is presented as the general/default period; the brief indicates no claim-type-specific sub-rule was found.

Statute text (for reference): https://law.justia.com/codes/georgia/2021/title-17/chapter-3/section-17-3-1/?utm_source=openai

Related reading

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