Software Tenant Time Zone Checklist

Time zone mistakes can change an appointment, report, deadline, or notification for an entire tenant. A clear model separates stored instants from displayed local time and makes the source of each setting visible.

Define the tenant and user settings

Document the default tenant zone, user preference, location-derived value, and fallback when no setting exists. State which setting controls scheduling, reporting, exports, and messages.

Store and display time deliberately

Keep an unambiguous event instant and display it with zone or offset context when it matters. Do not infer a business deadline from a browser setting without telling the user.

Handle scheduled work consistently

Define how jobs, reminders, recurring events, effective dates, and daylight changes behave. Preserve the original zone when a user travels, changes preference, or views a record created by another person.

The configuration effective-date checklist and batch job progress checklist cover scheduling and operational state.

Make exports and APIs explicit

Document timestamp format, offset, report zone, filters, file names, and API contract. Include enough context for a downstream system or customer to interpret the event without guessing.

Test boundaries and changes

Test tenant creation, user overrides, daylight changes, midnight, recurring jobs, late events, imports, exports, notifications, and API consumers. Track mismatched dates, support questions, and corrections.