Document to presentation: build a live deck, not a read-ahead memo

Before you touch the source, write one sentence: what should the audience decide, approve or understand by the end? If you cannot write that sentence, the document is not ready to become a deck.

Use the decision to choose what stays. A fact belongs on a slide only if it changes the decision, supports the recommendation or prevents a predictable objection. Everything else goes into speaker notes, an appendix or the read-ahead.

A live deck and a read-ahead memo are two different products. The read-ahead can carry context, methodology, footnotes and reference detail. The live deck should carry the argument.

This is why sending the same file before the meeting often produces a bad meeting. People either read ahead and arrive with the whole document in their heads, or they read the slides in the room and miss the conversation. Decide which job you are doing before you generate the deck.

For a live deck, assume the audience has not read the memo. Open with the tension or decision, not with a company overview. For a read-ahead, keep the detail; do not ask a live presentation to do that job silently.

A slide should make one point. If the title is “Background”, “Project update” or “Next steps”, the slide probably has no point yet. Rewrite the title as a claim:

• “The May cutover only holds if scope freezes Friday.”
• “The pilot is worth expanding, but not with the current support model.”
• “This pricing option fixes churn and creates a different sales problem.”

If the claim needs a paragraph of explanation, it belongs in the notes. If the slide needs to be read line by line, it is a document.

Speaker notes are not a transcript. They are the part of the presentation that only the presenter needs:

• the sentence to emphasize;
• the transition to the next slide;
• the objection or question most likely to come up;
• the fact that is too detailed for the slide but important if challenged.

This is also where a read-ahead can live without turning the live deck into a wall of text. The room sees the argument; the presenter keeps the evidence.

The same source can become several different decks. A five-minute status brief needs a conclusion and three takeaways. A working deck needs options, owners and next steps. A narrative proposal needs tension, evidence, trade-offs and an explicit ask. A workshop needs modules, exercises and facilitator notes.

Do not force every meeting into one template. Choose the job first, then the page count.

pastedeck reads the text you provide, identifies the communication task and reorganizes it into a live deck with speaker notes and a browser link. It does not turn images, complex charts, spreadsheet formulas or a brand template into a finished design system.

It also does not export an editable PowerPoint file. If your client requires a branded .pptx, a legal review or a designed external campaign, use the right tool for that job. The honest boundary is part of the product: this is for the argument and the meeting, not for pixel-perfect production.

Read only the slide titles from top to bottom. They should tell a coherent story without the body copy. Then read only the speaker notes. They should tell you what to do, not repeat what is on the screen.

If the titles tell the story and the notes tell you how to deliver it, you have a live deck. If both tell the same thing, you still have a document.