# Meetings Breakdown The Meetings Breakdown feature provides an overview of your team's meeting schedules, helping you identify if they're overwhelmed by excessive long meetings.

This feature can be accessed while creating a new custom dashboard or by navigating to the custom dashboards page -> selecting any metric -> "Meetings Breakdown" from the dropdown.

*Adding the metric as part of new dashboard creation*

#### The total time spent is broken down into the following categories of meetings: 1\. **Deep** - If the gap between two meetings is more than 2 hours, it's considered Deep work. This allows developers to focus on their tasks without interruption. *Ideally majority of the developers' time should be in this category.* 2\. **Shallow** - When the gap between two meetings is less than 2 hours, it's classified as Shallow work, as frequent meetings require context switching. 3\. **Private** - All meetings marked as Private in Google Calendar or personal time blocks fall under this category. 4\. **Team** - These are meetings with three or more people from the same organization. 5\. **External** - Meetings that include at least one person from outside the organization. 6\. **One\_On\_One** - Meetings involving just two people from the same organization.
You can filter this data based on specific teams and dates to gain the insights you need.
If google calendar is not integrated with Hivel yet, please follow the steps mentioned [here](https://hivel.zendesk.com/hc/en-in/articles/19341040186909-How-to-integrate-Google-Calendar-in-Hivel). If you encounter any issues or have further questions, feel free to contact us at . --- # Agent Instructions: 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://docs.hivel.ai/using-hivel/cockpit/meetings-breakdown.md?ask= ``` 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.