SPEED TO LEAD: RESPONSE POLICY WORKSHEET AND FICTIONAL EXAMPLE LOG
Canada Create | Prepared and checked 8 October 2026

This companion is an original teaching example. All enquiries, roles, event references and outcomes are fictional. The example checks a stated response policy; it does not measure a real business, establish consent or demonstrate a sales improvement.

START HERE
1. Complete CC061-definition-sheet.txt with your own policy choices, owners and review date. Blank lines are intentional fields for your decisions.
2. Read CC061-log-dictionary.txt before importing the CSVs.
3. Import timestamps as text, then parse their explicit offsets in your chosen tool. Preserve the original timestamp strings.
4. Reproduce a worked record using CC061-response-log.csv, CC061-staffed-calendar.csv and CC061-event-evidence.csv.
5. Test your own implementation with a closing-time enquiry, a planned closure, a missing response, a delayed import and an offset change before using it for performance reporting.

WHAT THE FILES DO
The definition sheet is an editable plain-text policy worksheet.
The three CSVs are static examples with saved values, not a formula-driven calculator. Changing a cell does not recalculate any other cell. You must implement and verify the calculations in the tool you choose.
The dictionary explains every column group, the calendar, event definitions, missing values and reporting rules. Keep it with the example data.

EXPECTED EXAMPLE RESULTS
12 enquiries: 11 eligible and 1 linked duplicate excluded.
15 calendar dates: 10 staffed weekdays and 5 closed dates, including the fictional company closure on 30 September 2026.
72 synthetic event records; some receipt confirmations occur before the separate import event.
Cutoff: 2026-10-08T17:00:00-04:00. This is a fictional reporting snapshot.
Attempt target: 10 due, 7 met, 3 late, 0 overdue missing; 1 eligible record not yet due.
Meaningful-response target: 10 due, 8 met, 1 late, 1 overdue missing; 1 eligible record not yet due.
Observed eligible events: 10 first attempts, 9 meaningful responses, 7 two-way contacts.
F08 remains without a meaningful response. F11 is not yet due; refresh its status at a new cutoff.
The 7/10 and 8/10 on-time results are fictional calculations, not performance benchmarks.

CALENDAR LIMITS
The sample calendar covers 25 September through 9 October 2026 in America/Toronto. It has no daylight-saving transition within that range. UTC-04:00 applies to those sample intervals only. Extend coverage using current named-zone rules before calculating beyond the supplied dates.
The closure on 30 September is a fictional company choice, not advice on statutory holidays or employer obligations. Lunch remains staffed under this example policy.
Merge overlapping coverage windows. Compute durations between UTC instants. Judge on-time results against the exact deadline; an expired deadline does not move merely because the office closes.

EVIDENCE AND PRIVACY
The ledger supports reconstruction of timestamps and arithmetic. Its short codes do not independently establish the content of communications or real consent, delivery or duplicate decisions.
Use access-controlled source evidence for a production audit. Do not place real customer contact details, message bodies, credentials or sensitive case narratives into broadly shared timing exports.
This is operational guidance, not a determination of communication permissions or legal obligations.
