Capture the obligation
A renewal calendar starts with one row for every contract that renews automatically. Record the vendor, the service, the contract owner, the start date, the end date, and the amount. Add the system where the signed contract lives so the row points to the evidence. A calendar without the contract link becomes a list of reminders that no one can check.
Include the small subscriptions as well as the large contracts. A design tool, a data feed, and a background-check service can each renew on a different cycle. Group them by owner so one person is not chasing every vendor alone. The full list is the only way to see the real recurring spend.
Record the notice window
The notice window is the most important field in the calendar. Write the number of days before the end date that notice must be given, and the channel the contract requires. Some vendors accept email, while others require a portal or a signed letter. Record the exact method rather than assuming an email is enough.
Calculate the notice deadline and put it in the calendar as its own date. Add a second reminder a week before the deadline for the owner to decide. A reminder on the end date is too late to stop the renewal. The assistant should see the decision date, not only the contract date.
Assign the owner and the decision
Every row needs one accountable owner who can recommend renewal, renegotiation, or cancellation. The assistant can maintain the calendar but should not own a spending decision. Name the backup who covers the owner during leave. A renewal that waits for one unavailable person can roll over by default.
Write the decision rule for each vendor in advance. A low-cost tool may renew if the owner confirms use, while a large contract may need a comparison and a finance review. Record the threshold and the approver. The assistant can then start the right process at the right time.
Set the reminder cadence
Use at least three reminders for each renewal: a planning note, a decision date, and a final notice deadline. Send the planning note early enough to compare alternatives and gather usage data. The decision date should leave time for a signature. The final reminder is a backstop rather than the main event.
Send reminders to the owner and to the assistant who maintains the calendar. Put the vendor and the amount in the subject line so the message is easy to find. Include the contract link and the notice method. A reminder without those details creates another round of searching.
Handle renegotiation and cancellation
When the owner wants to renegotiate, give the assistant a short brief with the current price, the usage, the alternatives, and the walk-away point. The vendor conversation should start from evidence rather than a vague request for a discount. Record the outcome and the new dates in the calendar. A verbal promise is not a renewal term.
For a cancellation, confirm the notice method and ask for written acknowledgment. Record the confirmation and the final service date. Tell the team who uses the tool so they can move their work before access ends. A cancellation that is not confirmed can produce another invoice.
Audit the calendar each quarter
Compare the calendar with the bank and card statements once a quarter. A recurring charge with no calendar row is an unmanaged renewal. A calendar row with no current charge may be a cancelled service that was never removed. Reconcile both directions before the next budget review.
Ask each owner to confirm the vendor is still used and the owner is still correct. Teams change, and a calendar that keeps a former employee as the owner will fail at the first decision. Update the row and the backup in the same review. The calendar is a living record, not a one-time import.
Sources
Open the original publisher and confirm the current version, definition, and scope before using a source for a business decision.
Turn the reading into a role brief
Bring the recurring tasks, tools, schedule, access limits, and owner-only decisions. Start with one work sample and one clear review path.
Plan a Philippines-based role