Where I work we deal a lot with events (yoga gyms, community sports centers, etc.) and the old code was saving EVERYTHING in UTC. Every 6 months we&#x27;d have some bug report coming in saying that some event was now one hour later or earlier on the website, or in some report, or in an admin edit screen.<p>I got fed up with this and migrated all the data so it&#x27;s saved in local time with the timezone information in a separate column. If an admin creates an event for 4pm, we save 4pm with the event location&#x27;s timezone. Since an event only takes place at one specific location, it makes no sense to have the data in UTC in the database. We can convert to UTC if we want but it&#x27;s not really useful. The thinking is that if a client is shopping for a class in a different timezone, why would we convert the class&#x27;s time to the client&#x27;s timezone? It makes no sense. It&#x27;s always in local time. This has helped so much.