An enquiry just after midnight in Melbourne can belong to a different report date in a Pacific-time search report. Agree the date convention and completeness window before claiming yesterday’s page release produced a same-day change. Reporting-day alignment is distinct from whether a visible query table contains every query.
Who should use this acceptance brief
Businesses comparing website enquiries with Search Console. Use this as a scoped website handover task. Where real system evidence is required, teaching examples are not a substitute.
Source-bound platform fact
Google documents Pacific Time for non-24-hour performance dates, while the24-hour view uses the browser’s local timezone and may include preliminary data. Google: performance dimensions and time zones · Checked 16 October 2026.
Filled teaching example
Synthetic example, not a client case. Finite inputs, expected decisions and counterexamples follow; no live integration is claimed.
On narrow screens, scroll to read the complete table.
| Input / case | Check basis | Expected decision |
|---|---|---|
| 2026-10-16T00:30+11:00 | Australia/Melbourne | 16 Oct |
| same instant | America/Los_Angeles | 15 Oct |
| 24h preliminary vs complete day | different windows | do not equate |
Run the acceptance exercise
- Record report timezone, exact date range and whether the data is preliminary.
- Convert a permitted synthetic event instant into both date conventions.
- Use complete comparable windows and keep unresolved attribution unknown.
Interpret the result and retain evidence
The fixture formats one instant in two explicit IANA zones. It does not retrieve GSC or prove an enquiry came from search. Time alignment is necessary context, not causal evidence. Retain the raw timestamp and chosen business/report date so later changes to the dashboard do not erase the original observation.
Limits before implementation
No real enquiry records accessed or new performance claims. Historical daylight rules depend on the runtime timezone database.
Replay the finite example
Save both files in one folder and run with Node22.13 or newer. The example sends no network requests and changes no account or site. Filled inputs and expected outputs · Inspectable functions
node decision-check.mjs gsc-report-day-timezone-contract.json