Full-service supervisor escalation-talk script - when the same finding fails closure twice in a row, switch from corridor remarks to a formal talk: set the frame, state the record, hear them out, fix the verification, close with the consequence

You are a field supervisor coach for a full-service restaurant chain. Write me a set of escalation-talk script cards.
Scenario: the same finding at the same store has missed closure on two consecutive store visits, and I am escalating the verbal remark to a formal talk.
I will provide: the finding and its visit history, the manager's tenure, the store's recent performance.

Pre-talk inputs (settle these before any words are spoken; an unsettled item means the talk waits):
- Scope of this talk: this one finding only, or this finding plus what the current visit surfaced
- What the escalation consequence is (support intervention / performance record / escalated to the regional manager) - if undecided, the word "consequence" does not appear in the talk

Five steps, order fixed:
1. Set the frame (the first sentence separates this talk from chat):
"I'm not mentioning this in passing today - this is a formal talk. I'll take notes, and at the end you sign and I file it."
2. State the record (the finding only - dates, places, current status, no adjectives):
"On [date] the visit found A and you agreed to fix it on the spot. On [date] the recheck found it not closed. Today the floor is unchanged. All three records are here."
3. Hear them out (three fixed questions, all asked before responding; do not interrupt while they talk):
"What did you do between those visits?" "Where did it get stuck?" "Whose help do you need?"
4. Fix the rectification (three elements or it does not count):
"the explanation I accept" + "the action" + "how I verify" - the verification must be a trace visible on the next visit's floor; verbal commitments do not go into the record
5. Close (state the consequence flatly - no threats, no soothing):
"This is occurrence number [X]. Per process, one more missed closure goes to [consequence]. Two copies of today's record - sign both."

Response cards for the three classic deflections:
- "We're short-staffed, everyone's slammed":
"Scheduling and headcount is a separate conversation we can have - but it's a separate thing. Today we fix this finding first; don't let the two items drag each other into never happening."
- "My people don't execute":
"Getting your people to do things is your job; I measure the result. If you need training support we'll talk training - but 'my staff won't do it' is not within the scope of explanations this talk accepts."
- "That standard isn't realistic":
"Fine. Give me the version you can actually deliver and we'll look at the verification together - but standard and verification can't both get cut."

Forbidden:
- No dragging in old grievances unrelated to this finding - an escalation talk carries one item to the table
- No "attitude" or "sense of responsibility" vocabulary about the manager - findings and records only
- No commitment accepted without a verification attached - "I'll stay on it" is not a rectification action
- No consequence announced on the spot that wasn't decided beforehand - consequences are chosen before the talk and only stated during it
- Keep the language plain - no "synergy", "leverage", "alignment" words a store manager has no reason to parse

Why it is written this way

The core move of an escalation talk is cutting the frame: the first sentence establishes the record and the signature, and every sentence after it carries different weight. Most supervisor remarks fail because they open in chat register - and promises made in chat register cost nothing, so they evaporate. Setting the frame is not posturing; it is pricing every sentence that follows.

Facts only, no adjectives, because an adjective instantly converts the talk into a rating of the person, and once defensiveness engages nothing gets heard. "All three records are here" is unarguable; "your store is always like this" is an hour of arguing. Among the deflection cards, "we're short-staffed" is the most common escape route - let the topic drift to scheduling and the talk is over - and the card's core move is acknowledging that as another issue while pinning this one down first.

"Consequences decided before the talk" guards against two failures: a penalty improvised on the spot either cannot be executed (credibility gone) or lands too heavy in the heat of the moment (open conflict). Decide alone beforehand, state only during the talk - the supervisor's emotions never get a vote.

"Verification must be visible on the floor" interlocks with the rectification closure audit: the fix promised in this talk gets closed out item by item by the audit next month - the paper-closed column will catch any "said it was fixed" IOU. Two tools sharing one closure standard is what gives the supervisor an unbroken chain.

Variables