Last sync: 4 min ago·GitLab ·Jira ·Sentry ·Microsoft 365 All sources healthy
Intelligence advisor Beta
Multi-turn conversation with your team's AI intelligence engine. Ask about risks, patterns, or specific people.
Start with a question, or pick one below:
Who on the team needs the most attention this week?Is Sara's overload a new pattern or has it happened before?Who is on leave and how does that affect team capacity?Show me the workload distribution across the team.
Ask the intelligence engine
Grounded in May 17 – May 30 operational window · 8 people · 3 active detections · 1 on approved leave
TeamEye AI · operational analysis
You
Who on the team needs the most attention this week, and why?
Intelligence advisor
● High confidence· Git · Jira · leave data · 12-week history
Two people need your attention right now.
Sara Jensen is the highest priority. She's been sustaining output at 4.2× her personal baseline for 9 of the last 14 days, including weekend pushes in three of the last four weeks. This pattern is consistent with early overload risk indicators. The longer it continues without intervention, the higher the risk of a hard stop — either sick leave or reduced capacity. I'd recommend a 1:1 this week focused on workload, not delivery status.
Alex Kim shows a rhythm break — output dropped 42% vs his personal baseline. MR reviews fell from 11 to 3. No external trigger (no leave, no public holidays) explains the drop. Worth a direct check-in to rule out a blocker or personal situation.
Marcus Chen is on approved vacation (May 26 – Jun 2, synced from Microsoft 365). His inactivity is expected and no alerts are active for him. He returns on June 3.
Suggested actions
Schedule a 1:1 with Sara this week — focus on workload sustainability, not delivery
Check in with Alex Kim directly — ask if there's a blocker or if support is needed
No action needed for Marcus Chen — on approved vacation until Jun 3
You
Is Sara's overload a recent thing or has she had this pattern before?
Intelligence advisor
● High confidence· 12-week Git history · baseline model
This is the first sustained overload pattern in Sara's 12-week history. Her baseline for the previous 10 weeks was steady — activity level between 55 and 65, consistent active days (4–5 per week), no weekend activity.
The current spike started approximately 16 days ago and has been sustained rather than a single-week anomaly. That makes it more concerning — a two-week crunch is survivable, but a pattern that extends beyond three weeks tends to have lasting effects on output quality and long-term team health.
Suggested actions
Schedule a 1:1 with Sara before the end of this week — ask what's driving the pace
Review sprint backlog: is Sara absorbing work that could be redistributed?
If the pattern continues into next week, consider flagging to the team lead
Answers are grounded in your team's GitLab activity data and approved leave schedule. Absence-aware — no alerts during approved leave.
1
Plain language answers — No dashboards to interpret. Ask in natural language and get a direct answer with context — the same way you'd ask a colleague who had read all the data.
2
Leave-aware answers — The AI knows who is on approved leave and factors that into every answer. It will never flag a team member as "silent" or "disengaged" when they have approved absence in the system. When you ask about Marcus, you get the correct context: he's on vacation, not disengaged.
You've seen how TeamEye works.
Book a live demo and see it running on your actual GitLab data — setup takes 5 minutes.