Three dates often get treated as one because they sit close together in the same clause. They are different. The term end is the date the current term ends or renews. The latest notice date is the last date generated by a confirmed notice rule. An internal reminder is an operational prompt to your own team before that date.
The example here is fictional. Northline Studio has SOW-S1 with Alder Works. The term ends on 30 September 2027. The original source says notice must be given at least 60 calendar days before the term ends. Amendment A1 later changes the notice period to 90 calendar days and leaves the term end unchanged.
1. Start with the term end, but do not stop there.
The term end in SOW-S1 is 30 September 2027. That date is a contract fact drawn from the term section, not a reminder date and not by itself a renewal decision. It remains the same after Amendment A1, because the amendment changes the monthly fee and notice period only.
A register can show the term end in one field and the current notice rule in another. That separation matters when an amendment changes only one of them. If the latest upload were allowed to overwrite everything, the unchanged term end and changed notice rule would be harder to audit.
| Field | Fictional sample value |
|---|---|
| Term end | 30 Sep 2027, from SOW-S1 § Term |
| Amended notice period | 90 calendar days before term end, from Amendment A1 § 3 |
2. The notice date comes from the selected rule.
Under the original R1 rule, 30 September 2027 minus 60 calendar days is 1 August 2027. That day is a Sunday. The fixture makes no weekend or holiday adjustment. A real agreement with business-day, holiday, receipt or method wording must be reviewed rather than silently shifted.
Under the amended R2 rule, 30 September 2027 minus 90 calendar days is 2 July 2027. The change is not a legal conclusion. It is calendar-day arithmetic applied to a rule that a person has reviewed and confirmed against the source.
- Sent and received are different ideas. A clause may care when notice is sent, when it arrives, or both.
- Calendar days and business days are different conventions. Agreedio must not convert one into the other without review.
- Months and days are different units. Two calendar months is not the same rule as 60 days.
3. Reminders are internal preparation dates.
Northline chooses internal reminders at 60, 30, 14, 7 and 1 days before the confirmed latest notice date. Against the amended 2 July 2027 date, that creates reminders on 3 May, 2 June, 18 June, 25 June and 1 July 2027.
These reminders help Maya Okafor review the Alder Works record before the notice window closes. They do not notify Alder Works. Marking one complete does not prove that notice was served, received or effective.
| Reminder offset | Internal reminder date |
|---|---|
| 60 days before 2 Jul 2027 | 3 May 2027 |
| 30 days before 2 Jul 2027 | 2 Jun 2027 |
| 14 days before 2 Jul 2027 | 18 Jun 2027 |
| 7 days before 2 Jul 2027 | 25 Jun 2027 |
| 1 day before 2 Jul 2027 | 1 Jul 2027 |
4. Ambiguous wording should stay unresolved.
The safe response to unclear wording is not to pick the most convenient date. If the clause could mean sent notice or received notice, or if it points to a missing schedule, the register should show that monitoring is off or needs review for that date.
This is where product discipline matters. Agreedio can show the excerpt, the selected arithmetic and the warning. It should not tell a reader that a date is legally sufficient. That is not legal advice, and readers should get qualified advice where the consequence matters.
5. Use the calculator as arithmetic, not authority.
The notice-date calculator at /tools/notice-date-calculator is useful for checking simple calendar-day subtraction. It is not a substitute for reading the source. The user supplies the date, offset and convention, and the output should be treated as a calculation with caveats.
The product record adds what a bare calculator cannot: the source excerpt, confirmation state, owner, amendment history and internal reminder schedule. That is why the date belongs in a checked register before anyone relies on it operationally.
What this guide does not cover
This guide does not explain whether a notice would be valid, how to serve it, or what a court or counterparty would accept. It does not cover business-day, holiday, time-zone, receipt or jurisdiction-specific rules. It shows the fictional fixture and the product boundary only.
Examples on this page use a fictional sample workspace. Nothing here is legal advice; obtain qualified advice for your own agreements.