Worked example: Alimony Child Support in Alaska
6 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
Run this scenario in DocketMath using the Alimony Child Support calculator.
This worked example shows how DocketMath can translate Alaska’s jurisdiction-aware rules into a calculation workflow for alimony and child support. It’s a practical “how it runs” walkthrough—not legal advice. If you’re preparing filings or a settlement proposal, use these outputs as a starting point and verify inputs with the court record and any local practice.
Scenario (Alaska; US-AK)
Assume these facts for a single example calculation:
Parties
- Payor: Alex
- Payee: Jamie
Children
- Number of children: 2
Income
- Alex (payor) monthly gross income: $6,500
- Jamie (payee) monthly gross income: $4,200
**Parenting time (rough)
- Alex overnights per year: 120
- Jamie overnights per year: 245
- (In other words: the children spend somewhat more time with Jamie.)
Support-related settings
- Requested support start month (for example run): January
- Additional deductions/credits: None added (so the example stays focused)
Alaska timing rule (default used here)
DocketMath includes jurisdiction-aware timing logic. For Alaska, the general/default statute of limitations period shown in this example is:
- 2 years under Alaska Statutes § 12.10.010(b)(2)
Source: https://law.justia.com/codes/alaska/title-12/chapter-10/section-12-10-010/?utm_source=openai
No claim-type-specific sub-rule was found for this specific calculator workflow, so DocketMath uses the general/default period rather than a narrower carve-out.
Note: This example uses Alaska’s general SOL (2 years) because no claim-type-specific sub-rule was identified for this calculator run. That’s why the “timing” output is tied to the default rule.
Inputs you would enter in DocketMath (/tools/alimony-child-support)
Use the calculator at /tools/alimony-child-support.
You’ll typically provide values like:
- Payor monthly income
- Payee monthly income
- Number of children
- Parenting time (or overnights)
- Any additional adjustments (if applicable)
- Optional start month/date for “timing” outputs
For this walkthrough, we’ll feed the example values above.
Example run
Let’s run the scenario through DocketMath using the calculator designed for alimony + child support in Alaska (US-AK, jurisdiction-aware rules). The key outputs you should expect from the tool are usually split into:
- A child support component (based on the inputs affecting child support)
- An alimony component (based on the inputs that drive alimony in the tool’s workflow)
- A combined view
- A timing/SOL check using the general default rule
1) Child support component (directional outcome)
With:
- Alex earning $6,500/month
- Jamie earning $4,200/month
- 2 children
- Parenting time split that favors Jamie (245 overnights vs. 120)
…DocketMath will compute a monthly child support estimate where:
- Higher payor income increases the obligation
- More parenting time with the payor typically reduces net child support, while more time with the payee increases it
- More children generally increases support obligations and complexity
In this example run, the tool would produce a monthly child support amount (displayed in the output after you enter the values). Since DocketMath is the calculator source, the precise figure should come directly from the /tools/alimony-child-support run.
2) Alimony component (directional outcome)
For alimony, DocketMath’s workflow will generally be sensitive to:
- Income gap ($6,500 vs. $4,200)
- Parenting-time impact (in many workflows, parenting time and household economics interact)
- Any user-provided toggles/inputs related to duration or need/capacity (depending on how the tool captures alimony parameters)
Given the facts:
- Income gap exists
- Jamie has somewhat more parenting time
…the alimony output may be smaller than child support, but it can still be non-zero. Again, use the /tools/alimony-child-support output for the exact number for this scenario.
3) Combined monthly estimate
DocketMath then aggregates:
- Monthly child support
- Monthly alimony
into a combined monthly obligation figure.
A combined total is often what matters for budgeting, because it can drive:
- proposed payment amount per month
- affordability checks
- negotiating ranges
4) Timing/SOL output (Alaska default rule)
DocketMath also computes a timing check using the general/default statute of limitations.
For Alaska:
- General SOL period: 2 years
- Statute: Alaska Statutes § 12.10.010(b)(2)
https://law.justia.com/codes/alaska/title-12/chapter-10/section-12-10-010/?utm_source=openai
Because no claim-type-specific sub-rule was found, the tool applies this 2-year default consistently for this calculator run.
Warning: A statute of limitations (SOL) timing output is not the same thing as eligibility or the ultimate merits of a support claim. It’s a procedural timing layer that affects whether a claim is timely, not whether support is substantively justified.
Sensitivity check
Now let’s change a few inputs to see how outputs typically respond in a tool like DocketMath. The goal is to understand directionality so you can sanity-check results.
To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.
Sensitivity matrix (what changes when you adjust inputs)
| Change to input | Example change | Likely direction on child support | Likely direction on alimony |
|---|---|---|---|
| Payor income increases | $6,500 → $7,000 | ↑ (payor capacity increases) | ↑ or stays ↑ (income gap widens) |
| Payee income increases | $4,200 → $5,000 | ↓ (payee capacity increases) | ↓ (reduced need/gap in many models) |
| Payor parenting time increases | 120 → 180 overnights | ↓ (more time with payor reduces net obligation) | Often ↓ (less imbalance tied to caregiving) |
| Number of children increases | 2 → 3 | ↑ (support obligation generally increases) | Could ↑ (caregiving burden/costs increase), depending on the tool’s alimony workflow |
Three quick “what-if” checks
Check A: Parenting time shift
- Change: Alex overnights 120 → 180
- Why it matters: more equal time usually reduces the net child support transfer in many frameworks.
- What you do in DocketMath:
- Update parenting time inputs
- Re-run /tools/alimony-child-support
- Expected result:
- Child support output should move downward.
- Alimony may also move downward, but the magnitude depends on the tool’s alimony assumptions.
Check B: Payor income increase
- Change: Alex monthly gross income $6,500 → $7,500
- Rationale: capacity increase tends to increase the support numbers.
- Expected result:
- Child support likely increases.
- Alimony likely increases or stays higher, especially if the income gap grows.
Check C: Payee income increase
- Change: Jamie monthly gross income $4,200 → $5,400
- Rationale: increased payee earning capacity can reduce net transfer.
- Expected result:
- Child support decreases.
- Alimony may decrease, depending on how the tool models need/capacity.
SOL layer sensitivity (default rule stays fixed in this example)
For the timing/SOL component, this particular example uses the general/default 2-year period under Alaska Statutes § 12.10.010(b)(2). Unless you change the underlying “event date” logic the tool uses to measure timeliness, the SOL length itself stays the same.
Pitfall: If you’re comparing runs over different dates, you may see SOL/timeliness flags change even when the support amounts don’t. That’s because one piece is economic (income/parenting inputs) and the other is procedural timing (2-year default under § 12.10.010(b)(2)).