Background
If you select a future start date and enable data collection, the survey launches on the set date, and sends notifications at the configured time. To configure your send-out time settings, see Set survey send-out time.
Alternatively, employees can respond to the survey after the round opens before receiving a notification, by accessing the survey via mobile app, personal dashboard, or kiosk mode.
If you don't set a send-out time for survey notifications, the fallback send-out time is 09:00. The time zone of the employee record works with the send-out time to assess when each employee should receive the notification.
You can set the time zone of the employee record manually (see Set employee record time zones in the user interface or Set employee record time zones using data import), or Peakon will detect it automatically for each employee, from the browser settings in the previous survey.
If no time zone is present on the employee record, there’s a fallback order for each individual employee.
- Survey schedule time zone.
- Company time zone.
- UTC time zone.
For subsequent survey rounds, the survey detects the time zone of each employee that doesn't already have a time zone on their employee record. Future survey rounds use the detected employee time zone for each employee, unless you override it on their employee record. We recommend setting the employee record time zones manually, if you're using VPN tools that affect employee IP address locations.
Configuration examples
Employee record time zone | Schedule time zone | Company time zone | Survey time | First survey round | Subsequent survey rounds |
---|---|---|---|---|---|
Not set or detected. |
Not set. |
Not set. |
Not set. |
09:00 UTC. The survey uses the standard survey time and time zone as fallback. |
Survey detects time zones from last time. 09:00 in the local time zone of each employee. |
Not set or detected. |
Not set. |
Copenhagen, Denmark. |
10:00. |
10:00 Copenhagen, Denmark. The survey uses the last fallback option: company time zone. |
Survey detects time zones from last time. 10:00 in the local time zone of each employee. |
Not set or detected. |
Lisbon, Portugal. |
Copenhagen, Denmark. |
10:00. |
10:00 Lisbon, Portugal. The survey uses the first fallback option: schedule time zone. |
Survey detects time zones from last time. 10:00 in the local time zone of each employee. |
Paris, France. |
Not set. |
Copenhagen, Denmark. |
Not set. |
09:00 Paris, France. The survey uses the standard 09:00 send-out time, since survey time isn't available. |
09:00 Paris, France. |
Paris, France. |
Not set. |
Copenhagen, Denmark. |
10:00. |
10:00 Paris, France. |
10:00 Paris, France. |
Paris, France. |
Lisbon, Portugal. |
Copenhagen, Denmark. |
10:00. |
10:00 Paris, France. |
10:00 Paris, France. |
Not set or detected. |
Lisbon, Portugal. |
Copenhagen, Denmark. |
Not set. |
09:00 Lisbon, Portugal. The survey uses the first fallback option: schedule time zone. It also uses the standard 09:00 send-out time, since survey time isn't available. |
Survey detects time zones from last time. 09:00 in the local time zone of each employee. |
Multiple time zones
If you have geographically dispersed employees, we recommend:
- Setting the time zones on employee record. Alternatively, let the first survey notify employees in the time zone of the schedule, and automatically detect each employee's time zone for the next survey round.
- Setting the time zone of the survey schedule to the most-eastern time zone of your employee cohort, when surveying geographically dispersed employees on the same survey schedule. This way the schedule can notify all employees at the selected send-out time in their local time zone.
Example: If schedule time zone is London, the survey round opens at 00:30 in London, which is already 11:30 in the morning in Auckland. If you set the send-out time to 09:00, the survey open time has already missed this, and instead immediately notifies Auckland employees at 11:30 in their local time. You can resolve this by setting the schedule time zone to the most-eastern time zone (Auckland), so the survey can notify everyone at 09:00.
Email send-out time
The time zone aware configuration only impacts the survey email and reminder emails.
Email type | Time zone aware? |
---|---|
Survey emails | ✓ Time zone aware |
Reminder emails | ✓ Time zone aware |
Daily digest emails | ✘ Weekdays 06:00 AM UTC for everyone |
Low participation emails | ✘ 03:00 AM UTC |
Schedule reminder emails | ✘ 03:00 AM UTC |
Instant sensitive comment notification email | ✘ Could be instant or in daily digest |
Comments
0 comments
Article is closed for comments.