How to calculate Offer Of Judgment Analyzer in Arkansas
6 min read
Published January 26, 2026 • Updated April 23, 2026 • By DocketMath Team
Trust release 4
This page includes a legal claim or source that failed the current primary-source review.
Quick takeaways
Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.
- In Arkansas, the offer-of-judgment acceptance window is 30 days from when the opposing party receives/was served with a written offer. This default period comes from Ark. Code Ann. § 16-66-402.
- DocketMath’s Offer Of Judgment Analyzer turns that 30-day statutory timing rule into specific calendar dates (deadline date) and then compares those dates to your entered acceptance/rejection dates.
- Your results mainly depend on two inputs:
- The offer “start” date you choose (the date you treat as when the written offer was provided/served/communicated), and
- The response timing you enter (acceptance date, rejection/response date, or “no response”).
- Based on the jurisdiction data provided, no claim-type-specific sub-rule was identified for this statute. So treat the 30-day period as the general/default rule under Ark. Code Ann. § 16-66-402.
Note: DocketMath is a calculation and workflow tool. This article explains how to calculate dates using Arkansas’s statutory timing rule, not how to win or lose a case.
Inputs you need
Before you open DocketMath’s Offer Of Judgment Analyzer at /tools/offer-of-judgment-analyzer, gather the details needed to drive the date math. In practice, the single most important choice is defining the “start” date consistently with your case record.
Use this checklist to confirm your inputs:
The statutory timing rule you’ll encode
Arkansas’s general rule provides:
- A party may offer a judgment in writing.
- The opposing party has 30 days to accept or reject the offer.
That timing language appears in Ark. Code Ann. § 16-66-402 (Justia source):
https://law.justia.com/codes/arkansas/2010/title-16/chapter-66/subchapter-4/16-66-402/
Warning: The calculator needs a reliable “start” date. If your workflow uses a date other than when the written offer was served/communicated (for example, the offer’s signature/drafting date), the computed deadline can drift by days—potentially changing whether a response is marked timely in your analysis.
How the calculation works
DocketMath’s Offer Of Judgment Analyzer is designed to translate the statute’s 30-day acceptance period into concrete calendar deadlines and timing comparisons.
DocketMath applies the Arkansas rule set to the inputs, then runs the calculation in ordered steps. It validates the trigger date, applies rate or cap logic, and produces a breakdown you can audit. If you change any one variable, the tool recalculates the downstream outputs immediately.
Step 1: Start the 30-day clock
Under Ark. Code Ann. § 16-66-402, the opposing party has 30 days to accept or reject after the written offer is made. In practical timelines, that typically means using the date your records treat as when the offer was provided to the opposing party—often your service/notice/communication date.
In DocketMath terms, set:
- Start date = your “offer provided/served” date
Then the calculator computes:
- Deadline date = Start date + 30 days
Step 2: Compute the deadline date
Because the statute specifies a flat 30 days period, the core math is straightforward:
- Deadline = start date plus 30 calendar days
Example (illustrative only—always plug in your real case dates):
- If the start date is March 1, 2026
- The 30-day deadline is March 31, 2026
DocketMath performs the same type of arithmetic based on your inputs.
Step 3: Compare the actual response date (if you have one)
Once the analyzer has the computed deadline, you can enter the response date(s) to evaluate timing outcomes.
Common comparisons:
- Timely acceptance: acceptance date is on or before the deadline
- Late acceptance: acceptance date is after the deadline
- No response: if you enter “no response,” the deadline acts as the cutoff point for acceptance consideration
Step 4: Keep jurisdiction rules attached to the timeline
For Arkansas, the relevant timing rule used in this workflow is Ark. Code Ann. § 16-66-402—the basis for the default 30-day acceptance/rejection period.
Clarity reminder for this article’s assumptions:
- No claim-type-specific sub-rule was identified for the 30-day window based on the jurisdiction data you provided.
- So the analyzer should apply the 30-day general/default rule under Ark. Code Ann. § 16-66-402.
Output fields to sanity-check
When you run the analyzer, review these computed/derived results:
- **Computed acceptance deadline (30 days)
- Days between start date and deadline
- Timeliness flag (if you entered acceptance/rejection/response dates)
- Timeline summary you can save for case notes or review
A practical audit note to keep with your case file:
- “Deadline computed from § 16-66-402 using 30-day clock; start date defined as service/notice/communication date.”
Common pitfalls
Even when the right statute is used, date tools can produce misleading “timely vs. late” outcomes if your inputs don’t match the legal record.
Pitfall: Using the wrong start date (for example, offer signed date instead of served/received date) shifts the 30-day clock and can flip the analyzer’s timing classification.
Pitfall checklist
- Offer signed date ≠ service/notice/communication date
- Email timestamp ≠ formal service/notice date (if separate)
- Mixing “business days” assumptions with the statutory “30 days” approach
- Your jurisdiction data indicates no claim-type-specific sub-rule for this 30-day period under Ark. Code Ann. § 16-66-402
- Without the acceptance/rejection date, you may get a deadline but lose the timeliness comparison
- If there were amended offers, re-serves, or substitute service events, confirm which event your “start date” represents
Quick diagnostic table
| What you see in DocketMath | Most common input issue to check |
|---|---|
| Deadline is earlier/later than expected | Start date used differs from your service/notice date |
| Timeliness outcome seems “reversed” | Acceptance date entered as the wrong calendar date |
| You expected business-day counting | Arkansas’s 30-day period here is treated as 30 days, not business days |
| Confusion about what rule applied | Confirm it’s Ark. Code Ann. § 16-66-402 default 30-day rule |
Sources and references
- Ark. Code Ann. § 16-66-402 (general offer acceptance/rejection timing; opposing party has 30 days)
https://law.justia.com/codes/arkansas/2010/title-16/chapter-66/subchapter-4/16-66-402/
Start with the primary authority for Arkansas and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.
Next steps
- Open DocketMath’s Offer Of Judgment Analyzer: /tools/offer-of-judgment-analyzer.
- Enter the offer start date based on your case record’s service/notice/communication event (the date you’re treating as when the written offer was provided).
- Enter the acceptance date (or rejection/response date). If there was no response, use your available “no response” option (if provided).
- Verify that the computed deadline reflects 30 days under Ark. Code Ann. § 16-66-402.
- Save the timeline summary to your case notes, along with a short statement of how you defined the “start” date.
If you need repeat calculations (e.g., an amended or re-served offer), keep your start date meaning consistent across runs.
