While someone in Madrid is just starting their day, another person in the Philippines might be wrapping theirs up, and someone in Alaska might still be asleep.
Naturally, that affects when people can vote!
🕒 Everyone lives their own “today”
In Happyforce, each person votes according to their local time.
That means the system understands that “today” isn’t the same everywhere.
The important thing is that each employee can vote only once per their own day, based on their time zone.
👉 If you’re in Madrid and it’s Tuesday, November 7th, you can vote for that day.
👉 If someone on your team is in the Philippines, when you go to bed it’s already Wednesday, November 8th for them — so they’ll vote for that day.
👉 And if you have someone in Alaska, while you start your Wednesday, they’re still living their Tuesday.
🧩 Where are votes stored?
Each Happiness Index (HI) vote is stored with the employee’s local date, not the company’s.
That way, everyone gets their full “day” to vote — no matter where they are.
Location | Local voting time | Employee’s day | Madrid day |
Madrid 🇪🇸 | 09:00 | Nov 7 | Nov 7 |
Alaska 🇺🇸 | 23:00 | Nov 6 | Nov 7 |
Philippines 🇵🇭 | 08:00 | Nov 7 | Nov 6 |
So even though all votes appear in the same dashboard, each one is recorded according to the voter’s real local day.
📊 What will you see in the dashboard?
The admin dashboard and Happiness Index (HI) metrics are calculated respecting each voter’s time zone.
This means that sometimes:
You might see votes from “tomorrow” if people in some countries have already started a new day.
Or the data from “yesterday” might adjust slightly as people in later time zones (like the Americas) finish their day.
👉 Don’t worry — the system automatically consolidates everything.
Once the planet 🌎 finishes a full rotation (and everyone’s “day” has ended), the data becomes final.
📅 What about surveys, score questions, or check-ins?
Here’s where things differ a bit.
Surveys, score questions, and check-ins don’t depend on each employee’s local time — they follow the company’s time zone, as configured in your Happyforce panel.
This means that:
They can only be answered between the start and end dates set in the admin panel.
These dates are applied according to the company’s time zone (for example, Europe/Madrid).
If an employee is in another time zone (like Mexico or Japan), they can still answer within that time window — but the start and end times are based on the company’s clock, not theirs.
👉 In short:
Happiness Index (How are you?) → follows each person’s local time zone.
Surveys, score questions, and check-ins → follow the company’s configured time zone.
🧠 In summary
Each person can vote once per their local day in the Happiness Index question.
HI votes are stored using the employee’s local date.
Surveys, score questions, and check-ins follow the company’s time zone and schedule.
The dashboard may display votes from different dates, but everything is accurately placed in each person’s real time.
💬 An easy way to picture it
Think of Happyforce as a big 24-hour coffee shop ☕️.
When you’re ordering your morning coffee, someone else somewhere is ordering their last one of the day.
Different times, same experience.
That’s how time zones work in Happyforce:
everyone votes in their own “today” for the Happiness Index,
and surveys or check-ins follow your company’s official schedule.
💡 Simple, fair, and perfectly synced with the world.
Would you like me to create a more formal (corporate) version as well — something you could publish in your Help Center (like Zendesk or Intercom) — keeping this structure but with a cleaner, documentation-style tone?