CC061 — FICTIONAL RESPONSE LOG: CALENDAR AND DATA DICTIONARY
All records, actors, evidence identifiers and outcomes are synthetic. No real customer information is present. The example proves arithmetic under stated assumptions; it does not demonstrate business performance, consent or sales uplift.

FILES
CC061-response-log.csv: one summary row per enquiry, F01–F12.
CC061-staffed-calendar.csv: explicit staffed intervals including zero-coverage dates.
CC061-event-evidence.csv: synthetic event ledger supporting the summary references.
CC061-definition-sheet.txt: reusable worksheet.
CC061-readme.txt explains how to use these static example files with the reusable worksheet.

CALENDAR
TOR-INTAKE-v1; America/Toronto; Monday–Friday 09:00–17:00 with continuous lunch cover.
September 30, 2026 is a fictional planned company closure. This is not a legal holiday assertion.
All sample coverage intervals use UTC-04:00 for these dates only, not as a permanent Toronto rule.
Explicit intervals cover September 25–October 9, 2026, inclusive. Extend the calendar before calculating beyond this range.
Intervals are treated as [open, close). Duration at an endpoint is zero; a response exactly at its computed deadline passes.
Report cutoff: 2026-10-08T17:00:00-04:00.
Sample attempt target: 15 staffed minutes. Sample meaningful target: 60 staffed minutes.
Exceptions do not pause the clock independently. The September 30 closure is already represented by zero coverage in the calendar.
No unplanned lunch or import-delay exclusion is permitted.

CALCULATIONS
Convert timestamps to instants, preserving source text. For receipt R and event E:
elapsed_minutes = (E - R) / 60 seconds.
staffed_minutes = sum over non-overlapping calendar windows [O,C) of max(0, min(E,C) - max(R,O)) / 60 seconds. Merge overlapping coverage windows first; two available people do not double the response clock.
Due time: consume the target only in staffed intervals on or after receipt; carry any remaining target forward.
Off-hours response before next opening can consume zero staffed minutes without implying zero elapsed wait. Judge compliance by the computed due timestamp, not only the staffed-duration total: a response after a closing-time deadline is late even if staffed minutes have stopped increasing.
No event: duration blank, not zero. Age columns are receipt-to-cutoff for every eligible row, even after response; filter to missing events to report unresolved age.
as_of fixes the snapshot. Statuses must be recalculated at another cutoff.
Status met: due by cutoff and qualifying event at or before deadline.
Status late: due by cutoff and qualifying event after deadline.
Status overdue_missing: due by cutoff with no qualifying event.
Status not_yet_due: deadline after cutoff. This status describes cohort eligibility, not completion; a response already completed early is not unresolved. If no records are due, report no due enquiries rather than a percentage.
Status excluded: non-eligible duplicate. Preserve exclusion evidence.
For this sample no response occurs after cutoff; future reports must ignore events after their chosen historical cutoff.

COLUMN GROUPS
record_id / fictional: row key and explicit synthetic-data label.
eligible / exclusion_reason / linked_record_id: cohort decision; F12 duplicates F01.
channel: form or missed_call. Live answered inbound calls are outside this example cohort.
source_received_at: original offset-bearing acceptance or inbound ring timestamp.
received_at_utc: the same instant normalised to UTC.
imported_at: later entry into the working queue; not the receipt event.
acknowledged_at: automatic source receipt; does not satisfy either SLA.
owner / backup / owner_accepted_at: named fictional role ownership and acceptance event.
inbound_ring_end_at: end of ringing for missed calls; response clock began at ring-start.
calendar_version / coverage_timezone: identity of the immutable example coverage rules.
customer_timezone: fictional known customer zone for scheduling; source basis assumed in this synthetic exercise.
attempt_target_staffed_minutes / meaningful_target_staffed_minutes: example management choices.
attempt_due_at / meaningful_due_at: deadlines derived from receipt and calendar.
first_attempt_at / attempt_outcome: first qualifying human action and eventual outcome. For calls, the timestamp marks dial initiation, not the start of the live conversation. A live_conversation outcome does not establish two-way contact at the dial timestamp.
meaningful_response_at / meaningful_evidence: first qualifying useful human response and evidence category. For reviewed written messages, use delivery-system acceptance, not draft creation or a scheduled-send time.
delivery_confirmation: email acceptance is not proof of delivery or reading; live_exchange identifies a substantive conversation.
first_two_way_at: established relevant customer exchange. Empty means not established.
attempt_elapsed_minutes / attempt_staffed_minutes: receipt-to-first-attempt durations.
meaningful_elapsed_minutes / meaningful_staffed_minutes: receipt-to-meaningful-response durations.
as_of / age_elapsed_minutes / age_staffed_minutes: fixed reporting cutoff and full record age.
attempt_sla_status / meaningful_sla_status: per-target status at cutoff.
exception_code / exception_pauses_clock: diagnostic classification; false means no extra discretionary pause.
requested_callback_at / callback_kept: requested instant and adherence, independent of core SLA.
next_action: fictional workflow disposition, not evidence that a real action happened.
evidence_ref / reviewer: synthetic ledger grouping and fictional audit role; no production records implied.

RECORD INTERPRETATIONS
F01: Friday close-to-Monday carry-over; first attempt 13 staffed minutes / 3,853 elapsed.
F02: Saturday voluntary attempt consumes zero staffed minutes. Monday human email consumes 12 staffed minutes. No recurring weekend promise.
F03: Pre-opening receipt; staff clock starts at opening.
F04: Missed call; voicemail does not qualify as meaningful. Human email accepted at 11:44; reading and reply unconfirmed.
F05: Lunch backup gap; clock keeps running, attempt late.
F06: Company closure on September 30; carry-over to October 1.
F07: 24-minute import lag. First attempt is measured from source receipt, not import.
F08: Failed call to invalid destination; attempt counts, meaningful response missing and overdue. Disposition records no usable return channel. It is not retroactively excluded.
F09: The synthetic scenario assumes the customer requested 2026-10-05 at 14:00 Toronto. requested_callback_at stores this supplied assumption; the compact event ledger does not contain the original message body. Callback honoured, unadjusted SLA late. Friday 180 minutes plus Monday 300 minutes = 480 staffed minutes to attempt; meaningful response 482.
F10: Source 10:00 at UTC-02:30 equals 12:30 UTC and 08:30 Toronto on October 5. Attempt 09:03 Toronto: 33 elapsed / 3 staffed minutes.
F11: Received October 8 at 16:50; no attempt by 17:00 cutoff. Ten staffed minutes consumed. Attempt due October 9 at 09:05; meaningful due 09:50.
F12: Verified duplicate, excluded once linked to original F01. Original deadline never resets.

EXPECTED TOTALS
12 rows; 11 eligible; 1 duplicate excluded.
10 records due per target; 1 eligible record not yet due.
Attempt: 7 met, 3 late, 0 overdue missing, 1 not yet due.
Meaningful response: 8 met, 1 late, 1 overdue missing, 1 not yet due.
10 first attempts; 9 completed meaningful responses; 7 established two-way contacts. F02 and F04 have meaningful responses but no two-way contact. F08 and F11 have no meaningful response at cutoff.
8 completed meaningful responses were on time. Completed-only 8/9 is not the due-cohort rate of 8/10.
All outcome rates are fictional illustrations.

IMPORT AND USE
These CSVs contain saved values, not spreadsheet formulas or an automatic calculator. Editing dates does not recalculate durations, deadlines or statuses. Recompute them using the stated rules before operational use.
Import timestamps as text to preserve offsets. Parse deliberately in the chosen tool.
Use the worksheet to replace the fictional policy before operational use.
Retain event-level evidence and append corrections; do not silently overwrite disqualified responses.
The example ledger has no corrections because no fictional bounce/correction case is modelled.
Do not put real contact details or sensitive enquiry narratives into broad audit exports.

CALENDAR AND EVENT COLUMNS
Calendar: calendar_version identifies the policy; date is the local calendar date; timezone is its named zone; open_at and close_at are offset-bearing coverage boundaries; staffed is true only for a covered interval; reason explains the interval or closure. Closed dates have empty boundaries.
Ledger: evidence_ref joins the response summary; event_id uniquely identifies an event; record_id joins the enquiry; fictional is always true here; event_type identifies the recorded milestone; event_at is its offset-bearing timestamp; actor identifies the fictional role or system; detail supplies a short scenario code or explanation.

EVIDENCE LIMITS
The 72-event ledger is a simplified fictional teaching dataset. Its outcome codes do not independently prove response content, delivery, permission, duplicate verification or callback-request wording. Those facts are declared scenario assumptions. A production audit needs access-controlled source evidence and correction history. Event IDs identify events; they are not a chronological sort key. Sort parsed event_at instants when reconstructing a timeline.
