Three abstract presentation cards and a separate notes card illustrating a slide handover.
Original AI-generated editorial illustration; not a real account, product sale or completed job. View full-size image.

A slide preparation service should return a presentation the client can edit, rehearse and use in the agreed setting. Start with the audience, the decision or explanation the deck supports, and the files required at delivery. Improving the appearance of a slide does not validate its claims or establish that the presentation will win a sale.

The sample brief below is an invented exercise for organizing and checking an existing presentation. Define the service boundary and approval steps before offering the workflow to a client.

Define the presentation job

Ask whether the client needs help with the argument, visual layout, data displays, speaker notes or final file checks. Those tasks can overlap, but they involve different decisions. A request to make slides consistent is not automatic permission to rewrite the message, change a forecast or replace an approved figure.

Record the presentation setting: live talk, recorded session or document sent for independent reading. A live speaker can explain a short diagram; a standalone reader may need more context. Establish the intended audience and the action they should be able to take after viewing it.

Confirm the application and version the client will use, the required editable format and any separate handout. Ask who owns the source material and can approve changes. Put the deadline for receiving content alongside the deadline for delivering the deck. Missing figures or late revisions can change the work substantially.

Inspect the source before styling it

Make a content inventory. Note each slide's purpose, supporting material, open questions and review owner. Mark charts without a source, images without clear permission and text whose meaning is uncertain. Present those questions to the client before polishing material that may need to be replaced.

Keep the supplied file separate from your working copy. Use a version identifier that appears in the review request and delivery note. If several people return different copies, ask the client to consolidate their instructions rather than silently choosing between conflicting edits.

Identify repeated layouts that can be made consistent. A deck may need a common heading treatment, an agreed chart legend and predictable placement of source notes. Establish those decisions on a small representative sample before applying them to every slide. Do not use a decorative template to hide an unresolved content problem.

Check how the slide will be read

Microsoft's accessibility guidance covers alternative text, meaningful links, contrast, unique titles and the reading order of slide objects. It explains that visual placement and the sequence used by a screen reader may differ. The instructions vary across applications and versions, so use the section that matches the client's environment.

Source: Microsoft's accessible PowerPoint guidance. Read 2026-10-26.

Build accessibility review into the brief instead of treating it as a final decorative check. Ask what the images need to communicate, whether a chart relies only on colour, and whether a reader can follow the intended order. The automated checker can help identify problems, but a result from a tool is not a guarantee that every user can understand the deck.

For the proposed service, record what you checked and what needs client confirmation. If a chart's meaning is unclear, writing alternative text may expose that gap. Resolve the underlying message rather than inventing an interpretation for the description.

Separate speaker notes from audience files

Microsoft documents a Notes Pages print layout that places one slide and its accompanying notes on a page. It also describes exporting notes-page copies to Word in supported versions. That is different from assuming that every slide-only export includes the presenter's notes.

Source: Microsoft's speaker-notes printing instructions. Read 2026-10-26. Confirm the available output options in the client's application and printer setup.

Agree on which notes belong in each deliverable. Private rehearsal prompts, internal questions and audience explanations may need different treatment. Before sharing a file, inspect the actual copy intended for that audience. Do not rely on a filename such as “final” to tell you whether internal material is still present.

If notes are part of the assignment, check whether they still correspond to the current slide order. A section moved during editing can leave a note referring to a chart that now appears elsewhere. Keep any print or export check separate from the editable-deck check.

Make a representative practice sample

For an invented sample, create a short deck explaining how a fictional community workshop will run. Use your own text and simple diagrams. Include an opening purpose, a sequence of activities and a closing action. Avoid invented attendance figures or claims about real organizations.

Prepare a review copy and a change note. Explain one content decision, one layout decision and one question that still needs approval. For example, if the source brief does not identify who supplies materials, flag that missing responsibility rather than filling the gap with an assumption.

Rehearse the sample in the intended viewing mode. Check whether labels remain readable, whether each slide supports its stated purpose and whether the notes help the speaker rather than repeat every visible word. Keep the exercise distinct from a portfolio claim about client results.

Inspect every required output

Open the editable file after saving it and inspect the beginning, middle and end. Check the complete deck, not just the sample layouts. Review links, image placement, chart labels, page order and any agreed media. Ask the client to confirm dependencies you cannot test in their presentation environment.

Open each separate export as well. Look for missing content, altered line breaks, clipped labels or an unexpected page size. If the scope includes a handout, assess it as a reading document rather than assuming that smaller copies of the slides will serve the same purpose.

Keep an issue list with the slide identifier, problem, proposed action and decision owner. Distinguish a correction you can make within scope from a change requiring subject-matter approval. Do not claim that design review is also a financial, technical or legal audit.

Check fonts for the next editor

A deck can look correct on your computer and still be awkward for the client to revise. Before agreeing that the presentation is editable, record the receiving application and whether the recipient needs to add text while offline. A font choice belongs in that handover decision, alongside the file format.

Microsoft's font-embedding guidance says that saving only the characters already used reduces file size but limits later editing in that font. For a PowerPoint deck that someone else will revise, its guidance recommends embedding the full character set. Embedding also depends on the font's permissions; not every font permits it. Check the font's embedding setting and the applicable licence before promising this delivery method. The source covers specific desktop versions, with separate Windows and macOS instructions. Read 2026-11-16.

Microsoft's modern font-picker guidance explains that a missing font may be substituted for viewing without changing the font assigned to the text. That replacement can alter the design or layout. It also distinguishes viewing an embedded font from creating the embedding: the latter requires a Windows or macOS desktop app. A font name displayed in the deck is therefore only part of the delivery check. Read 2026-11-16.

Apply that distinction to the fictional workshop sample. In a duplicate of the delivery file, replace the workshop name with a longer invented name and add a symbol that was absent from the original slides. Check the new text in the agreed receiving application, then inspect the slide show and any separate export. Record this as a practice exercise and confirm the receiving setup separately before using it for a client handover. A screenshot of the unchanged title would leave this editing requirement unanswered.

Add a font entry to the delivery note: the font used, the agreed embedding or installation arrangement, and who checked the recipient's environment. If that check is unavailable, mark it unresolved. Ask the client to approve a permitted alternative font and review any changed wrapping before release. Supply a font file only when its licence allows that transfer. Keep the approved editable deck and its checked audience export under the same version identifier so a later font substitution cannot silently become the new delivery.

Deliver an editable package with boundaries

Return the agreed files, a short version note and any unresolved issues. State which assets remain editable and which rely on a particular font, application or permission. Include only materials the client is authorized to receive; do not expose another customer's template or confidential example.

Agree on the number and type of revision rounds, how feedback will be consolidated and what happens when source content changes after approval. Count content collection, file checking and review time in the proposed workload. Quote against that defined workload and the client's revision needs.

For related work, compare virtual assistant services and proofreading. A practical next step is one original sample deck with a clear review note and checked output files. It should show what you can deliver without promising a business outcome you have not measured.