Content Planning and Briefs

Comparison Page Brief

Plan a fair comparison page with reader-led criteria, verifiable sources, explicit claim boundaries, balanced alternatives, and named update ownership.

Free editable Markdown · Product marketers, editors, and SEO teams · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Decision scope

Reader: [Role, context, and experience]
Decision: [What is being chosen]
Options included: [Names and exact plans or versions]
Options excluded and why: [Document scope]
Publisher relationship: [Owned product, partner, affiliate, or none]
Primary scenarios: [Two or more distinct jobs]
Last checked: [YYYY-MM-DD]

Criteria and evidence

Criterion 1: [Neutral definition] — **Why it matters:** [Reader need]
Criterion 2: [Neutral definition] — **Why it matters:** [Reader need]
Criterion 3: [Neutral definition] — **Why it matters:** [Reader need]
Evidence standard: [Documentation, reproducible test, or other source]
Unknowns: [Details that could not be verified]
Decision rule: [How criteria influence scenario recommendations]
Evidence log location: [Working document or repository]

Fairness and maintenance checks

The same criteria and evidence dates apply to every option.
Plan, version, region, tax, and billing assumptions are clear.
Facts, publisher tests, and opinions are labeled separately.
Strengths and material limitations are included for each option.
The page does not imply an affiliation that does not exist.
Screenshots and quotations retain relevant context.
Recommendations vary when reader needs vary.
A person owns updates and correction requests.

How to use this template

Describe the target reader, decision, shortlist, exclusions, and conditions that could change the choice.
Set neutral comparison criteria and an evaluation method before recording results.
Capture a dated source and exact qualification for every material feature, price, or policy claim.
Draft scenario-based recommendations that include drawbacks and cases favoring each option.
Assign a review owner and refresh trigger for changes in plans, products, evidence, or reader needs.

Define the decision before choosing criteria

Write down who is comparing the options, the job they need to complete, and the constraints that can change the answer. A freelancer choosing a writing tool may value low commitment and simple export, while a regulated team may prioritize access controls and documented processing. Turn those needs into neutral criteria before examining which option performs best. Include deal-breakers, recurring costs, migration effort, support, and limitations where relevant. If every criterion was selected after looking at the publisher's strengths, the page is marketing theater rather than a useful comparison.

Build a source-backed evidence table

For each cell, record the precise claim, source URL, access date, plan or version, geography, and any qualification. Prefer official documentation for features and terms, but distinguish a vendor's claim from independently observed performance. Run hands-on checks only when they can be described and reproduced; do not generalize from an undocumented trial. Use “not found in reviewed documentation” instead of “does not exist” when absence cannot be established. Prices, free limits, integrations, and policies change, so give them an owner and a scheduled review date.

Write for fit rather than a universal winner

A strong conclusion explains which option may suit which scenario and why. Acknowledge areas where the alternative is a better fit, and apply the same standard of evidence and specificity to every option. Avoid loaded headings, unequal screenshots, and vague superlatives such as “best” or “most accurate” without a defined measure. Separate fact, observed test result, and editorial judgment. If you compare your own offering, disclose that relationship prominently and invite readers to verify current details at the source.

See the fields in context

Fictional example: team note applications

MeadowNote and FieldJot are invented products with invented plans. The comparison illustrates fair criteria only.

Reader: A six-person volunteer group that needs shared meeting notes without complex administration.
Criteria: Guest access, export format, offline editing, monthly cost, and account recovery.
Evidence boundary: Features are recorded for fictional “Team Basic” plans checked on the same invented date.
Balanced result: MeadowNote suits groups needing offline edits; FieldJot suits groups prioritizing guest access.
Update trigger: Recheck when either fictional plan changes its price, export options, or sharing policy.

Frequently asked questions

Should a comparison page use a score?

Only if the scoring method is transparent, justified by reader needs, and consistently applied. A single total can hide tradeoffs, so scenario recommendations may be more useful.

Can official product pages be the only sources?

They are often appropriate for current features and prices, but they communicate the vendor's position. Claims about quality or outcomes may require reproducible testing or independent evidence.

How should unavailable information be handled?

State what you checked and when. Use a qualified “not verified” label rather than guessing or converting missing documentation into a definitive negative claim.

How often should a comparison be updated?

Base the schedule on volatility and impact. Also trigger an immediate review after a material pricing, plan, policy, ownership, or feature change.