{"id":1215,"date":"2026-11-07T14:30:00","date_gmt":"2026-11-07T14:30:00","guid":{"rendered":"https:\/\/cotocus.org\/blog\/?p=1215"},"modified":"2026-11-07T14:30:00","modified_gmt":"2026-11-07T14:30:00","slug":"key-dates-faq","status":"publish","type":"post","link":"https:\/\/cotocus.org\/blog\/key-dates-faq\/","title":{"rendered":"Key-Dates Calendar FAQ: Reminders, Owners and Lead Times Answered"},"content":{"rendered":"<p>Teams that adopt a <strong>key-dates calendar<\/strong> tend to ask the same dozen questions in roughly the same order. Does it replace our ticketing tool? How far ahead should reminders go? Who is supposed to own it? This FAQ answers them directly, using what is generally observed in operations teams rather than any single vendor&#8217;s view. Each answer is short enough to quote in a planning meeting.<\/p>\n<h2>What is a key-dates calendar, exactly?<\/h2>\n<p>It is one shared calendar that contains only the dates set by parties outside your team: certificate and credential expiries, licence and contract renewals, support end-of-life dates, vendor deprecation deadlines, audit windows and business peak periods. Each entry carries an owner, a lead time and two reminders. It is intentionally narrow. Internal milestones, sprint dates and meetings belong in other tools.<\/p>\n<h2>Why not just use our ticketing system?<\/h2>\n<p>Tickets are good at tracking work that has started. They are weak at surfacing work that has not yet begun but will become urgent on a known date. A calendar fires time-based alerts without anyone creating anything. The two complement each other: the calendar reminder triggers a ticket at the right moment, and the ticket carries the actual task. If your ticketing tool supports scheduled recurring tickets, you can link the two directly.<\/p>\n<h2>How far ahead should reminders fire?<\/h2>\n<p>The honest answer is: one lead time plus a margin. Estimate how long the slowest realistic version of the task takes, including approvals and procurement, then add enough buffer for holidays and absences. A certificate that renews automatically might need a check a few weeks ahead. A licence requiring budget sign-off may need two months. A support end-of-life that implies a migration might need a year. Avoid a single default, because it will be right for some entries and badly wrong for others.<\/p>\n<h2>How many reminders per entry?<\/h2>\n<p>Two is the sweet spot. The first, early one says &#8220;begin.&#8221; The second, close to the deadline, says &#8220;this is now urgent, and if it is not done, escalate.&#8221; More than two tends to produce notification fatigue, while one leaves you with no safety net if the first is missed. If you find yourself wanting five alerts, the entry probably needs an owner conversation rather than more pings.<\/p>\n<h2>Who should own the calendar?<\/h2>\n<p>Name one steward for the calendar as a whole, typically a team lead or a platform engineer, and one owner plus a deputy for every individual entry. The steward keeps conventions consistent and runs the quarterly review. The owners act on the dates. If a person leaves, the steward reassigns every entry that person owned, which is why a regular scan of owners matters.<\/p>\n<h2>What kinds of dates belong in it?<\/h2>\n<p>A practical inventory covers six families:<\/p>\n<ul>\n<li>Certificates and credentials with a lifetime.<\/li>\n<li>Domains and DNS contracts.<\/li>\n<li>Licences, subscriptions and support agreements.<\/li>\n<li>Cloud commitments and reserved capacity terms.<\/li>\n<li>Support lifecycles of operating systems, runtimes, databases and orchestrators.<\/li>\n<li>Vendor deprecations, audit windows and business-peak change freezes.<\/li>\n<\/ul>\n<p>If you are unsure whether something qualifies, ask: &#8220;If this passed without us noticing, would someone outside the team be the cause?&#8221; If yes, it goes on the calendar.<\/p>\n<h2>Does it apply to AI and data platforms?<\/h2>\n<p>Yes, and increasingly so. Model hosting services retire model versions on published schedules, data-platform tiers change, and GPU capacity commitments end. The roadmap thinking in <a href=\"https:\/\/cotocus.org\/blog\/aiops-roadmap-a-practical-guide-for-devops-sre-and-operations-teams\/\">a practical plan for AIOps adoption<\/a> gives a sense of how many moving external parts modern operations carry, and each of those parts has dates attached.<\/p>\n<h2>How do we keep it accurate?<\/h2>\n<p>Combine three habits. First, enter a date at the moment you learn it, not later. Second, link each entry to its source, such as a vendor lifecycle page, so you can recheck it. Third, run a recurring quarterly review of the next ninety days. During review, ask whether any date has moved, any owner has changed role, and any new system has appeared without an entry.<\/p>\n<h2>What does it cost to set up?<\/h2>\n<p>For a team of ordinary size, the initial inventory takes a few hours to a day, depending on how scattered your records are. After that, upkeep is minutes per month plus the quarterly review. No special software is required; any shared calendar with email alerts is enough. Larger organisations with hundreds of items may want a dedicated register, but the practice is the same.<\/p>\n<h2>Where do training and certification dates fit?<\/h2>\n<p>Personal development dates are worth including in a team calendar, since lapsed certifications can affect both individuals and the organisation&#8217;s ability to meet contractual requirements. The structured route described in <a href=\"https:\/\/cotocus.org\/blog\/azure-devops-training-roadmap-for-engineers-and-managers\/\">a learning roadmap for Azure DevOps skills<\/a> is a good example of a path where exam windows and renewal cycles are worth noting early.<\/p>\n<h2>Is there a good example from outside tech?<\/h2>\n<p>Finance offers one. Fixed filing deadlines and results days recur on a public schedule, which is why finance-education resources often publish them. Stocks Mantra, for instance, carries an <a href=\"https:\/\/www.stocksmantra.com\/\">important-dates resource for investors<\/a> in its collection. It is informational and not a recommendation of any action, but as a pattern for publishing external dates in one place it is a handy model.<\/p>\n<h2>What goes wrong most often?<\/h2>\n<ol>\n<li><strong>Entries without lead times.<\/strong> A deadline alone does not tell you when to start.<\/li>\n<li><strong>A single recipient.<\/strong> The alert goes to the one person on holiday.<\/li>\n<li><strong>Scope creep.<\/strong> Internal goals pile in and bury external deadlines.<\/li>\n<li><strong>No review.<\/strong> Moved dates and departed owners quietly make the calendar wrong.<\/li>\n<li><strong>Untested alerts.<\/strong> A retired mailing list or changed notification setting silently eats reminders.<\/li>\n<\/ol>\n<h2>What if a date is uncertain or keeps moving?<\/h2>\n<p>Some external dates are soft: a vendor says &#8220;expected in the second quarter,&#8221; or a regulator signals a change without a final notice. Record these with the earliest plausible date and label the entry as provisional in its title. Then add a short recurring check, perhaps monthly, to see whether it has firmed up. Treating a soft date as a hard one early is cheap. Treating it as unknown until it hardens can cost you the lead time you needed.<\/p>\n<h2>How do we measure whether it works?<\/h2>\n<p>The simplest measure is the count of incidents or near-misses caused by an expired or lapsed item, which should trend to zero. A second measure is the share of calendar entries with a named owner and tested alert, which should stay near the full set. If your team already tracks incident causes, add a category for &#8220;predictable date&#8221; and watch how often it appears over a year.<\/p>\n<h2>What is the first step?<\/h2>\n<p>Search your email and billing records for the words &#8220;expires&#8221;, &#8220;renews&#8221; and &#8220;end of support,&#8221; list what you find, and place each on a shared calendar with a named owner and two reminders. Resist the urge to be exhaustive on day one. A calendar with twenty accurate entries and a quarterly review beats a perfect inventory that never gets finished.<\/p>\n<p>The questions above repeat across teams because the underlying problem is the same everywhere. Fixed dates are easy to know and easy to forget, and a small, well-kept calendar is the cheapest remedy. If a question you have is missing here, the answer is probably a variation on &#8220;write the date down, name an owner, remind early, and check regularly.&#8221;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Short answers to the questions teams ask when they start a key-dates calendar: reminder timing, ownership, scope, upkeep and how to tell it is working.<\/p>\n","protected":false},"author":4,"featured_media":1216,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[129],"tags":[],"class_list":["post-1215","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"_links":{"self":[{"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/posts\/1215","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/comments?post=1215"}],"version-history":[{"count":1,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/posts\/1215\/revisions"}],"predecessor-version":[{"id":1253,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/posts\/1215\/revisions\/1253"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/media\/1216"}],"wp:attachment":[{"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/media?parent=1215"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/categories?post=1215"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/tags?post=1215"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}