Attorney Fees Guide for Maryland

8 min read

Published April 8, 2026 • By DocketMath Team

What this calculator does

Run this scenario in DocketMath using the Attorney Fee calculator.

DocketMath’s attorney-fee calculator for Maryland (US-MD) helps you estimate an attorney-fee award or fee exposure by modeling the most common drivers of fee amounts:

  • Hourly rate (or blended hourly rate)
  • Hours worked
  • Number of billing entries (optional, if you’re reconciling invoices)
  • Contingency fee percentage (if applicable to your situation)
  • Any multipliers you may be considering (used as a modeling parameter, not a promise of eligibility)
  • Costs and expenses (if you choose to include them separately from fees)
  • Time horizon (useful for reconciling invoices or budgeting; even when the legal rule focuses on reasonableness, timing can matter for planning)

This guide explains how the calculator’s inputs typically map to the way Maryland courts evaluate fee requests, without providing legal advice. Fee outcomes can depend heavily on case posture and the specific fee-shifting statute or agreement—so treat estimates as planning tools, not predictions.

Note on timing: Maryland has a general 3-year limitations period for many actions involving attorney-fee claims. Some matters can be governed by different, claim-specific rules. This guide uses the general/default period you provided: Md. Code, Cts. & Jud. Proc. § 5-106 (3 years). You also noted that no claim-type-specific sub-rule was found—so this is a baseline, not a guarantee for every fee claim.

To use the tool, go to /tools/attorney-fee.

When to use it

Use the DocketMath attorney-fee calculator when you need a grounded estimate for one of these planning tasks in Maryland:

  • Pre-filing budgeting: You’re forecasting what fee recovery might look like under a fee-shifting provision or what your own fee outlay could be.
  • Settlement discussions: You want a consistent number to discuss with opposing counsel or your client.
  • Invoice reconciliation: You’re converting time entries into an anticipated fee figure (for example, comparing an invoice subtotal to a model based on total hours).
  • Post-judgment planning: You’re preparing the arithmetic supporting a fee request (while recognizing that eligibility and reasonableness standards still control the final award).

It’s also useful for sensitivity testing—for example:

  • If you expect a higher hourly rate but lower hours (or vice versa), the calculator helps you see how sensitive the total is to those assumptions.
  • If you think some categories of work may be reduced, you can model reduced hours to understand a reasonable range.

Step-by-step example

Below is a practical walkthrough using a typical “lodestar-style” model (rate × hours) plus an optional multiplier.

Example facts (Maryland planning estimate)

You have an attorney invoice reflecting work in a Maryland civil case.

  • Hourly rate: $350/hour
  • Total billable hours: 28.5 hours
  • Estimated costs (separate from fees): $780
  • Multiplier: 1.0 (baseline)
  • Contingency model: not used in this example

Step 1: Enter the fee model inputs

In DocketMath attorney-fee:

  • Hourly rate = 350
  • Hours = 28.5
  • Multiplier = 1.0
  • Include costs = Yes
  • Costs = 780

Step 2: Compute the fee portion (rate × hours × multiplier)

The calculator’s fee subtotal follows this basic estimate:

InputValue
Hourly rate$350
Hours28.5
Rate × hours$350 × 28.5 = $9,975
Multiplier1.0
Estimated attorney fees$9,975

Step 3: Add (optional) costs

If you include costs separately:

  • Estimated total = $9,975 + $780 = $10,755

Step 4: Model alternative scenarios quickly

Now test two common adjustments:

  • Scenario A (reduced hours): 24.0 hours at $350
    • $350 × 24.0 = $8,400
  • Scenario B (reduced rate): 28.5 hours at $300
    • $300 × 28.5 = $8,550

Range (fees + costs):

  • Baseline: $10,755 total
  • Scenario A: $8,400 + $780 = $9,180
  • Scenario B: $8,550 + $780 = $9,330

Pitfall: Fee requests are often scrutinized for what counts as compensable work and how much. If you’re uncertain, running “reduced hours” scenarios can help you understand downside risk—without implying the court will adopt any specific number.

Step 5: Reconcile timing with Maryland’s general limitations period (planning anchor)

Maryland’s general/default limitations period you provided is:

  • 3 years under Md. Code, Cts. & Jud. Proc. § 5-106

That means if you’re assessing whether a fee-related action or request is timely under a general theory, your baseline time window is 3 years. Because you noted that no claim-type-specific sub-rule was found, treat this as a default anchor, not a universal rule for every fee claim.

Common scenarios

Maryland attorney-fee questions often fall into repeatable buckets. Use the calculator to organize assumptions clearly and test ranges.

1) Hourly billing with a straightforward estimate

Typical inputs

  • Hourly rate
  • Total hours
  • Costs (optional)
  • Multiplier = 1.0 (baseline)

What to watch

  • Make sure hours reflect work attributable to the matter you’re estimating.
  • If your records separate expenses, keep costs distinct from fees in the model.

2) Mixed billing (different rates / timekeepers)

If your invoice includes different timekeepers (for example, associate and partner rates):

How to model

  • Use an effective blended rate:
    • Effective rate = (Total billed fees across timekeepers) ÷ (Total hours across timekeepers)
  • Or run separate lines and sum (if your workflow supports it).

Why it matters

  • Totals can swing when hours are high; even small rate shifts can change outcomes meaningfully.

3) Contingency fee arrangements

If you’re using a contingency arrangement, the modeling approach may differ:

Typical inputs

  • Contingency percentage
  • Total recovery (if your model uses it)
  • Any paid/credited amounts

Calculator use

  • Run scenario planning for partial recovery or alternative outcome ranges so your estimate stays realistic.

4) Fee requests under fee-shifting provisions (planning range)

When a statute or contract allows fee shifting, the key practical point for estimates is that:

  • The requested amount often needs to be supported by billing/time records and reasonableness arguments.
  • Courts may reduce fees based on what they view as reasonable or compensable.

Calculator use

  • Run a baseline and then one or more “reduced hours” versions to reflect possible trimming.

5) Timing and limitations period planning (Maryland default)

If you’re tracking the age of events tied to a fee request (for planning purposes), anchor to:

  • **3 years under Md. Code, Cts. & Jud. Proc. § 5-106 (general/default)

Warning: The 3-year general limitations rule is not a substitute for analyzing whether a particular fee claim is governed by a different, claim-specific limitations framework. If the legal mechanism differs, timing analysis may change.

Tips for accuracy

Getting a useful estimate from DocketMath is mostly about matching inputs to your records and using scenarios responsibly.

Use your invoice structure, not memory

Before entering numbers:

  • Pull time entries and rate(s) from the attorney’s invoice or billing system.
  • Separate fees from expenses if your records do.

Calibrate hours carefully

A frequent source of error is hour totals that include:

  • administrative time,
  • tasks outside the relevant matter,
  • duplicated entries,
  • time that isn’t actually billable or isn’t attributable to the claim you’re modeling.

In the calculator:

  • Enter the hours you intend to support as compensable in your estimate.
  • Then run a “reduced hours” scenario to test sensitivity.

Keep the multiplier out of the baseline unless you mean to test it

If you don’t know whether a multiplier is appropriate, start with:

  • Multiplier = 1.0

Only adjust it as part of a scenario if you have a defensible reason to model that assumption.

Reconcile costs separately

Decide upfront whether you want:

  • fees only, or
  • fees + costs

Then keep that choice consistent so your totals don’t accidentally mix categories.

Use Maryland limitations timing as a planning anchor

When estimating whether a fee-related request is potentially timely (in a general-default way), use:

  • **Md. Code, Cts. & Jud. Proc. § 5-106: 3 years (general/default)

If you’re calculating based on dates (for example, from a judgment date or work completion date), write down:

  • the start date you’re using for modeling, and
  • the end date implied by 3 years.

Quick manual timeline check:

  • Start date: Day 0
  • Limitations period: 3 years
  • Latest modeled date: Day 0 + 3 years

Note: This is the general/default period (not a claim-type-specific rule). Use it as a baseline planning anchor.

Quick reference table (what to enter)

GoalBest inputs to use
Baseline fee estimateHourly rate, hours, multiplier = 1.0
Conservative planningReduced hours scenario or blended-rate sensitivity
Fees + expenses totalAdd costs separately from attorney fees
Mixed-rate billingUse blended rate or sum multiple rate lines
Fee-shifting planningRun multiple scenarios to reflect potential reductions
Timing planning (Mary

Sources and references

Start with the primary authority for Maryland and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

Related reading