How to calculate attorney fee in Maryland

Quick takeaways

• In Maryland, attorney fees are generally analyzed under the reasonableness standard in Md. Rule 19-301.5 (MRPC 1.5)—there is no general statutory “sliding-scale” contingency fee cap for typical tort or medical malpractice matters.
• DocketMath’s attorney-fee calculator helps you estimate totals based on inputs like hourly rate, hours, and/or contingency structure; the calculator then applies reasonableness-oriented logic rather than any Maryland contingency cap.
• If a case involves frivolous litigation or bad-faith conduct, Maryland courts can award sanctions under Md. Rule 1-341, which may affect what a party ultimately pays or receives (separate from the core fee agreement).
• The calculator won’t replace a legal review, but it can help you translate your fee agreement and billing records into a clear number you can sanity-check against Maryland’s MRPC 1.5 framework.

Inputs you need

Before you run DocketMath’s attorney-fee tool, gather the items that control the result. You can usually categorize inputs into three groups: billing-based, contingency-based, and case-impact inputs (like sanctions).

A. Billing-based inputs (hourly or hybrid)

• ☐ Hourly rate (e.g., $250/hour)
• ☐ Billable hours by phase (if you have phases, enter totals per phase)

  • Example phases you might track:

    • ☐ intake & legal research
    • ☐ pleadings & motion practice
    • ☐ discovery
    • ☐ hearings/trials
• ☐ Any fixed fees

  • Filing fees are not attorney fees, but some agreements include attorney flat fees.
• ☐ Estimated vs actual hours

  • For a running estimate, you may input estimated hours.
  • For an invoice-based check, use actual billed totals.

B. Contingency-based inputs (if your agreement is contingency)

Maryland does not impose a broad statutory sliding-scale contingency cap for general tort/medical malpractice cases, so your contingency math remains driven by the contract and reasonableness under MRPC 1.5.

Collect:

• ☐ Contingency percentage (e.g., 33⅓% of recovery)
• ☐ Is there a different percentage after a milestone?

  • Example: different percentage after filing of a specific motion or after trial.
• ☐ Gross recovery vs net recovery rules in the agreement

  • Some agreements specify what gets deducted before the attorney’s percentage is calculated.

C. Case-impact inputs (sanctions)

These do not determine the contractual fee amount, but they can change total exposure or recovery.

• ☐ Whether a party seeks/anticipates sanctions under Md. Rule 1-341
• ☐ If relevant: any known sanctions posture

  • For example, whether the court already issued an order.

D. Jurisdiction selector (Maryland)

• ☐ Jurisdiction: US-MD (Maryland)

How the calculation works

DocketMath’s attorney-fee (US-MD) approach can be thought of as “fee math + reasonableness lens” using Maryland’s rules.

Step 1: Choose the fee model you’re calculating

Pick one of these calculation modes based on the agreement and your records:

Step 2: Compute the base attorney-fee amount

• Hourly mode:
  Base fee ≈ (hourly rate) × (total billable hours you entered).

• Contingency mode:
  Base fee ≈ (contingency % / milestone rules) × (recovery amount per the agreement’s gross/net terms).

• Hybrid mode:
  Combine hourly amounts for certain work and contingency percentage for the recovery phase, per the agreement.

Step 3: Apply Maryland’s reasonableness framework (MRPC 1.5)

Maryland’s governing standard for fee reasonableness is Md. Rule 19-301.5 (MRPC 1.5). Practically, this affects how you interpret the output:

• If your inputs produce a number that seems disproportionate to the work performed, MRPC 1.5 factors become your checklist for why that result may (or may not) be justified.
• Because Maryland imposes no general statutory sliding-scale contingency fee cap for general tort or medical malpractice cases, you shouldn’t “expect” the calculator to automatically cap contingency percentages using a statutory schedule.

Step 4: Account for possible sanctions exposure (if applicable)

If the case includes (or risks) a sanctions motion, Md. Rule 1-341 can shift money between parties. DocketMath helps you keep these concepts distinct:

• Base attorney fee = derived from your fee agreement and/or hours.
• Sanctions = separate remedy potentially awarded for frivolous or bad-faith conduct.

So your “total dollars” picture may require adding (or at least tracking) the sanctions component separately from the contractual fee calculation.

Default vs claim-type-specific rules

Maryland’s fee rules in this context follow a general/default period, and no claim-type-specific sub-rule was found in the brief for the general contingency-fee cap concept.

In other words:

• Use Md. Rule 19-301.5 (MRPC 1.5) as the baseline reasonableness lens.
• Treat contingency caps as not automatically applied through a general sliding-scale statute for typical tort/medical malpractice scenarios.

Use DocketMath directly

You can run the Maryland-focused calculator here:

• Primary CTA: /tools/attorney-fee

If you’re troubleshooting differences between two fee calculations, you may also find it helpful to start with the same tool:

• /tools/attorney-fee

Common pitfalls

Fee math is straightforward, but disputes usually come from inputs and assumptions. Here are the most frequent Maryland-specific calculation mistakes and how to avoid them.

1. Using “cap thinking” instead of Maryland’s reasonableness standard

   • Many jurisdictions reference contingency caps. Maryland’s general rule is MRPC 1.5 reasonableness under Md. Rule 19-301.5.
   • Result: you might under-calculate or overwrite the contract math when you shouldn’t.

2. Mixing recovery amounts and agreement economics

   • Contingency calculations often hinge on whether the percentage applies to:

     • gross recovery,
     • net recovery after certain expenses,
     • or a milestone-defined amount.
   • Enter the recovery number consistent with the contract’s stated base.

3. Overstating hours by combining attorney and non-attorney time

   • DocketMath’s attorney-fee calculator is for attorney fee totals. If your records include paralegal time or third-party costs, track them separately unless your agreement explicitly includes them as “attorney fees.”

4. Forgetting milestone splits

   • If your agreement changes the contingency percentage after a specific stage, your single-percentage input can distort the output.
   • Enter milestone rules explicitly (or model them as separate contingency tiers if the tool supports it).

5. Not separating attorney fees from sanctions under Md. Rule 1-341

   • Sanctions are not the same thing as an attorney’s contractual fee.
   • Your final “money picture” should show:

     • base attorney fee (contract/hourly),
     • plus any sanctions component only if and when applicable.

6. Assuming “reasonableness” is purely about the number

   • Md. Rule 19-301.5 focuses on reasonableness; that includes factors beyond the final total—like time, labor, difficulty, and results.
   • DocketMath calculates numbers; you still need the reasoning checklist to interpret them.

Sources and references

• Md. Rule 19-301.5 (MRPC 1.5) — reasonableness of attorney fees
  https://mgaleg.maryland.gov/mgawebsite/laws/StatuteText
• Md. Rule 1-341 — frivolous litigation / bad-faith sanctions
  https://mgaleg.maryland.gov/mgawebsite/laws/StatuteText

Maryland note reflected in the brief: Maryland imposes no statutory sliding-scale contingency fee cap for general tort or medical malpractice cases; contingency fees are governed by the reasonableness standard in Md. Rule 19-301.5 (MRPC 1.5).

Next steps

1. Run DocketMath’s Maryland attorney-fee calculator using your agreement model:

   • Hourly: input rate + total hours.
   • Contingency: input percentage + recovery amount consistent with the contract’s gross/net base.
2. Compare the output to your MRPC 1.5 reasonableness checklist:

   • If the total seems high, verify inputs (hours, rates, milestone splits, recovery base) before questioning reasonableness.
3. **Create a “fees vs sanctions” line