A competitive intelligence report should tell a defined audience what materially changed during a defined period, how strong the evidence is, what the change may mean, and which decision now requires attention.
Many competitor reports become storage containers. They repeat company profiles, paste dashboard exports, and list every detected event. Readers finish with more information but no clearer choice. A useful report applies a materiality threshold, preserves the evidence trail, and gives each recommended action an owner and due date.
The report begins after the source collection and standing records exist. If those foundations are weak, start with the guides to choosing competitive intelligence sources and building a living competitor profile. The report should not recreate either one.
What a competitive intelligence report is
A competitive intelligence report is a recurring decision briefing built from reviewed evidence. It covers a stated period and audience. It selects changes that cross a defined materiality threshold, separates observation from interpretation, and records the actions or open questions that follow.
| Artifact | Primary job | Time orientation |
|---|---|---|
| Competitor profile | Maintain the current standing record for one competitor | Current state with dated history |
| Alert or change feed | Show detected events that may require review | Event by event |
| Dashboard | Make current monitoring data and workflow state inspectable | Continuously updated view |
| Competitive intelligence report | Explain material changes during a period and the decisions they affect | Weekly, monthly, quarterly, or triggered period |
| Competitive battlecard | Support a seller in one competitive buying situation | Current approved sales guidance |
A report may lead to an update in another artifact. A packaging change might update the standing profile and reopen a claim in the competitive battlecard. The report records why that change deserves attention and who will act.
Define the reader and decision before the reporting period
The same evidence requires different treatment for an executive, product manager, SEO lead, or sales leader. The audience determines the decisions covered, the required context, and the level of supporting detail. It should be possible to name the reader without writing “the company.”
- Audience — Name the role or decision group that will use the report.
- Decision scope — List the decisions the report may inform and the ones it will not address.
- Reporting period — State the exact start and end dates or the event that triggered the briefing.
- Competitor scope — Identify the companies, products, regions, and segments included.
- Evidence scope — List the public, internal, third-party, and unavailable sources relevant to the brief.
- Owner — Name the person accountable for editorial judgment and final distribution.
Put the scope on the first page Readers should see the audience, period, competitor set, evidence boundary, author, publication date, and next scheduled review before they interpret the findings.
Set a materiality threshold
A change belongs in the main report when it could alter a decision, change confidence in an existing view, or trigger a bounded investigation. Frequency alone does not make a signal material. Ten routine blog posts may matter less than one verified packaging change that affects an active evaluation.
| Materiality test | Question | Possible result |
|---|---|---|
| Customer relevance | Does the change affect a priority buyer, use case, region, or requirement? | Include, monitor, or exclude |
| Decision impact | Could it alter an available product, pricing, positioning, sales, or content decision? | Escalate to the relevant owner |
| Evidence strength | Is the observation verified, scoped, and current enough to support attention? | Report, qualify, or investigate |
| Persistence | Is this a durable change, a repeated pattern, or a temporary event? | Act now or wait for confirmation |
| Novelty | Does it change the standing profile or repeat information readers already know? | Summarize only the delta |
Document exclusions briefly. A reader may otherwise assume silence means complete coverage or no activity. “Thirty-seven routine posts reviewed; none crossed the stated materiality threshold” is more honest than omitting the coverage note.
Build the report from a review ledger
Before drafting, create one row for each candidate finding. The ledger keeps source review separate from narrative writing. It also exposes missing evidence before an interpretation reaches an executive summary. The competitor analysis framework provides the deeper method for testing a decision-led interpretation.
| Field | What to record |
|---|---|
| Observation | The smallest factual statement the evidence supports |
| Source | URL, document, interview note, system, or dataset |
| Observed date | When the reviewer inspected the source |
| Period and scope | The market, plan, product, channel, or sample represented |
| Source health | Successful, partial, failed, blocked, or unknown where monitoring is involved |
| Confidence | Low, medium, or high with a short reason |
| Materiality | Why this finding can affect a stated decision |
| Alternative explanation | Another plausible reading of the same evidence |
| Report status | Include, appendix, monitor, investigate, or exclude |
Use a report structure that supports decisions
The template below works for a monthly competitive report or a trigger-based briefing. Scale the number of findings to the decisions in scope. Do not lengthen every section simply because the report runs quarterly.
| Section | What it must answer | Editing rule |
|---|---|---|
| Report header | Who is this for, what period and scope does it cover, and who owns it? | Keep the boundaries visible |
| Executive summary | Which three to five changes matter most, and which decisions need attention? | Write it after the evidence review |
| Previous actions | What was assigned last time, and what happened? | Carry unresolved work forward explicitly |
| Material changes | What changed in product, pricing, packaging, positioning, messaging, market, or field evidence? | Organize by decision or theme, not by data source |
| Interpretation | What may the evidence mean, and what other explanation remains plausible? | State uncertainty in the sentence |
| Implications | Which customer, product, commercial, sales, or content decision could be affected? | Name the owner of that decision |
| Recommendations | What action, investigation, or deliberate wait follows? | Give each item an owner, due date, and reopening trigger |
| Coverage and method | Which sources, competitors, periods, and failures shaped the report? | Do not hide gaps in an appendix |
| Appendix | Where can a reviewer inspect the evidence? | Link to the ledger and supporting records instead of pasting exports |
Write the executive summary as a decision queue
Each summary item should carry enough information for a reader to route it. A compact pattern is: verified change, affected decision, confidence, recommended next step, and owner. If the recommendation depends on unavailable evidence, say which owner must supply it.
| Weak summary | Decision-ready summary |
|---|---|
| Competitor A changed pricing. | Competitor A moved audit history from its public Team comparison to Advanced on September 8. Medium confidence because negotiated terms are unknown. Revenue operations will compare the current quoted packages by September 15 before sales guidance changes. |
| Competitor B is targeting agencies. | Competitor B published an agency landing page and three agency workflow guides during August. This may indicate a coordinated acquisition test, but publishing does not prove traction. Growth will monitor the cluster and review first-party agency demand before proposing a campaign. |
Separate fact, interpretation, implication, and recommendation
The report becomes easier to challenge constructively when each layer is visible. A reader can accept the observation, question the explanation, and propose a different action without turning the discussion into a dispute about the entire report.
| Layer | Fictional example |
|---|---|
| Fact | Northstar published a new annual plan comparison on September 4 with onboarding listed as an add-on. |
| Interpretation | Northstar may be making service costs more explicit before a packaging change or sales push. |
| Alternative explanation | The page may clarify an existing policy without changing the offer. |
| Implication | Current total-cost comparisons may use an outdated assumption about included onboarding. |
| Recommendation | Revenue operations will compare a current Northstar quote with the public page before September 12. Sales guidance remains unchanged until then. |
Report confidence and coverage separately
Confidence describes the support for a finding. Coverage describes how much of the relevant evidence set was available and healthy. A clearly worded source can justify high confidence about one page while overall market coverage remains low.
| Notation | Use it when | Example wording |
|---|---|---|
| High confidence | Direct evidence is current, specific, and corroborated where the claim requires it | The public US pricing and documentation pages show the same plan assignment |
| Medium confidence | The observation is credible but its meaning, scope, or persistence remains uncertain | Three coordinated pages suggest an audience test; campaign investment is unknown |
| Low confidence | The evidence is indirect, incomplete, old, or dependent on an unverified report | Treat as an investigation lead, not a finding |
| Complete coverage | Every source defined for the period was checked successfully within its stated bounds | Complete does not mean every possible public or private source |
| Partial coverage | One or more expected sources failed, changed format, or were unavailable | Name the missing source and the decisions it could affect |
A quiet source is not proof of no change Distinguish no relevant activity from a failed check, blocked source, unsupported format, or incomplete period. Otherwise an operational gap becomes a market conclusion.
Cover material changes without building a data dump
The report may draw from several evidence families. Include a family only when it can affect the decisions named in the scope. Public monitoring, internal systems, interviews, third-party research, and financial evidence have different access rules and limitations.
| Change family | Useful evidence | Important limit |
|---|---|---|
| Product | Release notes, documentation, legitimate product access, and approved field evidence | A public claim does not prove capability quality or adoption |
| Pricing and packaging | Current public pages, quotes, terms, and comparable plan records | Displayed price may exclude discounts, services, taxes, or negotiated terms |
| Positioning and messaging | Homepages, landing pages, campaigns, interviews, and repeated narrative patterns | Copy changes do not prove a durable strategy or buyer perception |
| Market | Regulatory records, company announcements, reputable research, and customer evidence | Market estimates vary by method and may age quickly |
| Field | CRM records, buyer interviews, win/loss research, and sales notes where authorized | Anecdotes and coded loss reasons need validation |
| Publishing and SEO | New pages, meaningful revisions, search data, backlinks, analytics, and content inventory | Publishing does not prove rankings, traffic, or business results |
If private field evidence, buyer interviews, financial data, or reliable market research is unavailable, record the gap. Do not replace it with public publishing activity because that source is easier to collect.
Competitive intelligence report template
Copy the outline below into the document system your team already maintains. Keep links to evidence access-controlled where necessary.
- Header: audience, owner, period, competitor scope, evidence scope, published date, next review.
- Executive summary: three to five material changes, affected decisions, confidence, and immediate owners.
- Previous-action follow-up: prior recommendation, owner, due date, current status, result, and carry-forward decision.
- Material changes: fact, source, observed date, scope, confidence, interpretation, alternative explanation, and affected decision.
- Recommendations: action or investigation, owner, due date, expected evidence, success condition, and reopening trigger.
- Coverage: sources checked, failures, blind spots, excluded competitors, and materiality threshold.
- Appendix: evidence ledger, standing profiles, approved analysis, and supporting data.
Competitive intelligence report sample
This shortened sample uses fictional companies. The audience is a product and growth leadership group. The report covers September 1 through September 30 and includes three direct competitors in the US mid-market segment.
- Material change — Northstar moved onboarding from an included annual-plan item to a separately listed service on its public comparison page. Observed September 4. Medium confidence because current quotes have not been reviewed.
- Interpretation — The page may clarify an existing commercial policy or introduce a packaging change. The public page alone cannot distinguish those explanations.
- Implication — Current total-cost comparisons and related sales guidance may rely on an outdated assumption.
- Recommendation — Revenue operations will obtain and compare current quote evidence by October 5. The battlecard owner will review the affected claim after that comparison. No pricing response is authorized.
- Coverage note — All defined public pricing and documentation sources were checked. Private quote evidence and buyer feedback were unavailable when the report closed.
The sample does not pretend to resolve the competitor's intent. It records an inspectable change, limits the interpretation, names the decision at risk, and assigns the next evidence-gathering step.
Give every recommendation an owner and due date
A recommendation without ownership is commentary. An owner should control the action or know how to obtain the required evidence. The due date should match the decision window, not the next reporting cycle by default.
| Action field | Question it answers |
|---|---|
| Recommendation | What should happen next: act, investigate, monitor, or deliberately wait? |
| Owner | Who can complete or commission the work? |
| Due date | When must the evidence or decision be ready? |
| Expected result | What output will close the action? |
| Status | Open, in progress, complete, blocked, superseded, or no action |
| Reopening trigger | Which new event would make the team reconsider a closed decision? |
Begin the next report by reviewing this ledger. State what happened after the previous recommendation. This prevents recurring competitive intelligence reporting from producing the same unowned advice each month.
Choose cadence from the decision cycle
Weekly notes suit fast operational decisions with enough meaningful activity. A monthly competitive report fits many product, growth, content, and sales-planning cycles. Quarterly reporting can support portfolio or strategy review. Triggered briefs are appropriate when a launch, packaging shift, regulatory event, or verified market move cannot wait for the calendar.
A slower cadence should increase synthesis, not encourage a larger archive. Keep the underlying evidence available throughout the period, then report the changes that crossed the agreed threshold.
Use an SEO module when search decisions are in scope
An SEO competitive analysis report is a specialized module inside the broader briefing when the audience must decide what to create, update, consolidate, investigate, or monitor. Preserve the same period, evidence, confidence, implication, owner, and due-date controls used elsewhere in the report.
| SEO module section | Question | Evidence boundary |
|---|---|---|
| Competitor movement | Which relevant pages, revisions, or topic clusters appeared during the period? | Use monitored publishing evidence with source-health context |
| Search evidence | Which queries, rankings, SERP patterns, and backlinks affect the opportunity? | Use the SEO tools that provide those datasets |
| Owned coverage | Do current pages already serve the audience and intent? | Use content inventory, Search Console, analytics, and owner review |
| Opportunity analysis | Where do demand, audience fit, product relevance, and feasible differentiation overlap? | Do not infer demand or performance from publishing alone |
| Action | Should the team create, update, consolidate, investigate, or monitor? | Assign an owner, evidence requirement, priority, and due date |
Large keyword exports, isolated authority scores, routine ranking fluctuations, and every page published by every competitor belong outside the main narrative unless they change a decision. The SEO team use case explains where reviewed competitor publishing enters a wider search workflow. Content Radar does not provide keyword volume, rankings, backlinks, direct SERP analysis, technical audits, or owned-site performance.
Where Content Radar fits in the evidence workflow
Content Radar can help teams organize relevant competitors, monitor supported public publishing sources and compatible ecommerce stores, review detected content and product changes, and retain operational source context. Its Product Monitoring scope is limited to compatible public stores and documented product events. Its Content Monitoring scope is limited to supported public sources.
The Reports feature in Content Radar is an in-app summary computed from current monitoring data. It is not the strategic report artifact taught in this article. Content Radar does not generate report files, email or schedule report delivery, create strategic recommendations automatically, provide private CRM or buyer-interview data, supply financial intelligence, or replace a complete enterprise competitive-intelligence platform.
Human owners decide which monitored evidence is material, combine it with authorized internal and third-party sources, write the interpretation, and approve the action. Review the competitive intelligence platform comparison when the program needs broader sources, native enablement assets, field inputs, integrations, or multi-team governance.
The report earns trust through selection and traceability Include the few changes that can affect a defined decision. Let every interpretation lead back to evidence, every limitation remain visible, and every recommendation lead to an accountable owner.
Build the public-evidence layer for your report
Use Content Radar to review supported competitor publishing and product changes before human owners decide what belongs in a broader competitive intelligence report.
See how Content Radar works · Review Product Monitoring · Compare CI platform scope