Inputs you need for Attorney Fee in Philippines
5 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
To estimate an attorney fee using DocketMath for the Philippines (PH), you’ll typically need inputs that capture: (1) the case type, (2) where it will be filed (jurisdiction-aware forum level), (3) the filing stage / procedural posture, and (4) the scope and intensity of attorney work. This checklist follows how most fee calculations are built in practice: venue context first, then complexity and effort.
Before you begin, gather the following:
- Examples: collection of sum of money, civil damages, labor dispute, criminal matter, family case, administrative case
- Examples: Municipal Trial Court (MTC), Regional Trial Court (RTC), Court of Appeals (CA), Supreme Court (SC), or administrative tribunal
- Needed mainly to align the forum and procedural posture your calculation uses
- Options: pre-filing consultation, preparation of complaint/petition, hearings/trials, appeal, post-judgment motions
- Examples: monetary claim amount, injunction/temporary restraining order, declaration of nullity, reinstatement, etc.
- Provide the principal amount and, if known, whether you’re estimating including interest/penalties
- Estimate how many scheduled hearing dates you expect during the attorney’s involvement
- Check any documents you expect to be prepared, such as:
- Examples that often increase work time:
- Confirm if you expect additional effort for:
- Some users prefer a conservative estimate; others want a mid-point for budgeting
- Examples (use what matches your engagement):
Note (gentle disclaimer): Attorney fees depend heavily on the agreement between the client and counsel, the actual pleadings filed, and the procedural history. Use DocketMath for budgeting and planning—not as a substitute for reviewing your signed engagement terms or getting advice for your specific situation.
Where to find each input
Use this “where to look” guide so you don’t waste time hunting for numbers.
| Input | Where to find it | What to copy into DocketMath |
|---|---|---|
| Case type | Your demand letter, draft complaint/petition outline, or case brief notes | The closest match to the procedural posture you’re in |
| Court level / forum | Filed case documents (if already filed) or draft filing plan (if not) | MTC/RTC/CA/SC/tribunal—whatever matches your intended filing |
| City/Province | Address of parties/contract performance or filing plan | The venue context your calculation expects |
| Filing stage | Your timeline, attorney engagement scope, or status update | Pick the stage that matches where the attorney will start and end |
| Nature of relief | Complaint/petition prayers, settlement proposals, or remedy list | Specify the main remedy (money, injunction, etc.) |
| Amount in dispute | Demand letter, contract statement, spreadsheet, or complaint allegations | Enter principal; note if your estimate should include interest assumptions |
| Number of hearings | Scheduling info, calendar estimates, past docket patterns | Use a realistic count of expected appearances |
| Drafting scope | Your draft document list or attorney checklist | Select documents you expect counsel to draft |
| Complexity factors | Evidence inventory, witness list, number of transactions | Tick only the complexity items that truly apply |
| Service/compliance needs | Your discovery plan, service notes, or prior attempts | Add items that likely require extra coordination |
| Range vs single estimate | Your internal budgeting approach | Choose the mode that best fits your planning |
| Billing arrangement model | Engagement letter, retainer terms, or proposal | Select the model that matches your expected charges |
A practical workflow:
If you already have a docket number and document timestamps, align your stage and hearing count with what actually happened (or will happen). That alignment often matters more than perfect precision.
For convenience, open DocketMath here: /tools/attorney-fee.
Run it
With your inputs assembled, you can run the attorney fee estimation in DocketMath.
- Go to DocketMath → Attorney Fee tool: **/tools/attorney-fee
- Select:
- Case type
- Court level / forum
- Filing stage
- Enter numeric inputs:
- Amount in dispute (for monetary claims)
- Number of hearings/appearances
- Tick drafting scope and complexity factors that apply
- Choose:
- Whether you want a range or a single estimate
- Review the output, then make targeted adjustments.
How output changes (sanity-check guide):
- Forum / court level
- Higher court levels generally increase expected effort and procedural steps.
- Filing stage
- Running from “pre-filing consultation” through “appeal” usually costs more than only drafting a complaint.
- **Amount in dispute (money claims)
- Fee estimates often scale with claim size due to work profile and risk exposure.
- Number of hearings
- Each additional hearing appearance typically increases attorney preparation and attendance time.
- Drafting scope
- Adding motions, position papers, or appellate briefs can materially increase estimated work.
Pitfall to avoid: People often enter only “case type” and amount, then leave hearing count and drafting scope empty. That can understate effort-based fees—especially where multiple pleadings and scheduled hearings are expected.
If you want a budgeting approach, try two passes:
- Pass A (conservative):
- Lower hearing count
- Only essential drafting items (e.g., complaint/petition + initial pleadings)
- Pass B (realistic/mid):
- Expected hearing count based on typical scheduling for your forum
- Full drafting scope (including at least key motions and position paper/memorandum)
Then compare outputs and note exactly which inputs you changed. This makes it easier to reconcile the estimate with your prospective attorney’s proposal later.
Finally, compare your DocketMath result with the attorney’s fee proposal or engagement letter. You’re looking for alignment on the scope (which tasks are included), not only the final number.
Related reading
- Worked example: attorney fee calculations in Vermont — Worked example with real statute citations