Inputs you need for deadlines in United States (Federal)
9 min read
Published September 11, 2025 • Updated February 2, 2026 • By DocketMath Team
Inputs you will need
To calculate litigation deadlines in United States federal courts with DocketMath’s deadline calculator, you’ll need a short but precise set of inputs. Think of this as the “intake form” for a clean, reproducible calculation.
Use this checklist as you gather information (you can enter these directly in the DocketMath deadline calculator):
Core case context
Jurisdiction
- Value for this guide:
United States (Federal)/US-FED - Why it matters: Determines which rules engine to use (e.g., Federal Rules of Civil Procedure, Federal Rules of Appellate Procedure).
Court level / proceeding type
- Examples:
- District Court (civil)
- District Court (criminal)
- Court of Appeals
- Bankruptcy Court
- Why it matters: Different rulesets and timing schemes (FRCP vs. FRAP vs. local bankruptcy rules, etc.).
Local rule set (if available)
- Examples: S.D.N.Y., C.D. Cal., D. Mass, etc.
- Why it matters: Local rules often override or supplement default federal timing (e.g., shorter motion deadlines, special service rules).
Trigger event details
Trigger event type
- Examples (not exhaustive):
- Service of complaint
- Entry of judgment
- Service of motion
- Filing of notice of appeal
- Scheduling order issued
- Why it matters: The event type maps to a specific rule-based deadline (e.g., “14 days after entry of judgment” under a particular rule).
Trigger event date
- A specific calendar date (with certainty about the time zone and court’s “day” definition).
- Why it matters: All downstream dates are computed from this anchor.
Trigger event time (if relevant)
- Sometimes needed when:
- A rule measures hours instead of days.
- A filing cutoff is same-day (e.g., “within 24 hours of…”).
- Why it matters: Can shift the deadline into the next court day depending on cutoffs.
Service and delivery method
Service method
- Common options:
- ECF / electronic service
- Personal service
- Mail
- Overnight delivery / courier
- Why it matters: Some rules add or remove days based on service method; others do not.
Service location (if rule-dependent)
- Examples:
- Within the United States
- Outside the United States
- Why it matters: Certain time extensions or special rules may apply for foreign service.
Rule selection and customization
Governing rule / rule citation (if known)
- Examples:
- FRCP 6 (general time computation)
- FRCP 12 (responsive pleadings)
- FRAP 4 (time to appeal)
- Why it matters: Helps you choose the right template or event type in DocketMath and verify the logic.
Number of days / period length (if not fixed by rule)
- Examples:
- “30 days after service” (if specified in an order)
- “7 days before the hearing”
- Why it matters: Custom orders and stipulations often define their own timing.
Business days vs. calendar days
- Value options:
- Calendar days
- Court days / business days
- Why it matters: Changes how weekends and holidays are treated in the count.
Court calendar and holidays
Holiday set / court closure calendar
- Examples:
- Federal court holidays
- Specific court’s additional closure days (if available)
- Why it matters: Rules often push deadlines that fall on weekends or legal holidays to the next court day.
Weekend treatment
- Usually:
- Count weekends for longer periods, but
- Move the due date when it lands on Saturday/Sunday or a holiday.
- Why it matters: A 14-day period can land on a weekend and move to Monday.
Output preferences
Output granularity
- Options:
- Single final due date
- Step-by-step breakdown (with Explain++-style logic)
- Why it matters: More detail helps with documentation and review.
Time of day cutoffs (if relevant)
- Examples:
- 11:59 p.m. local time
- “Before midnight in the court’s time zone”
- “By 4:00 p.m. local time” (for certain in-person filings)
- Why it matters: For same-day or hour-based deadlines, the exact cutoff can change compliance.
Note: This checklist is about inputs for calculations, not what the law requires in any specific case. Always confirm the governing rules and any case-specific orders before relying on a computed date.
Where to find each input
Here’s where practitioners typically locate each data point before running a federal deadline in DocketMath.
Jurisdiction, court level, and local rules
Jurisdiction / court level
- Source:
- Caption of the complaint, notice of removal, or docket sheet.
- How it affects outputs:
- Selects the correct federal rules engine (e.g., FRCP vs. FRAP).
- Shifts the available event templates (e.g., district vs. appellate events).
Local rule set
- Source:
- Court’s website under “Local Rules” or “Standing Orders.”
- Links often appear on the CM/ECF login page.
- How it affects outputs:
- May shorten, lengthen, or modify default federal timing.
- Can add extra steps (e.g., meet-and-confer deadlines, reply limits).
Trigger event details
Trigger event type
- Source:
- Text of the governing rule, scheduling order, or minute entry.
- ECF docket description (e.g., “Order granting motion; responses due in 14 days”).
- How it affects outputs:
- Determines which deadline template DocketMath uses.
- Different events can invoke different computation rules even with the same number of days.
Trigger event date and time
- Source:
- ECF docket entry timestamp (for filings and orders).
- Certificate of service / proof of service (for served documents).
- How it affects outputs:
- The starting point of the count.
- Time of day may matter for hour-based or same-day deadlines.
Service and delivery method
Service method
- Source:
- Certificate of service attached to the filing.
- ECF Notice of Electronic Filing (NEF) for electronic service.
- How it affects outputs:
- Some rules previously added days for mail or other methods; modern amendments have narrowed this, and DocketMath’s logic follows the applicable version.
- In some contexts, electronic service is treated differently from mail.
Service location
- Source:
- Certificate of service describing where and how service was made.
- How it affects outputs:
- May change whether certain extensions or special provisions apply.
Rule selection and customization
Governing rule / citation
- Source:
- The rule or statute referenced in the order or scheduling notice (e.g., “pursuant to Fed. R. Civ. P. 12”).
- Federal Rules of Civil Procedure / Appellate Procedure text.
- How it affects outputs:
- Confirms you’re using the correct event type in DocketMath.
- Helps you validate the computed deadline against the rule language.
Number of days / period length
- Source:
- Scheduling orders, minute orders, stipulations, or specific rule subsections.
- How it affects outputs:
- Directly sets the length of the calculation window.
- Changing this input is often the main way to adapt a generic rule to a case-specific order.
Business vs. calendar days
- Source:
- Rule text (e.g., “days” vs. “court days” or “business days”).
- Sometimes clarified in local rules or standing orders.
- How it affects outputs:
- Calendar days count weekends; business days skip them.
- This can shift a deadline by several days in shorter periods.
Warning: Never assume “days” means “business days.” Federal rules often treat “days” as calendar days unless a specific rule or order says otherwise. Always confirm.
Court calendar and holidays
Holiday set / closure days
- Source:
- Court’s website (holiday schedule).
- Federal holiday lists published by the U.S. Office of Personnel Management.
- How it affects outputs:
- DocketMath excludes recognized holidays when rules require it and moves deadlines landing on a holiday to the next court day.
Weekend treatment
- Source:
- General time-computation rules (e.g., FRCP 6).
- How it affects outputs:
- Determines whether a weekend landing date is moved to Monday (or next business day).
Output preferences
Output granularity
- Source:
- Your workflow preference or your team’s documentation standards.
- How it affects outputs:
- A single date is fast but opaque.
- A step-by-step breakdown supports audits, file memos, and internal review.
Time-of-day cutoffs
- Source:
- Local rules, ECF procedures, or standing orders (e.g., filing cutoff times).
- How it affects outputs:
- For same-day or hour-based deadlines, can change whether a filing is timely.
Run it
Once you’ve gathered the inputs above, you’re ready to run your calculation in DocketMath’s deadline tool.
- Open the deadline calculator
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
If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.
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.