Update file asynchronous.md

## Q: When are live doc meetings held?

Live doc meetings are usually held in the host's time zone. However, leaders should [rotate meetings to accommodate a more diverse array of time zones](asynchronous/#minimize-time-zone-bias) as well as record them so that others can watch at a later time.

Live doc meetings are usually held in the host's time zone. However, leaders should [rotate meetings to accommodate a more diverse array of time zones](/handbook/company/culture/all-remote/asynchronous/#how-does-asynchronous-communication-work) as well as record them so that others can watch at a later time.

## Q: Where are live doc meetings held?

Whether you're communicating with a coworker or someone external to the company, it's helpful to be transparent about the boundaries you've set for your mental health, well-being, and life outside of work. This is especially impactful for managers and leaders, because it normalizes the conversation around mental health and sets an example for others on the team.

If you're invited to a sync meeting that you can [contribute to asynchronously](asynchronous/#how-to-decline-meetings-in-favor-of-async), this can be as simple as one line added to an email response. Here's an example from [Darren M.](https://gitlab.com/dmurph), GitLab's [Head of Remote](/handbook/company/culture/all-remote/):

If you're invited to a sync meeting that you can [contribute to asynchronously](/handbook/company/culture/all-remote/asynchronous/#gitlab-experts-advise-on-when-to-use-sync-vs-async), this can be as simple as one line added to an email response. Here's an example from [Darren M.](https://gitlab.com/dmurph), GitLab's [Head of Remote](/handbook/company/culture/all-remote/):

> "I'm intentionally limiting my sync sessions in 2021 to [prioritize well-being and family](/handbook/values/#family-and-friends-first-work-second). Thanks for understanding."

For onboarding, we're able to direct new hires to a huge repository of information and also teaching them to be self-sufficient and proactive when looking for answers. Because we've implemented a [handbook-first approach](handbook-first/#make-handbook-first-a-value), the GitLab handbook is always changing and growing as we learn new things.

In an all-remote setting where team members are possibly working from a variety of timezones, mastering [asynchronous workflows](asynchronous/#how-to-implement-asynchronous-workflows) is vital to avoiding dysfunction. Onboarding through documentation is more efficient because it's scalable, repeatable, and instills the basics of asynchronous work.

In an all-remote setting where team members are possibly working from a variety of timezones, mastering [asynchronous workflows](/handbook/company/culture/all-remote/asynchronous/) is vital to avoiding dysfunction. Onboarding through documentation is more efficient because it's scalable, repeatable, and instills the basics of asynchronous work.

**Additional resources:**

### 3. Is most communication about work done asynchronously?

There are [valid reasons](asynchronous/#best-practices-guidelines-and-async-feature-set) to work synchronously. Communicating *about work* is best done asynchronously. This includes status updates, FYIs, process documentation (e.g. how to [alert your security team about a suspected phishing attempt](/handbook/security/security-assurance/governance/phishing/#what-to-do-if-you-suspect-an-email-is-a-phishing-attack)). It also includes *meeting about a meeting*.

There are [valid reasons](/handbook/company/culture/all-remote/asynchronous/#gitlab-experts-advise-on-when-to-use-sync-vs-async) to work synchronously. Communicating *about work* is best done asynchronously. This includes status updates, FYIs, process documentation (e.g. how to [alert your security team about a suspected phishing attempt](/handbook/security/security-assurance/governance/phishing/#what-to-do-if-you-suspect-an-email-is-a-phishing-attack)). It also includes *meeting about a meeting*.

Prerequisites for this to work well are below.