How to calculate Settlement Allocator in California

Quick takeaways

• California settlement allocation in many multi-claim/multi-party scenarios is done using a “settlement allocator” that splits settlement proceeds proportionally across affected components (often by an agreed measure like time or another quantifiable driver).
• In this DocketMath workflow, the California default allocation period is anchored to Cal. Code Civ. Proc. § 382 and the California Rules of Court, Rules 3.760–3.771. No claim-type-specific sub-rule was found, so § 382’s general/default period approach is treated as the baseline.
• In DocketMath, you’ll typically (1) enter dates and component weights, (2) select the jurisdiction mode: US-CA, and (3) compute allocator percentages/amounts so your settlement breakdown stays consistent across documents.
• If your inputs don’t reconcile—especially date ranges, how you define the affected period, or missing/unclear weights—the allocator outputs may not match your record or settlement allocation narrative.

Inputs you need

Before you run the /tools/settlement-allocator calculator in DocketMath, gather the inputs below. The goal is to (a) define your allocation frame, and (b) define the proportional weights used to split the settlement.

1) Settlement and allocation frame

• Total settlement amount (numeric)

  • Example: 2500000
• Allocation frame start date (date)
• Allocation frame end date (date)

2) The components you will allocate to

Depending on how your matter defines “components,” enter one row per component with:

• Component label (e.g., “Class Period A,” “Claim Segment 1,” “Party Group East”)
• Component start date (date)
• Component end date (date)
• Component weight basis (choose the basis your workflow uses)

  • Common bases include:

    • time-proportion (e.g., days in period),
    • exposure-proportion (e.g., estimated units, transactions, affected volume),
    • claims/points weight (e.g., weighted damages drivers)

3) Jurisdiction settings (California)

• Jurisdiction: US-CA
• Allocation law mode: “General/default”, because no claim-type-specific sub-rule was found. (So, § 382’s general/default period approach is treated as the baseline for this workflow.)

4) Output options (what you want to see)

• Allocator output type

  • percentages only
  • amounts only
  • both
• Rounding preference

  • e.g., round to 2 decimals (percent) and nearest dollar (amount)

Quick checklist

• Total settlement amount captured
• Allocation frame dates are complete and internally consistent
• Each component’s date span is entered (no gaps unless you intend them)
• Each component has a weight basis (time or another driver)
• Jurisdiction mode set to US-CA
• Allocation law mode set to General/default for California (per this guide’s default assumption)

How the calculation works

California’s default allocation logic in this calculator is framed around Cal. Code Civ. Proc. § 382 and procedural guidance in Cal. Rules of Court 3.760–3.771. In practice, your allocator distributes a lump sum across defined components proportionally based on a measured basis (commonly time within a relevant period, or another quantifiable proxy you enter).

Step 1: Define the “affected period” (baseline rule)

For this California workflow, treat the period determination as the general/default baseline under § 382 and the related court rules without a claim-type-specific carve-out (because none was identified for this guide).

Concretely in DocketMath, that means:

• Your allocation frame (start → end) functions as the denominator period.
• Each component occupies part of that frame based on its start/end dates.
• If components extend beyond the allocation frame, you should either:

  • trim them to the allocation frame, or
  • confirm your entered dates already reflect the trimmed overlap.

Step 2: Compute component “basis” for proportional allocation

DocketMath converts each component row into a basis value, based on your selected weight basis.

Option A — Time-proportion basis

If you use time-proportion:

• Component basis = # of days in component within allocation frame

If you use exact days, agree on a convention:

• whether to treat dates as inclusive or exclusive, and
• keep that convention consistent across all components.

Option B — Exposure/units/points basis

If you use a non-time driver:

• Component basis = the entered exposure/units/points weight

Even with non-time drivers, dates still matter for:

• mapping component definitions onto the allocation frame, and/or
• validating that each component corresponds to the intended segment.

Step 3: Convert basis into allocator percentages

After computing each component basis:

• Total basis = sum of all component basis values
• Component allocator % = component basis / total basis

Then DocketMath applies your rounding preferences (e.g., 2 decimals).

Step 4: Allocate settlement amount

Finally:

• Component settlement amount = total settlement amount × component allocator %

Step 5: Verify totals and audit consistency

Allocator outputs should reconcile to:

• total settlement amount (within your rounding tolerance)
• 100% allocator (within your rounding tolerance)

Use this verification to catch common issues:

• a missing component row,
• a component basis accidentally entered as 0,
• component dates that fall completely outside the allocation frame.

Common pitfalls

1. Assuming claim-type-specific rules exist

• This guide intentionally uses the general/default allocation period approach because no claim-type-specific sub-rule was found. If your court order, settlement agreement, or allocation narrative requires a special method, you should encode that by adjusting your component definitions and/or basis inputs—rather than relying on a “claim-type” toggle that may not exist.

1. Date mismatches and trimming errors

• If component date spans don’t align with the allocation frame, you may under- or over-allocate.
• Fix by trimming component dates to the allocation frame (or confirming that your DocketMath configuration treats overlaps/trimming exactly as you intend).

1. Overlapping components without an overlap policy

• If two components overlap in time but you intend them to be mutually exclusive, your basis can effectively double-count the overlap.
• Decide an overlap policy:

  • disallow overlaps (make components mutually exclusive), or
  • allow overlaps and accept proportional allocation as defined by your basis/date logic.

1. Rounding drift

• Percent-level rounding can create small dollar differences after multiplication.
• Use DocketMath’s rounding settings and align them with how your settlement administration workflow handles final cent/dollar adjustments.

1. Using the wrong jurisdiction mode

• If you accidentally run a non-California mode, outputs may not match what you plan to use in California settlement administration.
• Confirm:

  • Jurisdiction: US-CA
  • Allocation law mode: General/default

Sources and references

• Cal. Code Civ. Proc. § 382 (representative/class action mechanism; settlement allocation principles tied to the statutory scheme)
  https://leginfo.legislature.ca.gov/faces/codes_displaySection?lawCode=CCP&sectionNum=382
• California Rules of Court, Rules 3.760–3.771 (procedures relevant to class action settlements and related court processes)
  (Cited here as procedural guidance accompanying § 382 in California settlement contexts.)

Next steps

1. Map your matter into components

• Describe each component in plain language (e.g., “liability exposure period,” “participant cohorts by time,” or “segmented group by dates”).

1. Set your allocation frame

• Enter allocation frame start/end dates that match the baseline approach you’re using under § 382.

1. Choose the basis

• If you have reliable time coverage: use time-proportion.
• If you have damages drivers or measurable exposure: use the appropriate exposure/points weight basis.

1. Run DocketMath: /tools/settlement-allocator

• Use jurisdiction mode US-CA.
• Confirm totals:

  • allocator % sums to ~100%
  • allocated dollars sum to ~total settlement amount

1. Export and cross-check

• Compare outputs against:

  • the settlement term sheet,
  • your damages/exposure spreadsheet, and
  • any allocation narrative used for internal approvals or filings.

Related reading

• How to calculate Settlement Allocator in Ohio — Full how-to guide with jurisdiction-specific rules
• How to calculate Settlement Allocator in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Settlement Allocator in Philippines — Worked example with real statute citations