Spreadsheet checks before running deadlines in Maine
7 min read
Published June 12, 2025 • Updated February 2, 2026 • By DocketMath Team
Sanity-checking your spreadsheet before you run deadlines in Maine is less about perfectionism and more about not getting surprised later. A small typo in a rule number or a wrong “business days” setting can quietly ripple through an entire case schedule.
This post walks through how to sanity-check your spreadsheet inputs before using DocketMath’s Maine deadline calculator, and what kinds of issues the checker is designed to catch.
What the checker catches
Think of the checker as a pre-flight inspection for your deadline model. It doesn’t replace legal judgment or research, but it does flag patterns that commonly break Maine-specific calculations.
Here are the main categories it reviews:
- Date ordering problems (end date before start date).
- Rates entered as whole numbers instead of percentages.
- Missing caps or discounts in the spreadsheet.
- Inconsistent rounding or day-count conventions.
1. Maine rule and statute references
If you’re encoding Maine rules (e.g., “M.R. Civ. P. 6(a)”) into a spreadsheet, the checker looks for:
Spelling and format issues
- Inconsistent abbreviations (e.g., “MRCP 6a” vs. “M.R. Civ. P. 6(a)”)
- Obvious typos in rule numbers (e.g., “Rule 60(a)” when, in a timing context, you almost certainly meant “Rule 6(a)”)
Cross-rule conflicts
- Two different rules assigned to what appears to be the same triggering event
- Rules that don’t match the described event (e.g., labeling a deadline “time to serve complaint” but citing a rule that only governs motion practice)
Why it matters in Maine: the interaction of the Maine Rules of Civil Procedure with local orders or specific statutes can be subtle. If a cell’s description says one thing and the rule citation suggests another, the checker prompts you to confirm which one is right before you rely on it.
2. Date-counting methods (calendar vs. business vs. court days)
Maine deadline rules can hinge on how you count days:
- Calendar days vs. business days
- Whether weekends are skipped only when the period is under a certain length
- Whether legal holidays are excluded from the count or only matter if they land on the last day
The checker scans your spreadsheet for:
- Cells labeled “business days” that appear to be used as calendar days (or vice versa)
- Mixed methods in the same chain (e.g., 20 calendar days followed by 3 “business” days that are actually being treated as calendar days)
- Missing handling for Maine court holidays on the last day of a period
Note: DocketMath’s calculator will apply its own jurisdiction-specific counting rules. The spreadsheet checker is about aligning your inputs with those rules so you’re not building on a wrong assumption.
3. Triggering events and dependency chains
Most Maine litigation timelines are not a simple “X days from complaint” calculation. They’re chains:
- Answer due X days after service
- Motion due Y days after answer
- Opposition due Z days after motion, and so on
The checker looks for:
Missing triggers
A deadline that depends on another deadline that doesn’t exist in your sheet.Circular references
A deadline that ultimately depends on itself (e.g., Event A → Event B → Event A).Direction errors
“X days before hearing” encoded as “+X” instead of “–X”.
You’ll see prompts like:
- “This deadline is marked as ‘before’ an event, but the formula adds days. Did you mean to subtract?”
- “Event ‘Opposition due’ depends on ‘Hearing date,’ but ‘Hearing date’ depends on ‘Opposition due.’ Please break the loop.”
4. Maine-specific edge conditions
The checker won’t interpret Maine law for you, but it does look for red flags in how you’ve modeled common edge cases:
Service method assumptions
- Extra days for certain service methods (mail, electronic, etc.) that are hard-coded differently across your sheet.
Local vs. statewide rules
- Labels like “local order” or “standing order” that are referenced but not actually defined anywhere in the sheet.
Court-specific quirks
- Deadlines tied to “court business days” but modeled as generic business days without any holiday logic.
Where it can, the checker will surface a note like:
Pitfall: This deadline depends on “mail service” but doesn’t add any extra days. Confirm whether your Maine rule set requires additional time for service by mail or another method, and adjust the model accordingly.
When to run it
You don’t need to run the checker every time you tweak a color or add a note. It’s most valuable at a few key points in your workflow.
Run the checker before importing a spreadsheet into the Deadline workflow. It is especially helpful when you have multiple entries or when a teammate provided the inputs.
1. Right after you draft a new Maine template
When you first build a Maine-specific spreadsheet model—say, a general civil case timeline:
- You’ve listed out major events (complaint, service, answer, motions, etc.).
- You’ve added formulas for “X days after/before Y”.
- You’ve dropped in rule or statute references.
Run the checker here to catch:
- Mis-labeled day types (business vs. calendar)
- Gaps in your chain (e.g., a response due from an event you never defined)
- Inconsistent rule citations for the same kind of event
2. After copying a model from another jurisdiction
If you’ve reused a spreadsheet from a different state or from federal practice:
- Maine may count days differently.
- Maine rules may not match the rule numbers or structure you copied.
The checker will help surface:
- Non-Maine rule references that slipped through
- Date-counting assumptions that don’t align with Maine practice
- Triggering events that exist in one system but not in Maine
3. Before sharing with your team
If you treat your spreadsheet as a “mini rules engine” that others will rely on:
- Run the checker before you send it around.
- Fix or annotate any issues it flags.
- Add comments where the law is genuinely ambiguous and different approaches are reasonable.
Warning: The checker can’t tell you whether your legal interpretation of a Maine rule is correct; it only highlights structural and consistency issues. Always confirm the underlying law and court rules independently.
Try the checker
You don’t need to overhaul your entire workflow to use DocketMath with a Maine spreadsheet. The process is:
Prepare your spreadsheet
- One row per event or deadline.
- Columns for:
- Event name
- Triggering event name (if any)
- Offset (e.g., +21, –3)
- Day type (calendar/business)
- Rule/statute reference
- Optional: columns for comments, court, or case type.
Run your sheet through DocketMath’s checker
- Upload or connect your spreadsheet.
- Select Maine (US-ME) as the jurisdiction.
- Indicate whether your offsets are:
- “Days after/before”
- “Same-day events”
- Let the checker run its structural and consistency pass.
Review the flagged items
You’ll typically see categories like:
Issue type Example prompt Typical fix Day-type mismatch “Marked ‘business days’ but used as calendar days.” Align label with intended counting method. Missing trigger “Deadline references ‘Answer filed’ but that event is missing.” Add the event or change the dependency. Circular dependency “Event A and Event B depend on each other.” Break the loop by anchoring one to a base date. Rule/reference inconsistency “Two events share identical description but different rules.” Confirm which rule applies; update as needed. Adjust and re-run (if needed)
- Fix the structural issues first.
- If you change triggers or offsets, re-run the checker to confirm the chain is stable.
- Once your sheet passes the sanity checks, you’re ready to calculate live deadlines.
From there, you can send your cleaned-up inputs to DocketMath’s deadline calculator to generate actual dates, including Maine-specific weekend and holiday handling.