Dates and times in BEHCA can sometimes look "wrong" — an entry shows up on the day before, or a chart bar is on a Monday when you logged it Tuesday. Almost always, this is timezone-related.
How BEHCA handles timezones
BEHCA stores all dates and times in UTC internally, but displays them in the profile's timezone. The profile's timezone is set by the profile's location.
This means:
-
A behavior at 11pm Sydney time is on the Sydney calendar day, not the UTC date.
-
If you live in Perth and your client lives in Sydney, the client's daily logs read in Sydney time — not your local time.
-
Charts and reports use the profile's timezone for "what day was this on?" decisions.
"My entry is on the wrong day"
The most common cause is logging late at night in a different timezone:
-
You're in California and logged at 11pm your time.
-
Your client is in New York. 11pm California = 2am NYC the next day.
-
The entry appears on the NYC date, which is one day after your local date.
Fix: This is correct behavior — the entry's "day" is the profile's day. If it bothers you, log earlier in the day.
"The chart shows nothing on a day I know we logged"
Two possibilities:
-
Wrong profile selected. Confirm you're looking at the right person's dashboard.
-
Entries are technically on a different day due to timezone (see above).
"I'm in Australia but dates show in US format"
Date format (MM/DD/YYYY vs DD/MM/YYYY) is a personal preference, not a region setting:
-
Web: Account Settings → Date Format.
-
Mobile: Account → Date Format.
Pick the format you prefer. It applies wherever you see dates.
"Time format is wrong (12-hour vs 24-hour)"
Same area:
-
Time Format preference.
-
12-hour (AM/PM) or 24-hour.
Independent of date format and region.
"EVV visit is on the wrong date"
EVV visits use the profile's timezone to determine which date they belong to. So:
-
A visit ending at 11pm in the client's local timezone is on that day.
-
A visit ending at 1am in the client's local timezone is on the next day.
If your billing summary or hours report seems "wrong", check whether you're looking at the data in the right timezone. Most reports respect the profile's timezone.
"I logged in Sydney at 9am but the entry says 6pm"
You logged with the profile's timezone matching your local time, but the timezone shown is UTC somewhere in the display. This is a display issue, not a data issue:
-
BEHCA stores in UTC, displays in profile timezone.
-
If a screen is showing UTC instead of profile time, it's a display bug. Refresh the page.
-
If it persists, contact support with a screenshot.
"Daylight saving time (DST) just started/ended and times look weird"
BEHCA respects DST automatically:
-
Entries from before the DST change keep their original times.
-
Entries from after the change use the new offset.
-
Schedules (MAR, EVV) automatically shift with DST so "8am" stays at 8am local.
If you see a one-hour gap in a chart at the time of DST change, that's expected — the clocks shifted forward.
"Profile traveled — should I change the timezone?"
If a profile temporarily travels to a different timezone (holiday, hospital stay):
-
Don't change the location for a short trip. The home timezone is still the right "home" for daily logging.
-
Change the location if they've moved permanently. This shifts the timezone for all future entries.
For EVV staff traveling with clients, talk to your Manager about your organization's policy.
"Different staff see different times for the same entry"
If two team members are in different timezones, they each see times in the profile's timezone, which is the same for both. So they should agree.
If they don't agree:
-
Check that they're actually looking at the same entry (entry IDs help).
-
Check their date format / time format preferences (cosmetic difference, not an actual time difference).
When to escalate
If a date or time genuinely seems wrong (not just a confusing display):
-
Note the entry (when you logged it, what time, what profile).
-
Note the issue (what time/date is shown vs. what should be).
-
Contact support.