What this calculator does

Run this scenario in DocketMath using the Pro Se Pleading Generator calculator.

DocketMath’s Pro Se Pleading Generator for Maryland (US-MD) is a drafting aid that turns your factual inputs into a first-pass pleading draft formatted for use in a Maryland court. In practice, it helps you:

• Convert key dates, parties, and events into a structured narrative
• Generate an initial “claim-style” layout (without pretending to provide perfect legal strategy)
• Produce a document you can review for completeness and accuracy before filing

This guide focuses on the calculator workflow and the specific Maryland timing rule it relies on for the general statute of limitations.

The timing rule used in the Maryland version

For Maryland, the calculator uses the general/default statute of limitations:

• General SOL Period: 3 years
• General Statute: Md. Code, Cts. & Jud. Proc. § 5-106
• Source: https://codes.findlaw.com/md/courts-and-judicial-proceedings/md-code-cts-and-jud-pro-sect-5-106/?utm_source=openai

Important clarification (so you’re not surprised)

The Maryland generator (for this guide’s setup) uses the general rule because no claim-type-specific sub-rule was found for this version. That means:

• If your situation has a different limitations period under a more specific statute, the general 3-year period may be wrong for your exact cause of action.
• Use the general rule as a screening starting point, not a guaranteed match.

If you’re unsure what your claim is “called” legally, the generator can still help you organize facts—but you should double-check limitations rules in Maryland for your specific situation.

When to use it

Use DocketMath’s Maryland pro se pleading generator when you need a clean first draft quickly—especially if you’re working from scattered notes or want your document organized in a “court-readable” format.

Consider using it when:

• You’re filing your first Maryland pleading and want help building structure
• You need to memorialize a timeline with specific dates (e.g., contract breach, property dispute events, injury-related events)
• You’re deciding whether your facts fall within the general 3-year limitations window under Md. Code, Cts. & Jud. Proc. § 5-106
• You want an output you can edit—rather than starting from a blank page

A quick checklist before you generate

Before you click the primary action button, gather:

• The dates of key events (or the best dates you can support)
• The names of the parties (spelling matters)
• The location(s) relevant to the dispute (where it occurred, where parties live/work)
• The relief you want (what you want the court to order or award)

To start, go to: /tools/pro-se-pleading-generator

Step-by-step example

Below is a realistic walkthrough showing what inputs you’d provide and how the output changes—using Maryland’s general 3-year timing framework under Md. Code, Cts. & Jud. Proc. § 5-106.

Example facts (you can map your details to these)

Imagine you are drafting a pro se pleading about a dispute that started after a transaction in Maryland.

• Incident date / event date: June 15, 2021
• Filing date you’re targeting: August 1, 2024
• Party names:

  • Plaintiff: “Jamie R.”
  • Defendant: “Ocean View Services LLC”
• Location: Baltimore County, Maryland
• Core allegation in plain language:

  • You paid for a service that was not performed as agreed.
• Relief you seek:

  • Return of the amount paid ($1,950), plus costs

Step 1: Enter the “event date”

In the generator, you’ll provide the date the relevant facts began (often described as the key event date in your timeline).

• Event date: 06/15/2021
• Generator logic (general rule): 3 years from the event date, based on Md. Code, Cts. & Jud. Proc. § 5-106

How the calculator frames the window (general SOL screen)

• Last day under the general 3-year period is typically around:

  • 06/15/2024 (depending on exact counting rules and tolling facts)
• Your planned filing date: 08/01/2024

Outcome of this step: the generator will flag that, under the general 3-year screen, the claim may be outside the limitations window.

Step 2: Confirm or refine your timeline details

You’ll typically be prompted to add a few supporting facts, such as:

• When you discovered the issue (if relevant)
• Any communications (dates of emails/letters)
• What happened after the event date

In this example, add:

• You notified Defendant by email on 02/10/2022
• Defendant responded on 02/18/2022 by saying they would complete the service
• They did not complete it

Outcome of this step: your draft timeline becomes more specific in the narrative. Even if the general SOL screen is unfavorable, the factual clarity helps you review whether a different limitations rule or a tolling concept might apply—this guide/tool won’t “decide” legal applicability for you.

Step 3: Describe the parties and dispute in a consistent narrative

Enter:

• Plaintiff/Defendant names
• State/county where events occurred
• A short summary of the dispute in chronological order

Outcome of this step: the generator produces a more coherent pleading structure, often including:

• A statement of parties
• A factual background section
• A request for relief section

Step 4: Add the relief you want (what the court should order)

Provide:

• Dollar amount: $1,950
• Costs or fees: describe what you paid for filing or related expenses (be accurate)
• Any additional non-monetary relief (if applicable)

Outcome of this step: the generator formats your requested relief so you can directly revise it to match your situation.

Step 5: Review the limitations language carefully

Because Maryland’s generator is using the general/default period (not a claim-type-specific period), your draft will likely incorporate a concept of a 3-year limitations check tied to Md. Code, Cts. & Jud. Proc. § 5-106.

Common scenarios

Maryland pro se filers often use a first-pass generator for recurring situations. Below are practical examples of how the inputs tend to affect the draft output—and where people commonly get tripped up.

1) Missing or approximate dates

If you only know “sometime in 2021,” enter your best estimate and explicitly describe uncertainty in your narrative.

• Effect on output: your draft will include the dates you enter, so your narrative may look more precise than your evidence supports.
• Best practice for accuracy: use exact dates where you have them (receipts, email headers, bank statements), and use “on or about” only if you truly can’t pin down the day.

2) You discovered the problem later than the event date

You might know:

• Service failure happened in June 2021

• You realized it in October 2021

• Effect on output: the generator’s SOL screening may still be based on the event date you provide. If you provide the discovery date instead, your 3-year calculation can shift.

• Key decision for you: choose the date that best matches the timeline you’re arguing—recognize this is not legal advice; it’s how the drafting inputs drive the output.

3) You’re targeting recovery of money

Requests like refund, repayment, or reimbursement are common.

• Effect on output: the relief section becomes a direct “what you want” list.
• Accuracy checklist:

  • Total amount you paid
  • Dates of payment
  • Any partial refunds
  • How you calculated the total

4) Multiple events across different years

Some disputes include:

• An initial breach

• Later communications

• Later refusal or nonperformance

• Effect on output: you may end up with a longer timeline section.

• What to watch: confirm consistency—every date in the narrative should connect to something you can state clearly (what happened on that date).

5) Potential mismatch with a non-general SOL statute

Even if you’re within 3 years under the general rule, your case might be governed by a different limitations statute.

• Effect on output: the draft may emphasize the general 3-year concept.
• Action you can take: use the output to organize your facts for later legal research and to prepare questions for a Maryland legal clinic or attorney if you want additional help.

Tips for accuracy

The quality of your output depends on the accuracy and completeness of your inputs. Use these tips to get a tighter first draft from DocketMath.

Use a date discipline

• Keep a simple timeline in a notebook (or Notes app) before you generate.
• Add exact dates in MM/DD/YYYY format.
• If you have multiple plausible dates, pick the one you can support with evidence.

Keep party names consistent

• Use the exact legal name of an LLC or business entity if you have it.
• Match spelling across all documents you reference in your pleading.

Write facts, not conclusions

Your draft

Related reading

• Pro Se Pleading Generator Guide for Alabama
• Pro Se Pleading Generator Guide for Arizona
• Pro Se Pleading Generator Guide for Colorado