# Better Timezone Management

**URL:** <https://forum.avicennaresearch.com/t/better-timezone-management/1037>\
**Category:** To Do\
**Tags:** team:study, be:average\
**Created:** [May 21, 2025, 9:51pm UTC](https://forum.avicennaresearch.com/t/better-timezone-management/1037 "2025-05-21T21:51:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mojtaba](https://forum.avicennaresearch.com/letter_avatar_proxy/v4/letter/m/e56c9b/32.png) [@mojtaba](https://forum.avicennaresearch.com/u/mojtaba)\
**Post date:** [May 21, 2025, 9:51pm UTC](https://forum.avicennaresearch.com/t/better-timezone-management/1037/1 "2025-05-21T21:51:16Z")

</div>

Avicenna should store all Time Zone changes for all participants, either by embedding the TZ in the stored date/time values, or having it in audit logs and then, when the data is being read by researchers/participants, converting the date/times to the corresponding TZ.

Have a clear distinction between what should be displayed/exported in the researcher’s TZ and what should be displayed/exported in the participant’s TZ, and then apply it. What about exports vs. UI?

Also, take the participant’s timezone and DST into account when creating sessions with CSV.

**Requests:**  
Z-21345

**Category:**  
Study - Participation

---

<div class="post-metadata">

**Author:** ![m.hashemian](https://forum.avicennaresearch.com/letter_avatar_proxy/v4/letter/m/a5b964/32.png) [@m.hashemian](https://forum.avicennaresearch.com/u/m.hashemian)\
**Post date:** [May 30, 2025, 5:37pm UTC](https://forum.avicennaresearch.com/t/better-timezone-management/1037/2 "2025-05-30T17:37:12Z")

</div>



---

<div class="post-metadata">

**Author:** ![mojtaba](https://forum.avicennaresearch.com/letter_avatar_proxy/v4/letter/m/e56c9b/32.png) [@mojtaba](https://forum.avicennaresearch.com/u/mojtaba)\
**Post date:** [August 10, 2026, 12:17pm UTC](https://forum.avicennaresearch.com/t/better-timezone-management/1037/3 "2026-08-10T12:17:35Z")

</div>