Inputs you will need

To calculate litigation deadlines in North Carolina with DocketMath’s deadline calculator, you’ll need a small but critical set of inputs. Think of these as the “ingredients” that control how the calendar behaves.

Use this checklist as you set up a calculation in US‑NC (North Carolina):

1. Trigger event

• Trigger event type (e.g., service of complaint, entry of judgment, service of discovery)
• Trigger event date
• Trigger event time (only if time-of-day matters under the rule)

How it affects the output:

• Determines when the clock starts (e.g., date of service vs. day after).
• Determines which rule set (and sometimes which sub-rules) DocketMath applies.

2. Method of service (if applicable)

• Service method (e.g., personal service, mail, designated delivery service, email/electronic)

How it affects the output:

• Controls whether additional days are added (for service by mail or certain electronic methods, depending on the rule).
• Can change when service is deemed complete (e.g., date sent vs. date received).

3. Document type / procedural action

• Type of paper or action (e.g., answer, motion, notice of appeal, responses to interrogatories)

How it affects the output:

• Determines which specific deadline DocketMath applies (e.g., 30 days to answer vs. 10 days to move to strike).
• Can change whether the period is counted in days, business days, or another unit.

4. Counting rules (days vs. business days)

• Calendar days vs. business days (often dictated by the rule)
• Whether to include or exclude weekends and holidays (per North Carolina rules for that deadline)

How it affects the output:

• Directly changes the end date.
• Controls whether the deadline rolls forward when it lands on a Saturday, Sunday, or legal holiday.

5. Court / jurisdiction context

• Jurisdiction: North Carolina (US‑NC)
• Court level (e.g., District Court, Superior Court, Court of Appeals, Supreme Court)
• Case type (civil, criminal, appellate, administrative) when relevant

How it affects the output:

• Ensures DocketMath applies North Carolina–specific rules, not federal or another state’s rules.
• Some deadlines vary by court level or case type (e.g., trial vs. appeal).

6. Holidays and court-closure rules

• Recognized North Carolina legal holidays
• Court-specific closure days (if known and relevant)

How it affects the output:

• Impacts whether a deadline that falls on a holiday or closure date moves to the next open day.
• Important when you’re near year-end, long weekends, or emergency closures.

7. Multiple, related deadlines (chains)

• Whether this event will trigger other deadlines (e.g., service of complaint → answer deadline → motion deadlines)
• Dependencies between deadlines (e.g., “X days after ruling on motion”)

How it affects the output:

• Allows DocketMath to chain calculations so that one trigger generates multiple dates.
• Helps you see a timeline instead of isolated dates.

8. Time-zone and filing cut-off assumptions

• Court’s time zone (usually Eastern for North Carolina state courts)
• Filing cut-off time (e.g., 5:00 p.m. local time, or e-filing rules if applicable)

How it affects the output:

• Can matter for same-day vs. next-day filing decisions.
• Helps you align the deadline date with your internal “file by” time.

Where to find each input

You already have most of this information in your file. The key is knowing where to look and how to label it consistently in DocketMath.

Trigger event and method of service

Look in:

• Proof of service / certificate of service
• Sheriff’s return or process server affidavit
• E-filing confirmation or email notice
• Stamped orders or judgments

You’re looking for:

• The date the document was served or entered.
• The method (e.g., “served by depositing in the U.S. Mail,” “served via electronic filing system,” “personally served”).
• Any language about when service is deemed complete.

Map that to DocketMath:

• Event type: “Service of complaint,” “Entry of order,” “Service of discovery,” etc.
• Service method: “Mail,” “Personal,” “E-service,” etc.

Document type / procedural action

Look in:

• The caption and title of the document (e.g., “Defendant’s First Set of Interrogatories”).
• The rule citation in your task list or notes (e.g., “NC R. Civ. P. 12(a)”).

You’re trying to answer:

• “What is this response or action supposed to be?”
• “Which North Carolina rule sets the timing?”

In DocketMath:

• Choose the matching action in the deadline calculator.
• If multiple rules might apply, pick the one that matches your actual planned filing (e.g., answer vs. motion to dismiss).

Counting rules and holidays

Look in:

• The text of the rule (for whether it says “days” or “business days” and how to count).
• Local rules or administrative orders for any special counting rules or local holidays.
• North Carolina court calendars for holiday closures.

In DocketMath:

• The jurisdiction setting (US‑NC) will automatically apply North Carolina’s standard counting rules for the selected deadline.
• You mainly confirm:

  • That the calculator is using the right rule for your event.
  • That any special local orders are accounted for in your workflow.

Court / jurisdiction context

Look in:

• The caption of the case (e.g., “In the General Court of Justice, Superior Court Division”).
• Notices of appeal or appellate filings (to identify Court of Appeals vs. Supreme Court).

In DocketMath:

• Set the jurisdiction to North Carolina (US‑NC) in the deadline calculator.
• Where the tool lets you choose court level or case type, match what’s in the caption.

Multiple, related deadlines

Look in:

• Your case management system or internal checklist.
• The rule series you’re working under (e.g., discovery rules, appellate rules).
• Any scheduling orders entered in the case.

In DocketMath:

• Start with the earliest trigger (e.g., service of complaint, entry of judgment).
• Use the tool to generate all relevant rule-based deadlines from that event.
• For later events (like entry of a ruling), repeat the process and link the calculations in your notes.

Time-zone and filing cut-off assumptions

Look in:

• Local rules and e-filing policies for the specific North Carolina court.
• Court website pages describing filing hours and electronic filing deadlines.

In DocketMath:

• The date-level calculation assumes the court’s local calendar.
• Capture any internal firm policy (e.g., “treat all deadlines as 3:00 p.m. firm internal cutoff”) in your case notes, even though the calculator focuses on the date itself.

Run it

Once you have your inputs, you’re ready to run a North Carolina deadline in DocketMath.

Step 1: Open the deadline calculator

1. Go to DocketMath’s deadline calculator.
2. Set the jurisdiction to North Carolina (US‑NC).

Step 2: Enter the trigger event

• Select the event type that matches your situation (e.g., “Service of complaint,” “Entry of order,” “Service of discovery requests”).
• Enter the trigger date.
• If the calculator supports time-of-day for that rule and it matters, enter the time as well.

Step 3: Add service and document details

• Choose the method of service (mail, personal, electronic, etc.).
• Choose the document/action type you’re calculating a deadline for (e.g., “Answer,” “Responses to interrogatories,” “Notice of appeal”).

DocketMath will:

• Apply the North Carolina timing rule associated with that action.
• Add any extra days required for the selected service method, if applicable.

Step 4: Confirm counting rules and holidays

• Check that the calculator is using:

  • The expected number of days.
  • The right day type (calendar vs. business).
  • The correct weekend/holiday adjustment (e.g., moving to the next business day).

If something doesn’t match the rule you’re working from:

• Adjust your event type or action type selection.
• Confirm you’re in US‑NC and not a federal or other state jurisdiction.

Step 5: Review and document

Before you rely on the result:

1. Review the output date(s) against the rule text you’re using.
2. Note any local rules, standing orders, or emergency orders that might alter the standard timing.
3. Record your assumptions (service method, time zone, filing cut-off, and any overrides) in your file or case management system.

Related reading

For more detail on using DocketMath with state-specific rules and building reliable deadline workflows, see:

• All DocketMath tools
• [How to build rule-based

Inputs you will need

Use this checklist to gather the core inputs before you run the Deadline tool.

• trigger event date
• rule set (civil/criminal or local rule)
• court level or venue
• service method
• holiday/weekend calendar
• time zone and filing cutoffs

Capture the source for each input so another team member can verify the same result quickly.

Where to find each input

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

Run it

Enter the inputs in DocketMath and run the Deadline calculation to generate a clean breakdown: Run the calculator.

Capture the source for each input so another team member can verify the same result quickly.

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

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