Remote work disputes: logging hours, availability and time zones

When a remote or hybrid job turns into a disagreement about whether you were available, responsive or working enough hours, the most useful record is a short daily log written the same day: when you started and stopped, breaks, what you worked on, and any message or meeting that fell outside your usual hours. Write the time zone next to every single time, because remote teams often see the same moment as three different clock readings.

Back the log with copies of what you already have: calendar invites, the messages you sent and received, schedule announcements and any written arrangement about your hours or location. Keep it neutral. The goal is a clear picture a reviewer can follow, not an argument about who was right.

Remote disagreements rarely start with a formal meeting. They tend to start with a passing comment that you seemed to be away a lot, a reply that came later than someone expected, or a manager in another city who assumes your day starts when theirs does. By the time it reaches a performance conversation, nobody remembers the specific mornings involved.

• A chat or collaboration tool shows you as away or idle while you were on a call, reading a long document or working offline.
• A message sent late in the sender's evening lands early in your morning, or the reverse, and the response time is described as slow.
• Core hours, on-call expectations or a coverage rota change, and the change is announced verbally or in a meeting rather than in writing.
• A return-to-office plan sets a number of in-person days, and attendance counts are later disputed.
• Your timesheet or reported hours are questioned weeks after the fact.
• Evening or weekend messages become routine, and later there is disagreement about whether answering them was expected.

The single habit that prevents the most confusion is writing the zone after every time. Not just once at the top of the page, but on each line: 08:52 ET, 13:10 PT, 17:45 MT. If your team spans countries, adding the UTC offset (08:52 ET, UTC-5) removes any doubt about daylight saving changes, which do not happen on the same date everywhere and are not observed in every province, territory or state.

Pick your own local zone as the default for your log, because that is the clock you live by, and note any other zone only when it matters, for example when you quote a timestamp exactly as it appears in a colleague's screenshot. Many tools display times in the viewer's zone, so a message you sent at 08:52 ET appears as 05:52 to someone in Vancouver or Los Angeles. When you copy a time from someone else's view, say so.

Travel deserves its own line. If you worked a week from another city, write the date you moved, the zone you were in, and whether you kept your home schedule or shifted to local hours. Mixed weeks are where most later misunderstandings hide.

1. Write the date and your location for the day: home, office, client site or travel, with the zone.
2. Note your start time, meal break, any other breaks and your stop time, as you actually worked them rather than as scheduled.
3. List the main tasks or deliverables in a few words each, so the hours have context.
4. Record any request, message or meeting outside your usual hours: who sent it by role, the time with zone, and what you did in response.
5. Note anything that affected availability: a connection outage, a system login problem, an approved appointment, a call that ran long.
6. Save or reference the supporting item, such as the invite or message, and give it a short ID so the log line points to it.
7. Close the entry and do not rewrite it later. If something needs correcting, add a dated note underneath.

Five minutes a day is enough. A log that is short and consistent is far more readable, and more believable to a reader, than long entries written in bursts when things feel tense.

A green, yellow or grey dot is a weak signal on its own. Status indicators often switch to away after a few idle minutes, stay away while you are on a phone call, or fail to update after a laptop sleeps. If your availability is being judged by status, a screenshot of the dot alone tells a reader very little.

• Capture the full screen so the system clock and date are visible, and write the zone in your log next to the screenshot ID.
• Note what you were doing at that moment, for example a client call on another platform or focused writing in a document.
• If the tool has a setting for idle timeout or automatic status, note what it is set to on your account.
• Keep the screenshot of your own status or your own messages; avoid capturing private conversations you are not part of.
• Follow your employer's rules on copying internal systems. Where screenshots of internal tools are restricted, write a dated description instead.

Your calendar is often the cleanest independent record of a remote workday. Invites show the organizer, the time the meeting was booked, the time it was scheduled for and any later changes. When a meeting is moved at short notice into your early morning or late evening, keep the updated invite and note the time zone it was sent from.

For after-hours messages, record the pattern rather than reacting to each one. A simple weekly tally works: how many messages arrived outside your agreed hours, from which roles, and how many asked for a response before the next workday. That gives a reviewer a factual picture without you having to characterize anyone's intentions.

Rules on hours of work, overtime and rest periods differ by province, territory and state, and some employers have written policies about disconnecting outside work hours. Keep a copy of any policy you were given, with the date you received it, rather than trying to interpret it in your log.

Here is what three neutral entries can look like. Notice that each one gives times with zones, refers to supporting records by ID, and describes events without adjectives about anyone.

• Tue 2026-03-03, home, ET (UTC-5). Start 08:45 ET. Lunch 12:15 to 12:45 ET. Stop 17:20 ET. Tasks: quarterly report draft, two client calls. Status showed away 10:05 to 10:50 ET while on client call by phone (calendar invite R-014).
• Tue 2026-03-03, 21:40 ET: message from team lead (in PT, sent 18:40 PT) asking for figures by 08:00 ET. Replied 07:35 ET Wednesday with figures attached (message copy R-015).
• Thu 2026-03-05, office, ET. Badge-in not recorded at front entrance; signed visitor log at 09:02 ET at reception's request. Noted for attendance count (photo of my own visitor pass R-016).

If your remote or hybrid setup was ever agreed in writing, find that record first: an offer letter, an email approving a work-from-home arrangement, a policy acknowledgement or a schedule you signed. Then keep the announcement of any change, the date it takes effect, and any questions you asked about it along with the replies.

Where the reason for working remotely relates to health, disability or family obligations, keep your request and the employer's response as separate dated records. In Canada this is often discussed as the duty to accommodate, and in the United States the ADA describes an interactive process; both are general frameworks and how they apply depends on your situation, so this is a point to raise with a qualified reviewer rather than to settle in your notes.

For in-person days, a quiet personal tally helps: date, arrival and departure times with zone, and how you can show you were there, such as a meeting invite for an in-room session. Rely on records you were given or created yourself; do not try to obtain building access logs or attendance reports you have no right to see.

• Days where you have no log entry, and whether your calendar or sent messages can fill them.
• Verbal changes to your hours or on-call duties that were never confirmed in writing.
• Which policy version applied on a given date, if the remote or attendance policy was updated.
• Whether your role is treated as hourly or salaried, and where that is stated, as a question rather than a conclusion.
• Any period where you worked from a different time zone and how your hours were reported then.

For general background, the Government of Canada publishes an hours of work page for federally regulated workplaces, which covers standard hours, overtime, breaks and schedule notice; most employees fall under provincial or territorial rules instead. The US Department of Labor has a fact sheet on hours worked that explains how federal wage law treats on-call time, short breaks and work done outside a scheduled shift.

Should I use my employer's time-tracking tool or my own log? Use whatever your employer requires for official reporting, and keep your personal log alongside it. Your own notes add context the official tool may not capture, such as why a status showed away or when an after-hours request arrived.

Can I start logging after a problem has already been raised? Yes. Start today, and reconstruct earlier weeks separately from your calendar, sent folder and saved invites, labelling those entries as reconstructed with the date you wrote them.

Is it fine to keep the log on a work laptop? A personal device you control is usually safer for personal notes, since work accounts can be suspended without warning. Keep copies only of items you are allowed to keep, and avoid moving confidential business information onto personal devices.

What if my manager and I are in different time zones and disagree on what 9 o'clock means? Write down the arrangement as you understand it, with zones, and ask for written confirmation. Keep the question and the reply in your file.

Everything above works in a notebook or a spreadsheet. If you want a tool built for it, SteadyFile lets you start a private work file in your browser at app.steadyfile.com, on your phone or computer, with no account needed to begin. Each dated entry has room for where you were, who was involved by role, what was said and which records it links to, so an after-hours message or a moved meeting can be tied to its invite or screenshot ID. The records index, people list and gaps list mirror the sections of this guide. With an account, each entry shows when it was created and keeps its edit history visible. When you need a second opinion, export a chronological packet a reviewer can read in a few minutes. Your employer has no access to the file.