How TimelyFiled works
A one-page build write-up. Updated November 8, 2026.
What it does
TimelyFiled calculates California superior court deadlines: discovery responses, motions to compel further, deposition notices and objections, expert exchange and discovery cutoffs, records subpoenas, and opposition and reply dates for regular motions and summary judgment. You can answer a few questions or drop in the papers you were served. It reads the document, shows what it found, and asks you to confirm before it calculates. Then it can save the dates to your calendar as an .ics file.
Every date shows its work
Most deadline tools give you a date and ask you to trust it. TimelyFiled shows the chain of reasoning, so an attorney can check it in under a minute. For interrogatories e-served on Friday, October 9, 2026:
- Served Friday, Oct 9, 2026 by electronic service.
- Add 30 calendar days. Day 1 is the day after service. Day 30 is Sunday, Nov 8. CCP § 2030.260(a); § 12
- Add 2 court days for e-service: Monday, Nov 9, then Tuesday, Nov 10. CCP § 1010.6(a)(3)(B)
- Nov 10 is a court day, so nothing moves. CCP §§ 12, 12a, 2016.060
Responses due Tuesday, Nov 10, 2026. The page also warns that rolling day 30 forward first would give Nov 12, because the statutes do not settle the order.
Each result lists every rule it used and the date that rule was last checked against the official text. Where the answer depends on a reading of the law rather than its text, the page says so. Where it needs a fact it cannot know, it asks instead of guessing.
Why it runs only in your browser
Litigation papers are confidential. TimelyFiled has no server, no account and no database. Documents are read by code running in your own browser tab (pdf.js for text, Tesseract for scanned pages), and nothing you drop or type is uploaded, stored or sent to an AI service. Closing the tab erases everything. The site is static files, so there is nothing to breach.
How it is tested
One command, node run-tests.js, runs every check, and a deploy is built only when it passes:
| Hand-counted edge cases: court holidays on a Friday, mail across holiday weekends, court days versus calendar days, counting back from hearings and trial | 31 |
| Rule and worked-example checks, including every published 2026 and 2027 court holiday | 73 |
| Document reader checks | 91 |
| Rules-file checks: every section the code names is listed with a status, and every number used in date math comes from a verified rule | 5 |
Each edge case was counted by hand on a calendar before it was run. The document reader was also tested on 164 real litigation documents from a working practice: it found the right deadline on 40 of 45 deadline-bearing papers and asked the user on the other 5, which were scanned pages with an unreadable date. It invented a deadline on 0 of the 117 papers that had none.
How the rules are kept current
Statutes change, so the rules are data, not code. Every period, every service extension and the court holiday table live in one versioned file. Each rule carries its status and the date it was last compared with the official text on leginfo.legislature.ca.gov. A rule read only from a secondary source is labeled that way and never drives date math. For example, the summary judgment periods use the current 81-day notice, 20-day opposition and 11-day reply under CCP § 437c as amended effective January 1, 2025.
A written checklist sets two reviews a year. Each January, after new laws take effect, every section is re-checked against the official text. Each fall, the next year's court holidays are matched against published superior court calendars. Until a year is checked, results in that year carry a warning. If a scheduled review is missed, every result says so.
What it does not do
Federal courts, other states, local rules, unlawful detainer discovery, and court orders that set their own dates. Emergency court closures cannot be predicted, so it asks you to check. It is a calculation aid, not legal advice. See the terms.
Guides: discovery response deadlines · motion deadlines · deposition notice deadlines
Built in JavaScript with no framework and no backend. Hosted as static files on Cloudflare Pages.