How to run deadlines in DocketMath for New Hampshire

Running New Hampshire deadlines in DocketMath is mostly about doing three things well:

• Picking the right jurisdiction (US-NH)
• Choosing the right calculator and trigger event
• Reading the output carefully (and documenting what you did)

This walkthrough focuses on the Deadline calculator for New Hampshire (US-NH) and assumes you already have a matter in mind (e.g., “deadline to respond to a complaint in New Hampshire Superior Court”).

Step-by-step

This section walks through a typical run using the Deadline calculator in DocketMath for New Hampshire.

• Select New Hampshire in the Deadline tool.
• Enter the trigger dates and any caps or rates.
• Run the calculation and save the output.

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

1. Start a new deadline run

1. Open DocketMath.
2. Go to the Deadline calculator.

   • From the main navigation, choose:
     Tools → Deadline (or go directly to /tools/deadline).
3. Click New calculation (or the equivalent “Start” button, depending on your interface).

You’ll land on a form that usually has these groups of inputs:

• Jurisdiction
• Event / Trigger
• Time period
• Service / method
• Calendaring options (weekends, holidays, etc.)
• Labels and notes

Each of these matters for New Hampshire.

2. Set the jurisdiction to New Hampshire (US-NH)

In the Jurisdiction field:

1. Start typing “New Hampshire” or “US-NH”.
2. Select New Hampshire (US-NH) from the list.

Why this matters:

• It tells DocketMath which ruleset and holiday calendar to use.
• It affects how weekends and state holidays are treated.
• It keeps your calculation distinct from, say, US-Federal or another state with different time-computation rules.

3. Choose the right trigger event

Next, pick the event that starts the clock.

Common New Hampshire examples:

• “Complaint served”
• “Order entered”
• “Judgment entered”
• “Motion served”
• “Notice of decision received”

In DocketMath, this usually looks like:

1. Event type: Pick from a dropdown (e.g., “Service of complaint,” “Entry of order”).
2. Event date: Enter the actual calendar date.
3. Event time (if available): Optional, but can matter for same-day or very short deadlines.

How to think about it:

• If the rule says “within 30 days after service,” your trigger is the service date, not the filing date.
• If the rule says “within 10 days after entry of judgment,” the trigger is the entry date on the docket.

4. Define the time period (days, weeks, months, etc.)

The time period is where you translate the rule text into an input.

Common patterns:

• “30 days after service” → 30 days
• “10 days after entry of order” → 10 days
• “3 months after judgment” → 3 months
• “1 year from date of injury” → 1 year

In DocketMath:

1. Enter the number (e.g., 30).
2. Choose the unit:

   • Days
   • Court days (if supported and jurisdictionally appropriate)
   • Weeks
   • Months
   • Years

For New Hampshire:

• Many civil rules count days and then address weekends/holidays separately.
• Some deadlines might be effectively “business days” only; others are calendar days.

If you’re unsure:

• Start with calendar days.
• Use the weekend/holiday options (see below) to match the rule’s treatment of non-business days.
• Add a note in DocketMath describing your interpretation.

5. Configure service/method (if applicable)

If the rule changes based on how service occurred (mail, electronic, personal), DocketMath may give you a Service / Method field.

Example workflow:

1. Select Method of service:

   • Personal
   • Mail
   • Electronic
   • Sheriff or certified mail, if separately listed
2. If the rule provides extra days for certain methods (e.g., “3 days if served by mail”), you have two options:

   • Use a built-in rule if DocketMath supports it for US-NH.
   • Or manually add those extra days as a separate calculation (e.g., base deadline + “mailing cushion”).

A simple pattern:

• Run the base deadline (e.g., “20 days after service”).
• Then, if mail adds 3 days, either:

  • Add a second deadline: “Base deadline + 3 days,” or
  • Adjust the time period to 23 days, and clearly note why in the description.

6. Set weekend and holiday behavior for New Hampshire

This is where the jurisdiction really matters.

In DocketMath you’ll usually see options like:

• If deadline falls on a weekend, move to next business day
• If deadline falls on a holiday, move to next business day
• Holiday calendar: **New Hampshire (US-NH)

For a New Hampshire state-court matter, you typically want:

• Holiday calendar: New Hampshire (US-NH), not federal-only.
• Weekend rule: Match how the New Hampshire rule extends deadlines that land on Saturday, Sunday, or legal holidays.

Common errors:

• Using no holiday calendar (deadline lands on a court-closed day).
• Using US Federal holidays when a New Hampshire-specific holiday is relevant.
• Forgetting that some rules count backwards (e.g., “at least X days before hearing”), which can interact differently with weekends.

7. Label and document the calculation

Before you run the calculation, add context:

• Title / Label examples:

  • “Answer to complaint – 30 days – NH Superior Court”
  • “Deadline to move to reconsider – 10 days after order – NH”
• Matter ID or file number (if your workflow uses them).
• Notes:

  • Cite the rule (e.g., “Based on N.H. R. Civ. P. [rule number]; 30 days after service; weekend/holiday extension applied.”).
  • Mention any assumptions (e.g., “Assumes service by mail; includes 3 extra days under [rule].”).

This documentation makes your DocketMath run reusable and auditable later.

8. Run the calculation and read the output

Click Calculate.

DocketMath will usually show:

• Final due date (and time, if applicable)
• Trigger event date
• Time period applied (e.g., “30 days”)
• Adjustments:

  • Weekend shift
  • Holiday shift
  • Additional days for service
• A timeline or breakdown showing intermediate steps

How to review:

• Confirm the trigger date matches your underlying document (complaint, order, etc.).
• Check the units (days vs months).
• Look at each adjustment:

  • Did a weekend move the date?
  • Did a New Hampshire holiday move it?
• Compare the result to your own quick, manual sense-check.

If anything looks wrong:

• Edit the calculation:

  • Change the jurisdiction (if you picked the wrong one).
  • Adjust the time period.
  • Turn weekend/holiday rules on or off.
• Re-run and re-check.

9. Save, export, or sync the deadline

Depending on your setup, you might:

• Save the calculation in DocketMath attached to a matter.
• Export the deadline:

  • Calendar file (e.g., .ics)
  • Spreadsheet or PDF summary
• Sync to a docketing or case-management system.

Best practices:

• Keep the label descriptive enough that someone else knows what the deadline is and how it was computed.
• Keep the notes with the rule citation and any assumptions.
• If you revise the calculation later (e.g., after learning service was by a different method), keep both versions or at least note the change.

Common pitfalls

Here are New Hampshire–specific patterns where users often go wrong in DocketMath.

• counting from the wrong triggering event
• ignoring court-closed days or holiday rules
• mixing calendar days with court days
• missing time-of-day cutoffs for filing

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

1. Wrong jurisdiction or holiday calendar

• Using US-Federal instead of US-NH.
• Using no holiday calendar at all, so a date lands on a court-closed day.
• Forgetting that New Hampshire may recognize holidays that don’t line up perfectly with federal holidays.

Mitigation:

• Always confirm the jurisdiction field says New Hampshire (US-NH).
• In the output, check whether any holiday adjustment was applied and that it references the expected holiday calendar.

2. Misreading “days” vs “business days”

Some rules are written in terms of days but have separate language about weekends and holidays. Others may effectively function like business days.

Common issues:

• Treating “10 days” as “10 court days” when the rule is actually 10 calendar days with a weekend/holiday extension.
• Or the reverse: assuming calendar days when the rule effectively needs business-day logic.

Mitigation:

• Decide whether to:

  • Use calendar days + weekend/holiday adjustment, or
  • Use a business-days or **court-days setting if the rule

Try it

Open the Deadline calculator and follow the steps above: Run the calculator.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

Related reading

• Why deadlines results differ in Canada

• Worked example: deadlines in New York

• Deadlines reference snapshot for New Hampshire

• Why we started the DocketMath blog