L2Lesson 13Free

Create the send-ahead version

Make the deck readable without you

After this, you'll be able to create a send-ahead revision plan and use it to move a deck from rough material toward a presentable file.

Before you start

Complete Write speaker notes first.

The idea

A send-ahead deck has to explain itself. It needs more context, clearer captions, and fewer moments that require the speaker. This lesson asks you to make a send-ahead revision plan, not a prettier version of scattered notes. The output should be specific enough that someone could open the deck file and see what changed.

A live-talk deck and send-ahead deck overlap as one confusing file. — The first move: turn the lesson input into a send-ahead revision plan.

Here is the before and after: Before, the live deck is sent as-is and readers miss the point. After, the send-ahead version adds context, source notes, and clear conclusions. For example, if you are preparing a sales presentation, the artifact should name the audience, slide job, proof, speaker note, or export check where that detail matters. A reviewer should be able to tell whether the deck is closer to being presented, sent, or handed off.

Now try it: Ask Claude to mark every slide that depends on your voice and rewrite it for a reader. Make one choice before asking Claude to write: which audience, which decision, which proof, which slide job, or which delivery mode matters most right now. That choice keeps the deck from becoming a generic presentation outline.

Create the send-ahead version runtime mapThe deck works when a send-ahead revision plan connects the input, the check, and the next step.

Messy inputThe raw pitch deck material before the lesson shapes it.
a send-ahead revision planThe thing you can inspect, edit, and reuse.
Review checkThe delivery check that catches a weak assumption.
Next stepThe output moves into the next lesson instead of sitting alone.

The lesson is done when the artifact moves the deck toward a real room, reader, or file handoff.

Try it (17 min)

Watch out for

Adding full speaker notes onto every slide.
Hiding definitions in the appendix when first-time readers need them.
Sending a deck with no clear ask because you planned to say it live.

Paste this into Claude

Review this deck as a send-ahead file. Mark slides that require a presenter. For each, recommend added context, caption, proof note, or appendix link. Deck: [paste slide text or outline].

If any input is missing, ask me up to three questions before producing the artifact. Then return five sections: Finished Artifact, Realistic Deck Example, Assumptions To Check, What I Should Use In The Next Lesson, and One Risk If I Present Or Send This Without Fixing It. Keep the answer practical enough that I can paste it into my deck working doc.

What a good response looks like

Finished Artifact:
- a send-ahead revision plan
- Why it matters: it gives the deck a concrete thing to inspect instead of a vague intention.
- Use it next: paste this artifact into the next lesson before asking Claude to write, build, import, publish, or review anything.

Reality Check:
- The artifact names the user, input, decision, owner, or proof it depends on.
- The weakest assumption is visible.
- The next step can be completed in one sitting.

What good looks like

Slides that depend on a presenter are marked.
Reader context is added without overcrowding.
Sources and definitions are clear.
The final ask still appears.

Go deeper (8 min)

Paste this into Claude

Without rereading the lesson, explain why a send-ahead revision plan matters in three bullets. Then apply it to a second deck example: [describe a different audience, room, or topic]. Return What Changed, What Stayed The Same, What To Check Before Presenting Or Sending, and the exact next action.

What a good response looks like

Transfer Check:
- What changed: the second example has a different audience, input, or delivery context.
- What stayed the same: a send-ahead revision plan still needs a source, a review check, and a next step.
- Before trusting it: inspect the delivery check that would catch a wrong assumption.
- Next action: run the check once, then carry the revised artifact into the next lesson.

What good looks like

You explained the lesson idea from memory before applying it again.
The second example changes the artifact instead of copying the first answer.
The delivery check names a real risk.
The next action can be done in one sitting.

When this breaks

Breaks when the reader cannot infer the spoken context because the deck becomes a puzzle.
Fails when added context bloats every slide because the file stops being scannable.

AI can help with this

Paste the exercise prompt into Claude with your real deck context. Ask Claude to interview you one question at a time, produce a send-ahead revision plan, challenge the weakest assumption, and rewrite the artifact once so it is ready for the next deck step.

Two outline deck strips separate: the send-ahead strip gains small context tabs while the talk strip keeps wider pacing gaps, with the golden dot on the send-ahead path.

You can now

You can explain a send-ahead revision plan in one sentence.

You can name the source material or decision it depends on.
You can name the assumption that still needs checking.
You can point to the check that proves it is ready for the next deck step.

Key takeaways

Live decks and send-ahead decks need separate review, even when they share the same source.

Send-ahead decks need context on the page.
Not every note belongs on the slide.
Definitions and sources reduce confusion.
The ask cannot depend on a live close.

Was this helpful?

Up nextCritique the deck before design

Write speaker notes Critique the deck before design

← Back to Slides & Pitch Decks

Review this deck as a send-ahead file. Mark slides that require a presenter. For each, recommend added context, caption, proof note, or appendix link. Deck: [paste slide text or outline]. If any input is missing, ask me up to three questions before producing the artifact. Then return five sections: Finished Artifact, Realistic Deck Example, Assumptions To Check, What I Should Use In The Next Lesson, and One Risk If I Present Or Send This Without Fixing It. Keep the answer practical enough that I can paste it into my deck working doc.

Finished Artifact: - a send-ahead revision plan - Why it matters: it gives the deck a concrete thing to inspect instead of a vague intention. - Use it next: paste this artifact into the next lesson before asking Claude to write, build, import, publish, or review anything. Reality Check: - The artifact names the user, input, decision, owner, or proof it depends on. - The weakest assumption is visible. - The next step can be completed in one sitting.

Without rereading the lesson, explain why a send-ahead revision plan matters in three bullets. Then apply it to a second deck example: [describe a different audience, room, or topic]. Return What Changed, What Stayed The Same, What To Check Before Presenting Or Sending, and the exact next action.

Transfer Check: - What changed: the second example has a different audience, input, or delivery context. - What stayed the same: a send-ahead revision plan still needs a source, a review check, and a next step. - Before trusting it: inspect the delivery check that would catch a wrong assumption. - Next action: run the check once, then carry the revised artifact into the next lesson.