What evidence should a quarterly GTM operating review retain?
A retention framework for quarterly GTM reviews that keeps decisions, sources, and open conditions traceable.
Question and scope
This protocol asks what evidence a quarterly GTM operating review should keep so a later reader can reconstruct the decisions. The scope is one review cycle covering pipeline, launches, enablement, and customer-facing commitments. The record includes the inputs, the discussion materials, the decisions, and the follow-up actions. It does not include every operational report produced during the quarter.
The framework is designed for a small revenue organization that needs a defensible record without building a large archive. It focuses on evidence that explains why a decision was made and what would cause it to be revisited. The output is a review packet with a short index and a retention note. The index should fit on one page and link to the underlying evidence.
Evidence categories
Keep five categories: the questions reviewed, the source data, the decision record, the open conditions, and the follow-up evidence. The questions define the scope. The source data includes the reports and extracts used, with dates and definitions. The decision record names the owner and the choice. Open conditions state what was unresolved. Follow-up evidence shows what happened next.
Not every slide or dashboard needs to be retained. Keep the source that supports a decision and a link to the system where the full data lives. If a report changes after the review, keep the version that was used and note the change. This is enough for a later reader to understand the basis of the decision without storing every intermediate file.
Retention standard
Set a retention period with the legal and privacy owners rather than inventing one. Keep the decision record and the minimum supporting evidence for that period. Remove personal or sensitive data that is not needed for the decision, or store it in an approved restricted location. The record should be useful without becoming a copy of the CRM.
Label each item with a retention class, an owner, and a review date. A decision record may need a longer retention than a working dashboard. A customer-specific extract may need a shorter retention or stronger access control. The classification should be simple enough that the team actually applies it. A short label is easier to apply than a detailed taxonomy nobody remembers.
Sampling the record
At the end of the quarter, sample several decisions and try to reconstruct each one from the retained evidence. Check whether the question, the source, the decision owner, and the follow-up are present. A record that cannot answer who decided and why is incomplete, even if it contains many files. Give the reviewer the packet and a short set of questions, not the meeting transcript.
Include at least one decision from each major category, such as pipeline, launch, and enablement. If a category had no decision, record that fact. Use the same reconstruction test each quarter so the team can see whether the record is improving. The sample is small enough to run in a short working session. Record the category mix so a gap in one area is not hidden by the overall result.
Reporting
Report the number of decisions reviewed, the number that could be reconstructed, and the missing elements. List the specific gaps by category rather than giving a general score. A record with a missing source is different from one with a missing owner, and the fixes are different. List the missing element for each decision so the fix is specific.
Separate the completeness of the record from the quality of the decision. A well-documented decision can still be wrong, and a good decision can have a thin record. The review is about traceability, not about relitigating the choice. End with one or two changes to the template and a date to check them. The review should improve the record, not reopen the decision itself.
Access and privacy
Restrict access to the review packet based on role and need. Keep customer-specific evidence in the approved system rather than in a shared folder with broad access. Record who has access and review it when the participant list changes. A retention policy that ignores access can create a larger risk than the one it was meant to manage.
Remove or redact personal information that is not necessary for the decision. If a later review needs the underlying detail, keep a link to the restricted source instead of copying it into the packet. The cited public sources describe privacy and security practice; they do not set a retention period for this organization. The access review should happen whenever the participant list changes.
Limits and sources of error
The reconstruction test depends on the person doing the reconstruction. Someone who attended the review may fill gaps from memory and rate the record as more complete than it is. Use a reviewer who did not attend, or give them only the packet and a short set of questions. A reviewer who attended the meeting is more likely to fill gaps from memory.
The sample may miss a category with few decisions, and a quarter with unusual events may not represent the next one. The record also changes if the team adopts a new tool or template. State these limits and compare the results only when the method and the sample rule are stable. State the sample and the period so the result is not overgeneralized.
Review cadence
Run the reconstruction test after each quarterly review, while the materials are still current. Update the template with the smallest change that addresses the most common gap. Repeat the test in the next quarter and compare the result. A record that improves over two or three cycles is more useful than a one-time cleanup. Keep the prior template version so the team can see what changed.
Review the retention classes annually with the legal and privacy owners. Keep the prior versions of the template so the team can see what changed. The aim is a review record that supports decisions, satisfies the organization's retention rules, and does not become an uncontrolled copy of operational data. The record should be useful to a reader who was not in the room.
The decision index
Create a one-page index for each quarterly review. List the decision, the owner, the date, the evidence link, and the follow-up date. The index is the first thing a later reader should open. It should be short enough to scan and specific enough to find the underlying record. Keep the index format stable so a reader can compare quarters.
Do not use the index as a substitute for the evidence. It is a map, not the record itself. Check that every link works and that the owner named in the index matches the decision record. A broken index makes the archive look complete when it is not. A map without working links is not a usable record.
Follow-up evidence
For each decision, record what happened after the review. The follow-up might be a metric, a customer response, a launch result, or a note that the decision was reversed. Link the evidence and the date. This is what lets a later reader distinguish a decision that worked from one that was never implemented. A short note is enough when the outcome is still pending.
Do not require a follow-up for every small decision. Use a threshold based on consequence or cost. A rate change or a launch delay deserves a follow-up; a routine meeting change may not. State the threshold in the review template so the team applies it consistently. Record the threshold so a later reviewer can see why an item was skipped.
What to do with the result
Use the reconstruction result to improve the template, not to score the team. If the most common gap is a missing owner, add an owner field to the decision record. If the gap is a missing source, add a source link to the review agenda. Choose the smallest change that addresses the most common failure.
Repeat the test in the next quarter and compare the result. Do not add more fields than the team will actually complete. A short record that is filled in consistently is better than a comprehensive template that is abandoned after one cycle. The goal is a record a new reader can trust. Compare the number of reconstruction failures, not only the overall impression.