> For the complete documentation index, see [llms.txt](https://playbooks.equalexperts.com/remote-working/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://playbooks.equalexperts.com/remote-working/office-hours.md).

# Office Hours

Be respectful of different time zones and try to schedule calls that are inside of everyone’s working hours when possible. Use tools like <https://everytimezone.com/> to find a convenient time for everyone, and enable Secondary Time Zone in Google Calendar settings to see other regions’ times from within your calendar.

![](/files/-M5Wgo4m0J0LLYlnsdoD)

**‌**Publicise what the team's collectively overlapping core hours are. Don't forget about daylight saving different public holidays and working weeks.

Use this time wisely. Things that you need to do as a group do in the overlapping time, things you can do without the group do when it isn't. Oh, and try and avoid booking meetings with teammates that are outside their core hours.

Maintain core hours for your timezone, so at least people will know when they can expect you to be available. Unfortunately, due to time zones, not everyone can be present in core hours, so if you have an important discussion with a stakeholder or client, then record the conversation on zoom. That way, all team members can gain context when they get into work.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://playbooks.equalexperts.com/remote-working/office-hours.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
