Your slides, after the talk

You sit back down, and within twenty minutes someone from the session emails asking for the deck. It feels like a small, easy yes — you already made the slides, forwarding the file costs nothing. It’s a smaller decision than it feels like only if the deck was built to stand alone in the first place, and most conference decks weren’t. A slide that made complete sense while you were narrating it — the dense chart, the caveat you said out loud but never put in writing, the punchline you delivered a beat after the bullet appeared — is a different document once it’s read cold, by someone who wasn’t in the room.

The deck was never meant to stand alone

Think back through your own slides the way a stranger would read them without your voice attached: does the axis label on the dense chart explain itself, or did you explain it out loud while gesturing at it? Is the caveat that made the headline number honest actually written down, or did you say it and move on? None of this means the deck is bad — a slide built to support a live talk is doing its job correctly by being incomplete on its own, the same way a speaker’s notes aren’t meant to be read as an essay. It just means “here’s the file” and “here’s what I actually communicated” are not automatically the same thing, and it’s worth noticing the gap before you close it by hitting send.

The clearance question didn’t end when you sat down

The essay on presenting covers getting slides cleared before you speak — unpublished data, a partner’s confidential material, anything under an NDA. That review doesn’t automatically extend to indefinite, standalone circulation after the talk; a slide that was fine to display once, live, with you there to frame it and answer questions about it, isn’t automatically fine as a PDF that outlives the room and travels wherever the recipient forwards it next. If anything on the deck came close to that line when you built it, it’s worth the same thirty-second check again before you send the file, not an assumption that clearance was a one-time gate you already cleared.

Two honest options, not one default

For a simple, self-contained deck — a process overview, a timeline, nothing that depended on your narration to make sense — forwarding the file as-is is a completely fine answer, and there’s no need to manufacture extra work. For anything with real substance — the talk with the dense data slide, the argument that only worked because you built it up across twenty minutes — a short leave-behind version is worth the hour: strip the slides that needed you standing next to them, add the two or three sentences of context that were only ever spoken, and keep it to what genuinely survives without your voice. Build it once, in the days right after the talk while the context is still fresh, and reuse the same file for every request that comes in afterward instead of deciding fresh each time.

Before it goes further than one inbox

A colleague forwarding your deck to their own team is a different thing than a stranger posting it publicly, and it’s worth being explicit rather than assuming either one is obviously fine. If you post your own slides publicly afterward — on LinkedIn, on a company site — check the organizer’s own policy on redistributing conference materials first; a flagship annual like RAPS Convergence or the DIA Global Annual Meeting usually has one, and it exists precisely because a room full of speakers has a room full of different comfort levels about where their material travels next. And if the talk had co-presenters, the deck isn’t only yours to publish on your own timeline — a quick check with them costs one message and avoids finding out later that they’d have said no.