Website and Conversion Content

Comparison Page Evidence Table

Build a dated, source-backed feature comparison using fair criteria, exact plans, qualified unknowns, equivalent evidence, and named update ownership.

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

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Comparison scope

Target reader and task: [Decision context]
Options: [Products, methods, or plans]
Exact versions/plans: [Comparable scope]
Market and currency: [Region]
Publisher relationship: [Owned, affiliate, partner, or none]
Evidence cutoff: [YYYY-MM-DD]
Status definitions: [Yes, no, partial, unknown, not applicable]
Test method: [Documentation or reproducible workflow]

Evidence cell

Criterion: [Neutral definition]
Why it matters: [Reader need]
Option and plan: [Exact]
Status: [Defined label]
Evidence statement: [What is documented or observed]
Source type: [Official documentation, test, policy, other]
Source URL and access date: [Location; YYYY-MM-DD]
Version or environment: [Relevant detail]
Qualification: [Limit, add-on, beta, quota, or unknown]
Reviewer: [Name and date]

Fairness checks

Criteria were defined before results were collected.
Every option receives equivalent evidence effort.
Plan, region, date, and version are clear.
Missing documentation is not converted into a false negative.
Checkmarks do not hide limits or add-ons.
Commercial relationships are disclosed.
Public interpretation includes cases favoring different options.
Every volatile cell has an update trigger.

How to use this template

Define the audience, options, exact plans, market, date, and neutral criteria.
Set evidence rules and status definitions before researching individual products.
Capture one source-backed record for every material cell and qualification.
Review equivalent treatment, ownership disclosure, uncertainty, and public-table clarity.
Publish only verified distinctions and schedule cell-level refresh or correction ownership.

Define neutral criteria first

Start from the target reader's task and constraints, then specify what each criterion means and how it will be evaluated. “Easy to use” is too vague; “a new workspace can export notes in a documented open format” is observable and relevant to some readers. Separate availability, capability, limit, quality, and editorial preference. Include criteria where competing options are stronger when those matter to the decision. Freeze the method before collecting results to reduce selective interpretation.

Capture evidence at cell level

Each feature cell should link to a source record with product, plan, version, market, source type, URL, quoted or observed detail, and access date. Mark “yes,” “no,” “partial,” “unknown,” and “not applicable” only after defining them. If documentation was not found, write that qualified observation rather than declaring the feature absent. For hands-on tests, preserve steps, environment, sample data, and result. Apply equivalent effort and evidence standards to every option.

Publish meaning, not a wall of checks

Translate evidence into a concise table focused on decision-relevant distinctions. Add notes where a checkmark would hide a quota, add-on, beta status, or plan restriction. Provide scenario-based interpretation and acknowledge uncertainty. Disclose ownership, affiliate, or commercial relationships. Assign an update owner and trigger for product, price, plan, policy, or source changes. If a source expires, the cell should return to review rather than silently remaining true.

See the fields in context

Fictional example: community event registration tools

QueueNest and SignHarbor are invented products, plans, and sources.

Criterion: Export attendee records in CSV without a paid add-on.
QueueNest: Fictional Basic documentation says CSV export is included; checked for the invented EU plan.
SignHarbor: Documentation reviewed does not identify export availability, so the cell is “unknown,” not “no.”
Qualification: The comparison does not test whether exported fields meet any specific privacy or reporting requirement.
Update trigger: Recheck both fictional sources after a plan or documentation revision.

Frequently asked questions

Is official documentation enough evidence?

It is suitable for many feature and plan claims, while still representing the vendor's description. Quality or performance claims may need reproducible testing or other evidence.

How should an unknown value appear?

State what was checked and when, label the cell unknown, and provide a verification route. Do not guess.

Can a single score summarize the table?

Only with a transparent weighting based on a defined reader scenario. Scenario-specific recommendations often preserve tradeoffs more honestly.

When should a cell be rechecked?

After relevant product, plan, price, policy, region, version, documentation, or test-method changes, plus a periodic risk-based review.