Extract Every Deadline From a Contract or Court Order
Have Claude extract every fixed date, recurring obligation, and triggered deadline from a legal document into a verifiable list you can docket.
When to use this
Deadlines hide in dense contracts, scheduling orders, and leases, and a missed deadline can become a malpractice claim. This workflow uses Claude as a second set of eyes to surface every date and obligation, with the controlling language quoted, so none slip through. Claude drafts the list and shows its arithmetic, but you confirm every date and own the calendar.
Deadlines are scattered throughout legal documents: a fixed closing date in one section, a 30-day cure period buried in a default clause, a recurring insurance certificate obligation in an exhibit, an expert disclosure cutoff in a scheduling order. Reading for all of them by hand is tedious, high-stakes work where things get missed.
Claude can comb a document and pull every date, obligation, and notice trigger into one organized table, quoting the language that creates each one. It is particularly useful for conditional deadlines that are easy to overlook because they only fire when something else happens. Think of it as a thorough first pass alongside your own read.
The one thing Claude cannot do is compute your actual calendar dates. It does not know your jurisdiction's counting rules, court holidays, weekend and mailing extensions, or which counting method governs. So every relative deadline it calculates is a worksheet you must confirm against the governing rules. Used this way, Claude helps you catch deadlines; it never owns your calendar.
The Workflow
Paste the document and state what it is and your role
Open one Claude conversation and give it the full text of the document, including exhibits and schedules, in <document> tags, followed by the context it needs: what kind of document this is, which side you represent, and today's date as an anchor. Context shapes which obligations matter to you and who owes them.
Prompt<document type="[CONTRACT / SCHEDULING ORDER / COMMERCIAL LEASE / SETTLEMENT AGREEMENT]" date="[DOCUMENT DATE]"> [PASTE THE FULL TEXT OF THE DOCUMENT HERE, INCLUDING EXHIBITS AND SCHEDULES] </document> I am a lawyer reviewing the document above so I can docket every deadline. Context: - I represent: [CLIENT ROLE, e.g., the buyer / the defendant / the tenant] - Today's date: [DATE] - Governing law / court (if stated): [JURISDICTION] Read the entire document carefully. Do not extract dates yet. Confirm you have read it, tell me how many sections or articles it contains, and list any exhibits, schedules, or incorporated documents it references, noting which ones are included above and which are missing.
What you get: Claude confirms it has read the document, reports the rough structure, and lists referenced exhibits or incorporated documents, flagging any that are missing. This reminds you to paste attachments you left out before extraction.
Extract every date, obligation, and trigger into a table
Ask Claude to pull everything time-related into a single structured table. Have it separate fixed calendar dates from conditional deadlines that only fire when something happens, and quote the language and section for each so you can verify against the source.
PromptNow extract every deadline, time-sensitive obligation, and notice trigger in the document. Include three categories: (1) fixed calendar dates, (2) recurring or ongoing obligations, and (3) conditional or triggered deadlines (anything that runs from an event, e.g., "within 30 days of service" or "upon written notice"). Put everything in one table with these exact columns: | Item | Date or trigger | Triggering language (quoted) and section | Who owes it | Rules: - Quote the operative triggering language verbatim and cite the section, article, or paragraph number. - In "Who owes it," name the responsible party from my perspective (my client, the other side, or both). - Do not skip anything time-related, even if it seems minor. Err on the side of over-inclusion. - If a date is ambiguous or you are unsure whether something is a deadline, include it and add FLAG in the Item column with a short note. - If a provision refers to a deadline set by a rule or statute rather than stating it, list it as [APPLICABLE RULE: attorney to confirm] instead of stating the period. - Do not compute any calendar dates yet.
What you get: A single table covering fixed, recurring, and conditional deadlines, each with the quoted triggering language, its section cite, and the responsible party. Ambiguous items are marked FLAG and rule-based periods are left as placeholders. No dates are computed yet.
Show the math for relative deadlines, but flag that you must verify
For every deadline that runs from an event, have Claude lay out its arithmetic transparently so you can check it. The point is not to trust Claude's date; it is to see the raw building blocks and then compute the real date yourself under the governing rules.
PromptFor each conditional or triggered deadline in the table, show the raw computation as a draft only. For each one, give me: - The trigger event and where it is defined (quote it) - The number of days or months stated - Whether the document says calendar days or business days (quote it if stated; write "not specified" if not) - A naive end date assuming straight calendar counting from the stated trigger date, if one is known Then, for every computed date, add this exact caution on its own line: "DRAFT DATE: verify against governing rules; do not docket as-is." You do NOT know my jurisdiction's date-computation rules (court holidays, weekend roll-overs, mailing or service extensions, or which counting method applies). Do not try to apply any of those rules. Show the naive arithmetic so I can compute the real date myself.
What you get: For each relative deadline, Claude shows the trigger, the day or month count, the calendar-vs-business-day language, and a naive end date, each stamped with the DRAFT DATE caution. It does not apply holiday, weekend, or mailing rules, leaving the real computation to you.
Produce a clean tickler list to enter into your docketing system
Have Claude reformat everything into a plain, scannable list you can transfer into your calendar or docketing software. Keep the source cite on each line so that when you verify a date, you can jump straight back to the controlling language.
PromptNow produce a clean tickler list I can enter into a docketing system. Format each entry as a single line: DEADLINE: [item] | DATE: [fixed date OR "trigger + N days, TO BE COMPUTED"] | OWNER: [who] | SOURCE: [section cite] Group the list in three parts: (1) Fixed dates, (2) Triggered deadlines to be computed, and (3) Recurring obligations. Keep the DRAFT DATE caution on any computed entry and keep every FLAG. At the very top, add a one-line reminder that every date must be verified against the governing rules before it is docketed. At the bottom, list any referenced exhibit or document I haven't given you.
What you get: A grouped, one-line-per-item list (fixed dates, triggered deadlines to compute, recurring obligations) with owner and section cite on each line, ready to paste into your calendar or docketing software, topped by a verify-before-docketing reminder.
Verify every date and obligation before docketing
This is the step you own. Open the document alongside Claude's list and confirm each entry against the source. Re-compute every relative deadline yourself under the governing rules: your jurisdiction's counting method, court holidays, weekend roll-overs, and any mailing or service extensions. Check that nothing was missed (review the exhibits and any incorporated documents) and that Claude did not invent a deadline that is not in the text. Only after you confirm a date should it go into your docketing system.
What you get: A docket you can stand behind: every fixed date checked against the document, every triggered deadline independently computed under the governing rules, exhibits reviewed, and any invented or missing items corrected. The verified list is what you docket, never Claude's raw dates.
Example Output
Illustrative example — names, facts, and figures are fictional.
VERIFY EVERY DATE BELOW AGAINST THE GOVERNING RULES BEFORE DOCKETING. (Fictional purchase agreement.) --- FIXED DATES --- DEADLINE: Closing date | DATE: 2026-08-14 | OWNER: Both parties | SOURCE: § 2.1 DEADLINE: Buyer's earnest money deposit due | DATE: 2026-06-19 | OWNER: My client (buyer) | SOURCE: § 3.2 DEADLINE: Seller delivers title commitment | DATE: 2026-07-01 | OWNER: Other side (seller) | SOURCE: § 5.1 --- TRIGGERED DEADLINES (TO BE COMPUTED) --- DEADLINE: Buyer's objection to title defects | DATE: title commitment receipt + 10 business days, TO BE COMPUTED (DRAFT DATE, verify) | OWNER: My client | SOURCE: § 5.2 DEADLINE: Seller's cure of noticed defects | DATE: objection notice + 30 calendar days, TO BE COMPUTED (DRAFT DATE, verify) | OWNER: Other side | SOURCE: § 5.3 DEADLINE: Inspection contingency expires | DATE: effective date + 21 days (calendar vs. business: not specified), TO BE COMPUTED (DRAFT DATE, verify) | OWNER: My client | SOURCE: § 6.1 DEADLINE [FLAG]: Notice of financing denial; clause says "promptly," no day count | DATE: ambiguous, confirm intended period | OWNER: My client | SOURCE: § 7.4 --- RECURRING OBLIGATIONS --- DEADLINE: Maintain hazard insurance through closing | DATE: ongoing until 2026-08-14 | OWNER: Other side (seller) | SOURCE: § 8.2 DEADLINE: Monthly property condition report | DATE: 1st of each month until closing | OWNER: Other side | SOURCE: § 8.3 MISSING: Exhibit B is referenced in § 5.1 but was not included. Paste it so I can check it for additional deadlines.
Tips
- •Always paste the exhibits, schedules, and any incorporated documents too. Deadlines often hide in attachments, and Claude can only extract from what you give it.
- •Treat business days versus calendar days as a trap. Have Claude quote the exact language, then apply your jurisdiction's counting method yourself; the two can differ by a week or more.
- •Re-run the extraction in a fresh conversation for a critical document and compare the two tables. A second pass can surface an obligation the first one glossed over.
- •Never docket a Claude-computed date as-is. Use its arithmetic as a worksheet, then confirm the real date against court holidays, weekend roll-overs, and mailing or service rules before it touches your calendar.
A note on confidentiality
The documents here range from public scheduling orders to confidential deal documents: purchase agreements with price and financing terms, leases, settlement agreements that often carry their own confidentiality clauses, and loan documents with borrower financial covenants. Check whether a settlement agreement or NDA restricts sharing the document, and redact pricing, account numbers, and personal information you don't need to find deadlines (dates, triggers, and obligations are what matter). Run client work on a commercial plan (Team or Enterprise) whose terms exclude your content from model training. On Pro or Max, disable model training in Privacy settings; a commercial plan's contract terms are the stronger answer for client work. Confirm this use fits your duties under ABA Formal Opinion 512 and Model Rule 1.6. Every output is a draft for attorney review: verify each date and quoted provision against the source before docketing.
Frequently Asked Questions
Can I just trust the dates Claude calculates and docket them?
No. Claude does not know your jurisdiction's date-computation rules (court holidays, weekend and mailing extensions, or which counting method applies), so every computed date is a draft. Use its arithmetic as a worksheet, then compute and confirm the real calendar date yourself before docketing. The calendar is your responsibility.
What types of documents does this workflow work on?
Any document with embedded deadlines or time-sensitive obligations: commercial contracts, scheduling and case-management orders, leases, settlement agreements, loan documents, and corporate agreements with notice or cure provisions. The same extract-then-verify approach applies; tell Claude the document type and your role up front so it knows which obligations matter to you.
Will Claude catch every deadline on its own?
Treat it as a strong first pass, not a guarantee. Claude can catch conditional deadlines that are easy to skim past, but it can only extract from the text you paste, so missing exhibits mean missing deadlines. Read the document yourself against Claude's list, paste any incorporated attachments, and confirm nothing was added or omitted before you rely on it.
Prompts used in this workflow
Get New Workflows Like This Every Week
Join the free Claude for Lawyers newsletter — practical workflows, prompts, and guides for everyday practice.