A renewal packet can look complete and still carry the wrong contract or a deadline that has already passed. Sales support teams assemble these packets from folders, CRM attachments, and the memory of the last renewal cycle. When the customer asks a simple question about termination notice, the answer depends on which version of the agreement the packet actually contains. This protocol describes a bounded test of whether renewal packets include the current contract and a traceable notice deadline. It measures what the packet contains and whether the reader can verify it, not whether the customer renews.
Research question and scope
The research question is whether a sales support renewal packet contains the current contract and a notice deadline the customer can trace to a clause. The scope is one team and one renewal cycle during a fixed review window, not a comparison across industries or contract types. The test asks whether the packet gives the account owner a defensible statement about the agreement, not whether the packet is attractive. It does not measure customer satisfaction, win rate, or the quality of the renewal conversation. Those outcomes require a separate review after the renewal period closes.
Population and unit of analysis
Begin with the list of renewals that entered preparation during the review window. Record the renewal identifier, the account, the account owner, the packet preparer, the renewal date, and the packet contents. The unit is one renewal packet, so an account with several agreements can contribute several rows. Include packets prepared for standard renewals, early renewals, and multi-year renewals if they use the same template. Exclude renewals that were cancelled before a packet was prepared, and note each exclusion with a reason.
Set the review window
Choose a window that covers a normal renewal cycle for the team. Four to six weeks often captures the preparation period, the customer review, and the first follow-up, while a longer window helps when renewals cluster at quarter end. Freeze the start and end dates before coding and keep them fixed after the first result appears. If the packet template changes during the window, split the result at that date or note the change beside the finding. A stable window keeps the denominator honest and makes a later repeat measurement comparable.
Define the current contract
The current contract is the fully executed version that governs the term being renewed, including any signed amendments. Define it before coding and state whether unsigned drafts, order forms, or email confirmations count as part of the agreement. A folder named current does not prove that the file inside is the executed version, so the test should check the signature block and the effective date. Where an amendment exists, the packet must include it or cite it explicitly. Write the rule down so two reviewers classify the same packet the same way.
Define the notice deadline
The notice deadline is the last date on which either party may give notice under the agreement. It is not the renewal date, and it is not the date the customer usually decides. Record the clause that establishes the deadline, the number of days required, and the date the deadline falls. If the contract sets the deadline by reference to the term end, calculate the date and show the arithmetic. A packet that names a deadline without the clause leaves the customer unable to check it. A packet that omits the deadline entirely fails the test even if the renewal date is correct.
Build the evidence dictionary
Each row needs the renewal identifier, the account, the renewal date, the contract file name, the contract effective date, the amendment status, and the notice deadline. Add the packet preparer, the review date, and the reviewer initials. Record where the contract file came from, such as the document system, the CRM attachment, or the customer portal. If the deadline was calculated, record the clause and the calculation. The dictionary should let a later reviewer reproduce the coding without asking the original analyst what a category meant.
Test design
Use a census when the renewal volume is small and a documented sample when it is large. Freeze the packet and the source documents before coding so edits made during the test do not move the target. Have one reviewer code every packet and a second reviewer check a subsample without seeing the first result. Record every disagreement and resolve it against the written definition rather than personal preference. If a packet includes a contract but the reviewer cannot confirm it is executed, mark it unverified rather than complete.
Separate presence from accuracy
A packet can include a contract and still include the wrong one. Code presence and accuracy as separate fields so the result shows both problems. Presence asks whether a contract file is attached, while accuracy asks whether it matches the executed version and covers the term being renewed. The same separation applies to the notice deadline, which can be present, absent, or present but wrong. Reporting a single pass rate hides the difference between a missing document and a plausible but outdated one. The repair for each problem is different.
Check the packet against the renewal date
The age of the packet matters because a deadline that was future when the packet was built may have passed by the time the customer reads it. Calculate the number of days between the packet preparation date and the notice deadline, then compare it with the renewal date. A packet prepared two weeks before the deadline leaves little room for review, while one prepared after the deadline is already late. Report the median and the range rather than only an average, since one very old packet can distort the picture. This comparison shows whether the gap sits in preparation, review, or sending.
Code by renewal type
Different renewals carry different risks. A standard renewal may depend on a clean contract copy, while an early renewal may depend on an amendment that changes the term. Assign a simple renewal type before coding and compare completeness by type. A team with strong standard packets and weak amendment packets may still be exposed where the risk is highest. Report the types beside the result so the reader can judge whether the gap matters for the coming quarter.
Resolve disagreements before counting
Reviewers often disagree about whether an unsigned order form counts as part of the contract or whether a deadline stated in an email is traceable. The answer depends on the team's definition, not on the reviewer's preference. Write the rule before coding, apply it consistently, and recode rows classified under an older rule. Record the rule change and its effective date so the next test remains comparable. A short calibration on ten packets before the full review prevents most disputes and saves a second pass.
Fix the packet template
Most missing items come from a template that does not ask for them. Add a field for the contract version, the effective date, the amendment status, and the notice deadline with its clause. Put the fields near the top of the packet so the preparer sees them before writing the cover note. Add a short prompt that asks the preparer to confirm the signature block rather than the folder name. The template change is small, but it makes the expected evidence obvious to someone preparing a packet under time pressure.
Limitations and next action
The result can support a change to the packet template, the preparation checklist, or the handoff to the account owner. It cannot prove that the customer read the packet or that the renewal terms were understood. A high completeness share can hide packets that include an old amendment without checking whether it still applies. Pair the test with a short review of customer questions and a check that the owner answered them from the same documents. Where the packet includes a verbal term, compare it with the promise register before the customer sees it. Report presence, accuracy, and deadline status separately so the repair matches the gap.
Report the result
Report the number of packets, the share with a contract attached, the share with an executed contract, and the share with a traceable deadline. Add one short example of a strong packet and one weak packet with identifying details removed. Show the gap by renewal type so the reader can see where the repair belongs, then compare it with the quote follow-up checklist to confirm that revised terms reach the customer with the same evidence. State the limitation beside the numbers rather than in a separate appendix. The output should end with one template change, one owner, and one recheck date.
Review cadence
Run the test before a renewal season, after a contract template change, and at least once a quarter. A monthly check helps during a busy period when packets are assembled quickly and deadlines approach. Keep the same definitions so the results remain comparable across cycles. End each review with one change, one owner, and one recheck date. Archive the packet list, the source documents, and the coding sheet beside the finding.
Sources
The sources below offer general context on recordkeeping and small-business operations. They do not describe a local renewal packet result or a benchmark for this team, and they were checked on November 10, 2026. Use them as background only and keep the local observation separate from any external claim. The list is not a substitute for the contract record or the manager review.
- IRS: Recordkeeping: https://www.irs.gov/businesses/small-businesses-self-employed/recordkeeping
- U.S. Small Business Administration: Manage your business: https://www.sba.gov/business-guide/manage-your-business
- NIST Cybersecurity Framework: https://www.nist.gov/cyberframework
- U.S. Department of Labor: Recordkeeping: https://www.dol.gov/agencies/whd/recordkeeping
- U.S. Census Bureau: Small Business data: https://www.census.gov/programs-surveys/susb.html