orbit-team-workload

You can visualize team workload by fetching live team structures from Notion and cross-referencing them with Orbit workload data. This process aggregates open tasks, overdue items, and estimated hours per member to generate a dashboard showing individual capacity signals and potential bottlenecks.

Identifying overloaded team members is done by aggregating open tasks, overdue items, and estimated hours per person from Orbit. The system cross-references this workload data with your live Notion team structure to clearly indicate whether each individual is overloaded, busy, or available.

Yes, fetching the specific Notion page ID `2e63846840c880e0a084f983351d943c` is required to retrieve the live matrix team structure. This page provides the foundational team composition data needed to cross-reference individual workload metrics from Orbit.

Orbit workload data integrates by using Orbit MCP to pull per-member task metrics, which are then mapped against the live team structure fetched from Notion. This integration visualizes project distribution across the team and highlights overall capacity constraints.

You can check real-time team bandwidth by generating a detailed dashboard that aggregates current tasks and capacity signals. By syncing live Notion team structures with Orbit workload data, it clearly indicates if members are available, busy, or overloaded at that moment.