FUNNEL PAGE COMPARISON: DECISION AND EVIDENCE WORKSHEET Purpose: Decide what evidence could resolve one proposed page change. This is a planning document. It does not allocate traffic, run an experiment, choose statistical thresholds, collect analytics or establish an improvement. All filled cases are fictional; no participants, submissions or results exist. FILLED VERSION RECORD — REPAIR-CLASS ENQUIRY Actual offer assumed for the exercise: A conversation about available sessions. An enquiry does not reserve a place. Version A button: “Get started” Version B button: “Ask about repair sessions” Planned difference: Button wording only. Intended unchanged: Offer, surrounding copy, form fields and destination. Verification that conditions are unchanged: NOT RUN; these are planned versions. Question: Does the proposed wording make the information-request step clearer to likely readers? Outside this question: Bookings, revenue, fulfillment and causal conversion lift. Known false promises should be corrected, not retained for an experiment. EVIDENCE MATCH Meaning question -> Relevant readers interpreting identified versions. Limit: Does not estimate an audience-wide conversion effect. Function question -> Authorized action and receiving-result checks. Limit: Does not establish preference or motivation. Observed outcome difference -> Comparable version-linked records, defined units, windows and unknowns. Limit: Alone, does not establish the cause. Causal difference -> Suitable controlled design and analysis, actually executed. Limit: This worksheet supplies no design certification or execution evidence. C01 — PREPARE A CLARITY CHECK Available in fictional plan: Static A/B page versions; question about expectation. Decision: Prepare the existing comprehension-check method, with no live sending. Record: Version seen, relevant reader context, prior exposure, observation and interpretation separately. Possible useful evidence: A reader expects the button to reserve a place and identifies the wording that led to that expectation. This is a planned observation type, NOT an observation that occurred. Action that evidence could inform: Review wording against the real offer. Cannot establish: More bookings/sales or successful submissions. Current execution status: NOT RUN. Owner/date: UNASSIGNED. C02 — HOLD A BEHAVIORAL COMPARISON Question: Does B produce more saved enquiries? Assumed available report: Button clicks, without a link from displayed version to a confirmed new enquiry. Decision: HOLD the saved-enquiry comparison. Next task: Measurement owner determines whether appropriate version and receiving records can be obtained, with permitted observation window and clear definitions. Current availability for this question: UNAVAILABLE, not zero saved enquiries. Cannot establish: Save-rate difference, causal lift, bookings or revenue. Current execution status: NOT RUN. Owner/date: UNASSIGNED. C03 — KEEP THE RECORD DESCRIPTIVE Assumed changes: Button wording, session price and promotion all change together. Assumed later records: Enquiry totals, but no comparable exposed audiences or version histories. No numerical values are supplied by this example. Decision: Record changes and observations; do not attribute a difference to copy. Next task: Reframe a future comparison around a supportable question. Cannot establish: Which change caused the result or whether the button won. A smaller total has the same attribution problem as a bigger total. Current execution status: NOT RUN. Owner/date: UNASSIGNED. BLANK COMPARISON BRIEF Decision owner / date / intended review point: Page and exact version/artifact A: Page and exact proposed version/artifact B: Real offer and intended visitor action: Question this comparison should answer: Why the answer could change a decision: Exact planned differences: Intended unchanged conditions and how to inspect them: Corrections that must happen regardless of performance: Questions this exercise will NOT answer: EVIDENCE NEEDS — COPY A RECORD FOR EACH REQUIRED INPUT Required observation or record: Unit / group / eligibility definition: Version/exposure linkage needed: Outcome definition and receiving evidence needed: Entry / follow-up windows / timezone: Repeated events, prior exposure, missing and unknown records treatment: Available source / permission / actual access state: Appropriate method for this question and why: Design/analysis work still required before execution: Unresolved input and smallest next task: INTERPRETATION AND DECISION Other changes or conditions that could explain a difference: Prior exposure or audience differences to preserve: Evidence that would support revising the page: Evidence that would support retaining it: Evidence that would require more investigation: Unacceptable false promise, accessibility or receiving-step problems: Reason to hold or stop this comparison: Observation / interpretation / limit (keep separate): Contradictory evidence preserved: Actual decision and evidence references (blank until available): Next action / owner / date: Do not label the highest observed number a winner without suitable evidence. No universal sample size, duration or stopping rule is provided. Do not substitute clicks for saved enquiries or missing records for zeros. Record “unknown” when the actual evidence cannot settle the question. CFAI workflow/access: https://www.clickfunnels.ai/agents This file grants no access and establishes no experiment/analytics feature. Comprehension method: https://www.clickfunnels.ai/learn/funnel-page-comprehension-check Primary research-planning guidance: https://www.gov.uk/service-manual/user-research/plan-user-research-for-your-service General comparison design (digital-health source; no health outcomes transferred): https://www.gov.uk/guidance/ab-testing-comparative-studies