Signals & Briefings

What is a signal?

A signal is an automatically detected pattern that surfaces something worth exploring with a team member. Signals are derived from messaging activity (Slack or Teams), calendar data, code contributions (GitHub, GitLab, Azure DevOps), and AI tooling behaviour when connected.

Examples include a shift in messaging pace, a heavy meeting week, after-hours commits, a step-up in code output, or increased activity in help-style channels.

How are severities determined?

Severities reflect how far a pattern sits from that person’s personal baseline:

• High — The pattern is clearly outside normal behaviour; worth a direct conversation when it fits the context.
• Medium — A notable change worth watching or raising lightly in a 1:1.
• Low — A mild deviation; it may or may not be meaningful depending on what else you know.

What is a briefing?

A briefing is an AI-generated document that helps you prepare for a 1:1. It summarises recent signals and activity patterns and suggests thoughtful questions. Briefings are generated in the context of your upcoming meetings and remain available to review anytime.

How does TeamPlot find my 1:1 meetings?

TeamPlot reads your connected calendar and looks for recurring 1:1-style events with people on your team. Team members should have a calendar email set so meetings can be matched correctly.

Dismissing signals

Signal dismissal is on the roadmap. Today, signals older than fourteen days roll off the dashboard automatically. If a signal is not relevant, you can note it in the briefing agenda for your own reference.