Field notes · 2026-03-04
Handing over exports safely for a usage report
A checklist for preparing application usage extracts before an external reporting engagement begins.
Most delays in account usage reporting come from incomplete hand-offs, not from analysis itself. A clean export shortens the cycle and protects both parties.
Strip fields you do not need for the agreed metrics. Personally identifying columns beyond an account ID and role label are rarely required for aggregate usage reporting.
Document the time zone, the exact start and end timestamps, and whether weekends are included. Those details prevent false ‘drops’ when someone later re-runs a query.
Transfer via your approved channel—encrypted share, secure portal, or courier of physical media if your policy requires it. Confirm deletion or return of working copies when the engagement closes, as set out in your agreement.