Inputs you need for Damages Allocation in United States Federal
4 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
To allocate damages in a United States Federal case using DocketMath (the damages-allocation calculator), you’ll generally need inputs that separate liability buckets (what damages are attributed to each recognized theory/category) and timing (the date range each damages amount covers).
Think of this as building a “damages allocation dataset”: clean, consistent inputs that let the calculator apply the same rules to each bucket, rather than a legal strategy guide. (This is not legal advice.)
Core allocation inputs (most common)
- equal split across buckets
- weighted allocation (by units, impacted scope, loss-causation factors, etc.)
If you’re modeling recoveries, credits, or offsets
Federal damages work often requires keeping recoveries distinct from damages so you can show net results cleanly. Gather:
If your case uses apportionment or multi-part injury
You’ll typically get more reliable allocation outputs when you can break the harm into measurable segments, such as:
Common allocation mistakes in federal matters often come from mixing damages types (for example, treating interest as principal) or using inconsistent time windows across theories. DocketMath can compute consistent allocations once your inputs align to the modeling structure you intend.
Where to find each input
Use these “source locations” within typical federal case materials. Exact file names vary by docketing system, but the categories stay consistent.
Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.
1) Pleadings and claim charts
Look for:
Common places:
- Complaint / Amended Complaint
- Court scheduling orders that request damages disclosures
- Your own damages spreadsheet or claim chart (if you maintain one)
2) Expert reports or declarations
Collect:
Common places:
- Expert report exhibits (tables, appendices)
- Declarations that include a consolidated damages table
3) Damages disclosures and discovery responses
For timing and offsets:
Common places:
- Rule-based disclosures under your scheduling order
- Discovery responses focused on damages and offsets
- Supporting declarations or stipulations
4) Judgment documents and orders
If you’re updating, reconciling, or recalculating:
Common places:
- Opinion and Order
- Judgment / Amended Judgment
- Post-trial memoranda adopting specific figures
Quick “input integrity” checks
Before you enter anything into DocketMath, confirm:
Run it
Ready to calculate? Use DocketMath’s damages-allocation calculator here:
Enter the inputs in DocketMath and run the Damages Allocation calculation to generate a clean breakdown: Run the calculator.
Capture the source for each input so another team member can verify the same result quickly.
Step-by-step workflow (calculator-ready)
- Choose your jurisdiction mode: US-FED
- DocketMath applies jurisdiction-aware handling for federal allocation logic and date-driven components within the workflow.
- Enter totals by damages bucket
- Input one total damages number per theory/category you want allocated.
- Set the damages period
- Enter the start and end dates you want reflected in the allocation model.
- Add your allocation rule(s)
- If you have segment-level data, use weighted allocation.
- If you only have totals, choose a simplified approach—but keep the rule explicit so results are traceable.
- Enter offsets/netting inputs (if relevant)
- Add other recoveries/credits you want reflected in the calculator’s net allocation outputs.
- Review the output breakdown
- Check whether the tool’s principal vs. interest vs. other components match how you structured your inputs.
What changes when you adjust inputs?
Use this as a sanity-check while testing runs:
| You change | Likely effect on outputs |
|---|---|
| Damages period end date | Changes time-dependent components (especially if your model includes interest or period weighting) |
| Switching allocation weights | Moves dollars across segments/theories while the overall total may remain constant (in weighted setups) |
| Adding offsets/recoveries | Reduces net damages and typically changes residual allocation amounts |
| Reclassifying damages type (principal vs. interest) | Helps prevent double counting and changes how totals are reported |
Pitfall to avoid: Don’t paste damages figures that already include interest into a field intended for principal-only. If you do, your “interest” line can effectively be counted twice.