Craft · Lesson 3
Callbacks and tags
Stack a second punch on a working setup and revisit that setup later in a new context.
The principle
A setup is expensive. You spend twenty or thirty seconds building a scene, establishing a character, laying down a premise, and then you get one punch. One. The audience laughs, the moment passes, and you are back to writing a new setup from scratch. Tags and callbacks are how you get a second, third, and fourth laugh out of material you have already paid for.
A tag is a second or third punch on a setup that already landed. You do not rebuild the scene or re-explain the premise. You hit a different assumption the first punch left behind. The audience is still laughing from the first punch when the second lands, so the second one hits a brain that is already open, already on your side. You are not earning a fresh laugh from zero; you are spending the goodwill the first punch deposited.
A callback stretches the same idea across the whole set. You plant a phrase or image early, then bring it back later in a new context. The new context is what makes it work: the audience hears the old phrase, their brain goes "oh, that thing again," and that recognition is itself a laugh layered under whatever new punch you attach. The reference is private. You and this specific audience shared that earlier moment, and now you are nodding at each other. It is the closest a set gets to an inside joke.
At the set level, callbacks are a planning tool. You decide in the writing that a phrase from minute three reappears in minute twelve, and you build the later joke around that reappearance. One closes the set, because a callback to something that already landed is the most reliable final beat you have. One recovers a bombed joke, because referencing the thing that worked pulls the room back under your control. If the same phrase returns three or four times, you have a running gag, which compounds the shared-joke effect each time it surfaces.
The judge scores construction. A single funny word is luck. A tag is a visible second layer. A callback is a visible thread running through the whole piece. The difference between "got lucky" and "built something" is exactly this: can the reader see the architecture, or just the one sharp edge?
In a joke
Illustrative example, same topic in both versions.
Before (one setup, one punch, nothing stacked on it):
"I turned on every notification on my phone. Now it texts me my step count every hour. I am not going to take more steps. I am just going to stand in my kitchen in my underwear and be angry at a number."
After (same setup, one tag, one callback later in the sequence):
"I turned on every notification on my phone. Now it texts me my step count every hour. I am not going to take more steps. I am just going to stand in my kitchen in my underwear and be angry at a number. And at eleven it says 'only 340 steps,' so I have to pace to the bathroom and back, which is not exercise, that is a small military campaign against a software update.
...[four minutes later, different topic, different context]...
So I went to the gym to hit the step target, and the instructor asks how I am feeling, and I say 'I am angry at a number,' and she looks at me like I have lost my mind."
What changed: the kitchen setup now carries a tag that hits a second assumption (the pacing is not exercise, it is a campaign) while the audience is still processing the first punch. The callback drops the phrase "angry at a number" into an unrelated scene (the gym) where the audience has to re-recognise it, and that recognition is the laugh. The setup was written once and spent twice.
Your turn
Take the joke you just wrote for tonight's challenge. Read the setup out loud. Now write one tag: a second punch that hits a different assumption the first punch left behind, without re-explaining the premise. Then, two or three lines later in the same piece, write one sentence that reuses a specific phrase or image from that setup in a completely different context. You have ten minutes. Do not rewrite the setup. Stack on it.
In one line
Tag the setup that worked. Callback to it from a new context.