Pro Se Pleading Generator Guide for Arizona
7 min read
Published March 22, 2026 • By DocketMath Team
Pro Se Pleading Generator Guide for Arizona
Run this scenario in DocketMath using the Pro Se Pleading Generator calculator.
What this calculator does
DocketMath’s Pro Se Pleading Generator helps Arizona users draft a first-pass pro se pleading by turning your answers into a structured document you can review, edit, and file. The calculator is designed to help you:
- Organize your case facts into a readable pleading format
- Generate common legal headings and request language (based on your selections)
- Flag key timeline inputs so you can check deadlines before you submit
- Apply Arizona’s criminal statute of limitations framework when you’re building content that depends on timing
This guide focuses on Arizona criminal limitation timing using A.R.S. § 13-107(A) and related time windows you may see referenced in practice.
Note: This tool is for drafting support, not legal advice. Always verify requirements for your specific court, case type, and filing rules.
When to use it
Use DocketMath’s Pro Se Pleading Generator when you need a fast way to convert case details into a draft that you can polish. It’s especially helpful if you:
- Are filing as pro se in an Arizona matter and want a structured template
- Need to present dates clearly (incident date, discovery date, filing date, and any relevant intervals)
- Are preparing to address potential statute of limitations issues in your narrative or supporting statements
Statute of limitations timing (Arizona criminal)
Arizona’s general rule for criminal limitation periods is drawn from A.R.S. § 13-107(A). For purposes of this guide’s timing logic:
- General SOL period: 2 years
- Statute cited: A.R.S. § 13-107(A) — 2 years
- Referenced exceptions used by this guide:
- O2: “exception O2” (as captured in your tool’s internal option set)
- P3: a different referenced window of 3 years under A.R.S. § 13-107 (captured by the calculator as “exception P3”)
In plain terms: if your facts match the calculator’s selected exception options, your computed limitations window may shift from the default 2 years to a 3-year window.
Warning: Statute of limitations can depend on case-specific factors (including offense classification and how the relevant triggering event is treated). The generator can help you structure dates, but you still must confirm the right rule for your charge and procedural posture.
Step-by-step example
Below is a realistic “walk-through” showing how inputs affect the output. This example is illustrative and focuses on how the generator handles timing and pleading structure.
Scenario: A pro se defendant drafting a limitations-focused narrative
Assume you’re preparing a draft for an Arizona criminal case and you want to include a timeline that supports your limitations position.
Example inputs you might enter
Check the boxes and enter dates in the order your tool requests.
- Case type: Arizona criminal
- Incident date (alleged offense date): 2023-03-15
- Date of filing / notice date (when charges were filed): 2025-04-01
- Statute of limitations rule selection:
- If nothing special applies, select the default tied to A.R.S. § 13-107(A) (2-year window).
- If your facts match an exception, select the matching calculator option:
- Exception O2 (3-year or altered window depending on how the tool defines it)
- Exception P3 (3-year under A.R.S. § 13-107 as captured by this generator)
For this example, assume you select the default:
- Default SOL period: 2 years under **A.R.S. § 13-107(A)
What the calculator will compute
- Start with incident date: 2023-03-15
- Add the applicable SOL period:
- 2 years → 2025-03-15
- Compare to the charge filing/notice date:
- Filing/notice date: 2025-04-01
- Outcome in the draft timing language:
- The timeline supports the idea that the prosecution date is after the 2-year mark (based on the selected rule).
Pitfall: Many people accidentally use the wrong date as the “start” date (e.g., using a later “discovery” date instead of the alleged offense date). Make sure the date you enter matches the event your charge timeline uses.
Example output structure (what you’ll see in the draft)
Your generated pleading often includes sections that read like:
- Caption and case identifiers (if you provide them)
- Statement of facts ordered by date
- A limitations/timeline paragraph keyed to your chosen SOL rule
- A request for the relief you select (e.g., dismissal language tied to limitations, or an evidentiary/timeline request)
Even if the generator’s exact formatting varies with your selections, the core mechanics are consistent: your selected SOL window and dates drive the timeline paragraph.
Common scenarios
Arizona pro se drafting often runs into the same fact-pattern categories. Use the checklist below to determine what inputs you’ll likely need for a clean generator output.
Scenario checklist
When the 2-year default matters most
Default rule: 2 years under A.R.S. § 13-107(A).
If your charge was filed more than 2 years after the alleged offense date, your draft will typically reflect that timeline.
When exception options (O2 / P3) change the result
The generator includes “exception” selections that can shift the computed window:
- Exception O2: captured as a different rule path in the tool’s SOL logic set
- Exception P3: referenced in the brief as a 3-year window under A.R.S. § 13-107
If you select one of these options, the calculated “end date” likely changes, which changes how your draft’s limitations narrative reads.
Note: If you’re unsure whether an exception selection fits your facts, you can still use the tool to draft your timeline without making aggressive legal conclusions. Keep it factual: “On X date, Y occurred; charges were filed on Z date.”
Tips for accuracy
Getting the calculator’s output right depends on disciplined date entry and clear fact sequencing.
Date accuracy rules
Use these practical rules when you fill in your inputs:
- Enter dates in YYYY-MM-DD format if the tool requests it
- Use the same “start date” consistently throughout your draft
- Avoid mixing:
- offense date vs. report date vs. discovery date
- If you know only approximate dates, tighten them where possible (e.g., “March 15” instead of “March”)
Consistency checks before you copy into a filing
Before you finalize the draft, run this quick review:
How inputs change outputs (fast map)
Here’s a simple “cause → effect” table:
| Your input change | What it changes in the draft |
|---|---|
| Incident/offense date | The computed limitations end date shifts accordingly |
| Charges filing/notice date | Determines whether the draft describes the filing as before/after the window |
| SOL rule selection (default vs O2/P3 option) | Changes the total limitations period used (2 years default tied to A.R.S. § 13-107(A); 3-year paths captured as O2/P3 in tool logic) |
| Factual narrative choices (what occurred and when) | Alters the ordering and wording in the facts section |
Warning: The tool’s SOL logic is only as accurate as your selections. If the charge involves a different statutory framework than the generator’s option set, the draft timeline may not match the governing law for your exact offense.
Gentle filing reminder (non-legal advice)
Courts may require specific formatting, signature blocks, service statements, and local rule compliance. A strong draft is only one part of a successful filing—always check:
- the court’s pro se filing guidelines
- required caption/case number placement
- any page-length or formatting rules
