← Every exhibit

Table Table 2 Revenue operations & AI

Which fields make a handoff reproducible?

FieldMinimum evidenceWhy it stays separate
Process keyStable identifier joining the process instance across records or entitiesOpportunity, quote, contract, and delivery rows can otherwise be counted as separate deals
Handoff typeNamed transition such as marketing to SDR or AE to legalLatency and acceptance are not comparable across every interface
Entry criteriaRule or evidence that permits the handoff attemptA task created in a queue is not proof that the process was eligible
Sender and releaseAccountable sender, release event, and timestampA changed stage without a release event is not a complete handoff
Receiver and acceptanceIntended receiver, acceptance event, timestamp, or explicit non-acceptanceOwnership cannot be inferred from assignment alone
Evidence packetFields, document, event, or decision record required by the receiverA fast acceptance of an empty packet is not a healthy transition
Latency clockStart event, end event, timezone, and review windowA duration changes when the start or end event changes
Exception stateMissing evidence, capacity issue, conditional branch, or other reasonA returned transition should not disappear into a new owner or stage
Next eventPlanned action, date, trigger, or explicit no-next-event stateA current stage does not show what keeps the process moving
DispositionAccepted, held, returned, excluded, or open at horizonDifferent unresolved states require different operating decisions

Swipe or scroll horizontally if the table is wider than your screen.

Cite Embed

Reference & Evidence

Source: Table from this essay. Sources and interpretation are given in the article.