A vendor renewal calendar is not a list of contract end dates copied into a spreadsheet. For a virtual assistant, it is the working record that says when a decision must start, who approves it, and what happens if nobody responds. A renewal that is noticed two weeks before the end date is already late for most approval paths. The calendar should make the notice window visible before the date becomes urgent.
Start with the notice date and the notice window
Begin with the date the vendor requires for notice, not the date the contract expires. Many agreements renew automatically unless the buyer gives written notice inside a stated window. The assistant should record both dates and label which one triggers action. A calendar that shows only the end date invites an accidental renewal.
Read the notice clause and write the window in plain language beside the date. If the clause says thirty days before the anniversary, record the last safe day to send notice as a separate field. Add the method the vendor accepts, because email, portal, and certified mail are not interchangeable. The assistant should not guess which method counts as valid notice.
Set the first reminder earlier than the contractual minimum to leave room for an approval. A renewal that needs a budget owner and a legal review may take longer than the notice window allows. The reminder should name the first action rather than simply announce the date. That action might be requesting a current quote or confirming the account owner.
Record the owner and the approval path
Every row needs a business owner who can say whether the service is still needed. The assistant may maintain the calendar, but the assistant does not own the decision. Record the owner's name, department, and a backup contact. A renewal with no named owner should be flagged rather than silently tracked.
Write the approval path in the order it actually runs. A software renewal may need the team lead, then finance, then a procurement review above a set amount. The calendar should show the threshold that changes the path. The assistant can then route the request without asking the same question each year.
Record the evidence each approver expects to see. Finance may want the prior year's spend and the new quote, while legal may want the liability and termination terms. Store links to those documents beside the approval step. A request that arrives without the expected evidence restarts the clock.
Capture the contract terms that decide the renewal
Summarise the amount, term, seat count, and any automatic increase in the row. A renewal decision is difficult when the only available figure is last year's invoice. Record the notice method, the cancellation charge, and the minimum term as well. These terms often decide whether renewing is cheaper than switching.
Note the services that sit outside the main agreement, such as support hours or extra storage. A vendor may renew the base contract while quietly ending a bundled service. The assistant should list every component that has its own end date. A partial renewal can leave a gap that nobody notices until the service stops.
Keep the current contract file separate from the renewal quote. Label each file with the version and the date received. The assistant should never overwrite the signed agreement with a draft. A clear file history makes a disputed charge easier to resolve.
Set reminders at fixed intervals
Use a standard reminder pattern so every vendor gets the same attention. A workable pattern is ninety, sixty, thirty, and seven days before the notice deadline. Adjust the pattern only when the approval path or the contract value justifies it. The assistant should record why an exception was made.
Send each reminder to the owner and the assistant together. A reminder that reaches only the assistant creates a silent queue. The message should state the days remaining and the next action. It should also link to the row rather than repeat every term in the email.
Escalate when a reminder passes without a response. The escalation should go to the owner's manager and name the date the notice window closes. Keep the tone factual and include the cost of an automatic renewal. An escalation that arrives after the deadline is only a complaint.
Define what the assistant does when nobody answers
Write a default instruction before the first renewal reaches its window. The default might be to request a written quote, to pause the renewal, or to escalate to finance. The assistant should not choose among those options alone. The instruction should name who can change the default.
Record the vendor's cancellation method and the confirmation the team should expect. If the default is not to renew, the assistant needs the exact steps and the deadline. A cancellation that is sent to the wrong address may not stop the charge. The calendar should store the confirmation reference once it arrives.
Tell the owner what happens if the deadline passes without a decision. Some contracts convert to a month-to-month term, while others renew for a full year. The calendar should state the consequence in the row. A visible consequence makes a late decision easier to escalate.
Review the calendar every month
Set a monthly review that looks forward across the next two quarters. The review should confirm owners, dates, and approval paths rather than only scanning for red flags. It should also catch vendors that were added without a calendar row. A short review is more reliable than a yearly cleanup.
Check that every closed renewal has a filed confirmation. Mark the row as complete only when the signed document or cancellation notice is stored. Record the final amount and term so the next cycle starts from accurate figures. A row marked complete without evidence will be rebuilt next year.
Remove vendors that are no longer used, but keep the historical row in an archive. The archive helps explain prior spend and notice obligations. The assistant should record the reason for removal and the date. A deleted row can hide a contract that still has a termination obligation.
Key takeaways
Track the last safe notice date rather than the contract end date, and store the accepted notice method beside it. Start reminders before the contractual minimum so the approval path has room to run. A calendar without a notice window cannot prevent an automatic renewal. A row that shows only the contract end date should be treated as incomplete until the notice clause is read.
Name a business owner and a backup for every row. Write the approval path with the amount threshold that changes it, and list the evidence each approver expects. The assistant maintains the record but does not own the renewal decision. A backup matters most during the month when the owner is on leave and the window is already open.
Summarise amount, term, seat count, cancellation charge, and every component with its own end date. Keep the signed agreement separate from the renewal quote. These details decide whether renewing is cheaper than switching. Record the vendor's accepted notice method in the same row so the final action cannot be sent the wrong way.
Set a default action for an unanswered reminder and name who can change it. Review the calendar monthly and archive closed rows with their confirmation. A visible consequence for a missed deadline turns a late notice into an escalation rather than a surprise. The monthly review should also catch vendors that were added without a row at all.
Continue building the workflow
Related support: onboarding operations support, contact us. The U.S. Small Business Administration - Manage your business publishes guidance on managing business records and day-to-day operations.
Related reading
Set a document signature routing sheet for a virtual assistant
A routing sheet that fixes the signer order, the version each signer sees, the reminder cadence, and the filed copy so a virtual assistant can manage signatures without chasing the wrong person.
Build a recurring invoice checklist for a virtual assistant
A cycle checklist that starts from the billing date, verifies source records, matches the contract, routes approval before the cut-off, and records what changed since the last invoice.
Write a client reassignment note for a virtual assistant
A reassignment note that lists the open commitments, the client's preferences, the access that must move, and the date the old owner's access ends.
