← Cowork Billing hub

Cowork Usage Tracker

Copilot Cowork exports are point-in-time snapshots — there is no history or trend API. Upload your exports over time and this tool reconstructs the missing time series: per-user and per-department usage deltas, trends and a grounded forecast. 100% in your browser.

All processing happens locally. Your files never leave your device. No uploads, no servers, no telemetry. Checkpoints are stored in this browser only.

1 Choose your export period

The Cowork export never records the date range it covers, so the same “credits used” number means different things. Tell us which period your export represents — this grounds every calculation, table and forecast. Required.

Trends only compare checkpoints of the same period type. Keep one history per type — don’t mix Month-to-Date with Last-Month numbers, or the projection breaks.

2 Load an export & save a checkpoint Tracking:

Drop the Copilot credit CSV here or click to browse

No file selected

Drop Entra CSV files here or click to browse (multiple allowed)

No file selected

The date this snapshot represents. Defaults to today; set it to the day you pulled the export.
A friendly name. Leave blank to auto-name from the as-of date.

After loading the demo, scroll down ↓ to Checkpoint history, then click View trends & forecast.

Checkpoint history

Stored in this browser (IndexedDB). Export a bundle to back up or share within your tenant — it still runs 100% offline on import.

Two or more checkpoints of the same period type unlock department roll-ups, run-rate forecasting and a pool-exhaustion projection.

Where do I get these files?

  1. Copilot credit export — in the Microsoft 365 admin center, open Copilot → Cost management → Consumption and Export CSV. Pull this on a regular cadence (e.g. weekly) — each export becomes a checkpoint.
  2. Entra user export(s) — in the Microsoft Entra admin center, open Identity → Users → All users and choose Download users. This carries Department, Cost Center, Job title and more, used to roll usage up by org. It rarely changes, so you can reuse one export across checkpoints.