What role does NetBox's site-level time_zone field actually play in timestamp conversion?

NetBox persists timestamps in PostgreSQL as UTC and renders them in the web UI according to each user's preferred time zone, defaulting to the installation-wide TIME_ZONE setting when no preference is set. The REST API serializes datetime fields as ISO 8601 strings in UTC, leaving regional interpretation to the client.

The dcim.Site model includes an optional time_zone field that records a site's regional offset. Despite its presence, no built-in scheduler, maintenance window, or reporting logic appears to consume this value, and it does not change how timestamps for that site's objects are stored, displayed, or filtered.

For teams managing multi-region deployments, this raises an unresolved design question: whether site.time_zone is intended purely as descriptive metadata, or whether it is meant to anchor regional date conversion in custom integrations and future features.

1. What is the documented purpose of the site-level time_zone field in NetBox 4.x?
2. Can it be relied upon to drive regional date conversion in custom scripts or plugins?
3. Does any built-in feature currently consume this field for scheduling or reporting?