The Test Bench240 guides, 20 benches
Conversion.sale
The Test Bench - a field guide to conversion for small online businesses
Home / Bench 20 - Audits, checklists and mistakes / Guide

Audit Timing: Seasons, Sales and When Not to Judge

Funnels have seasons, and an audit or a read that ignores them manufactures findings. This guide sets the timing rules: audit in representative weeks, verify repairs within the same season's shape, and keep a calendar of your business's known distortions beside the baseline.

Published 24 October 2026Evidence checked on 24 October 2026Small online businesses, global English edition

The short answer

Judge a funnel against its own season's shape. Audit deep work in representative trading weeks, not during sales, launches or stock crises; verify repairs against the same season's baseline segment; and keep a written calendar of the year's distortions (promotions, seasonal peaks and troughs, campaign flights, the trade's calendar) attached to the baseline, so a future reader can tell weather from climate. Most 'mystery' movements in small-store funnels are calendar events that nobody wrote down. The calendar is four lines a quarter and it retires more false findings than any tool.

The distortions are knowable in advance

List yours honestly: retail has its peaks and its January; services have weather, budget cycles and school terms; software has renewal seasons and conference months; every business has its promotional calendar and its stock or capacity cycles. Add the irregulars as they are scheduled - a price rise, a range change, a marketplace promotion - because a distortion known in advance is data, while the same event discovered during a read is an argument. The calendar lives with the baseline and is consulted before any audit date or read window is approved.

Placing audits inside the year

The deep audit belongs in a representative stretch - ordinary traffic, ordinary range, ordinary prices - ideally six to eight weeks before your peak season, so its fix list ships and verifies before the peak makes everything unreadable and precious. The hour audit runs monthly regardless, with its findings window-flagged per the mistakes guide. Auditing during the peak is not forbidden; it is specialised: peak audits hunt mechanical defects and capacity failures (the site under load, the checkout under volume), and their rate findings are quarantined until a normal window can try them.

When a read must cross a season boundary

Sometimes a repair ships at a season's edge and its window straddles the change. The honest options: extend the read until a comparable clean window exists inside the new season and compare against the new season's prior-year or early baseline; split the verdict (kept on mechanism and qualitative evidence, rate verdict deferred); or revert-to-baseline comparisons using the same weeks last year where the business has the history. What is not available is pretending the boundary is not there. The log entry names the boundary and the option chosen, so the verdict's confidence is part of the record.

Year-ago comparisons: uses and abuses

Same-period-last-year is the small store's seasonal control, and it misleads when the business changed shape between the years: new ranges, new channels, a price architecture replaced. Use year-ago for shape (the week's pattern, the season's depth) rather than for level, unless the shape held. Where the business is young and last year is another country, the honest control is the season's own early weeks plus the distortion calendar's notes - thinner evidence, labelled as such, beats a confident comparison to a business you no longer run.

Plan the year's measurement like the year's trading

At the year planning sitting, place the four deep-audit windows, the peak-season defect watch, and the baseline refresh dates on the same calendar as the trading events they must avoid or serve. Measurement planned in advance survives contact with a busy year; measurement improvised around one does not happen, and the year passes with opinions where the funnel file should be. Four windows, written down in January, is the entire ask - and it is the difference between a business that knows its seasons and one that is surprised by them annually.

Capacity seasons count too

Trading seasons are only half the calendar; the other half is the business's capacity to act. An audit delivered into the quarter when the one technical person is migrating platforms, or the owner is opening a second location, produces a fix list that ages unworked - and an unworked list teaches the business that audits are theatre. Place the deep audit where its list can ship: the review rhythm should hold one honest conversation a year about capacity, setting the audit count and sizes to the hours that genuinely exist. A smaller audit fully worked compounds faster than a grand one admired and shelved.

Sources and evidence on the record

Evidence basis: Method guide. Any figure quoted is attributed to a named published source listed below; worked examples are labelled illustrations with round numbers, not measurements. Applies when: At annual planning and before setting any audit or read window

Next on the bench

Bench 20 - Audits, checklists and mistakes CRO Audits, Checklists and Mistakes: The Working Guide An audit is a disciplined inspection: baseline first, evidence per finding, findings converted into a prioritised fix list, and the list verified after repair. This bench holds the audit methods, the checklists that run them, and the mistakes catalogue that keeps a small business from paying tuition twice. Bench 20 - Audits, checklists and mistakes The Full-Day Audit: Evidence, Recordings and the Funnel File The deep audit spends a day building the funnel file: segmented rates, a recording sample per weak stage, visitor voice from surveys and tickets, and findings written to the standard the fix list can act on. This is the method, in order, with the time boxes. Bench 01 - Foundations and measurement Set a Baseline Before You Change Anything A baseline is the honest before-picture: conversion by device and source over the last 60 to 90 days, written down before any change ships. Without it, every result afterwards is a guess wearing a number.