ActivityLog Contact us
Use cases · Client and project briefings Delivery and change

A briefing on any client or project, ready when you need it

ActivityLog gathers everything that happened for one client or project: who worked on it, the hours, the meetings, what shipped, the documents and what is still open. It drafts a weekly summary from those facts that you can edit and send.

For you

Your weekly report, drafted for you

Pick your week and ActivityLog lists what you did: hours by client, meetings, changes, tickets and documents. Edit the draft and send it to your boss in a couple of minutes.

My weekly summary, drafted from my week

The summary writer for one person and one week: the facts on the left (hours by client, meetings, changes, tickets, documents) and the editable draft on the right, ready to copy or email.

My weekly summary, drafted from my week
For your organisation

A partner update without the chasing

Pick a client or project and see the week in one place: people, hours, meetings, changes and open items. Turn it into a summary for the partner or the business without asking the team for updates.

One client, one week

The client page for Ana Trujillo: people involved, hours, meetings, changes and documents for the week, and the open items still waiting.

One client, one week

A partner update for the client

The summary writer scoped to the client: the same facts written up as a short update you can edit and send to the partner.

A partner update for the client

Where the data comes from

A briefing is built from the activity ActivityLog already collects, tagged with the client or project it belongs to. Nothing extra has to be filled in.

Microsoft 365

What we collect

Meetings and calls with their attendance time, mail sent and received, documents opened and shared. Never message or file content.

How it connects

Read-only Microsoft 365 connection approved once by your admin.

Azure DevOps and the knowledge base

What we collect

Changes, builds and deploys; tickets and the pages people edited.

How it connects

DevOps service hooks and the knowledge-base integration.

HubSpot

What we collect

Deals, stages and logged calls, emails and meetings for the account.

How it connects

A HubSpot private app with read access.

Harvest

What we collect

Submitted time entries per client and project.

How it connects

A Harvest connection with read access to time entries.

How it works

  1. Collect

    Activity flows in from the tools your team already uses.

  2. Tag to the client or project

    Each item is matched to its client or project from the account, the site, the repository or the project rules you set.

  3. Brief

    The client or project page shows the people, hours, meetings, changes, documents and open items for the period you pick.

  4. Write and send

    The summary writer drafts the update from those facts. You edit it, then copy it, download it or email it. An optional AI draft uses the facts only, never message or document content.

Questions

Does the summary read our emails or documents?

No. It is built from counts and names of activity (meetings, changes, tickets, documents touched), not from their content. The optional AI draft gets the same facts and nothing else.

How does activity get matched to a client?

From the customer account and domain, the SharePoint site, the repository and your own project rules. Anything that cannot be matched shows as Unassigned.

Can I change the summary before it goes out?

Yes. The draft is always editable, and nothing is sent until you copy, download or email it yourself.

Built from

  • Microsoft Teams
  • Outlook
  • SharePoint and OneDrive
  • Azure DevOps
  • Knowledge base
  • HubSpot
  • Harvest

See it with your own sources.

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