Counts and connections from the tools your teams already use. Understand collaboration, engineering flow, 1:1 habits and AI adoption, then bring that evidence into reviews, 1:1s and the weekly rhythm.
Never the content of anyone’s messages, code or prompts.
Who works with whom across the organisation
Connect what your teams work in. Accounts link by work email, with name matching and self-linking for the rest. Calendar and Cara activity needs no extra setup.
Meetings, meeting time and who meets whom
From connected calendarsPull requests opened and merged, reviews given, time to merge
Read-only app · 90-day backfillIssues completed and comments
Never titles or descriptionsIssues completed and comments
Never titles or descriptionsMessages sent, thread replies, mentions and reactions
Channels October is added toMessages, calls and channel replies
Microsoft 365 usage reportsDeals won, tickets closed, calls and meetings logged
Never amounts, contacts or notesActive days, messages, Codex threads and seats
Enterprise API or CSV uploadMessages, Claude Code sessions, commits and pull requests
Enterprise analytics or Console keyDays using October’s assistant
Built in · no setupOrg charts show who reports to whom. Work Insights shows who works with whom, where work waits and where help is needed. Admins see the whole organisation; managers see their own reporting line.
Who works with whom across the organisation
Illustrative product views · Northstar is an example organisation
Work Insights doesn’t ask anyone to fill anything in. The same signal shows up where it helps: in reviews, 1:1s, the Friday wrap, onboarding and Cara.
A Work tab brings pull requests, reviews, issues, deals and tickets into the review. The employee sees it first; reviewers see it after the self-review is in.
Catch me up. Tom merged 9 pull requests since your last 1:1, including the billing retry work, and reviewed 34 for others.
“Catch me up” cites what shipped. The agenda can suggest a neutral workload or collaboration check-in, plus follow-ups people mentioned in public channels.
Here’s what Platform shipped this week, Alex.
Two suggested wins are waiting for the team.
Managers get what their team shipped this week, counted rather than described. No repository names, no PR numbers, no content.
Work signals flag after-hours spikes, heavy review load and people who have gone quiet, measured against each person’s own usual rhythm.
Everyone gets a work rhythm on their dashboard: meetings against a usual week, time outside working hours and wins waiting to be claimed.
How long do our pull requests wait for review?
Median 4.2 hours to first review this quarter, down from 6.8. Platform waits longest. Two reviewers carry 41% of the load, so sharing reviews would help most.
Cara answers questions about collaboration, engineering flow and AI adoption, scoped to what each person is allowed to see.
Optional conversation insights pick up what people said they would do, what’s waiting on them and what they finished. Text is deleted within 24 hours.
Not an input to the probation decision.
Track connection at 30, 60 and 90 days, plus collaboration footprints for succession, buddy and mentor suggestions that skip anyone already stretched.
Each employee has their own Work data page: the activity collected about them, who they worked with and the accounts it’s linked to. Nothing is hidden from the person it describes.
What Work Insights collects about you, and the accounts it is linked to
An analytics admin switches collection on. Nothing is gathered before then, and it can be paused at any time.
Turn off individual view and reports show team totals only. Groups under three people are hidden.
Daily totals are deleted after 13 months by default. Erase one person’s data or everything, whenever you need to.
After-hours is only measured from the moment collection starts, and always against each person’s own working hours.
Optional conversation insights reads public channels only, holds text encrypted for 24 hours at most and filters sensitive topics.
No leaderboards, no lines of code, no keystrokes. Never used for ratings, calibration, pay or employee relations.
Explore the detail behind Work Insights.
No. It keeps counts and connections: who worked with whom, and how often. Message, email, code, pull request, prompt and document content is never stored. Optional conversation insights reads public channels to pick up follow-ups and deletes the text within 24 hours.
Everyone sees their own data under Profile → Work data. Managers see their reporting line, and analytics admins see the organisation. You can switch individual view off so reports show team totals only, with groups under three people hidden.
No ratings are generated from it. Counts can inform the conversation in a review or 1:1, and AI drafts never use them for ratings. Conversation insights and team tone are never used for ratings, calibration, pay or employee relations.
Calendars, GitHub, Linear, Jira Cloud, Slack, Microsoft Teams, HubSpot, ChatGPT and Codex, Claude and Claude Code, plus October’s own assistant, Cara. Each tool is optional.
Daily totals are kept for 13 months by default, then deleted. Admins can shorten retention, erase a person’s data on request or delete everything collected.
Work Insights is part of Advanced Analytics in October People. It stays off until an analytics admin turns it on, and nothing is collected before then.
We’ll connect a few of your tools in a walkthrough and show what Work Insights brings into reviews, 1:1s and the weekly rhythm.