Table of Contents

Definition

Bucket two in The No-Read. A cast member who knows the standard and normally performs to it, but is temporarily unable due to an offline life circumstance — health, family, financial, mental, situational. Not a training problem, not indifference, a capacity problem rooted outside the restaurant. The operator move is intervention in favor of the cast member: adjusted schedule, time off, resources, whatever the situation needs. Time-bound by definition — bandwidth returns, performance returns. If it doesn’t return, the bucket call changes, collapsing to No Commitment or back to No Knowledge if something fundamental shifted.

Explanation

The clean separation from the other two buckets is what makes this classification usable rather than a soft, sympathetic catch-all. [No Bandwidth] specifically requires that the cast member both knows the standard and has previously demonstrated they can meet it — this isn’t about training gaps and it isn’t about willingness. Something genuinely outside the restaurant has temporarily reduced their capacity, and the operator’s correct response is support, not correction.

The time-bound requirement is what keeps this bucket honest and prevents it from becoming a permanent excuse. Bandwidth problems are, by definition, temporary — if the situation drags on indefinitely without resolution, the operator has to re-run the read, because either the capacity truly isn’t returning and the classification needs to shift toward [No Commitment], or something more fundamental has changed and it belongs back in [No Knowledge]. Leaving a cast member parked indefinitely in [No Bandwidth] without re-checking the read is its own version of avoidance.