What should a quarterly competitive landscape review retain for the next owner?
A retention standard for quarterly competitive reviews that preserves evidence, decisions, and open questions for a successor.

Purpose of the retention standard
A quarterly competitive review is often useful in the room and hard to use three months later. The slides summarize a discussion, but the source links, the rejected interpretations, and the reasons for a decision disappear. A retention standard fixes that gap by naming what the next owner must be able to recover. It should be small enough to maintain and specific enough to test.
The next owner may be a new analyst, a product marketer covering a leave, or a leader preparing the annual plan. They need to know what changed, what the team decided, and what remains uncertain. Retaining everything creates a storage problem, while retaining only the final slide creates a memory problem. The standard should sit between those extremes.
Define the review record
The review record should include the scope, the period covered, the competitors watched, and the sources used. It should also include the decisions the team made and the evidence behind each one. Add a short list of open questions with an owner and a next check date. This record becomes the index for everything else.
Use one location with a stable name so the next owner can find it. Link to the source files rather than copying them into the record. If a source is gated or likely to change, keep a dated capture note with the relevant excerpt. The record should be readable without the original presentation and should not depend on a private chat thread.
Keep the source evidence
For each material finding, retain the source URL, the publisher, the date, and the exact claim it supports. A link alone is not enough because pages change and disappear. Add a short excerpt or a capture date when the finding affects a decision. This evidence lets the next owner verify the claim rather than trusting a summary.
Separate primary sources from secondary commentary. A competitor's own documentation is different from an analyst's interpretation of that documentation. Keep the source type beside the evidence so the next owner can weigh it correctly. If the team relied on a seller's account, record that it is an internal observation and not a public fact. Record the date of the observation next to the source type.
Record decisions and rationale
Write down the decisions the review produced. A decision might be to update a battlecard, change a qualification question, or stop tracking a competitor. Record the owner, the date, and the evidence that supported the choice. A decision without a rationale is hard to revisit when the market changes. Add the review date so the next owner knows when the rationale was last checked.
Include the alternatives the team considered and the reason they were rejected. This is often the most valuable part of the record because it prevents the next owner from repeating a discarded idea. Keep the alternatives short and factual. If the team disagreed, record the disagreement rather than smoothing it into a false consensus. A short note on the rejected option is enough for the next review.
Preserve open questions
List the questions the team could not answer. Include the question, why it matters, the evidence needed, and the owner of the next check. An open question is not a failure of the review. It is a map of where the team's knowledge ends, and it helps the next owner decide where to spend research time.
Distinguish a question that needs more evidence from a question that needs a decision. The first belongs in the research plan, while the second belongs with the decision owner. Mixing them makes the record look unresolved when the team has simply not assigned the next step. Label each question by type and name the person who will act on it.
Assign ownership and dates
Every retained item should have an owner and a date. The source evidence needs an owner for refresh, the decisions need an owner for follow-up, and the open questions need an owner for the next check. A record with no dates becomes a static archive that no one knows how to use. The dates should be realistic and tied to the next review cycle.
Name a backup for the review record itself. The next owner may be unavailable, and the backup should be able to explain the record without the primary author. Give the backup access to the location and a short orientation to the structure. A retention standard that depends on one person is not a standard. Test that access before the review closes rather than after a handoff.
Decide what to discard
Not every artifact belongs in the record. Discard duplicate slides, unverified speculation, and personal notes that do not support a decision. Keep the source evidence and the rationale. If a document contains sensitive customer information, follow the team's retention and access rules rather than copying it into a shared review folder. When in doubt, keep the evidence and remove the duplicate copy.
Set a review date for the record itself. At the next quarterly review, check whether the decisions were followed and whether the open questions received an answer. Remove items that are no longer relevant and archive the rest. A record that is never pruned becomes harder to use and less likely to be trusted. Note the removal date so the archive does not become a second record.
Storage and access
Store the record where the next owner has permission to read it. A folder that only the current analyst can open is not a retention solution. Use the team's approved document system and a naming convention that includes the review period. Test the access with the backup before the review closes. A permission test that fails is a fix item, not a reason to delay the handoff.
Keep the record separate from the seller-facing battlecard. The review record contains evidence and reasoning that may not be appropriate for a live sales conversation. The battlecard should point to approved claims, while the review record preserves the trail. Mixing the two creates a risk that internal analysis reaches a buyer. Label the internal record clearly so a seller does not mistake it for approved material.
Test the handoff
Ask a person who did not attend the review to answer three questions using only the record. The questions should cover what changed, why a decision was made, and what remains open. If the reader cannot answer, the record is missing context. This test is more useful than a checklist that only confirms the files exist.
Record the test result and the missing pieces. Fix the record before the next review rather than waiting for a real handoff. A short test with a colleague takes less time than reconstructing a quarter of work after the owner leaves. The standard is working when a new reader can use it without a meeting.
Review and improve
At the end of each quarter, review the retention standard itself. Which parts did the next owner actually use? Which parts were never opened? Add the missing evidence and remove the sections that create work without helping a decision. Keep the standard short enough that a busy analyst will maintain it. The next owner should be able to explain the standard after reading it once.
The cited public sources describe privacy, security, and research practice. They do not prescribe a retention period for this record. Follow the team's own data rules and keep only what the next owner needs. A good review record is not the largest one; it is the one that lets a successor continue the work without asking the original author.