Tracking workflow completion rather than total executions

Count completion against eligible work whose allowed completion window has closed. A workflow start or enrolment count shows activity, and can include repeat entries and work that has not finished. A completion rate needs a defined result and a denominator from the same cohort.

Define one unit of work

Choose whether the unit is a contact, request or campaign occasion. If one contact makes two valid requests, a contact-level count hides the second task. If a repeated submission is a duplicate, treating it as new work inflates the denominator. Keep a request or occasion reference where that distinction matters.

Define completion in operational terms. For routing, it could mean that the destination record shows the intended owner. For a requested resource, it could mean that the current asset was made available through the agreed route. The campaign owner must choose a result appropriate to the task; reaching the last workflow action may be a narrower observation.

Use a cohort that can finish

Select opportunities that became eligible within a stated period and are due to have finished by the reporting cut-off. Remove records that never met eligibility before forming the cohort. Classify every due opportunity as confirmed complete, authorised cancellation, failed or outcome unknown. Show work not yet due separately.

Completion rate = confirmed completions ÷ eligible opportunities due to finish. A cancellation after eligibility remains in the denominator but gets its own label. If the team uses a different approved cancellation rule, publish that rule and its counts beside the rate. Do not silently discard failures or unknown outcomes.

A separate timeliness rate counts confirmed completions made by the agreed deadline.

For illustration, suppose 40 eligible requests were due by Friday. If 32 have a confirmed result, three remain under investigation and five failed, the confirmed completion rate is 32/40, or 80%. The three uncertain requests are not completed. This is hypothetical arithmetic, not a campaign result.

Reconcile platform counts

Use HubSpot's action logs and enrolment history to review workflow events, then match a request to its destination result when that result defines completion. Access requires an eligible subscription and permissions, and historical records have retention limits.

When a count changes unexpectedly, review affected records' enrolment history and action logs, including Record, Diagnose, Action, Event and Time; check the enrolment and path for individual records. Classify confirmed outcomes and unresolved cases consistently using the team's completion definition. Compare rates only when the unit, finish line, cut-off and workflow version are comparable.