How should a GTM team audit a competitive intelligence watch list?
An audit method for testing whether a competitive watch list is relevant, sourced, and connected to real decisions.
Question and scope
This protocol asks whether a competitive intelligence watch list is doing useful work. The scope is the active list used by sales and product marketing over one quarter. The audit covers coverage, signal quality, source discipline, routing, and use in decisions. It does not attempt to measure the entire competitive landscape. The report should name the list version and the quarter it covers.
The method is designed for a team that already collects competitor updates but is unsure whether the list is too broad, too noisy, or disconnected from selling. It uses the watch entries, source links, and notes from deal reviews. The output is a short report with a keep, change, or remove recommendation for each part of the list. A list that cannot be audited cannot be improved with confidence.
What the audit covers
Audit five parts: the list of watched competitors, the signal categories, the capture routine, the routing rules, and the evidence archive. For the list, check whether each competitor appeared in an active opportunity or changed a buying question. For the signals, check whether they are specific enough to act on and consistent across weeks. Each part should have at least one check that produces a yes or no answer.
For the capture routine, check whether entries have a source, a date, and a clear observation. For routing, check whether findings reached an owner who could change a message or a deal. For the archive, check whether a reviewer can reconstruct an earlier signal after the source page changes. A gap in any part can make the whole list less useful.
Coverage and relevance measures
Measure coverage as the share of active opportunities in which a watched competitor was named. Measure relevance as the share of watch entries that were used in a deal review, a battlecard update, or a positioning decision. Report both with the number of opportunities and entries. A list can cover many competitors and still be irrelevant if nobody uses the updates.
Add a gap count for competitors that appeared in deals but were not on the list. Review the gaps with sellers before adding names, because a single mention may not justify ongoing monitoring. A useful list has a reason for each entry and a reason for each exclusion. The audit should make those reasons visible.
Evidence quality
Sample watch entries and check four things: the source URL opens, the observation matches the source, the date is recorded, and the interpretation is labeled as interpretation. Count an entry as unsupported if any of these is missing. Do not accept a summary that cannot be traced to the original material. An entry that fails two checks should be marked incomplete rather than passed.
Check whether the source is primary or secondary. A vendor page, a regulatory filing, or a public job posting is different from a trade article that summarizes it. Record the source type so the reader can judge the weight. If two entries conflict, keep both and note the conflict rather than choosing the more convenient one.
Sampling and collection
Take a consecutive sample of weekly updates over the quarter, or every other week if the volume is high. Include at least one update from each watched competitor. If a competitor has no updates, record that as a finding rather than skipping the entry. The sample should show the routine as it actually ran, not a cleaned-up version.
Use a coding sheet with fields for competitor, signal type, source, date, observation, interpretation, routing owner, and action. Test the sheet on five entries and resolve disagreements before the full review. Record the reviewer and the date. Keep the raw entries so a second reviewer can repeat the coding. Keep the coding notes beside the sample so a second reviewer can repeat the work.
Reporting
Report the coverage and relevance measures, the evidence-quality counts, and the routing results. Show the numerator and denominator for each rate. List the entries that were removed or added during the audit with a short reason. A report that only says the list is noisy does not give the team a decision. Show the list of removed entries with the reason so the decision is visible.
Separate what the audit observed from what it recommends. The observation might be that half of the entries had no source link. The recommendation might be to require a link before an entry can be marked complete. End with one owner and one date for each change, and a date to recheck the list. A recommendation without an owner and a date is only an observation.
Limits and sources of error
The audit depends on how consistently the team records watch entries. A team that logs every signal may look noisier than a team that logs only the ones it uses. A team that routes everything to a group channel may show weak attribution even when the information was useful. State the recording practice beside the result.
The sample may not represent a different quarter or a different sales segment. A competitor that is quiet in one period may become active in the next. The cited public sources describe market research and evidence practice; they do not provide a benchmark for this list. Avoid comparing the team's rate with an external number that was collected differently.
Review cadence
Run the audit quarterly while the watch list is active. If the list changes significantly, run it again after the change. Keep the coding sheet and the sample so the next audit can use the same definitions. Compare the results over time only when the method and the sample rule are the same. Record the audit date and the list version with the result.
Use the audit to prune the list, not to justify collecting more. A smaller list with strong sources and clear routing is more useful than a large list that nobody reads. Record the removed entries and the reason so the team can restore one if the market changes. A shorter list that is actually used is the better outcome.
Deal-level use test
Pick several active opportunities and ask the account owner whether the watch list changed the conversation. Record the specific decision, such as a different proof point or a new objection to address. If the list did not change anything, ask what information would have helped. This test is more useful than a count of page views.
Do not use one deal to judge the whole list. Look for a pattern across deals and segments. A competitor may be relevant to enterprise buyers and irrelevant to a small-business segment. Report the segment beside the result so the team does not overgeneralize. The segment matters because a competitor can be relevant in one buying motion and invisible in another.
Archive and source stability
Check whether the archived source still opens and still contains the claim. If a page has changed, compare the archived copy with the current page and record the difference. A source that disappears is not proof that the claim was wrong, but it is a reason to mark the entry unverified. Keep the archive date with the copy.
Test a small sample of links each quarter. Record broken links, redirects, and pages that now require a login. Assign the repair to the entry owner rather than the auditor. A stable archive makes the watch list more credible when a seller repeats a claim in a live deal. A broken source is a finding that should reach the list owner, not just the auditor.
What to do with the result
Use the audit to make one change to the list or the capture routine. If relevance is low, remove the entries that never informed a decision. If evidence quality is weak, require a source link before an entry can be marked complete. Write the change and the owner. Keep the change small enough to test in the next cycle.
Set a date to rerun the audit with the same coding sheet. Do not add new competitors during the rerun unless a seller can name the deal they affect. Compare the coverage and evidence counts, not only the overall impression. A short list that is used is the goal. Record the result beside the prior audit.