Why Attorney Fee results differ in Philippines

The top 5 reasons results differ

When you run DocketMath’s attorney-fee calculator (PH), differences in output usually come from jurisdiction-aware inputs and which internal rule branch the calculator routes to. Often, two runs look similar at a glance but differ in a few key fields—especially when the matter is at a different litigation stage, follows a different procedural path, or has different documentation/scope assumptions.

Here are the most common drivers of “different attorney-fee results” in the Philippines (PH), listed from most frequent to less frequent.

1. **Case stage mismatch (pre-litigation vs. court proceedings)

   • DocketMath’s PH logic is typically sensitive to whether the scenario is treated as pre-filing / pre-litigation versus active court proceedings.
   • Output can diverge when one run assumes an “earlier phase” and the other assumes a “court stage” computation approach.

2. **Wrong or missing “amount involved” (or a different fee base)

   • Many attorney-fee computations depend on the amount involved (claim value) and what that amount includes.
   • If one run uses ₱1,000,000 and another uses ₱900,000, or if one run includes/excludes items like interest, damages, or costs inconsistently, the resulting fee can change materially.

3. **Inconsistent fee arrangement inputs (contingency vs. fixed/retainer vs. hybrid)

   • Results often change when the selected fee model changes.
   • For example, a contingency-style setup and a fixed/retainer setup are not interchangeable—switching the model changes how the calculator interprets downstream inputs.

4. **Service scope differences (what work you’re counting)

   • Even with the same claim value, the calculator can produce different outputs if your inputs imply different scope (e.g., number of hearings, major pleadings, motions, or workstreams).
   • A common reason: one run counts only initial filings while another run counts additional procedural steps.

5. Procedural/venue context affecting which rule branch applies

   • DocketMath’s PH jurisdiction-aware design may route to different computation paths based on the procedural context you select.
   • Small classification differences (for example, treating the matter as a different procedural posture) can cause the calculator to apply a different branch, leading to different results.

Gentle pitfall to avoid: if two runs differ, it’s rarely because “the law changed day-to-day.” It’s more often because inputs caused the tool to route to different calculation branches.

How to isolate the variable

To find the exact reason your numbers differ, use controlled comparisons inside DocketMath. The goal is to ensure only one input changes between runs, so you can attribute the difference to a single cause.

• Freeze the jurisdiction and tool settings so both runs use the same rule set.
• Compare one input at a time (dates, rates, amounts) and re-run after each change.
• Review the breakdown to see which segment or assumption drives the difference.

Step-by-step isolator checklist

Practical “one-change” method

1. Start with Run A (your best representation of the facts).
2. Duplicate it into Run B.
3. Change only one element (stage OR amount OR scope OR fee model).
4. Re-run and compare outputs.
5. If the result changes, that input is the likely culprit. If it doesn’t, revert and test the next input.

Use the tool to reproduce quickly

If you want the fastest confirmation, run both scenarios directly in DocketMath at: /tools/attorney-fee.

Note: This is not legal advice—just a practical way to troubleshoot calculation inputs and routing behavior.

Next steps

To make your attorney-fee estimate in PH more consistent—and to reduce “why don’t these match?” surprises—do the following:

1. Create a single fact sheet for the calculation (use it for every run):

   • Amount base used (and what it includes/excludes)
   • Fee model type
   • Case stage
   • Work scope counts
   • Procedural context assumptions

2. Record exactly what changed between Run A and Run B

   • Use one line per input change (e.g., “Stage changed from X to Y”).
   • This turns guesswork into a clear diagnosis.

3. Run a small sensitivity check

   • Change only one input by a small increment (e.g., claim value ±5%) to see which inputs have the strongest effect.

4. Check the rule branch/routing signals

   • If DocketMath shows different rule branches or different routing cues, treat that as your most direct explanation for the output divergence.
   • Then adjust inputs to match the intended scenario.

If you align the inputs above and still get surprising results, the most productive next action is to verify that the two runs describe the same stage, same amount base, same fee model, and same scope.

Related reading

• Worked example: attorney fee calculations in Vermont — Worked example with real statute citations
• Attorney Fees Guide for Alaska
• Attorney Fees Guide for American Samoa