How to run attorney fee calculations in DocketMath for Australia

Step-by-step

Run this scenario in DocketMath using the Attorney Fee calculator.

This guide walks you through running attorney fee calculations in DocketMath for Australia (AU) using the attorney-fee calculator. The goal is to help you set up inputs correctly and interpret outputs without getting lost in assumptions.

1) Open the correct calculator

1. Go to the primary CTA: /tools/attorney-fee
2. Confirm you’re using the AU jurisdiction setting (Australia).
3. Choose the fee basis your scenario requires (the calculator will reflect this via its input fields).

If you’re new to the tool, also review the calculator mechanics here: /tools/attorney-fee.

2) Enter client and matter details (where prompted)

Depending on the calculator layout, DocketMath may ask for inputs such as:

• Client type or billing mode (e.g., hourly vs fixed where supported)
• Date-related assumptions (e.g., when work was performed)
• Currency and formatting (if available)

Practical tip: keep your dates consistent across all work line items. Even “close enough” date differences can change which rules or components apply, especially if the calculator uses time-based logic.

3) Add attorney time or fee line items

For most AU fee scenarios in a time-based model, you’ll typically enter:

• Rate (e.g., hourly rate)
• Units (hours or billable increments)
• Number of attorneys/roles (only enter what the calculator actually supports)
• Disbursement components (if the calculator separates them from professional time)

A practical workflow:

• Start with one consolidated line item for your first run.
• If you need more detail later, split by task type (for example, “pleadings” vs “appearances”) only if DocketMath lets you model that breakdown.

4) Configure multipliers, caps, or adjustments (if the calculator supports them)

Some fee models require adjustments beyond simple hours × rate. In DocketMath, these are usually handled through options like:

• Additional percentages
• Allowances for complexity
• Client billing adjustments
• Other adjustment toggles (some tools separate these from disbursements)

Run the calculator twice to see what’s driving changes in the output:

• Pass A (baseline): keep multipliers/adjustments OFF (as supported by the UI).
• Pass B (refined): turn on only the multipliers/adjustments you truly expect.

Comparing Pass A vs Pass B quickly shows whether the estimate changes mainly because of time inputs, rates, or adjustment logic.

5) Select output options and review totals

Once inputs are set, DocketMath typically returns values such as:

• Professional fees subtotal
• Disbursements subtotal (if you entered disbursements separately)
• Grand total
• A breakdown table by line item, rate, or category (depending on the calculator)

Before treating a result as “final,” validate the breakdown:

• Are units counted exactly how you entered (for example, 2.5 hours vs 2.0)?
• Did your selections include/exclude disbursements?
• Does the output align with your own spreadsheet for the same assumptions?

This is where you reduce the risk of a number looking correct but being based on an unexpected option or input mode.

6) Run scenarios to understand sensitivity

Estimates become more useful when you can test “what if” changes.

Try changing one variable at a time, for example:

• Increase/decrease hours by ~10%
• Change rate within a realistic range (for example, $400/hr to $450/hr)
• Toggle disbursement inclusion (if available)
• Toggle a single supported adjustment/multiplier

What you’re checking:

• What most strongly moves the grand total
• Whether the calculator responds consistently (e.g., doubling hours roughly doubles base professional fees)

7) Export or capture results for your records (workflow tip)

If DocketMath offers any save/export/copy option, use it to:

• Preserve the exact inputs and selections
• Share results internally (for example, with a team member reviewing the assumptions)
• Track iterations (baseline vs refined vs final)

Keeping your own short “change log” helps you explain why results differ when multiple people contribute to timekeeping.

Common pitfalls

Running fee calculations is often more about inputs and interpretation than arithmetic. Below are frequent issues when using DocketMath’s attorney-fee calculator for AU.

• using gross recovery when net applies
• mixing recoverable and non-recoverable time
• skipping statutory prerequisites
• forgetting fee caps or schedules

Input pitfalls that commonly distort totals

• Double counting professional time

  • Example: entering the same task once as time-based professional work and again as a separate flat-fee line item.
• Mixing units

  • Hours vs billable increments (for example, entering 0.25-hour units when you meant 0.25 hours) can shift totals.
• Using inconsistent dates

  • If the calculator uses dates to apply logic or rate periods, slight mismatches can change the output.
• Leaving default adjustments enabled

  • Some calculators preselect add-ons. If you don’t explicitly change them, they may affect the total.
• Confusing disbursements with fees

  • If you enter disbursement amounts both in disbursement fields and again inside a time/rate line, the grand total can inflate.

Interpretation pitfalls (even when the math is correct)

• Treating an estimate as definitive entitlement

  • AU fee outcomes can depend on arrangements and procedural facts not captured by a generic calculator. Treat DocketMath outputs as estimates based on your inputs.
• Ignoring assumptions about who pays

  • Even if the tool provides a total, responsibility for costs may depend on context outside what a calculator can model.
• Assuming all tasks are billed the same way

  • If parts of the matter follow different billing approaches, splitting tasks into multiple line items typically produces a more realistic estimate—only if the calculator supports that level of modeling.

Try it

Here’s a hands-on approach to build confidence in the DocketMath /tools/attorney-fee output.

Open the Attorney Fee calculator and follow the steps above: Run the calculator.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Quick test plan (3 runs)

1. Run 1: Baseline

   • Enter one attorney role (as supported)
   • Enter 2.0 hours at a single rate
   • Leave adjustments at their default OFF state (if the UI provides toggles)
2. Run 2: Add disbursements

   • Add a disbursement amount (for example, $150) if available as a separate input
   • Keep hours and rate unchanged
3. Run 3: Add a small adjustment

   • Turn on one supported adjustment/multiplier
   • Use a modest factor so it’s easy to see the proportional change

What to check after each run

Confirm the following every time:

• The professional fees subtotal tracks your entered hours × rate (to the extent the calculator’s base model does that)
• The disbursements subtotal appears only after you add disbursements
• The grand total updates logically when toggling adjustments
• The breakdown table reflects your line items (rather than merging them unexpectedly)

Scenario checklist (before you share results)

Use this quick checklist to reduce surprises:

If the output seems off, go back to Run 1 and add inputs one at a time until you identify what changed the estimate.

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