ILT Deck Engine
An engine I built that studies two approved instructor-led decks, then builds the next course’s full deck and facilitator notes in the same style.
- Slides in one delivered deck
- 265
- Documents built for each course
- 4
- Cold start to a 20-slide deck
- 2 days
Python, python-pptx, Claude Code, PowerPoint, LibreOffice
A client asked for instructor-led training (ILT) decks of 200 slides and more, quickly, in the exact branding and patterns of the decks they already had. They gave me two of those finished decks and the two Word standards the decks had been written from. Having both the source and the result for two topics meant I could measure how a standard becomes a deck. I studied the pair once and built an engine that makes the next one.
What I built
- The study
- I traced all 545 slides of the two approved decks back to the passages of the Word source they came from. That turned the house style into numbers. A content slide carries three to four passages, about 150 to 205 words of source. Facilitator notes run in four parts, about a quarter source fact and three quarters the designer’s framing.
- One engine and a pack for each client
- The engine never branches on the client. Brand, template, density and voice live in a client pack as data, which means a new client is a new pack and the engine stays the same.
- A catalogue of slide types
- Every slide in the two decks was sorted into about 30 types, each with its own recipe: a section divider, a definition, a process flow, a worked example, a knowledge check. The engine draws nine kinds of visual (table, matrix, process, cycle, hierarchy, columns, comparison, callout, timeline) as native PowerPoint shapes, and the client can edit every one of them.
- Four documents for each course
- A run produces the deck, the facilitator guide, the participant workbook and the knowledge check.
- Every fact traces to the source
- Each claim on a slide points to a passage in the client’s standard. The engine never makes up a table or the data in a diagram.
What a run needs
The engine is a method that an instructional designer drives. Claude writes the slide text inside the session under a written contract. The engine plans, selects, assembles and renders, and it refuses whatever breaks the contract. A run has twelve checkpoints, each naming who acts, and at four of them the engine stops and waits for the instructional designer.
What it delivers
The first deck went to the client on 26 August 2026. It had 265 slides and took two days of building and three review rounds. A second company’s deck, 20 slides from a standards document the engine had never seen, took two working days from a cold start. That run also found a defect in the engine itself: every measurement assumed the first client’s page size. A colleague who heard the first deck had gone down well asked for a demo. The engine now travels as a zip that unpacks and runs its own tests, more than 2,800 of them, before I send it.
