Table of Contents

Definition

Plural form of [Table Arc], read as the accumulation that builds or breaks the macro relationship. The industry almost exclusively discusses the Guest relationship at the macro level — retention, loyalty, lifetime value — but every macro relationship is the sum of the [Table Arcs] that either opened or closed. A cast member who cannot read and advance the arc inside a single visit cannot build the macro relationship, regardless of how well they execute the service sequence.

Explanation

Retention and loyalty are lagging numbers. They report on something that already happened. [Table Arcs] is the mechanism that actually produced the number — the accumulation of every in-visit arc a Guest has run with the operation, each one either advancing the relationship or letting it stall.

This is why service-sequence execution and relationship-building are not the same skill, even though operators often conflate them. A cast member can hit every step of service correctly and still fail to advance a single [Table Arc], because reading the arc requires sensing where the Guest actually is in the moment — opening up, in a hurry, celebrating, decompressing — and adjusting accordingly, not running the same script regardless of who’s sitting at the table.

Every macro number the operator cares about — retention, frequency, lifetime value — is downstream of whether [Table Arcs] are closing or stalling, visit after visit. An operator who wants to move the macro number has to look at the micro arc first, because that’s where the relationship is actually being built or lost.