When this helps
Workbook-grounded and author-clarified; proposed reconstruction. Teachers develop slides from an approved lesson sequence to organise explanation, support attention, cue interaction and display accessible visual material during live teaching. The complete deck must remain editable, source-grounded and connected to companion resources where students need standalone access.
Proposed and author-clarified. Slide development can become a transfer of notes into bullet-heavy pages or an aesthetic exercise detached from the lesson plan. Generated decks may invent claims, repeat generic layouts, use inaccessible assets and leave teachers with an uneditable artefact whose sources are unclear. Trying to make projected slides serve simultaneously as a complete standalone resource can also undermine live readability.
Pattern response
Proposed and author-clarified. Build and retain a storyboard from the approved lesson structure before generating individual slides. Define what each segment must help students notice, understand or do; ground claims and assets in inspectable sources; then produce a complete, editable deck using a restrained visual system. Design primarily for live teaching and place necessary depth in speaker notes or accessible companion resources. Inspect the rendered deck for accuracy, readability, accessibility, pacing, technical integrity and asset rights. Require the teacher to revise and approve every slide and retain authority during delivery.
- A coherent slide narrative linked to lesson outcomes and activities.
- A retained storyboard and complete editable deck with grounded claims, purposeful visuals and accessible structure.
- A source and asset record that supports checking and reuse.
- Speaker notes and defined accessible companion resources carrying detail unsuitable for projected slides.
- Teacher-approved, rendered quality assurance across all slides before delivery.
Workflow at a glance
- 01
Frame the slide brief
The teacher defines how slides support the lesson and which information belongs on slides, in notes or in companion resources; accessibility or design specialists may advise.
MOD-001 · MOD-015 - 02
Build the slide narrative
The teacher judges narrative, disciplinary emphasis, pacing and interaction; designers may advise how visual form serves those decisions.
MOD-027 · MOD-028 - 03
Ground and render the deck
The teacher verifies disciplinary meaning and decides what appears; design, media or accessibility contributors check specialist aspects without assuming pedagogical authority.
MOD-013 · MOD-047 - 04
Evaluate accessibility and approve
The teacher approves the complete package and remains responsible for its use and live adaptation; learners or accessibility reviewers may test whether important information is perceivable and understandable.
MOD-042 · MOD-044
Human checkpoints
The teacher determines the narrative, verifies disciplinary content, approves assets and decides how slides serve live teaching. Designers, media specialists and accessibility reviewers may assist with visual, technical and access decisions. Students may help test readability and companion resources. GenAI structures, drafts and renders provisional material; it cannot decide what the class needs, approve the teaching package or determine when the teacher should depart from the prepared deck.
Risks and misuse
Reconstructed risks
- Generated claims, quotations or references appear on slides without verification.
- Dense or decorative layouts reduce accessibility and live readability.
- Images reproduce stereotypes or lack suitable reuse rights.
- The deck dictates the lesson rather than supporting interaction and adaptation.
- Slides become unreadably dense because they are expected to function as the only standalone resource.
- Speaker notes or companion resources contradict the visible deck or lose source provenance.
- Automated export produces clipping, missing fonts or broken media that is not visually inspected.
Use this pattern
Begin with the recurring problem and the authorised inputs. Follow the workflow in order, keep intermediate outputs inspectable and retain the named human decisions.
- Minimum viable implementation: storyboard an approved lesson in a table, use GenAI to draft concise slide content and notes, build an editable deck, then render and inspect every slide before teacher approval.
- Robust implementation: add an agreed visual system, structured storyboard, source and asset register, rights review, accessibility criteria, companion-resource templates, editable version history and inspection in the intended teaching environment.
- Low-code implementation: connect a curriculum and lesson store, GenAI drafting interface, presentation template and renderer while keeping storyboard approval, source verification and teacher sign-off visible.
- Local or privacy-preserving implementation: keep unpublished teaching and learner-context material in controlled storage, use only necessary audience information and process locally where policy or risk warrants it.
- Speculative implementation: regenerate a family of decks and companion resources from approved storyboards when curriculum or design-system elements change, while preserving prior versions and requiring slide-by-slide rendered review.
Reusable modules
Related patterns
Technical and provenance detail
Data and information flow
Proposed and author-clarified. The approved lesson plan, learner context, sources and visual brief lead to a retained storyboard before slide production. Each proposed slide carries its instructional purpose, lesson position, content, source and asset needs, delivery action and companion-resource relationship. Teacher-approved content flows into the editable deck, notes and accessible companion materials. The final package retains the storyboard, source and asset record, editable source, rendered output, accessibility findings and approval decision. Sensitive learner information is not required merely to personalise examples or imagery.
Source provenance
- Pattern ID: DP-037
- Original workbook row(s): 63.
- Original label(s): Slide Content Drafting.
- Inherited source category/theme: DEVELOPMENT OF MATERIALS AND LESSON PLANS.
- Source status: workbook-derived source; the source supplies concise labels rather than a complete pattern narrative.
- Extraction notes: Original labels, row relationships, categories, themes, rationales, and confidence assessments are preserved below.
- Editorial interventions: The problem statement, response, forces, risks, workflow, and module mapping are documented reconstructions that retain explicit provenance labels and remain open to author and practice-based validation.
- Author clarification (2026-08-20): The pattern produces a complete, editable slide deck, with the storyboard retained as an intermediate review artefact. It supports live teaching first; speaker notes, transcripts, handouts or accessible companion resources carry necessary standalone detail. The pattern belongs to a macro-to-micro teaching-design sequence: DP-034 grounds course and unit intent, DP-035 connects industry-valued graduate attributes, DP-036 develops the lesson plan, DP-037 develops the live slide deck and DP-038 develops reusable in-class questions.
Open questions
- What rendered checks should be mandatory before a generated deck is used?
- How can the deck preserve useful presenter flexibility rather than becoming a fixed script?
- Which source and asset metadata should travel with slides intended for reuse by others?
- What is the smallest accessible companion set that supports standalone access without duplicating the deck unnecessarily?