How to run Structured Settlement in DocketMath for North Carolina
Step-by-step
You can run a Structured Settlement calculation in DocketMath for North Carolina (US-NC) by following a consistent setup flow. The goal is to (1) select the correct jurisdiction-aware rules and then (2) map your settlement terms into the calculator’s inputs.
Note: DocketMath applies jurisdiction-aware timing rules. For North Carolina, the system uses the general/default period because no claim-type-specific sub-rule was found in the available jurisdiction dataset.
1) Open the Structured Settlement calculator
- Go to the primary CTA: /tools/structured-settlement
- Confirm you’re using the Structured Settlement calculator (not a general settlement or damages tool).
- Select Jurisdiction: North Carolina (US-NC).
2) Enter the settlement “economic” terms
In DocketMath, you’ll typically enter fields that describe the present value (or lump-sum equivalent) and the payout schedule. Use the values from your settlement paperwork.
Common inputs include:
- Total settlement amount (or lump-sum equivalent)
- Payment timing (start date or first payment interval)
- Payment structure (e.g., level payments, annual payments, or a custom schedule—depending on what the tool supports)
- Number of payments / years
- Discount rate / interest rate assumptions (if DocketMath prompts you for a rate to convert between lump sum and structured payments)
As you update these inputs, DocketMath recalculates outputs such as:
- the payment stream (amounts by period), and
- the present value comparison (so you can see whether the stream is consistent with the lump sum you entered).
3) Apply jurisdiction-aware timing rules (US-NC)
After you set the economics and schedule, DocketMath applies the North Carolina timing logic available in its jurisdiction rules.
For US-NC, DocketMath uses the general/default period because no claim-type-specific sub-rule was found. Practically, that means:
- You should expect one governing timing rule for the calculation cycle rather than different timing logic based on claim categories.
- If your settlement documentation references a specialized timing concept tied to a claim type, you may need to verify that your inputs represent that schedule in the way DocketMath expects.
Warning: If your agreement cites a different schedule rule tied to a specific claim type, DocketMath may still apply the general/default period (because no claim-type-specific sub-rule was found). Don’t assume the tool automatically mirrors every contract nuance—especially if the contract differentiates timing by category.
4) Run the calculation and review outputs
- Click Calculate.
- Review the output panel for:
- Schedule of payments (payment amounts and timing)
- Present value / discounting results (if displayed)
- Validation messages (for missing or inconsistent fields)
If you notice inconsistencies—such as payments that don’t align with your intended structure—go back and correct inputs like:
- start date / first payment timing,
- number of payment periods,
- discount/interest rate,
- payment schedule/structure type.
5) Adjust inputs until the output matches the settlement’s intent
Structured settlement outputs are sensitive to assumptions. Small changes can materially change the present value and the implied payment stream.
To converge efficiently:
- Change one variable at a time (for example, adjust the rate only),
- Re-run,
- Compare differences in:
- present value, and
- payment amounts by period.
Key input effects to watch:
- Number of payments: changes how the present value is distributed across time.
- Discount/interest rate: changes how future payments “cost” in present value terms.
- First payment date: shifts the time value across all subsequent payments.
6) Export or save results (if available)
If DocketMath offers download/export options:
- Save the run with a clear name (example: “US-NC structured settlement — annual payments”).
- Record the inputs you used, especially the rate and timing, since re-running with a small change can alter both schedule and present value.
This is also helpful if you need to recreate the same calculation later.
Common pitfalls
Most issues in structured settlement runs come from input mapping (timing, schedule structure, or rates) rather than the calculator “getting math wrong.”
For US-NC, watch for these pitfalls:
Pitfall checklist
- You selected US-NC in the jurisdiction dropdown before calculating.
- Your payment schedule inputs (first payment timing + number of periods) don’t align with the settlement agreement.
- Your discount/interest rate doesn’t match the assumption your agreement uses (or the assumption you intend to model).
- You entered a total settlement amount but the payment structure type implies a different total (for example, a level vs. custom schedule mismatch).
- You expected claim-type-specific timing logic, but DocketMath uses the general/default period because no claim-type-specific sub-rule was found.
- You changed multiple inputs between runs, making it hard to identify what caused output differences.
Pitfall: The most common “wrong result” is a timing mismatch. If the first payment date is off by even a few months, the discounted present value and period amounts can diverge substantially.
Quick diagnostic table
| Symptom in output | Likely cause | What to check in DocketMath |
|---|---|---|
| Payments look too high relative to lump sum | Rate or schedule mismatch | Verify discount/interest rate and payment structure type |
| Present value doesn’t match expected lump sum | Timing or rate mismatch | Confirm first payment timing and number of periods; re-check the rate |
| Payment schedule ends earlier/later than expected | Period count mismatch | Confirm number of payments/years aligns with the agreement |
| Calculation warns about missing values | Incomplete schedule inputs | Fill all required timing/schedule fields (especially start timing and period count) |
Try it
If you want a quick, low-friction test run:
- Set Jurisdiction = North Carolina (US-NC).
- Enter:
- total settlement amount,
- your payment structure (level/custom—matching your agreement),
- first payment timing,
- number of payments,
- the rate assumption DocketMath asks for.
- Click Calculate.
- Change only one variable (for example, the rate) and re-run to see how outputs react.
Here’s a simple validation path to confirm your schedule mapping:
- Run A: enter your agreement’s values exactly.
- Run B: adjust only the first payment date by +6 months.
- Compare:
- present value output (should change due to discounting), and
- per-period payment amounts (may change depending on how the tool calibrates the stream).
If Run B doesn’t change outputs meaningfully, check whether:
- you updated the correct timing field, and
- the calculator is using that timing field to generate the schedule.
Note: Because North Carolina uses a general/default period (no claim-type-specific sub-rule found), don’t expect the tool to vary timing logic based on claim categories unless you’ve represented those differences explicitly through your payment schedule inputs.
Related reading
- How to calculate Structured Settlement in Philippines — Full how-to guide with jurisdiction-specific rules
- Worked example: Structured Settlement in Philippines — Worked example with real statute citations
- Inputs you need for Structured Settlement in Philippines — Input checklist with sourcing guidance
Run the numbers for your matter against the verified rule for this jurisdiction.
Calculate now