The baseline method, step by step
Week one of the pilot, and the two weeks before it if the business can start early.
BASELINE METHOD — [workflow], agreed [date] between [business owner] and [builder] 1. PERIOD: [14] consecutive days before go-live, including weekends. The same length after go-live, starting on day [3] of live operation (the first two days are shakedown and are logged but not counted). 2. UNIT: one row per [enquiry / booking / request / document]. Everything that arrives on [channels] counts, including the ones nobody replied to. 3. SHEET: the pilot baseline sheet (columns: date, channel, time received, time first replied, replied by, handled fully by agent, outcome, escalated + reason, staff minutes, notes). Kept by [name]; checked by [builder] twice a week. 4. DEFINITIONS, fixed now: "first reply" = first substantive message, not an auto-acknowledgement; "booked" = [confirmed in system]; "complete" = [all checklist items received]; "after hours" = [19:00–09:00 and Sundays]. 5. STAFF MINUTES: recorded by the person at the time, in whole minutes, including system entry. Where that is impractical, a two-day time sample is taken in each period and scaled. 6. SOURCE OF TRUTH: timestamps from [WhatsApp export / system log], not memory. Where the before-period has no log, the sheet is filled from the chat history, and the report says so. 7. WHAT IS NOT MEASURED: revenue, retention, lifetime value. These are modelled in the report from the measured rates and labelled as models.
If the business cannot log the two weeks before, the pilot’s week one is the baseline and the report says the comparison is one week against one week.