Customers are looking for a centralized governance model for segment time zones (similar to Journey settings). Currently, segment time zone is managed per record with no default configuration. This creates operational overhead and inconsistency risks in large-scale implementations. 

While the current design ensures correctness and reusability, large enterprises need a governance layer on top—such as defaulting, validation, or policy enforcement—to avoid operational inconsistency across hundreds of segments.

Can this feature be included in the roadmap or planned capability to introduce a centralized/default time zone setting for Segments (similar to Journey settings) in Customer Insights – Journeys?