How to run Attorney Fee in DocketMath for Philippines
6 min read
Published April 15, 2026 • By DocketMath Team
Step-by-step
Run this scenario in DocketMath using the Attorney Fee calculator.
This guide shows how to run an Attorney Fee calculation in DocketMath for the Philippines (PH), using jurisdiction-aware rules so your inputs produce results that align with common PH attorney-fee structures (for example, contractual fee arrangements and fee calculations that are driven by procedural milestones where applicable). This is not legal advice—it’s a practical way to model fee scenarios consistently inside DocketMath.
Follow these steps in order so the tool applies the right PH logic.
Open DocketMath’s Attorney Fee calculator
- Go to: /tools/attorney-fee
Confirm the jurisdiction setting is PH
- In the calculator’s jurisdiction selector, choose Philippines (PH).
- Why this matters: DocketMath uses the jurisdiction code to drive rules like:
- which fee input fields are shown,
- how totals are derived,
- and how scenario assumptions are interpreted.
Select the fee calculation method
- Choose the method that matches how the fee is structured in your case management workflow. Typical modeling options include:
- Contractual / agreed fee model (e.g., a fixed amount or percentage)
- Tiered fee model (e.g., different rates across stages or thresholds)
- Rule-triggered / scenario model (where the tool is designed to estimate based on procedural milestones you enter)
- If DocketMath offers a “scenario” selector, pick the scenario that matches your intended output (e.g., the procedural posture you want to model).
**Enter the core numbers (the calculator’s inputs) Use the fields exactly as labeled. Common inputs for attorney-fee modeling include:
- Case stage / milestone (example: filing, motion practice, trial, appeal—whatever the calculator provides)
- Claim amount / principal amount (the monetary baseline for percentage-based modeling)
- Fee type
- Fixed fee (enter the amount)
- Percentage fee (enter the percentage)
- Hourly rate model (enter rate and hours, if available in the UI)
- Adjustments
- e.g., “additional services,” “other costs,” or a “complexity multiplier” if the tool supports it
Tip: If you’re unsure which amount to use as the “principal,” use the monetary amount your internal docketing system records as the baseline for fee computation. The key is to match the label your DocketMath UI expects (principal vs. total claim).
Specify the payment / billing timing assumptions
- Some outputs depend on whether the fee is modeled as:
- a lump sum, or
- a staged payout across phases.
- Enter the timing options the UI requests so DocketMath can reflect installment totals and summaries.
Review the output breakdown After you run the calculation, DocketMath should show:
- Estimated attorney fee total
- How the total was computed (for example: principal × percentage, plus any adjustments)
- A stage-by-stage or component breakdown (if the method uses tiers or milestones)
- Derived figures (like subtotals per phase)
Use the breakdown to sanity-check your inputs. If the output is dramatically higher or lower than expected, it’s usually because:
- the percentage entered is off (e.g., you entered 10 when the field expects 0.10, or vice versa),
- the principal amount is not the same baseline used in your agreement, or
- the stage/milestone selected doesn’t match the case posture you intended.
Export or copy the result for your docket notes
- If DocketMath provides a copy summary or export option, capture:
- the jurisdiction (PH),
- the calculation method,
- the principal/stage assumptions,
- and the final totals.
- This helps make your fee notes reproducible when you revisit the case.
Common “gotcha” to remember: Changing the jurisdiction after entering numbers can change which fields appear and how totals are computed. Finalize PH first, then input amounts.
Common pitfalls
These are frequent “why did the number change?” issues when running attorney-fee calculations in DocketMath (PH).
Using the wrong baseline amount
- Example: you enter total claim but the tool expects principal amount (or vice versa).
- Fix: match the calculator’s label. If your docket has multiple amounts, select the one that corresponds to the tool’s “baseline.”
Percentage mis-entry
- Entering 15 when the UI expects 0.15, or entering 0.15 when it expects 15%.
- Fix: check the field hint/unit (for example, whether the field shows % vs. expects a decimal) before running.
Selecting the wrong stage/milestone
- Many attorney-fee models change based on procedure stage (pre-filing vs. appeal, etc.).
- Fix: align the selected milestone with where the case currently stands in your docket timeline.
Forgetting to include supported adjustments
- If the method includes a complexity multiplier or “additional services,” leaving it at default can understate the estimate.
- Fix: only add adjustments you truly intend to model—don’t “fill in” unrelated fields.
Assuming outputs are interchangeable across jurisdictions
- PH settings may interpret the same inputs differently than other country profiles.
- Fix: keep the jurisdiction constant when comparing scenarios, and change only one variable at a time.
Relying on the total without checking component math
- Even if the final total “looks right,” component breakdown can reveal inconsistent assumptions.
- Fix: review the breakdown view to confirm the math behind the total (for example: principal × percentage, plus any adjustments).
Try it
You can run a quick PH attorney-fee estimate now.
- Open DocketMath Attorney Fee: /tools/attorney-fee
- Then do this 3-variable test:
- the total
- the component breakdown
If you manage filings and deadlines in your workflow, you can cross-check that the stage you selected matches your docket timeline. For related planning or cost estimation work inside DocketMath, you can also look for other calculators from your DocketMath dashboard (use what’s relevant to your process).
Note (non-legal advice): If your goal is internal tracking (not billing in court), keep a record of the exact method and assumptions you selected in DocketMath so later recalculations remain consistent.
Related reading
- Worked example: attorney fee calculations in Vermont — Worked example with real statute citations