How to run deadlines in DocketMath for North Carolina

Step-by-step

Run this scenario in DocketMath using the Deadline calculator.

This guide walks you through running deadlines in DocketMath for North Carolina (US-NC) using the platform’s deadline calculator. It’s written to help you model timelines—not to provide legal advice.

1) Open the deadline tool

1. Go to /tools/deadline
2. Select North Carolina (US-NC) as the jurisdiction if the tool asks.

If you’re using an older workflow or saved views, confirm the jurisdiction is set before you enter any dates.

2) Choose the deadline mode (what “deadline” means in the calculator)

In most DocketMath deadline setups, you’ll provide:

• a starting date (the event date or other trigger you’re modeling),
• a deadline rule (the time period),
• and optionally an adjustment approach (e.g., whether weekends/holidays matter, depending on the calculator’s options).

Because this walkthrough is about a North Carolina general baseline, you’ll typically use the default/general period rather than a claim-specific carve-out.

3) Use the correct baseline period for North Carolina (default/general)

DocketMath needs a time period to count from your starting date.

For North Carolina, your guide’s jurisdiction data lists the General SOL Period: 3 years. Use that as your baseline.

The jurisdiction data also references the SAFE Child Act. The referenced NC DOJ page focuses on supporting survivors and does not replace the general timing rule for every fact pattern.

Key constraint for this guide:

• No claim-type-specific sub-rule was found for this template run.
• Use the general/default 3-year period as the baseline in DocketMath.

4) Enter the event (starting) date

Pick the date that best matches the “start” concept shown in the DocketMath interface. Examples you might see in the UI:

• “Date of incident / event”
• “Notice date”
• “Accrual date” (if the tool uses that label)

Enter the date carefully in the format DocketMath expects (commonly YYYY-MM-DD, if the UI uses that standard).

How outputs change:
DocketMath counts forward from your anchor date, so changing the starting date by even a few days can shift the calculated deadline date.

5) Set the period to 3 years (general/default)

In the deadline rule or time-period field:

• select 3 years (or enter 3 with units set to years).

If the tool provides multiple “SOL” options, choose the one aligned with the general/default run for this guide’s setup (and avoid selecting any claim-type-specific option).

6) Configure any date-adjustment options (if available)

Some calculators include options for how to handle:

• weekends and court holidays,
• “last day” behavior,
• or “next business day” adjustments.

Use the options described in the tool. If you’re unsure, keep the default behavior and document the run settings—especially if you plan to compare scenarios.

7) Review the output: deadline date and timeline

After you run the calculation, DocketMath typically shows:

• a deadline (target) date, and
• the counted duration from the starting date.

For practical case management, record:

• the starting date you entered,
• the period used (3 years), and
• the deadline date returned by DocketMath.

8) Run scenario comparisons (optional but useful)

Even with a baseline of “3 years,” the start date is often the most sensitive input. Run a few scenarios to understand the scheduling impact:

• Scenario A: starting date = original event date
• Scenario B: starting date = later notice/accrual date
• Scenario C: starting date = discovery date (only if your tool’s labels support that concept)

This helps you see how DocketMath responds to factual timing differences.

9) Save or export your result (if your workflow supports it)

If your DocketMath environment provides export/share options:

• save the run name with the date you used (example: “NC general SOL 3y — incident 2024-05-10”),
• export a PDF/screenshot for internal tracking.

The goal is transparency: others should be able to replicate your timeline inputs and outputs.

Common pitfalls

The deadline tool is only as accurate as the inputs. These are common mistakes when running North Carolina general/default deadlines in DocketMath.

• Using a claim-type-specific period while the rest of your workflow assumes the general/default 3-year baseline
• Confusing the “start date” field (event date vs. notice date vs. accrual/discovery date)
• Editing the jurisdiction after entering dates (this can change which rule set the tool applies)
• Assuming “3 years” equals the same number of days in every scenario (leap years and date math can affect the final calendar date)
• Forgetting date adjustment settings (e.g., “next business day”) when the tool offers them
• Relying on one run for all purposes (different procedural deadlines may attach to different stages)

Pitfall example: If you enter a starting date like “May 1,” but the relevant triggering date is actually “May 6,” the computed deadline may shift by 5+ days—enough to matter for internal deadlines and scheduling.

Try it

Use this mini-exercise to confirm the DocketMath workflow end-to-end.

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

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

Quick checklist (before you click Calculate)

Example run (use your own dates)

1. Set Starting date: enter a specific calendar date (use a hypothetical event date if you’re testing).
2. Set Period: 3 years (general/default).
3. Click Calculate.
4. Note the generated deadline date.

Then run one comparison:

• change only the starting date by +7 days, re-calculate, and observe how the deadline date moves.

This confirms two key behaviors:

• DocketMath is counting forward from your anchor date, and
• the output is sensitive to the precise start date you provide.

When you’re ready for production use, make sure your internal records capture:

• the starting date,
• the selected general/default 3-year period, and
• the DocketMath deadline output.

Related reading

• Why deadlines results differ in Canada — Troubleshooting when results differ
• Worked example: deadlines in New York — Worked example with real statute citations
• Deadlines reference snapshot for New Hampshire — Rule summary with authoritative citations