Write down the decision first
Choose the workflow and decision the pilot should support. For a fleet, that could be whether every reported defect receives an owner and a verified resolution. For a hotel, it could be whether room readiness is checked after linked repairs close. Select one primary outcome and record its definition before collecting results.
Record a baseline and eligible population
List the sites, assets, users and dates included. Count the work that actually qualifies for the measure. For on-time completion, define which due dates are used and how cancelled, rescheduled and still-open jobs are handled. Preserve source exports so someone else can reconstruct the numerator and denominator.
Separate adoption from outcomes
A signup is not activation, and an opened page is not completed work. Track the first actual asset, approved procedure, scheduled task and completed work record. Then inspect repeat use. Operational changes such as fewer missed tasks should be measured separately from software usage. Seasonal demand, staffing and changes in asset mix can explain apparent improvements.
Publish evidence with consent and limits
A case study should identify the observation window, actual workflow, data source and limitations. Obtain written permission for any customer name, logo, quote or screenshot. Redact personal and commercially sensitive details. There are no customer benchmark results on this page; the downloadable worksheet is a collection framework for future evidence.