Use AI to document sales metric definitions and reporting changes

Write the definition before explaining a trend

Choose one sales metric and obtain its current report settings, field definitions and permitted sample records. Document the unit counted, numerator, denominator if relevant, date field, time zone, reporting window, pipeline, owner filter and exclusions. A dashboard title such as meetings is not enough to establish what the number represents.

Ask AI to turn those settings into a plain-language definition plus a list of unknowns. Require a source for each rule and keep the actual report configuration authoritative. Do not let the model fill a missing time zone or assume that all teams use the same lifecycle definition. A compelling explanation of an undefined metric is difficult to verify.

Make rule changes visible beside the results

Create a change log with effective date, old rule, new rule, owner, reason and effect on comparability. Separate definition changes from data corrections and real business events. Where the evidence permits, prepare a like-for-like comparison using the same rules for both periods; otherwise label the break instead of inventing an adjustment.

For a fictional activity report, one team counts completed meetings while another counts calendar bookings. A rise after those reports are combined does not demonstrate improved meeting attendance. HubSpot’s sales analytics documentation also notes that activity date filtering can depend on the activity type. Check the report’s actual date property before explaining an apparent weekly change.

Test the definition against a small record set

Select fictional boundary cases: an activity on the last day of the period, a duplicate booking, a reassigned deal and a canceled meeting. Write the expected inclusion decision under the approved definition and compare it with the report. Use deterministic calculations for the totals; AI can help organize discrepancies but should not be the sole arithmetic validator.

Have the report owner approve the definition and retain a link to its settings. Add the definition where managers can find it when reviewing the dashboard. Record substantive rule revisions with actual dates. This makes a trend discussion more reproducible; it does not establish causation, prove that one rep is better or justify ranking people using incomplete activity counts.

Review checklist

• Define the counted unit and actual date property.
• Record filters, window and exclusions.
• Log definition changes separately from business events.
• Check boundary cases and arithmetic independently.
• Have the report owner approve the final definition.

Source context and limits

HubSpot documents report descriptions, properties and filters, including activity date behavior. The definition register is our proposed reporting discipline; no dashboard data or results were tested for this guide.