ActivityLog shows how a team's week splits between meetings, mail, documents and delivery work, from the tools they already use. Spot overload early, without timesheets or surveys.
See how much of your week went to meetings and mail, and which days had no room for real work.
Michael Suyama's headline numbers from My week, with meeting hours set against tracked hours. Meeting hours come from Teams attendance; tracked hours add his document and delivery work. When the two numbers are close, there was little time left for focused work.
Michael's activity per day, stacked by source. Thursday is almost all Teams and Outlook, with no Azure DevOps work: a day with no focus time.
The team's activity by client, compared month by month, shows where focus is shifting before anyone reports it. Meetings, calls, mail and file work by day show when meetings are eating the week. Built for planning, not for ranking people.
The team's activity for the month broken down by client, from Microsoft 365, the knowledge base and Azure DevOps. Run it for this month and last to see which clients are taking more of the team's attention and which are getting less. Activity with no client shows as unassigned.
Headline numbers across the team: active users, Teams meetings, calls, files touched, emails sent and Entra sign-ins, each from the matching Microsoft 365 service. Compare weeks rather than reading one number on its own.
Team activity per day, coloured by service: Teams, Outlook, SharePoint, OneDrive and Entra. A day dominated by Teams is a meeting day; a day dominated by SharePoint is document work.
The picture of a team's week is built from Microsoft 365 and your delivery tools. It counts meetings, calls, mail, files and delivery work. It does not watch screens or count keystrokes.
Meetings and calls with the time each person was actually in them. Not chat or meeting content.
The read-only Microsoft 365 connection, approved once by your Microsoft 365 admin. It reads Microsoft's own audit trail. Call times come from Teams call records.
Mail sent and calendar changes, with times. Never the message body.
The same Microsoft 365 connection.
Files opened, edited, uploaded and shared. File names, never the content.
The same Microsoft 365 connection.
Sign-ins, succeeded and failed.
The same Microsoft 365 connection.
Pull requests, pushes, builds and releases: the delivery side of the week.
Service hooks in your Azure DevOps project send each change to a web address you create in ActivityLog. It arrives within seconds.
Microsoft 365 and Azure DevOps report meetings, calls, mail, files and delivery work. Nothing is installed on anyone's computer.
Each activity is tied to a person by their work email. A second address, such as a login at a partner company, can be added as an alias so it lands on the same person.
Meeting and call hours come from real attendance. Mail, file and delivery activity are counted per person and per day, by service, so you can see how a week split up.
People protect their focus time; managers spot overload early and move work. It is built for planning, not for ranking people.
No screen capture, no keystrokes, no app tracking and no message content. It shows the activity Microsoft 365 and your delivery tools already record about meetings, mail and files. We built it to spot overload and plan work, and we recommend you do not use it to rank people.
Work in tools you have not connected does not show, and neither does time spent thinking, on paper or on calls outside Teams. Low activity is a reason to ask, not a conclusion.
Microsoft 365 activity arrives 30 to 90 minutes after it happens, because that is when Microsoft publishes it. Azure DevOps arrives within seconds.
ActivityLog is in beta. Connect the tools you already use and get this report for your organisation.
See pricing →Questions first? Talk to us → · All use cases
