How to calculate Attorney Fee in ACT (Australia)

Quick takeaways

Run this scenario in DocketMath using the Attorney Fee calculator.

• In the ACT, what people often call “attorney fees” for court proceedings are usually court costs that may be assessed by reference to a scale (often described as taxed costs) rather than a simple hourly-rate multiplication.
• DocketMath’s Attorney Fee calculator is best used as a scenario builder: estimate the fee component that you expect to be claimed, then use that estimate to sanity-check (and later reconcile with) what the court or costs assessor may consider recoverable.
• Your estimate can change the most when you adjust:

  • the forum / proceeding type (e.g., Supreme Court matters versus other pathways),
  • the stage you’re modelling (filing, pleadings, interlocutory steps, hearing),
  • the number of attendances / units you include, and
  • whether you’re modelling on a scale-based approach versus an agreed/contract invoice approach.
• Note: This is a practical guide to calculating a costs-style estimate for ACT using DocketMath. It’s not legal advice; costs outcomes can vary depending on the exact orders made, how a matter settles, and the costs assessment process.

Inputs you need

Before you open DocketMath, collect the details that drive the ACT “attorney-fee-style” estimate logic. The Attorney Fee tool is jurisdiction-aware for AU-ACT, so you should select the ACT configuration early and let it guide which fields and default assumptions you see.

Core inputs (practical checklist)

• Jurisdiction: ACT (Australia) — AU-ACT
• Proceeding type / forum: confirm what court or pathway the matter uses (for example, whether you’re modelling Supreme Court costs).
• Costs basis / calculation mode (choose the one that matches your purpose):

  • Scale-based estimate (common when modelling recoverable costs), or
  • Agreed/contract-based estimate (use this when modelling an invoice/contract total rather than what might be assessed recoverable).
• Work segments / stages to include:

  • pre-hearing steps (drafting, filings, correspondence),
  • pleadings and procedural events,
  • hearing preparation,
  • hearing attendances.
• Quantities per segment:

  • number of attendances,
  • number of documents or procedural steps (if your scenario breaks work down that way),
  • hearing length (often represented as days and/or hearing events depending on the tool’s structure).
• Rate or scale factor (depending on your chosen mode):

  • scale-based: unit/item factors are used to compute totals,
  • contract-based: use your hourly rate or fixed fee inputs, plus your time estimate.
• Disbursements (if you want recoverable total estimates to look realistic):

  • filing/service-related amounts,
  • transcription,
  • expert-related outlays (if applicable and included in your model).
• GST treatment (only include GST if it matches how you’re presenting/analyzing the figure):

  • GST inclusion/exclusion can change the final displayed amount.
• Costs outcome assumption (optional, but helpful):

  • some models assume “successful party” recovery; if your scenario assumes a different outcome, re-check your assumptions.

How inputs affect the output (what to watch)

Run at least two scenarios:

1. Minimum scope: fewer stages/attendances (e.g., something that settles early).
2. Full scope: include the likely steps to conclusion (e.g., you expect to proceed to hearing).

Then compare. In practice, totals often move most due to:

• attendances / units, and
• hearing days (or equivalent hearing-event inputs), rather than changes to small drafting categories.

How the calculation works

DocketMath’s Attorney Fee calculator applies a two-layer structure:

1. Calculate the base legal work amount from your selected inputs (scale units or contract time/rate).
2. Adjust the total for additions such as disbursements and any applicable tax (like GST) based on your settings.

1) Base fee calculation (scale-style vs contract-style)

A. Scale-based estimate (most common for “costs” modelling)

When you choose scale-based modelling, the calculator generally uses an item/unit approach:

• each work stage you select corresponds to one or more costs items / units,
• each unit is multiplied by an ACT-relevant factor (internal to the tool’s AU-ACT mode),
• the calculator sums those selected items to reach a base legal work subtotal.

A simplified view of the math:

• **Base legal work = Σ (item quantity × item factor/rate)
• **Total = Base legal work + disbursements + GST/tax adjustments (if applicable)

Because real costs assessments can involve detailed item-by-item scrutiny, treat the tool output as an estimate of what might be claimed/recoverable, not a guarantee of the final assessed amount.

B. Contract/agreed fee estimate (invoice-style)

If your objective is to estimate what an invoice might total (not what the court may assess as recoverable costs), use contract-style inputs:

• Base legal work = (estimated hours × hourly rate) or (fixed fee × chosen scope),
• then add disbursements and apply any GST assumptions that match your representation.

This mode answers a different question than recoverable-costs modelling—so label your scenario accordingly.

2) Disbursements and additions

Disbursements can significantly affect the overall result.

Include them in DocketMath when you have:

• a specific list with amounts (e.g., service fees, filing fees, transcription), or
• a budget category you want included in the estimate.

A simplified view:

• **Estimated total = base legal work + Σ(disbursements) + GST/tax adjustment (if applicable)

3) ACT jurisdiction-aware logic (what changes because it’s AU-ACT)

When you set the tool to AU-ACT, DocketMath structures inputs and labels to align with typical ACT costs modelling conventions (for example, how you break work into stages and attendances).

Important practical caution:

• ACT costs outcomes can be affected by the specific costs orders made by the court (such as “party/party” assumptions) and the stage the matter settles (early settlement usually reduces what’s arguably claimable).

So if you model a “full hearing” scenario but your matter settles early, your estimate may not reflect what ends up recoverable.

4) Worked example (numbers you can replicate)

Illustrative example only—use your own DocketMath inputs for real estimates.

Assume you run a scale-based estimate with:

• Hearing days: 2
• Attendances: 3
• Pre-hearing drafting steps: 2 items
• Base legal work subtotal from the tool: $6,800
• Disbursements: $1,250
• GST: $0 (or excluded based on your settings)

Then:

• Estimated total = $6,800 + $1,250 = $8,050

Now change just one input: add one more attendance.

• If your extra attendance corresponds to an effective item/unit factor of $450, then:
• Base legal work increases by $450
• New estimated total: $8,500

Takeaway: don’t rely on a single lump-sum assumption if your case’s procedural steps and attendance count differ from the template; build granularity into your scenario.

Common pitfalls

These issues commonly cause ACT attorney-fee (costs-style) estimates to drift away from how a costs assessment typically ends up looking.

• Treating time as identical to recoverable costs

  • Contract hours may not map cleanly to recoverable scale items. Pick the mode that matches your purpose (scale-based for recoverable-costs-style estimates; contract-based for invoice-style totals).
• Over-including stages after a settlement or discontinuance

  • If you assume the matter goes to hearing but it settles earlier, you may inflate the figure. Run “settled early” versus “proceeded” scenarios.
• Forgetting disbursements

  • Even relatively modest outlays (service, filing, transcription) can add hundreds or thousands—especially when they’re included alongside multiple procedural steps.
• GST assumptions mismatch

  • Ensure your GST inclusion/exclusion setting matches the figures you’re analyzing and the intent of the estimate.
• Inconsistent quantities

  • Example: entering “2 days” of hearing time and also adding attendances that already assume those same days (double-counting). Make sure your quantities represent distinct work units as your scenario defines them.
• Double-counting across modelling frameworks

  • Pitfall: running a scale-based estimate and then adding an agreed-fee time cost for the same work on top. Choose one modelling framework for the base work and keep the layers clear.

Sources and references

Costs in ACT court proceedings are governed by a framework of legislation and court rules relating to costs and costs assessment/taxation. For a starting point, look for:

• Supreme Court Costs Rules (ACT) (for the structure and assessment of costs in Supreme Court proceedings)
• Court processes/orders governing costs (including how costs are ordered and recovered)

Reminder: This guide is about using DocketMath to build an estimate, not about providing legal advice. If you share your forum and stage (e.g., Supreme Court ACT, and where the matter is), you can translate that into a modelling checklist—but the tool output still won’t substitute for a legal review of your specific costs orders.

Next steps

1. Open DocketMath: /tools/attorney-fee
2. Select AU-ACT.
3. Choose the right calculation mode:

   • scale-based for recoverable-costs-style estimates, or
   • contract/agreed for invoice-style totals.
4. Enter inputs using the checklist above, then run:

   • Scenario A: narrower scope (earlier settlement / fewer steps),
   • Scenario B: full expected scope (include hearing and key procedural stages).
5. Compare totals and identify drivers

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