Notice period

A notice period is the minimum amount of warning you must give a vendor to cancel or change a contract before it renews. Common notice periods are 30, 60, or 90 days ahead of the renewal date.

The notice period is what turns a renewal date into a real deadline. If a contract renews on 1 March with 90 days notice, the actual last day to act is at the end of November, which StackTrackr calls the cancellation deadline.

Take one renewal date, 1 October, and vary only the notice period. At 30 days the decision belongs to 1 September. At 60 days it moves to 2 August. At 90 days it is 3 July, which is the summer before a renewal that most teams would think of as an autumn problem. Nothing about the contract changed except a number in the termination clause, and the deadline moved by a full quarter.

That number is in the termination clause, not on the vendor's pricing page, and it is worth reading the clause for two more things while you are there: the method notice has to take, and who it has to reach. A clause that requires written notice to a named address is not satisfied by telling your account manager on a call, and a support ticket is rarely notice at all.

The notice period is stored in days against each tool, next to the termination clause itself and the renewal date, so the three things that decide your exit sit on one record rather than in three systems. Change the number and the cancellation deadline, the lifecycle state and the reminder schedule all recompute immediately.

The contract that the clause came from belongs on the same record, in the document vault, so the wording is one click away at the moment somebody has to act on it rather than somewhere in a shared drive.