Systems and records
Contract notice deadline dataset: one deadline, several dates
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
Represent a notice deadline as a derived answer, not a typed date. Store the anchor event and the term inputs behind it, the notice offset, the counting convention, the business-day calendar and time zone, the delivery rule and address in force, and the contract version each came from. Keep the computed deadline beside those inputs, record actual dispatch and receipt evidence, and leave the label unresolved until counsel confirms any disputed input.
License terms
Contract notice deadline
Key takeaways
- A notice deadline is computed from an anchor, an offset, a counting convention, a calendar, a time zone and a delivery rule, and each can change separately.
- The contract's own computation language controls; court rules such as FRCP 6 are an example of an explicit convention, not a default for private agreements.
- Dispatch, delivery and receipt belong in separate fields with evidence, because the notices clause decides which one must fall inside the window.
- Conflicting documents, doubtful addresses and unstated conventions should produce an unresolved label rather than a guessed date.
- Only counsel-screened, nonprivileged process evidence belongs in a dataset, with an exclusion record showing what was held back.
How do you represent a notice deadline that depends on several dates?
Store the deadline as a derived answer, never as a typed-in date. A usable record keeps every input that produced it: the anchor date (usually the end of the current term), the offset (for example 90 days), the direction of counting, the counting convention, the business-day calendar, the time zone, the delivery rule that decides when notice counts, and the contract version each input came from. The computed date sits beside those inputs with a status that says whether counsel has confirmed it.
That split matters because the inputs change on different schedules. An amendment can lengthen the notice period without touching the term. A renewal moves the anchor date by a full term while the offset stays the same. A new notice address changes which delivery evidence counts. A record that holds only the final date cannot be recomputed when any of these move, and a model trained on it learns to copy dates rather than reason about them.
A contract notice deadline dataset built this way turns each deadline into a small task: here are the governing documents, here are the dated facts, apply the rule and produce the last day to give notice, with the clause and version that justify each step. The rest of this page gives the field-level structure for that task, the authority questions a legal operations team has to answer before filling it, and the cases where the model should hand the question back to counsel.
Which dates feed a contract notice deadline?
Most notice deadlines combine four to six dates, and only some of them appear on the signature page. The anchor is rarely the signing date. It is usually the expiration of the current term, which itself depends on the effective date, the initial term length and how many renewals have already occurred.
Public contract review datasets show how these elements are usually labeled. The Contract Understanding Atticus Dataset, an expert-annotated set of commercial contracts, groups its clause labels into categories that include dates and renewal terms alongside parties, governing law and license grants. Those labels identify where a date is stated; they do not compute the deadline, which is the gap a task structure fills.
| Date or value | Where it usually lives | How it moves the deadline | Common trap |
|---|---|---|---|
| Effective date | Preamble, signature block or a defined term | Starts the initial term and every later term | Effective date differs from the last signature date |
| Initial term and renewal term length | Term clause | Sets the anchor: the end of the current term | Renewal term shorter than the initial term |
| Number of renewals so far | Renewal history, order forms, invoices | Shifts the anchor forward by whole terms | A missed renewal treated as a termination |
| Notice period | Renewal or termination clause, later amendments | Offset counted back from the anchor | Amendment changed the period but not the clause cross-reference |
| Counting convention | Interpretation or notices clause, governing law | Decides whether the anchor day and weekends count | Calendar days assumed where business days were written |
| Delivery rule | Notices clause | Decides whether dispatch or receipt must fall inside the window | Email notice used where the clause requires courier |
| Notice address and recipient | Notices clause, address-change notices | Decides which delivery evidence is valid | Notice sent to an address replaced by a later notice |
| Time zone and place | Notices clause or principal place of business | Decides which calendar day a late delivery falls on | Server timestamp in UTC compared with a local-day deadline |
Whose counting convention applies: the contract's, a statute's or a court rule's?
The contract's own computation language comes first; record it word for word and treat everything else as a fallback that counsel chooses. Many agreements say nothing about how days are counted, and teams fill the gap with habits borrowed from litigation calendars.
Court rules are a useful reference for what an explicit convention looks like, not a default for contracts. Federal Rule of Civil Procedure 6(a) excludes the day of the triggering event, counts every day including intermediate weekends and legal holidays, includes the last day, and rolls a deadline that lands on a Saturday, Sunday or legal holiday forward to the next day that is not one. Rule 6(d) adds three days after the period would otherwise expire for certain service methods, including mail. These rules govern time periods in federal civil litigation; whether anything similar applies to a private notice period is a question for counsel under the governing law.
Holiday calendars need their own authority field. The federal list of legal public holidays in 5 U.S.C. 6103 names eleven days, including Juneteenth National Independence Day, but a contract may define business days by reference to banks in a named city, to the recipient's location or to nothing at all. Store the calendar identifier and its source, not a boolean that says holidays were considered.
Time zones are the quiet failure. The maintainers of the IANA time zone database warn that predictions of future local times will be wrong if governments change their rules after the prediction was made. A deadline record should therefore store the local date and the named zone, such as America/Chicago, rather than a precomputed UTC instant, and recompute when the database changes.
Does the clock stop when notice is sent, delivered or received?
Whichever moment the notices clause names: record dispatch, delivery and actual receipt as three separate fields, then let the rule pick one. Agreements commonly deem notice given on personal delivery, on a set number of days after mailing, or on confirmed transmission, and those rules change which date must fall inside the window.
Where a contract is silent, general law supplies a default that counsel must identify. The Uniform Commercial Code, for example, separates giving notice, which means taking reasonable steps to inform the other person whether or not that person actually learns of it, from receiving notice, which happens when it comes to the person's attention or is duly delivered to a place the person holds out for such communications. A dataset that stores only a sent date cannot represent a receipt rule, and one that stores only a received date cannot represent a dispatch rule.
Keep the evidence object with each timestamp: the courier tracking record, the certified-mail receipt, the email server log or the signed acknowledgment. The evidence type is part of the label, because a clause that requires courier delivery is not satisfied by an email that arrived earlier.
The date evidence and rule task structure
The asset below is a counsel reviewed date evidence and rule task structure. Each row is a field a legal operations team fills from nonprivileged records; the last column is the check that keeps the task honest. Fields marked as counsel decisions are filled only after a qualified lawyer has reviewed them, and the reviewer and review date travel with the record.
At a glance
The date evidence and rule task structure
| Field | What it holds | Source authority to record | Validation rule |
|---|---|---|---|
| matter_and_contract_ids | Pseudonymous contract family ID, document IDs and version numbers | Contract management system record | Every input below cites one of these document IDs |
| anchor_event | The event the period counts from or to, such as end of current term | Clause reference in the governing version | Anchor must be derived from term fields, not typed |
| term_inputs | Effective date, initial term, renewal term, renewals completed | Term clause, renewal history | Computed anchor equals effective date plus elapsed terms |
| notice_offset | Length, unit and direction, such as 90 calendar days before | Clause text in the latest amendment that changed it | Unit is calendar or business days, never blank |
| counting_convention | Exclude or include anchor day, weekend roll rule, holiday calendar ID | Contract text, or counsel decision with date | Marked contract-stated or counsel-selected |
| delivery_rule | Dispatch, delivery or receipt; permitted methods; deemed-receipt offsets | Notices clause in the governing version | Evidence type must be a permitted method |
| notice_party_and_address | Recipient role and address version in force on the send date | Notices clause and any address-change notices | Address version effective on or before dispatch |
| computed_deadline | Last local date and zone on which the rule is met | Calculation trace from the fields above | Recomputed value matches stored value |
| actual_notice_event | Dispatch, delivery and receipt timestamps with evidence objects | Courier, mail, email or acknowledgment records | Status is timely, late or unresolved, never inferred |
| review_and_exclusions | Reviewer role, review date, open questions, excluded documents | Counsel review log | Unresolved inputs block a timely or late label |
Which document, amendment or signatory controls the task?
Counsel decides precedence, and the task records that decision rather than guessing it. Typical contract families include a master agreement, order forms or statements of work, and amendments signed years apart, and each can restate the term, the notice period or the notices clause.
Two authority questions recur. The first is which document governs the input: an order-of-precedence clause may rank the master agreement above an order form, while a later amendment may expressly supersede both for one clause. The second is whether the notice itself was given by someone with authority to give it, which matters when a clause requires notice from an officer or a named role.
| Conflict found in the records | Decision counsel records | Evidence to keep | Task status until resolved |
|---|---|---|---|
| Amendment changes the notice period; master agreement clause unchanged | Whether the amendment supersedes for this term | Both clause texts with version and signature dates | Unresolved; computed deadline withheld |
| Order form states a different renewal term | Which document controls the term length | Order-of-precedence clause and the order form | Unresolved; anchor withheld |
| Address-change notice sent by email | Whether the change itself was validly given | The change notice and its delivery evidence | Both addresses carried as candidates |
| Notice signed by a non-officer | Whether the signer had authority under the clause | Signature block and any delegation record | Timeliness labeled; validity unresolved |
| Unsigned or undated amendment in the folder | Whether it was ever effective | Draft metadata and any execution evidence | Excluded from inputs and logged |
Worked example (illustrative): a 90-day non-renewal window after an amendment
The figures in this case are illustrative and do not describe a real agreement. A services agreement took effect on April 1, 2024 with a 12-month initial term and automatic 12-month renewals unless either party gives notice of non-renewal at least 60 days before the end of the current term. An amendment signed in 2025 lengthened the period to 90 days, required notice by courier, and moved the supplier's notice address.
Step one fixes the anchor. With one renewal completed, the current term ends on March 31, 2026, a Tuesday. Step two applies the offset: counting back 90 calendar days from March 31 lands on December 31, 2025, a Wednesday. Step three is where the record earns its keep. If counsel reads at least 90 days before the end of the term as excluding the last day of the term, the last timely day becomes December 30, 2025. The task stores both candidates, marks the convention as counsel-selected, and keeps the clause text that caused the ambiguity.
Step four checks delivery. In the illustrative records the customer's notice was handed to a courier on Monday, December 29, 2025 and delivered on Friday, January 2, 2026, after the New Year's Day holiday. Under a receipt rule the notice is late on either reading; under a dispatch rule it is timely on either reading. The label is therefore unresolved until counsel confirms which delivery rule the amended notices clause sets, and that unresolved label is the honest training target.
The exception worth keeping is the address. The courier delivered to the supplier's pre-amendment address. If the amendment's address change was validly given, the delivery evidence fails the address check regardless of timing. A model that sees only the dates would call the notice timely under a dispatch rule; the full task shows why a careful reviewer would not.
Clauses that do not fit a single deadline field
Several common clauses produce no single last day, and forcing them into one field corrupts the dataset. Flag them with a clause type and keep them out of the computed-deadline column.
- Termination for convenience on a stated number of days' notice at any time: there is no deadline, only an effective date that follows the notice; store the offset forward, not backward.
- Evergreen agreements with no fixed term: the anchor is undefined until a party acts, so the task becomes a calculation of the earliest effective end date.
- Cure periods: a default notice opens a period for the other side to cure, and termination rights depend on what happened during that period, which needs its own event record.
- Notice windows with a start as well as an end, such as no earlier than 120 and no later than 90 days before expiry: store both bounds, because early notice can be as ineffective as late notice.
- Statutory notice duties that apply regardless of the contract, such as consumer automatic renewal rules in some jurisdictions: counsel identifies whether one applies, and the task records the statute as a separate authority input.
- Deadlines set by a court or agency order rather than by a clause: these belong in a docket record with the order as the authority, not in the contract family.
What legal must screen out before deadline records leave the department
Only process evidence leaves: dates, clause text, delivery records and the computed result, screened by counsel. Lawyers' memos on how a clause should be read, emails seeking legal advice and deadline analyses prepared for a dispute stay out, and the exclusion record lists them by category so a reviewer can see the screen was applied.
The reason is waiver risk as much as confidentiality. Federal Rule of Evidence 502 exists because disclosure of privileged communications or work product can waive protection, and it limits when waiver extends to undisclosed material; it is not permission to share. Counsel decides whether a given record is privileged before it is copied anywhere.
Contract text carries its own restrictions. Many agreements treat their terms as confidential information of both parties, so the counterparty's identity, pricing and negotiated language may need removal or a consent decision even when the deadline facts are harmless. Access to the contract repository, privacy permission over named signatories, ownership of the documents and a contractual right to license them are four separate questions, and de-identifying counterparties does not by itself answer the last one.
Notice deadline packets as licensable contract operations records
A history of notice deadlines with full inputs, counsel decisions and outcomes is the kind of operational record legal AI teams cannot generate from public contracts, because public filings rarely include the delivery evidence or the review log. Whether a given company may license such records depends on its agreements and on counsel's privilege and confidentiality screen.
Legal operations teams can have SourceX run rights review, contracting, preparation and delivery for selected contract records once counsel's screen is done. Delivery follows the company's approval of scope and its signature, and that path opens with an assessment that takes no upload.
Frequently asked questions
What should a counsel reviewed date evidence and rule task structure include?
It should include the contract and version IDs, the anchor event and the term inputs that produce it, the notice offset with its unit, the counting convention, the delivery rule, the notice address in force, the computed deadline, the actual notice evidence and a review log. Each input cites the clause and document version it came from, and unresolved inputs block a timely or late label.
Does Federal Rule of Civil Procedure 6 decide how contract notice periods are counted?
Not by itself. Rule 6 governs computing time in federal civil litigation, and it is a useful example of an explicit convention. A private contract notice period is governed by the contract's wording and the governing law, so counsel decides the convention and the task records that decision.
Should a notice deadline dataset store the computed date or the rule?
Both, kept apart. The rule inputs let anyone recompute the deadline after an amendment, a renewal or a time zone change, and the stored computed date lets a validator confirm the recomputation matches. A dataset with only the computed date teaches a model to copy dates.
Which source controls when an amendment and the master agreement disagree?
That depends on the order-of-precedence language and on whether the amendment expressly supersedes the clause, which is a legal judgment. The task should carry both texts with their signature dates, record counsel's decision and withhold the computed deadline until it is made.
When should a legal operations team stop and send a deadline task to counsel?
Send it whenever the counting convention is not stated in the contract, documents conflict on the term or notice period, the delivery method differs from the one the clause permits, the address or signer is in doubt, or a statute may impose its own notice duty. In those cases the right label is unresolved, not a best guess.
Sources
- The Contract Understanding Atticus Dataset (CUAD) is a dataset for legal contract review curated by the Atticus Project. Source
- CUAD is an expert-annotated dataset of commercial contracts with 41 label categories that include dates and renewal terms. Source
- Federal Rule of Civil Procedure 6(a) excludes the trigger day, counts every day, includes the last day and rolls a weekend or legal-holiday deadline forward; Rule 6(d) adds 3 days for certain service methods including mail. Source
- 5 U.S.C. 6103 lists eleven legal public holidays, including Juneteenth National Independence Day and New Year's Day. Source
- The tz database predicts future timestamps, and those predictions will be incorrect after governments change the rules. Source
- UCC Article 1 (section 1-202) separates giving notice, by taking reasonable steps whether or not the other person learns of it, from receiving notice when it comes to the person's attention or is duly delivered to a place held out for such communications. Source
- Federal Rule of Evidence 502 addresses when disclosure of attorney-client privileged communications or work product waives protection and limits subject-matter waiver. Source
See if your company qualifies
A short company assessment. No data uploads are needed.