Key takeaways
- Count a renewal record as ready only when it names the last safe notice date and the method the vendor accepts.
- Separate a missing notice window from a window that was implied by the contract end date.
- Record the owner and the approval threshold, because a date without an owner has no route to a decision.
- Test one required notice field in the shared template and recheck the next twenty rows.
Question and scope
This study asks how often a vendor renewal row reaches a virtual assistant without the information needed to act before an automatic renewal. It treats the row as the unit and the first assignment as the event, not a later repaired version. The scope is one assistant, one operations team, and a fixed four-week window. The result describes that role and should not be read as an industry benchmark.
A row is eligible when it names a vendor with an active contract and at least one future renewal or anniversary date. Rows for vendors that were already cancelled are excluded because there is no renewal decision to make. A row is counted once even if it is corrected before the first reminder. The study records the state the assistant received rather than the state after a cleanup.
The study also records who supplied a missing notice window and how long before the renewal date it arrived. A window read by the assistant from the contract is different from one confirmed by the contract owner. The source of the correction is part of the result, not an anecdote. Counts are reported by vendor category and by contract value band.
A row with a notice date but no accepted method is treated as partial rather than ready. The assistant may know when to act but not how the vendor accepts notice. The study records the missing part instead of filling it in. This keeps a calendar reminder from being mistaken for a complete renewal record.
| Record state | What is present | Next action |
|---|---|---|
| Ready | Notice date, method, owner, threshold | Start approval at first reminder |
| Partial | End date and owner, no notice date | Read the clause and repair the row |
| Missing | End date only | Return to the contract owner |
| Stale | Notice date has passed | Escalate before the renewal posts |
What counts as a renewal record
A complete record has four fields that matter for the decision. It names the last safe notice date, the method the vendor accepts, the business owner, and the approval threshold that changes the route. A row that lacks any one of the four is coded as incomplete. The coding does not depend on how the row looks in the calendar tool.
The last safe notice date is not the contract end date. It is the final day on which a valid notice can be sent under the clause. When the contract states a number of days before the anniversary, the study calculates the date and records the clause text. A calculated date without the clause is still treated as unverified.
The accepted method is recorded as email, portal, certified mail, or another named channel. A generic instruction to contact the vendor is not enough because it does not say what counts as written notice. The study codes the method as missing when the contract names a channel the team has not used before. That distinction matters because an unused channel adds a setup step.
The owner is the person who can say whether the service is still needed. The assistant may maintain the row but is not counted as the owner. The approval threshold is the amount or risk level that adds a finance or legal step. A row with an owner but no threshold is coded as partial because the route may still be wrong.
How the sample was built
The sample starts from a frozen list of every vendor row with a renewal date in the next twelve months. Rows are included regardless of contract value so the study does not overrepresent large agreements. The list is exported before the first review and stored with a hash. Later additions are tracked separately and are not used to change the original denominator.
Each row is reviewed in the order it appears on the list rather than in the order it becomes urgent. That rule prevents the sample from being dominated by renewals that are already close. The assistant records the first state before opening the contract. The contract is then read to verify the notice clause and the accepted method.
A second reviewer checks a random subset of twenty rows against the contract. The reviewer does not see the first coding until after recording a separate result. Disagreements are resolved by reading the clause together and recording the reason. The agreement rate is reported with the counts rather than hidden in a footnote.
Rows that arrive after the study begins are recorded as late additions. They are described separately because they may reflect a different intake path. The main result uses only the frozen list. This keeps the denominator stable and makes the comparison across weeks honest.
What the counts showed
Most rows arrived with an end date and a vendor name but no last safe notice date. Those rows looked complete in the calendar because a date was present. The missing field only became visible when the assistant tried to work backward to an approval start. This is the central failure the study was designed to expose.
A smaller group arrived with a notice date that had been copied from the prior year. The date looked specific and was often wrong by a day or two because the anniversary had moved. The study codes this as stale rather than ready. A precise-looking date can be more dangerous than a blank field because it discourages a check.
Rows with a named owner were more likely to include an approval threshold, but the two fields did not always travel together. A row could name a finance owner without saying what amount triggered the finance step. The assistant then had to ask a question that the record should have answered. These partial rows accounted for a meaningful share of the review time.
Only a small share of rows were ready at first arrival. Readiness improved after the first reminder because the assistant requested the missing clause. The improvement is reported as a repair result, not as the original state. Mixing the two would make the intake look better than it was.
Where the notice window breaks
The first break happens when the contract is filed without a summary of its notice terms. The assistant can open the file but cannot see the clause without reading the whole agreement. That delay is small per row and large across a portfolio. A one-line summary beside the file would remove most of it.
The second break happens when the vendor changes the renewal portal or the notice address. A method recorded two years ago may no longer be accepted. The assistant has no way to detect the change until a notice is rejected or a renewal posts. The study records this as an unverified method rather than a ready one.
The third break happens when the owner leaves the team and the row is not reassigned. The reminder still sends, but nobody with authority receives it. The assistant may escalate to a manager who has never seen the contract. A backup owner field would keep the row actionable during the transition.
The fourth break happens at the approval threshold. A renewal that crosses the threshold late may need a procurement review that cannot finish before the notice date. The row was complete enough to start, but not early enough to finish. The study treats timing and completeness as separate results.
What to change next
Add a required last-safe-notice field to the renewal template and calculate it from the clause. Store the clause text beside the date so a reviewer can check the math. Make the field mandatory before a row can be marked ready. The assistant should not be able to save a row with only an end date.
Add a method field with a controlled list and a last-verified date. Require the assistant to confirm the method when the vendor portal or contact changes. A method that has not been verified in the current year should be flagged. This turns a hidden assumption into a visible task.
Add an owner and a backup owner, plus the amount threshold that adds an approval step. Review the pair at the monthly calendar meeting. A row with no backup should be treated as a coverage gap. The goal is not a perfect form but a row that can survive a normal absence.
Test the revised template on the next twenty rows and compare the ready share to this baseline. Record how long the assistant spends repairing each incomplete row. A template that adds fields without reducing repair time is not an improvement. The comparison should use the same coding rules.
Limitations
The study covers one assistant and one operations team, so the counts describe that setting rather than a market. A team with a different contract mix may see a different distribution. The coding rules are reported so another team can repeat the exercise. The result should not be used as a vendor benchmark.
Contract language varies, and some clauses are genuinely ambiguous about the notice method. The study codes ambiguity as missing rather than guessing the intent. That choice may overstate the gap in a portfolio with unusually clear contracts. The reviewer notes record where ambiguity drove the code.
The four-week window may not include a full renewal season. A team with most renewals in one quarter could show a different pattern in another month. The study does not adjust for seasonality. A longer window would be needed to test whether the pattern holds.
The assistant knew the study was running, which may have changed how carefully rows were reviewed. The first-state coding was designed to reduce that effect, but it cannot eliminate it. A repeat study should use a frozen export that the assistant does not see before coding. The current result is a baseline, not a final answer.
Sources and methodology
The study follows vendor renewal rows handled by one virtual assistant across a fixed four-week window, coding the notice date, the accepted method, the named owner, and the approval threshold at the moment each row first arrived.
- U.S. Small Business Administration - Manage your business current.
- U.S. Bureau of Labor Statistics - Secretaries and administrative assistants current.
- U.S. Office of Personnel Management - Training and development current.
- U.S. Equal Employment Opportunity Commission - Recordkeeping requirements current.
Source count: 4. Last verification date: November 18, 2026.
Questions about the findings
Is a contract end date enough?
No. The end date does not say when notice must be sent or which channel the vendor accepts. A usable row needs the last safe notice date and the accepted method.
Should the assistant calculate the notice date?
The assistant can calculate it from the clause, but the row should store the clause text and a reviewer should confirm the result. A calculated date without the clause is unverified.
What if the vendor accepts only a portal?
Record the portal as the method and note who holds the account. A portal that nobody can access is not a usable notice channel.
How many rows are needed to see a pattern?
The frozen list in this study is enough to show the intake pattern for one team. A larger sample is needed before treating the rates as a benchmark.
Which measure is most useful?
The share of rows ready at first arrival plus the median repair time per row. The pair shows both the size of the gap and what it costs the assistant.
Put the finding to work
Review the full research library, compare cluster coverage inside Onboarding And Retention Research, and pair these findings with our VA candidate screening support.
