What this calculator does

Run this scenario in DocketMath using the Fee Waiver Indigency calculator.

DocketMath’s Fee Waiver & Indigency Screener (Minnesota) helps you run a practical, structured check for whether your situation may fit Minnesota’s fee waiver / indigency pathways. This is a screening tool, not a final determination. It’s designed to help you organize facts before you seek relief.

In Minnesota, many people connect fee relief to criminal case processing (like assessments, costs, and related charges). This guide focuses on the indigency screening side and the timing reality of when a request could be possible.

Because fee eligibility rules can depend on the specific court process, you should use this screener to answer two questions:

• Indigency lens: Do the basic facts you have align with what courts commonly consider when evaluating ability to pay?
• Timing lens: Are you still likely within the relevant Minnesota timing window for challenging or seeking relief based on the general rule?

For timing, Minnesota’s general/default period in the provided data is a 3-year lookback under Minnesota Statutes § 628.26.

Important: This guide uses general/default timing. No claim-type-specific sub-rule was found in the provided data, so you should treat this as a baseline—not a guarantee for every procedural scenario.

You can start the screener here: /tools/fee-waiver-indigency

What you input (in plain language)

DocketMath’s screener generally works with inputs like:

• Your approximate household income (and whether it’s steady or irregular)
• Whether you have dependents (household size)
• Essential monthly expenses (housing, utilities, medical needs)
• Any public benefits (when applicable)
• Whether you have cash on hand and/or savings/assets that may affect ability to pay

You’ll get an output that is typically framed as a screening result (for example: “may be consistent with indigency screening factors” vs. “may be difficult under typical screening factors”), plus a list of next-step evidence items to gather.

When to use it

Use the DocketMath fee waiver & indigency screener (Minnesota) when you’re trying to act on fee-related issues and you need two things quickly:

1) You’re preparing a request for fee waiver / indigency relief

Examples include situations where you’re:

• Facing court-related fees or costs
• Trying to reduce or avoid payments based on inability to pay
• Coordinating a plan to request relief in a criminal case context

2) You need a timing “sanity check” before you file

Minnesota’s general/default statute period in the provided data is:

• 3 years under Minnesota Statutes § 628.26
  (General SOL period provided: 3 years)

This matters if you’re considering whether you can still pursue relief based on a general timing window.

3) You’re dealing with older case events

If your court costs, assessments, or related fee issues arose months or years ago, this guide helps you decide whether your timing is likely within a general 3-year window.

For context, some Minnesota resources that summarize criminal record categories may include examples such as gross misdemeanors (which sometimes show up in fee-related discussions).
Source: https://minnesotacourtrecords.us/criminal-court-records/gross-misdemeanor/

Step-by-step example

Below is a realistic walkthrough of how the DocketMath screener approach can work for a Minnesota user. This example is simplified, but it shows how inputs and outputs usually connect.

Scenario: A household with limited income seeking fee relief

Assume the user is dealing with court-related fees in Minnesota after a criminal matter.

Step 1: Confirm the general timing baseline

• Event date you’re concerned about: January 15, 2022
• Today’s date (for example): March 1, 2026
• Time elapsed: ~4 years, 1.5 months

General/default rule in provided data:

• 3 years under Minnesota Statutes § 628.26
  (No claim-type-specific sub-rule was found in the provided data.)

Screening timing outcome (baseline):

• Likely outside the general 3-year window for a baseline SOL-style argument.

This doesn’t necessarily end your options—some remedies don’t map perfectly to every timing rule—but it is a strong “check the deadlines” signal.

Step 2: Provide financial facts

Example inputs the user enters:

• Household size: 3 (the user + 2 dependents)
• Monthly take-home pay: $2,050
• Work stability: part-time / irregular hours (average is low and varies)
• Housing: $1,050/month rent
• Utilities & transportation: $350/month
• Medical / prescriptions: $160/month
• Any cash savings: $500
• Public benefits: yes (one benefit supporting partial income)

Step 3: Watch the screener logic shift (how outputs change)

A typical indigency screener looks for patterns like:

• Low income relative to basic living costs
• Dependents increasing household burden
• Minimal liquid savings
• Benefits suggesting income constraints

How the output might change based on inputs:

• If household expenses were much lower (e.g., rent $600 instead of $1,050), the screener result could shift away from “consistent with indigency factors.”
• If the user reported $15,000 in readily available savings, the result could shift toward “may be harder to justify inability to pay,” even if income is low.
• If income were higher (e.g., $3,800/month) while expenses stay the same, the screening direction could shift toward “less consistent.”

Step 4: Review evidence checklist prompts

Even at screening stage, the screener may suggest evidence types such as:

• Recent pay stubs or income statements
• Benefit award letters or documentation
• Lease and utility bills
• Medical bills / prescription documentation
• A brief statement of monthly budget pressures

What you would learn from this example

In this example:

• Indigency facts: the financial profile may be consistent with indigency screening factors because income is tight, dependents exist, savings are limited, and essential costs are heavy.
• Timing: the general 3-year window under Minnesota Statutes § 628.26 suggests timing is likely a challenge relative to a baseline SOL-style argument.

In practice, that often means:

• You may have meaningful indigency support,
• but you should carefully confirm whether the request is still procedurally viable given the time elapsed.

Gentle reminder: This is screening, not legal advice. If timing is close or uncertain, consider asking a qualified legal professional or court resource for guidance on your specific procedural posture.

Common scenarios

The DocketMath screener is especially helpful when you fit one of these patterns. Each scenario below shows what to expect in the direction of the screening output (not a legal determination).

1) Income is low but stable; savings are minimal

Common inputs:

• Wages near the lower end
• Minimal liquid savings
• Dependents or high essential costs

Likely screening direction:

• More consistent with indigency factors because ability to pay is constrained month-to-month.

2) Income fluctuates (seasonal work, gig work, irregular hours)

Common inputs:

• Irregular paychecks
• Month-to-month variability

Likely screening direction:

• The tool often flags that you should document an average or recent trend.
• If expenses stay steady while income dips often, the screener output can trend toward “may fit.”

3) Public benefits are part of the household picture

Common inputs:

• Participation in benefits programs
• Benefit amounts that replace or supplement wages

Likely screening direction:

• Screening often becomes more “indigency-aligned,” particularly when benefits are a substantial share of total income.

4) Household has higher income but large unavoidable expenses

Common inputs:

• High rent due to family needs
• Medical costs or disability-related expenses

Likely screening direction:

• The output can go either way, depending on the expense-to-income balance. The screener typically focuses on net affordability, not just raw income.

5) Older fee event date (timing risk)

Common inputs:

• The fee or assessment issue arose more than 3 years ago

Likely screening direction:

• Timing may reduce the feasibility of relief if the request is anchored to general timing rules.
• Reminder: in the provided data, the general/default timing is 3 years under Minnesota Statutes § 628.26, and no claim-type-specific sub-rule was found.

Tips for accuracy

To get the most reliable screening result from DocketMath’s Fee Waiver & Indigency Screener (Minnesota), focus on data quality and consistency.

Use monthly totals, not annual numbers

Courts and screening tools usually work with monthly ability to pay.

• Convert annual income to monthly take-home where possible
• If income varies, use a recent average (for example, a 3–6 month average)

Include dependable “baseline” expenses

A strong screening packet usually includes recurring, verifiable costs:

• Rent or mortgage
• Utilities
• Transportation needed for work/medical access
• Medical / prescriptions
• Child care costs (when applicable)

Be precise about savings and cash access

Screeners commonly ask about:

• Cash savings
• Money readily available without liquidation penalties
• Large assets that could be converted to cash

If you only track “account balances” without distinguishing liquid vs. restricted funds, screening can be less accurate.

Cross-check the timeline against the general SOL baseline

Using the provided Minnesota general/default timing data:

• 3 years baseline

Related reading

• Fee Waiver & Indigency Screener Guide for Alabama
• Fee Waiver & Indigency Screener Guide for Arizona
• Fee Waiver & Indigency Screener Guide for Colorado