Overview
Upvise records the timezone based on your device's current timezone setting at the exact moment you create your daily diary form. It does not reference the diary/subform date or your physical location.
This approach supports a mobile and flexible workforce, but it can lead to confusion when:
Entering backdated data
Working while travelling
Entering data during a timezone shift, such as daylight saving changes
Key Concept: Timezone Is Device-Based at Data Entry
When you enter data into Upvise using the Daily Diary (timesheet) the timestamp is stored using your device’s timezone at that moment.
✅ This is not influenced by the diary/subform date you're entering.
✅ Upvise does not store historical timezone rules or adjust automatically for them.
The timezone is captured automatically into a hidden system field (e.g.,
timezone
in Daily Diary).The only way to apply a different timezone is to manually change your device’s timezone before data entry.
Device Settings
To ensure timestamps are accurate:
✅ Enable "Set Time Automatically" or "Automatic Timezone" in your mobile or desktop settings.
When travelling or switching regions (e.g., crossing state lines or to a different country), make sure your device has come online in the new timesone (mobile data or Wi-Fi) so the timezone can update automatically.
Important to Know
Timezone is captured at time of data entry, using your device’s current timezone.
This is managed by your phone or computer system settings.
The field is not meant to be edited.
If you backdate data (e.g., enter data for 4th April 2025, today), the current timezone still applies.
If there's a mismatch, you can update the times in the Workbench after syncing.
User Stories
Field Worker in Melbourne
“I’m submitting today’s Timesheet while working on-site in Melbourne.”
Device Timezone: GMT+10
Timesheet Date: Today
✅ Times sync correctly to Workbench using GMT+10.
Office Admin Entering Backdated Data
“I'm entering a diary entry today for a job we completed on 4th April”
Device Timezone: GMT+10
Diary Date: 4 April (backdated)
✅ Time still syncs with GMT+10—based on the current device setting, not the date being entered in the subform.
Travelling Engineer in NZ
“I’m in New Zealand today (GMT+13), entering today’s Timesheet.”
Device Timezone: GMT+13
Timesheet Date: Today
✅ Syncs using GMT+13 automatically, based on the current device timezone.
Retrospective Entry While Adjusting Timezone
“I want to enter data for 4th April as if I were in New Zealand on that date.”
Step 1: Manually set device to GMT+13
Step 2: Enter timesheet for 4 April
✅ Syncs with GMT+13, even for backdated entries—because it uses the current device setting.Remember to re-enable automatic timezone back in your device settings after.
Timezone Shifts: Daylight Saving in AU & NZ
Upvise does not track timezone shifts like Daylight Saving Time (DST). It only captures whatever your device is currently using. Here’s how DST may impact your data:
Example:
Melbourne (Victoria)
5 Oct 2024 11.30pm You create & submit a Daily Diary.
Device Timezone: GMT+10
⏱ Timestamp saved using GMT+10
6 Oct 2024 4:00am DST starts, and the timezone shifts to GMT+11
The next daily diary entry is saved with GMT+11, even if you have "backdated" the diary date to a previous day.
Your records will reflect two different timezones, based on the timezone of your device at the time the form was created.
Sample DST by Region (2024–2025)
Region/State | Standard Time | DST Time | DST Starts | DST Ends |
---|---|---|---|---|
NSW, VIC, ACT, TAS | AEST (GMT+10) | AEDT (GMT+11) | 6 Oct 2024 (2am → 3am) | 6 Apr 2025 (3am → 2am) |
South Australia | ACST (GMT+9:30) | ACDT (GMT+10:30) | 6 Oct 2024 | 6 Apr 2025 |
Queensland | AEST (GMT+10) | No DST | — | — |
Western Australia | AWST (GMT+8) | No DST | — | — |
Northern Territory | ACST (GMT+9:30) | No DST | — | — |
New Zealand | NZST (GMT+12) | NZDT (GMT+13) | 29 Sep 2024 (2am → 3am) | 6 Apr 2025 (3am → 2am) |
Tip
If timezone accuracy is important for reporting, compliance, or billing:
Temporarily switch your device to the appropriate timezone before entering data for a past event.
You can always adjust timestamps later in Workbench, after the sync is complete.