Tolling the statute of limitations in Arkansas

Direct answer

Run this scenario in DocketMath using the Statute Of Limitations calculator.

In Arkansas, the default statute of limitations (SOL) is 6 years under Ark. Code Ann. § 5-1-109(b)(2). DocketMath’s “statute-of-limitations” calculator can help you model how tolling affects a deadline by using the dates and tolling windows you provide.

Your brief note is important: no claim-type-specific tolling sub-rule was found. So this guide treats § 5-1-109(b)(2) as the general/default SOL period. If your situation involves a special fact pattern that changes the analysis, you’d still enter the relevant dates/tolling inputs into DocketMath and then re-check the resulting deadline.

What you need to know

Arkansas’s default rule for this guide is a 6-year SOL: Ark. Code Ann. § 5-1-109(b)(2). That means, absent a recognized tolling event you can place on a timeline, the clock runs under Arkansas’s default framework starting from the SOL “start” point used in your analysis.

“Tolling” is often used as an umbrella term for time-based effects, including:

• Pause (time stops running for a period)
• Extend (effective deadline moves later)
• Reset (less common; different treatment after a trigger)

DocketMath is designed for a “deadline modeling” workflow. You enter:

1. the baseline SOL period and
2. the relevant start date, and then
3. any tolling window(s) (date ranges) to see how the effective deadline changes.

The inputs that matter most (typical workflow)

Before you run DocketMath, gather these items:

• Start date for SOL calculation (often tied to the relevant event; verify your starting point)
• Baseline SOL period: 6 years in Arkansas under **Ark. Code Ann. § 5-1-109(b)(2)
• Tolling window(s) you believe apply (start and end dates)
• Whether tolling is:

  • a single continuous window, or
  • multiple separate windows
• A comparison date (e.g., filing/charging date or any milestone you’re trying to test for “timely” status)

If any tolling boundary date is uncertain (even by days), the computed deadline can shift. That’s why it’s worth tightening the factual dates where possible.

Step-by-step

Use these steps to model Arkansas SOL tolling with DocketMath using jurisdiction-aware defaults (US-AR).

1. Open DocketMath’s statute-of-limitations calculator

   • Go to: /tools/statute-of-limitations

2. Confirm jurisdiction

   • Select US-AR (Arkansas) so the tool uses Arkansas’s default 6-year SOL rule.

3. Set the baseline SOL period

   • For this guide, use 6 years as the baseline because Ark. Code Ann. § 5-1-109(b)(2) is the general/default SOL period identified in your brief.
   • Enter 6 years rather than guessing a different period.

4. **Enter the baseline date(s)

   • Provide the SOL start date your analysis uses (the tool may prompt for different “event” types—choose the one that matches your scenario).
   • Enter your comparison date (for example, the filing/charging date you’re checking against the deadline).

5. **Add tolling window(s)

   • If your scenario includes a tolling period, input the start and end of each tolling window.
   • If there are multiple windows, add them as separate windows so the tool totals the tolled time correctly.

6. Run the calculation and interpret results

   • DocketMath should produce an effective deadline after tolling.
   • Compare your comparison date to the effective deadline:

     • before the deadline,
     • on the deadline, or
     • after the deadline.

7. Stress-test the tolling inputs

   • If you’re uncertain about a tolling boundary, try a small “what if” change (for example, shift a tolling start date by a week).
   • This helps you identify which tolling date facts most affect whether the deadline is met.

Key statutes and citations

This guide’s default SOL baseline comes from:

• **Ark. Code Ann. § 5-1-109(b)(2)

  • General/default SOL period: 6 years

What this means for your modeling

• If your scenario does not involve a tolling event with a date range you can document, the 6-year baseline applies.
• If tolling is part of the scenario, the analysis becomes how the tolling affects elapsed time, which is operationalized in DocketMath through tolling windows (date ranges you input).

Scope note (important)

This write-up does not invent claim-type-specific tolling rules. Per your brief, no claim-type-specific sub-rule was found, so the practical approach is:

• use § 5-1-109(b)(2) as the default baseline, then
• model tolling by entering the applicable tolling windows you have.

Common pitfalls

When using DocketMath to “toll” the clock in Arkansas, watch for these common errors:

• Using the wrong SOL period

  • This guide uses 6 years under Ark. Code Ann. § 5-1-109(b)(2) as the baseline. Don’t switch periods unless you have a clearly applicable rule for your situation.

• Assuming tolling without usable dates

  • DocketMath needs start/end dates for tolling windows. A label (“tolling happened”) isn’t enough to compute an updated deadline.

• Relying on approximate boundary dates

  • “Late February” vs. “February 24” can change whether a deadline is met.

• Double-counting the same time

  • If the same real-world event is represented twice (e.g., overlapping pause windows and another adjustment), you may unintentionally count some days more than once.

• Forgetting jurisdiction settings

  • Make sure the tool is set to US-AR. Otherwise, a different state’s assumptions could silently change the output.

• Skipping sensitivity checks

  • If the tolling date boundaries are uncertain, run small variations to see how “fragile” the deadline result is.

Practical takeaway: Many deadline disputes hinge on whether tolling begins/ends on the exact date reflected in the record. Treat those dates as high-impact inputs.

Run the numbers

Below are simplified example scenarios to show how Arkansas’s 6-year default (from Ark. Code Ann. § 5-1-109(b)(2)) interacts with tolling windows when modeled in DocketMath.

Baseline assumption

• Jurisdiction: US-AR
• Baseline SOL: 6 years (default)
• Illustration format: “event date → baseline deadline,” then add tolling time.

Scenario A — No tolling

• Event date: Jan 15, 2020
• Baseline SOL deadline: Jan 15, 2026
• Comparison date: Jul 1, 2025
• Result: Comparison date is before the deadline

Scenario B — Tolling pauses for 90 days

• Event date: Jan 15, 2020
• Baseline deadline: Jan 15, 2026
• Tolling window total: 90 days
• Effective deadline: ~Apr 14, 2026 (baseline deadline + 90 days)
• Comparison date: Feb 1, 2026
• Result: Likely within the deadline (exact outcome depends on the exact tolling window boundaries you input)

Scenario C — Multiple tolling windows

• Event date: Jan 15, 2020
• Tolling window #1: 45 days
• Tolling window #2: 30 days
• Total tolled time: 75 days
• Effective deadline: ~Mar 31, 2026 (baseline + 75 days)
• Comparison date: Mar 15, 2026
• Result: Within deadline (again, depends on exact start/end dates)

How DocketMath outputs change as inputs change

As you add tolling windows in DocketMath:

• The effective deadline moves later by the amount of tolled time you enter.
• Whether your comparison date is timely may flip if it sits near the boundary.

Quick sanity-check table:

Related reading

• Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
• Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
• Choosing the right statute of limitations tool for Connecticut — How to choose the right calculator