How to run Structured Settlement in DocketMath for Philippines

Step-by-step

Run this scenario in DocketMath using the Structured Settlement calculator.

Below is a practical, jurisdiction-aware walkthrough for running a Structured Settlement in DocketMath for the Philippines (PH) using the structured-settlement calculator. This guide is for scenario modeling and documentation prep—not legal advice.

1) Open the Structured Settlement calculator in DocketMath

1. Open the Structured Settlement tool here: /tools/structured-settlement
2. Confirm you’re using the structured-settlement calculator (not another payout/interest tool).
3. Set the jurisdiction to PH (Philippines) if DocketMath prompts for it, or select it in the jurisdiction section.

What you’ll typically change

• Jurisdiction (PH): ensures the tool applies PH jurisdiction-aware assumptions and formatting (where applicable).
• Payment structure parameters: frequency, number of installments, and payout timing.

2) Define the settlement value (the “principal” of your structure)

In the tool, locate the input for the overall settlement amount (often labeled something like Total settlement amount, Lump sum to structure, or Settlement value).

• Enter the gross settlement amount you want to model.
• If your scenario includes reductions (e.g., fees or deductions), decide how you want to represent them in your structure model—then enter the resulting amount the tool should structure (or model the reductions separately, if the tool supports that workflow).

How outputs change

• The installment amounts scale with the settlement value you enter.
• Output totals (such as sum of payments and any present value metrics) track the value you selected.

3) Select the payout pattern (lump sum vs. installments)

Structured settlements are usually modeled as either:

• Immediate or partial lump sum plus scheduled payments, or
• Only periodic installments over time.

In DocketMath, choose the payout structure option that matches your documents.

• Lump sum portion (if applicable): set the initial payment amount or initial percentage.
• Installment plan: set frequency and count (or end condition).

Inputs to look for

• Frequency: monthly / quarterly / semi-annual / annual (whatever the tool supports)
• Number of periods: total installment count
• Start timing: immediate vs. start after a defined delay

How outputs change

• Earlier payments generally increase the “effective” value of the stream compared with the same total spread later (because earlier cashflow is typically more valuable than later cashflow).
• If the tool uses date inputs, the output schedule will reflect the exact calendar spacing.

4) Enter dates/timing inputs carefully for PH modeling

If DocketMath supports date-based timing, use real dates from your proposal or draft agreement:

• First payment date
• Last payment date (or let the tool compute it from count/frequency)
• Deferral period (if you’re modeling a delay)

How outputs change

• If the first payment date is off, every subsequent installment can shift by a period.
• If you’re comparing options (e.g., 60 vs. 72 payments), consistent and correct dates help prevent “looks similar but totals differ” outcomes.

5) Set discount rate / assumptions (if the calculator asks)

Many structured settlement tools include a discount rate or assumption inputs.

In DocketMath, you may see fields such as:

• Discount rate
• Growth rate (depending on the calculation framework)
• Calculation basis (if offered)

Choose assumptions based on your modeling goal:

• For present value comparisons between schedules: keep the discount rate consistent across scenarios.
• For cashflow schedule display only: keep assumptions consistent (or set them to the same baseline) and focus on nominal payment timing and totals.

How outputs change

• A higher discount rate usually lowers presented present value (future cashflows are discounted more).
• Nominal installment amounts may remain unchanged, while present-value metrics change.

6) Validate the schedule preview before exporting

Before saving or exporting, review the schedule output table and totals:

• Installment count matches your input
• Payment amounts are consistent with your settlement value and any lump sum
• Totals at the bottom match expectations (sum of installments, sum including lump sum)
• Timing matches the start/end dates

Use the tool’s visual summary (schedule grid or chart) to quickly spot irregularities.

7) Run scenario comparisons (at least 2 options)

Model two or more payout structures and compare them side-by-side. For example:

• Option A: partial lump sum + 36 monthly payments
• Option B: no lump sum + 48 monthly payments
• Option C: partial lump sum + a longer installment tail

In DocketMath, rerun the calculator for each option, keeping:

• Total settlement amount the same
• Assumptions consistent (especially discount rate, if present)
• Start date consistent (unless you are intentionally testing a timing change)

What to compare

• Nominal totals (sum of scheduled payments)
• Present value (if shown)
• Cashflow timing (first payment date, last payment date)

8) Use the tool output for documentation-ready summaries

Once the model looks correct:

• Use any export/share/download function DocketMath provides (often CSV/PDF-like outputs).
• Add the schedule summary to your internal case file or settlement correspondence.

Gentle reminder: Treat the output as modeling support. Confirm any final numbers against your transaction documents and applicable professional guidance.

Common pitfalls

Structured settlement modeling usually fails in predictable ways. Here are the most common issues when running PH structured settlement scenarios in DocketMath.

• “Monthly” vs. “quarterly” can change counts and spacing drastically.
• A shift by one period can move every subsequent line item.
• If you enter a lump sum and also reduce the installment base (or if the tool defines both in an overlapping way), the lump sum may appear twice depending on the input setup.
• If you compare options but change discount/growth assumptions, you may confuse “timing effects” with “assumption effects.”
• Some calculators compute installments from assumptions, while others require you to specify installment amounts or total value. If the tool offers multiple calculation modes, ensure you selected the intended one.
• Always check the output totals row against the input settlement value.
• If the schedule count is off by one period, the final “tail” changes both nominal totals and any present-value figures.

Pitfall to watch: If your scenario includes a deferred period, confirm whether DocketMath treats it as “skip periods” or as a “delayed first payment.” That distinction can change the cashflow curve substantially.

Try it

To run a PH structured settlement scenario in DocketMath right now:

1. Open the tool: /tools/structured-settlement
2. Set Jurisdiction = PH (if prompted).
3. Enter:

   • Total settlement amount
   • Choose lump sum + installments or installments only
   • Set frequency (e.g., monthly)
   • Set number of periods (or an end date, if supported)
   • Enter first payment date (if available)
   • Keep discount/growth assumptions consistent if you want to compare scenarios
4. Review the schedule table and totals summary.
5. Run a second scenario and compare outputs (e.g., switch monthly → quarterly, or move the start date).

Quick validation checks:

• The sum of scheduled payments matches your modeled total
• The first payment lands on the correct date
• The last payment count matches the planned duration

Related reading

• Structured Settlement Calculator Guide for Alabama
• Structured Settlement Calculator Guide for Arizona
• Structured Settlement Calculator Guide for Colorado