Spreadsheet checks before running Structured Settlement in California
5 min read
Published April 15, 2026 • By DocketMath Team
What the checker catches
Before you run a Structured Settlement workflow in California, DocketMath’s spreadsheet checker helps you validate whether your spreadsheet inputs are consistent with the default limitations period that most often controls the timing for filing. It’s a data-quality and timing-logic guardrail—especially useful when dates come from multiple sources (emails, demand letters, case management exports, or scanned documents).
In California, the general/default limitations period is 2 years, governed by CCP §335.1 (the “general” rule). No claim-type-specific sub-rule was found in the materials provided for this brief, so this checker is intentionally designed around the general/default 2-year period, not a specialized timeline.
The checker focuses on common spreadsheet issues that can lead to “late filing” errors or incorrect assumptions about timing. Typical items it can catch include:
- Missing or ambiguous dates
- Accrual/event date (or the event date you’re using as accrual)
- Filing/target date (e.g., complaint filed date or notice served date—whichever your sheet uses for the comparison)
- Inconsistent date formats
- For example, mixing
MM/DD/YYYYwithYYYY-MM-DDacross rows or tabs
- Wrong year boundary logic
- Off-by-one errors around leap years (e.g., 2020) and exact-day calculations
- Confusing start/end date meaning
- Using a “settlement offer date” as if it were the accrual/event date
- Silent row omissions
- Claims appearing “timely” because the spreadsheet excludes the row that contains the earliest relevant event date
- Mismatch between worksheet tabs
- One tab pulling from an accrual date column while another tab (timeline) uses a different date column
Note: This checker is for spreadsheet accuracy and default jurisdiction-aware timing logic. It does not replace legal analysis of accrual specifics for a particular claim type. It also uses the default general rule (2 years under CCP §335.1) when no claim-type-specific sub-rule is provided.
Jurisdiction-aware rule the checker applies (US-CA)
| Jurisdiction | Rule used by checker | Statute / reference |
|---|---|---|
| California (US-CA) | Default limitations period: 2 years | CCP §335.1 (general rule) |
When to run it
Run the spreadsheet checker right before you launch the Structured Settlement calculator in DocketMath, so you’re not building a structured payout model on top of flawed inputs.
A practical cadence:
- After you import or rebuild the spreadsheet
- Especially when dates are pasted in from emails, settlement demand letters, case management exports, or scanned documents.
- **Before you finalize the “timeline” row(s)
- Lock in the earliest relevant date used as the accrual/start point in your spreadsheet.
- Immediately before you press Calculate in DocketMath’s structured-settlement flow
- This reduces rework if the tool flags late/invalid timing logic.
To keep your sheet checker-friendly, choose and document a single “source of truth” date convention:
- Use one accrual/event date column for all rows.
- Use one filing/target date column for limitations comparisons.
- If you have multiple events (e.g., injury date vs. discovery date), keep them in separate columns—don’t overwrite or recombine them without clear rules.
Input checklist (spreadsheet columns)
Pitfall: If your accrual/start date is accidentally copied from a later event (like a settlement conference date), your sheet may look “timely” even though the underlying timing logic would differ. The checker helps surface this by verifying date presence/format and relationships against the default 2-year rule—but you still need consistent meaning for each date column.
Try the checker
You can try DocketMath’s structured settlement workflow starting from the primary CTA. If your goal is spreadsheet checks for California timing logic, start here:
- Primary CTA: Run the Structured Settlement checker
What to do:
- Open DocketMath’s Structured Settlement tool.
- Select/confirm jurisdiction: US-CA.
- Provide the date inputs your spreadsheet uses:
- Accrual/event date (the date you treat as starting the limitations clock)
- Filing/target date (the comparison end date)
- Review the checker output:
- Look for flags related to missing dates, invalid formats, and timing mismatches against the default 2-year period.
- Fix rows indicated by the checker:
- Adjust date cells, unify formats, and ensure the correct columns are mapped.
How outputs change when inputs change
The checker’s results depend primarily on:
- (1) Start date (accrual/event date in your sheet)
- (2) End date (filing/target date in your sheet)
| Scenario | Start date vs. end date | Likely checker outcome (default rule) |
|---|---|---|
| Clean data, event and filing within 2 years | End date ≤ 2 years after start | Pass / no limitations timing flag (default 2-year period) |
| Late timing based on your dates | End date > 2 years after start | Flag for “outside default limitations window” |
| Missing accrual/start date | Start date blank | Data quality flag (cannot compute) |
| Date stored as text | Non-date formatting | Format/parse flag; calculation may not run correctly |
Gentle disclaimer: the checker evaluates spreadsheet date logic against the general/default limitations period (2 years under CCP §335.1, as referenced in California limitations law summaries). If your spreadsheet is built for a specific claim type with a different limitations period, you would need to adjust the rule set accordingly—but under this brief, no claim-type-specific sub-rule was provided, so the checker stays anchored to the general/default period.