Name the handoff, not the ticket
Label the system boundary you care about—or the next board rename breaks every flow report.
Teams often treat event names as disposable labels. A designer renames a screen, an engineer ships a new component, and suddenly queue_exit and handoff_done both exist for the same moment. Flow reports that once looked clean become archaeological digs.
Prefer verbs that describe the boundary crossed. Keep platform out of the event name—put it in a property so web and app stay comparable during flow reviews. Write allowed properties on the same day you create the signal.
In Baseline Audit engagements we spend the first day on inventory alone, because until synonyms are visible every later fix guesses at the wrong root.