Calculating Average Meeting Hours per Employee Across Your Entire Google Workspace Org (SQL + Worklytics)

Introduction

Meeting overload is crushing productivity across organizations worldwide. The average executive spends 23 hours a week in meetings, nearly half of which could be cut without impacting productivity. (Worklytics) For HR analysts and workplace insights teams, understanding meeting patterns at scale requires more than anecdotal evidence—it demands data-driven analysis across your entire organization.

Worklytics provides Google Calendar Data Analytics to measure and optimize employee engagement, integrating with Google Calendar data along with over 25 other tools in your tech stack. (Worklytics) By leveraging Worklytics' BigQuery export capabilities, you can calculate rolling 30-day averages of meeting hours per full-time employee (FTE), compare them against industry benchmarks, and surface organizational hotspots using just a 20-line SQL query.

This tutorial demonstrates how to extract actionable insights from Google Calendar data without manual data cleansing, thanks to Worklytics' pre-modeled tables that eliminate the complexity of raw calendar data processing. (Worklytics)

Why Meeting Hours per Employee Matter for HR Analytics

Meeting metrics serve as a critical indicator of organizational health and productivity. Technology is the highest-growing proportion of the HR budget, with most firms planning to increase their investment in HR tools over the next two years. (HR.com's State of Today's HR Tech Stack and Integrations 2024) However, many organizations struggle to achieve business objectives with their HR technology stacks due to challenges with integrating multiple solutions and difficulties with reconfiguring the stack to adapt to changing business needs.

Worklytics can analyze trends and patterns for team meetings and employee collaboration, providing real-time team metrics, customizable dashboards, and actionable insights from your Google Calendar data. (Worklytics) This capability becomes essential when you consider that excessive meeting time correlates with:

Reduced individual productivity: Employees with limited focus time struggle to complete deep work
Meeting fatigue and burnout: Over-scheduled employees report higher stress levels and lower job satisfaction
Inefficient resource allocation: Teams spending disproportionate time in meetings may indicate process inefficiencies
Manager effectiveness issues: Managers who over-schedule meetings often struggle with delegation and prioritization

By calculating average meeting hours per employee, HR teams can identify departments or teams that may benefit from meeting hygiene training, process optimization, or workload rebalancing.

Understanding Worklytics' Google Calendar Integration

Worklytics integrates with Google Calendar to generate actionable analytics from calendar data, enabling businesses to measure and optimize employee engagement. (Worklytics) The platform aggregates and anonymizes data, creating actionable insights and information-rich reports while maintaining privacy compliance with GDPR, CCPA, and other data protection standards. (Worklytics)

The integration captures comprehensive meeting data including:

Meeting duration and frequency: Total time spent in scheduled meetings
Participant counts: Number of attendees per meeting
Meeting types: Recurring vs. ad-hoc meetings, internal vs. external participants
Time distribution: Meeting patterns across days, weeks, and months
Collaboration patterns: Cross-functional meeting participation

Worklytics generates over 400 metrics and provides insights at your fingertips, allowing you to see just how engaged your employees are and how they use the tools available to them. (Worklytics) This comprehensive data collection forms the foundation for calculating meaningful meeting hour averages across your organization.

Setting Up BigQuery Export with Worklytics

Before diving into SQL queries, you need to configure Worklytics to export your Google Calendar data to BigQuery. Worklytics provides a dataset for SQL queries, making it straightforward to access pre-processed meeting data. (Worklytics)

The setup process involves:

1. Configuring the Worklytics connector: Link your Google Workspace to Worklytics with appropriate permissions
2. Setting up BigQuery destination: Create a BigQuery dataset to receive exported meeting data
3. Defining export parameters: Specify date ranges, organizational units, and data granularity
4. Validating data flow: Ensure meeting events are properly captured and anonymized

Once configured, Worklytics automatically exports meeting data to your BigQuery dataset, typically with a 24-48 hour delay to ensure data completeness and privacy processing.

The 20-Line SQL Query for Meeting Hours per Employee

Worklytics' pre-modeled tables eliminate manual cleansing by providing clean, structured data ready for analysis. (Worklytics) Here's the core SQL query to calculate rolling 30-day average meeting hours per employee:

Query Component Purpose Key Fields
Base table Meeting events with participant data meeting_id, duration_minutes, participant_email, date
Employee mapping Link meeting participants to FTE status employee_id, employment_status, department
Date filtering Rolling 30-day window date >= CURRENT_DATE() - 30
Aggregation Sum meeting minutes per employee SUM(duration_minutes), COUNT(DISTINCT employee_id)
Calculation Convert to hours and average SUM(duration_minutes) / 60 / COUNT(DISTINCT employee_id)

The query structure leverages Worklytics' normalized data model, which handles common data quality issues like duplicate events, cancelled meetings, and partial participant lists automatically.

Breaking Down the SQL Logic

Step 1: Filtering Active Employees

The first component identifies active full-time employees within your organization:

WITH active_employees AS (
  SELECT DISTINCT employee_id, department, manager_id
  FROM `your_project.worklytics.employee_roster`
  WHERE employment_status = 'ACTIVE'
    AND employment_type = 'FULL_TIME'
    AND date = CURRENT_DATE()
)

This ensures your calculations only include current FTE staff, excluding contractors, interns, or recently departed employees who might skew averages.

Step 2: Aggregating Meeting Data

Next, the query sums meeting minutes for each employee over the rolling 30-day period:

meeting_hours AS (
  SELECT 
    e.employee_id,
    e.department,
    SUM(m.duration_minutes) / 60.0 AS total_meeting_hours
  FROM active_employees e
  JOIN `your_project.worklytics.meeting_events` m
    ON e.employee_id = m.participant_employee_id
  WHERE m.date >= CURRENT_DATE() - 30
    AND m.meeting_type IN ('SCHEDULED', 'RECURRING')
  GROUP BY e.employee_id, e.department
)

This step handles the core aggregation while filtering out informal or cancelled meetings that shouldn't count toward formal meeting time.

Step 3: Calculating Organizational Averages

Finally, the query computes department-level and organization-wide averages:

SELECT 
  department,
  COUNT(employee_id) as employee_count,
  AVG(total_meeting_hours) as avg_meeting_hours_per_employee,
  PERCENTILE_CONT(total_meeting_hours, 0.5) OVER (PARTITION BY department) as median_meeting_hours,
  MAX(total_meeting_hours) as max_meeting_hours
FROM meeting_hours
GROUP BY department
ORDER BY avg_meeting_hours_per_employee DESC

This provides both averages and distribution metrics to identify outliers and understand meeting hour patterns across different organizational units.

Comparing Against the 23-Hour Executive Benchmark

Manager effectiveness is crucial for team performance, retention, and organizational success, yet traditional measurement methods rely on annual surveys which often deliver outdated insights. (Worklytics) The 23-hour weekly meeting benchmark for executives provides a useful comparison point for your calculated averages.

To incorporate this benchmark into your analysis:

WITH benchmark_comparison AS (
  SELECT 
    department,
    avg_meeting_hours_per_employee,
    CASE 
      WHEN avg_meeting_hours_per_employee > 23 THEN 'Above Executive Benchmark'
      WHEN avg_meeting_hours_per_employee BETWEEN 15 AND 23 THEN 'Within Normal Range'
      WHEN avg_meeting_hours_per_employee < 15 THEN 'Below Average'
    END as benchmark_category,
    (avg_meeting_hours_per_employee / 23.0) * 100 as benchmark_percentage
  FROM department_averages
)

This categorization helps identify departments that may be over-meeting relative to executive-level expectations, suggesting opportunities for meeting optimization.

Identifying Organizational Hotspots

Worklytics can help improve areas like productivity & performance, company culture, employee engagement, remote & hybrid work, meetings & collaboration, and retention & turnover. (Worklytics) By extending your SQL analysis, you can surface specific hotspots that require attention:

High-Meeting Departments

Identify departments with consistently high meeting loads:

SELECT 
  department,
  avg_meeting_hours_per_employee,
  employee_count,
  (avg_meeting_hours_per_employee * employee_count) as total_dept_meeting_hours
FROM department_averages
WHERE avg_meeting_hours_per_employee > 20
ORDER BY total_dept_meeting_hours DESC

Meeting Distribution Patterns

Analyze how meeting time distributes across your organization:

SELECT 
  CASE 
    WHEN total_meeting_hours < 10 THEN 'Low (< 10 hrs/week)'
    WHEN total_meeting_hours BETWEEN 10 AND 20 THEN 'Moderate (10-20 hrs/week)'
    WHEN total_meeting_hours BETWEEN 20 AND 30 THEN 'High (20-30 hrs/week)'
    ELSE 'Excessive (> 30 hrs/week)'
  END as meeting_load_category,
  COUNT(*) as employee_count,
  ROUND(COUNT(*) * 100.0 / SUM(COUNT(*)) OVER (), 2) as percentage
FROM meeting_hours
GROUP BY meeting_load_category
ORDER BY employee_count DESC

This analysis reveals what percentage of your workforce falls into different meeting load categories, helping prioritize intervention strategies.

Visualizing Results in Looker Studio

Worklytics brings siloed data under one digital roof, allowing you to see if Google Calendar is a useful and frequent part of collaboration and meeting processes and workflows. (Worklytics) Once you've calculated meeting hour averages, Looker Studio provides powerful visualization capabilities to make insights actionable.

Key Dashboard Components

Executive Summary Scorecard:

• Organization-wide average meeting hours per employee
• Percentage above/below the 23-hour executive benchmark
• Total meeting hours across all employees
• Month-over-month trend indicators

Department Comparison Chart:

• Horizontal bar chart showing average meeting hours by department
• Color-coded by benchmark categories (green for normal, yellow for elevated, red for excessive)
• Drill-down capability to individual team analysis

Distribution Histogram:

• Employee count by meeting hour ranges
• Overlay showing organization median and benchmark lines
• Interactive filtering by department, role level, or tenure

Trend Analysis:

• Time series showing rolling 30-day averages over the past year
• Seasonal patterns and anomaly detection
• Correlation with business events (product launches, reorganizations, etc.)

Setting Up Automated Reporting

Looker Studio can connect directly to your BigQuery dataset containing Worklytics data, enabling automated dashboard updates as new meeting data flows in. Configure scheduled email reports to deliver weekly or monthly meeting insights to HR leadership, department heads, and executive teams.

Advanced Analytics: Beyond Basic Averages

Worklytics can be used to identify and monitor driving factors that negatively impact employee retention, making meeting analysis part of a broader employee experience strategy. (Worklytics) Consider these advanced analytical approaches:

Meeting Efficiency Scoring

Combine meeting duration with participant counts to calculate efficiency metrics:

SELECT 
  department,
  AVG(duration_minutes * participant_count) as avg_person_minutes_per_meeting,
  AVG(duration_minutes) as avg_meeting_duration,
  AVG(participant_count) as avg_participants_per_meeting
FROM meeting_events
WHERE date >= CURRENT_DATE() - 30
GROUP BY department

Cross-Functional Collaboration Analysis

Measure how much meeting time involves cross-departmental collaboration:

WITH cross_dept_meetings AS (
  SELECT 
    meeting_id,
    COUNT(DISTINCT department) as dept_count
  FROM meeting_participants p
  JOIN employee_roster e ON p.employee_id = e.employee_id
  GROUP BY meeting_id
  HAVING COUNT(DISTINCT department) > 1
)
SELECT 
  department,
  SUM(CASE WHEN cd.meeting_id IS NOT NULL THEN duration_minutes ELSE 0 END) / 60.0 as cross_dept_meeting_hours,
  SUM(duration_minutes) / 60.0 as total_meeting_hours,
  ROUND(SUM(CASE WHEN cd.meeting_id IS NOT NULL THEN duration_minutes ELSE 0 END) * 100.0 / SUM(duration_minutes), 2) as cross_dept_percentage
FROM meeting_events m
LEFT JOIN cross_dept_meetings cd ON m.meeting_id = cd.meeting_id
GROUP BY department

Manager vs. Individual Contributor Patterns

Analyze meeting loads by organizational level:

SELECT 
  CASE 
    WHEN manager_level = 0 THEN 'Individual Contributor'
    WHEN manager_level = 1 THEN 'First-Line Manager'
    WHEN manager_level >= 2 THEN 'Senior Manager+'
  END as role_category,
  AVG(total_meeting_hours) as avg_meeting_hours,
  PERCENTILE_CONT(total_meeting_hours, 0.5) OVER (PARTITION BY manager_level) as median_meeting_hours
FROM meeting_hours h
JOIN employee_roster e ON h.employee_id = e.employee_id
GROUP BY role_category
ORDER BY avg_meeting_hours DESC

Privacy and Compliance Considerations

Worklytics uses a proxy to completely anonymize all data at the source, ensuring that individual employee privacy is protected while still enabling organizational insights. (Worklytics) When implementing meeting hour analysis, consider these privacy best practices:

Data Anonymization

• Aggregate data at department or team levels rather than individual employees
• Use employee IDs rather than names or email addresses in analysis
• Implement minimum group sizes (e.g., 5+ employees) before reporting metrics
• Exclude sensitive meeting types (HR discussions, performance reviews, etc.)

Compliance Requirements

• Document data retention policies for meeting analytics
• Ensure employee consent for workplace analytics where required
• Implement access controls limiting who can view detailed meeting data
• Regular audits of data usage and sharing practices

Ethical Analytics

• Focus on organizational patterns rather than individual performance monitoring
• Use insights to improve processes, not penalize employees
• Transparent communication about what data is collected and how it's used
• Regular review of analytics practices with employee representatives

Actionable Insights and Next Steps

Employee experience is a top priority for many organizations, with many hoping that additional training and the introduction of AI and automation innovations will enhance the end-user experience. (HR.com's State of Today's HR Tech Stack and Integrations 2024) Once you've calculated average meeting hours per employee, the real value comes from taking action on the insights.

Immediate Actions for High-Meeting Departments

Meeting Audit Process:

1. Review recurring meetings for continued relevance
2. Implement "meeting-free" time blocks for focused work
3. Establish default meeting durations (25 or 50 minutes instead of 30 or 60)
4. Require agenda and objectives for all meetings over 30 minutes

Process Optimization:

• Replace status update meetings with asynchronous updates
• Implement decision-making frameworks to reduce discussion meetings
• Train managers on effective meeting facilitation
• Create templates for common meeting types

Long-term Organizational Changes

Culture Shifts:

• Establish "meeting hygiene" as a core productivity skill
• Recognize and reward teams that optimize their meeting practices
• Include meeting efficiency in manager effectiveness evaluations
• Create cross-functional working groups to address collaboration inefficiencies

Technology Solutions:

• Implement meeting scheduling tools with automatic optimization
• Deploy AI-powered meeting assistants for note-taking and action items
• Use calendar analytics to suggest optimal meeting times
• Integrate meeting data with project management tools for better resource allocation

Measuring Success and Continuous Improvement

Worklytics helps streamline and optimize meetings, track productivity and performance metrics, analyze diversity, equity, and inclusion, assess management and leadership metrics, and get insight into employee satisfaction, retention, and turnover. (Worklytics) Establish key performance indicators (KPIs) to track the success of your meeting optimization efforts:

Primary Metrics

Average meeting hours per employee: Target reduction of 10-15% over 6 months
Meeting efficiency score: Ratio of decision meetings to information-sharing meetings
Focus time availability: Hours per week without scheduled meetings
Cross-functional collaboration quality: Meaningful inter-department meeting participation

Secondary Indicators

Employee satisfaction scores: Survey responses about meeting effectiveness
Project delivery timelines: Correlation between meeting optimization and project completion
Manager effectiveness ratings: Improvement in leadership assessment scores
Retention rates: Impact of meeting culture on employee turnover

Quarterly Review Process

1. Data Analysis: Run updated SQL queries to measure progress
2. Stakeholder Feedback: Gather input from department heads and team leads
3. Process Refinement: Adjust meeting policies based on results
4. Communication: Share success stories and lessons learned organization-wide

Conclusion

Calculating average meeting hours per employee across your Google Workspace organization doesn't have to be a complex, manual process. Worklytics' BigQuery export capabilities combined with pre-modeled data tables enable HR analysts to generate comprehensive meeting insights with just a 20-line SQL query. (Worklytics)

By leveraging the 23-hour executive benchmark and surfacing organizational hotspots through Looker Studio visualizations, you can transform raw calendar data into actionable insights that drive meaningful workplace improvements. The key is moving beyond simple averages to understand meeting patterns, efficiency metrics, and the relationship between collaboration time and organizational outcomes.

Worklytics generates and pushes over 400 metrics to you, providing the comprehensive data foundation needed for sophisticated workplace analytics. (Worklytics) As organizations continue to evolve their hybrid work practices and optimize for productivity, meeting hour analysis becomes an essential tool for HR teams focused on creating better employee experiences while maintaining operational effectiveness.

Start with the basic SQL query outlined in this tutorial, then gradually expand your analysis to include efficiency scoring, cross-functional collaboration patterns, and correlation with business outcomes. Remember that the goal isn't to minimize meetings entirely, but to ensure that the time your employees spend in meetings drives real value for both individuals and the organization as a whole.

Frequently Asked Questions

How can I calculate average meeting hours per employee using Worklytics and SQL?

You can use Worklytics' BigQuery export feature with a simple 20-line SQL query to calculate rolling 30-day average meeting hours per employee. The query aggregates Google Calendar data across your entire Google Workspace organization, providing insights into meeting patterns and productivity metrics.

What is the average number of meeting hours executives spend per week?

According to Worklytics research, the average executive spends 23 hours a week in meetings. Nearly half of these meetings could be cut without impacting productivity, highlighting the significant opportunity for organizations to optimize their meeting culture and improve workplace efficiency.

How does Worklytics integrate with Google Calendar for meeting analytics?

Worklytics seamlessly integrates with Google Calendar to provide actionable analytics for businesses while maintaining privacy. The platform can analyze trends and patterns for team meetings and employee collaboration, and integrate Google Calendar data with over 25 other tools in your tech stack for comprehensive insights.

Can I get sample SQL queries for analyzing meeting data in Worklytics?

Yes, Worklytics provides sample SQL queries for event-level data analysis in their knowledge base documentation. These queries help you extract meaningful insights from your Google Workspace meeting data, including calculating average meeting hours, attendance patterns, and collaboration metrics across your organization.

What privacy protections does Worklytics offer when analyzing meeting data?

Worklytics is built with privacy and security as core principles, using a proxy system to completely anonymize all data at the source. The platform aggregates and anonymizes employee work data to create actionable insights while ensuring individual privacy is protected throughout the analytics process.

How can meeting analytics help identify productivity issues in my organization?

Meeting analytics can reveal patterns of meeting overload that crush productivity across organizations. By analyzing metrics like average meeting hours per employee, meeting frequency, and collaboration patterns, you can identify teams or individuals spending excessive time in meetings and implement targeted interventions to optimize workplace efficiency.

Sources

1. https://docs.worklytics.co/knowledge-base/data-dictionary/getting-started/sample-sql-queries-aggregate-level-data-and-collab.-graph
2. https://docs.worklytics.co/knowledge-base/data-dictionary/getting-started/sample-sql-queries-event-level-data
3. https://eightfold.ai/wp-content/uploads/State-of-Todays-HR-Tech-Stack-and-Integrations-2024-Research-Report.pdf
4. https://worklytics.co/privacy
5. https://worklytics.co/resources/manager-effectiveness-score-google-workspace-data-no-surveys
6. https://www.worklytics.co/integrations/google-calendar-data-analytics
7. https://www.worklytics.co/integrations/google-meet-analytics