A competitive intelligence checklist works best as a set of standing best practices you revisit before every research cycle, not a box-ticking exercise you complete once. The checklist below is organized into the phases that actually matter — scope, sourcing, analysis, and distribution — and it reflects the specific gaps we see most often when we audit a client’s existing CI process at Salterra.
If you only take one thing from this checklist, take this: every item on it exists because we’ve watched a team skip it and pay for the omission later, usually in the form of intelligence that was collected but never used.
Before any research happens, get the foundation right. A CI program built on a shaky foundation produces plenty of activity and very little useful output.
A common failure mode is over-indexing on one source — usually search rankings — and missing signals that live elsewhere. Before calling your source coverage complete, confirm you’re checking:
Missing even one of these consistently creates blind spots. Teams that only watch pricing pages get blindsided by a positioning shift; teams that only watch content get blindsided by a pricing move. Coverage breadth is what prevents a CI program from being surprised by moves that were visible the whole time in a source nobody was checking.
Bad intelligence is worse than no intelligence because it gets acted on with false confidence. Before treating any finding as reliable, check it against these standards:
That last point deserves emphasis. It’s tempting to fill gaps with plausible-sounding guesses — “they probably raised prices because of rising costs” — but presenting a guess with the same confidence as an observed fact is how CI programs lose credibility. Label inferences as inferences.
Collecting information is the easy part; turning it into useful analysis is where most of the real value gets created or lost. Before finalizing analysis, confirm:
Intelligence that never reaches a decision-maker has zero value, regardless of how rigorous the research behind it was. Before considering a research cycle complete, verify:
A CI program degrades quietly if nobody maintains it, and by the time the degradation is obvious, months of blind spots have usually accumulated. Build these maintenance habits into the recurring calendar:
This is the step that proves the whole program is worth running, and it’s the one we most often find missing during a CI audit. For every significant finding, the log should capture what was found, what decision it informed (or why no action was taken), who made the call, and when. Without this record, a CI program is nearly impossible to defend when budget or time gets questioned, because there’s no evidence connecting the research to real business outcomes.
We recommend reviewing this log quarterly alongside the broader program review. If a quarter passes with no entries, that’s a clear signal the intelligence being produced isn’t reaching decision-makers in a usable form — and it’s worth diagnosing why before investing more time in collection.
When we walk into an existing CI process at a client’s business, the checklist items that are missing tend to follow a pattern. Source coverage is usually fine — teams are good at gathering. Data quality is often shaky, with speculation quietly presented as fact. Reporting and distribution is where things most often break down completely, with findings sitting in a shared folder that nobody outside the research team ever opens.
If you’re auditing your own process for the first time, start with reporting and distribution rather than source coverage. It’s tempting to assume the fix is “collect more,” but in our experience the fix is almost always “route what you already have to the right person, on a schedule tight enough to matter.”
Use the scope and source sections at the start of every research cycle, and revisit the maintenance section on a quarterly basis. Treating it as a living reference rather than a one-time setup task is what keeps a CI program from drifting off track.
The decision log. Teams are usually diligent about collecting and organizing information but stop short of recording what actions the intelligence actually drove, which makes the program's value nearly impossible to demonstrate later.
No. Every item here can be done with a shared document, a search engine, and a calendar reminder. Tools can add efficiency at scale, but they aren't a prerequisite for running a disciplined process.
A reasonable rule of thumb is anything that would change a decision currently in progress — an active deal, a pricing review, or a content plan already underway. Everything else can typically wait for the standard cadence.
The core phases stay the same, but smaller businesses can usually run a lighter version — fewer competitors tracked, a simpler digest format, and less formal routing since fewer people are involved in decisions. The discipline matters more than the scale.
Terry has 30+ years in software and SEO. He’s the founder of Salterra Digital Services and SEO Spring Training, host of the Roundtable SEO Mastermind, and lead instructor at SEO University — teaching the exact tactics his team uses on client work.
This guide is one lesson from the Competitive Intelligence System course. Get every lesson, framework and checklist — plus the full 38-course catalog — inside SEO University.
Practitioner-focused training across the full digital marketing stack — from technical SEO to conversion optimization and the AI search era. By Salterra Digital Services, since 2011.