Fee Waiver & Indigency Screener Guide for Maryland

7 min read

Published March 22, 2026 • By DocketMath Team

What this calculator does

DocketMath’s Fee Waiver & Indigency Screener (Maryland) helps you screen whether you may qualify for court-fee waivers based on income and related financial information you enter into the tool.

This guide is designed for practical planning. It’s not legal advice, and a screener is not a final approval—Maryland courts evaluate eligibility using the information before them and the court’s procedures.

Key baseline used by the screener in this guide:

Note: Fee waiver eligibility and the underlying claim’s timing are separate issues. This guide highlights timing using Md. Code, Cts. & Jud. Proc. § 5-106 (3-year general period), but it does not change how fee waivers are decided.

When to use it

Use DocketMath’s Fee Waiver & Indigency Screener when you need a quick, structured way to gather the basic financial facts courts typically look at for indigency-related requests.

Common moments to run the screener:

  • Before filing in Maryland so you can prepare your fee waiver request package early.
  • After calculating that filing costs or service fees are likely to be a hardship.
  • During a case intake workflow (self-help center, clinic, or internal checklist) to standardize information collection.
  • When timing matters: if you’re planning around deadlines, the general SOL baseline for many claims is 3 years under Md. Code, Cts. & Jud. Proc. § 5-106.

Timing context (general SOL baseline)

Maryland’s General SOL period is 3 years, governed by Md. Code, Cts. & Jud. Proc. § 5-106. There wasn’t a claim-type-specific sub-rule identified here, so treat 3 years as the general/default period when you’re doing broad planning.

Warning: A court may apply exceptions, accrual rules, or different limitations periods depending on the claim type. This guide uses the general SOL baseline for orientation only.

Step-by-step example

Below is a realistic walkthrough showing how inputs can affect the screener’s results—while keeping your expectations grounded. Since the exact internal calculation thresholds are tool-specific, focus on how to enter information accurately and how the output categories change when you adjust numbers.

Example: “Jordan” (Maryland)

Assume Jordan is filing a civil case in Maryland and wants to screen for fee waiver eligibility.

Step 1: Enter household basics

Jordan inputs:

  • Household size: 1
  • Dependents: none (or “0”)
  • Any steady contributions: none

Effect on output: Household size generally increases screening sensitivity. A larger household can shift outcomes because “financial need” calculations typically scale with household resources.

Step 2: Enter monthly income

Jordan provides:

  • Gross monthly income: $1,250
  • Monthly income from all sources: $1,250 total

If Jordan later learns they forgot one income stream and updates the screener to:

  • Gross monthly income: $1,900

Effect on output: Increasing income usually makes eligibility less likely in screener models that compare income against thresholds.

Step 3: Enter financial obligations (if the tool asks)

Jordan enters:

  • Required monthly expenses (rent, utilities): $850
  • Other recurring obligations (minimum debt payments): $120

Effect on output: Tools that incorporate expenses may shift results toward “more likely eligible” when expenses are high relative to income (though the final decision still depends on what the court accepts).

Step 4: Add assets (if requested)

Jordan enters:

  • Cash/checking/savings: $300
  • Other assets: $0

If Jordan later updates:

  • Cash/checking/savings: $2,500

Effect on output: Higher liquid assets may push the screener toward “not likely” even if income seems modest.

Step 5: Review the screener output

Jordan runs DocketMath and receives a result that typically lands in one of these planning categories (wording may vary by tool interface):

  • Likely eligible (prepare a fee waiver request package)
  • Unclear / needs more documentation
  • Less likely (consider alternative fee planning steps)

At this point, Jordan also checks case timing using the general SOL baseline:

  • If the underlying claim’s relevant event occurred more than 3 years ago, the general period under Md. Code, Cts. & Jud. Proc. § 5-106 suggests timing may be a concern.
  • If it occurred within the last 3 years, timing aligns more closely with the general baseline.

Pitfall: Don’t “double count” expenses. If your tool asks for income (gross vs. net), use the prompted definition consistently. Mixing definitions can swing outcomes significantly.

Step 6: Prepare documentation checklist (practical use)

Even before you file, use your screener run to build a document checklist such as:

  • Proof of income (e.g., pay stubs, benefit statements)
  • Recent bank statement(s)
  • Lease or housing cost proof
  • Any documentation of dependents
  • Any court-specific forms generated from the tool

Common scenarios

Below are frequent fact patterns in Maryland matters and how they tend to move the screener output.

Scenario table: what changes the result

ScenarioTypical inputsLikely screener directionWhy it moves
Recently unemployedLow or zero current income; possible benefitsMore likelyIncome is reduced, which often dominates eligibility screening
Part-time work with steady incomeModest gross monthly incomeUnclear/variesEligibility often hinges on whether income is below threshold
High liquid savingsLow income but significant cash/savingsLess likelySome screenings treat liquid assets as a meaningful factor
Large householdMore dependents; higher total household sizeMore likelyNeed may be evaluated per household size
Multiple income sourcesSmall paycheck + regular side incomeLess likelyCombined income can exceed thresholds faster than expected
Unexpected support paymentsIrregular assistance (family)Unclear/variesSome tools can’t model irregular income reliably—document it carefully
Recent eviction or increased rentHigher expense entriesMore likely/unclearExpenses can make hardship look more severe, if the tool includes them

Scenario callouts

  • If income is seasonal or fluctuates: run the screener using the most current monthly total you can document.
  • If you receive benefits (e.g., unemployment, disability, public assistance): include them in the “income” fields if the tool prompts for “all income” or “income from all sources.”
  • If you recently made large withdrawals: bring bank statements that explain the timing. A screener may interpret cash-on-hand without seeing why it changed.

Note: This guide references Md. Code, Cts. & Jud. Proc. § 5-106 only for the general 3-year SOL baseline used in planning. It does not replace claim-specific limitation analysis.

Tips for accuracy

You’ll get a more useful screener result when your entries reflect the numbers you can prove with documents. Use these accuracy checks before running /tools/fee-waiver-indigency.

Data quality checklist

Use DocketMath efficiently

If you’re also managing deadlines and filings, integrate the screener with your case workflow rather than running it once and forgetting it.

  • Start here: /tools/fee-waiver-indigency
  • Then follow up with timing-oriented review inside DocketMath resources (e.g., how you’re tracking key dates for a Maryland filing plan)

Inline link you can use now: **Run the screener

Timing sanity check using the general SOL baseline

When you’re doing “can we still bring this?” planning, remember:

  • General SOL: 3 years
  • Statute: Md. Code, Cts. & Jud. Proc. § 5-106
  • No claim-type-specific sub-rule identified in this guide: so treat 3 years as the general/default period for broad planning.

Practical steps:

  • Identify the event date you believe started the clock (based on your facts).
  • Count forward 3 years from that date for an initial screen.
  • If you’re near or beyond 3 years, consider more detailed timing review before filing.

Related reading