# Workspace Timezone Browser Default Check

Expose a browser-derived default before treating a client calendar as locally timed.

## Scope
Preparation and review only. No account action or professional decision.

## Inputs
Workspace settings capture, browser timezone, client-stated target zone and selected wall-clock times.

## Workflow
1. Keep browser and workspace settings as separate evidence.
2. Record that Planable initially sets timezone from the browser; do not assume it stayed unchanged.
3. Compare actual workspace zone with the supplied client target.
4. Return mismatch and missing-setting questions without changing any timezone.

## Output contract
workspace | browser_zone | setting_zone | target_zone | mismatch | capture_time | hold

## Fictional acceptance test
Fictional browser zone is Asia/Kolkata and client target is America/New_York. Without a workspace settings capture the actual configured zone remains unknown. Do not equate the browser default with a current client setting.

## Review gates
Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

## Method source
https://help.planable.io/hc/en-us/articles/21715280074524-Change-workspace-name-time-zone

Checked October 13, 2026. Oct13 live AIS Search Console: marketing Copilot37 impressions, Planable/Claude43, Planable/ChatGPT24, campaignbrief12, investoragent19, MuseIndia103. Social calendar/reporting topics follow parent-query leads; other professions follow documented workflow needs, not measured exact intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.