Draft · Rev 01
Document
Every asset that hits the screen, accounted for.
I'm Tim Kloppenburg. I manage show content — decks, video, graphics, playback — from first draft to final cue. Before a single file loads in, I know the show top to bottom: what plays, when, why it's there, and what breaks if it moves.
- Prepared by
- Tim Kloppenburg
- Role
- Content Manager
- Scope
- Keynotes · General sessions · Broadcast · Hybrid
- Status
- Available for booking
- Revision
- 01 — 2026-08-13
- Contact
- See cue 08
Cue 01
What I run
Content management is not file wrangling. It's owning the single source of truth for everything the audience sees — and being the person who can answer any question about it, instantly, in a dark room, ninety seconds before doors.
Content ownership Rev 01
| Item | Scope | Owner | Status |
|---|---|---|---|
| Content intake | Chasing decks from every presenter, in every format, at every hour. One intake path, one naming convention, one version that is current. | TK | Owned |
| Version control | Every revision logged, dated and reversible. When slide 14 is rewritten at midnight, the change is tracked and the old cut still exists. | TK | Owned |
| Playback prep | Files built for the system they'll actually run on — codec, frame rate, aspect, audio config, naming that matches the run of show. | TK | Owned |
| Rehearsal & show | In the room from first tech through the last cue. Live edits, last-minute swaps, reissued run of show — fast, and communicated. | TK | Owned |
| Speaker support | Presenters get one calm point of contact. Their content works, their confidence monitor shows what they expect. | TK | Owned |
| Documentation | A run of show anyone can pick up and follow. Cue numbers, file names, durations, owners — five departments telling one story. | TK | Owned |
Cue 02
Top to bottom
Most content problems on show site aren't content problems. They're someone making a local decision without knowing what it costs three cues later. So I start by understanding the entire show — every segment, every hand-off, every dependency — and then the file work becomes obvious.
-
Phase 01T‑minus 6 weeks
Read the whole show
Objectives, audience, run of show, segment by segment. Who speaks, what they need, what the moment is supposed to feel like. I ask the questions producers wish someone had asked earlier.
- Draft run of show, annotated with content owners
- Every screen, surface and aspect ratio mapped
- Known risks flagged in writing, early
-
Phase 02T‑minus 4 weeks
Build the spine
Naming convention, folder structure, intake path, deadlines that are real. Set up once, correctly, and it holds under pressure for the whole run.
- Single intake channel — no content by side-channel
- File spec published to every contributor
- Version log live from day one
-
Phase 03T‑minus 2 weeks
Chase, check, conform
Content arrives late and wrong — that's normal, and it's planned for. Every file is opened, checked against spec and conformed before it ever reaches the playback system.
- Fonts, links, embedded media, build order — all verified
- Aspect and safe-area checked against the real screen
- Status visible to the producer at all times
-
Phase 04Load‑in
On site, in the room
Content on the playback machines, cued to the run of show, tested on the actual screens with the actual switcher. Backed up in two places before the first rehearsal call.
- Playback and backup machines mirrored
- Every cue fired once before anyone watches
- Run of show reconciled with video, audio and lighting
-
Phase 05Rehearsal
Absorb the changes
Rehearsal is where the show actually gets written. Changes come fast and from everywhere; my job is to take them all, keep them straight, and make sure the version on the machine is the version everyone agreed to.
- Change log kept live, timestamped and attributed
- Reissued run of show after every major pass
- Nothing changes on the machine without a record
-
Phase 06Show
Quiet, and ready
By showtime nothing should be interesting. I'm on headset, one cue ahead, with the answer to any question and a fix for the thing that just changed.
- Live edits handled without stopping the show
- Every department told, every time
- Final files and change log archived for the client
Cue 03
The system
Thorough is a process, not a personality trait. Being careful under pressure isn't something you summon on show day — it's something you build weeks earlier, so that on show day there's nothing left to be careful about.
- Naming
- One convention, no exceptions. Every file self-describes: show, segment, cue, version, date. You can read a filename in the dark and know exactly where it belongs.
- Versions
- The current one is obvious. Never two files that might be the latest. Superseded cuts are archived, not deleted — recoverable in seconds if a decision gets reversed.
- Redundancy
- Two of everything that matters. Mirrored playback machines, a local backup and an off-site copy. Tested by actually failing over, not by assuming it would work.
- Change log
- Written down, every time. Who asked, what changed, when, and which cue it affects. It ends the "I thought we cut that" conversation before it starts.
- Comms
- Departments hear it from me. A content change is a video change, an audio change and a lighting change. Everyone affected is told directly.
- Handoff
- The client keeps the record. Final content, final run of show, full change history — packaged and handed over. Next year's team starts from fact, not from memory.
Cue 04
Shows
Plates are placeholders — drop Tim's real show photography into
assets/gallery/.
Cue 05
Credits
- 20XXClient / show nameContent Manager
- 20XXClient / show nameContent Manager
- 20XXClient / show nameContent Manager
- 20XXClient / show nameContent Manager
- 20XXClient / show nameContent Manager
- 20XXClient / show nameContent Manager
- Formats
- Corporate keynotes · General sessions · Product launches · Broadcast · Hybrid
- Tools
- PowerPoint · Keynote · Google Slides · Playback systems · Media servers
- Scale
- Single-screen breakouts through multi-screen arena shows
Cue 06
Building the tools
Tim is Chief Operating Officer of SmartSuite Tech, where the same frustrations that show up on show site get built into software. Presenter tools have always been designed by people who don't run shows — SmartSuite is what happens when the people who do get to design them instead.
- Role
- Chief Operating Officer
- Company
- SmartSuite Tech, Inc. ↗
- Field
- Presentation & live-show software
- Position
- Patented technology
-
ShippingPatented
SmartNotes
Speaker notes that live inside the deck. Clickable pages of notes per slide, no scrolling, and everything saved right inside the .pptx — so the notes travel with the file instead of beside it.
-
In developmentPatented
SmartPrompt
A pro teleprompter built into the slides. Script where it's needed, scroll-free and cue-friendly on stage, across PowerPoint, Keynote and Google Slides.
Cue 07
The operator
I've spent my career in the part of a show nobody in the audience thinks about. It suits me. I like knowing how a thing works all the way down — not just my piece of it, but why the segment before it exists and what the director is going to want when it changes.
That tends to make me the person producers call when a show is complicated, when there are too many stakeholders, or when last year's went badly and this year's can't.
- Based
- TODO
- Travels
- Anywhere the show is
- On headset
- Comfortable
- Under pressure
- Quiet
Cue 08
Contact
Tell me about the show. Dates, venue, screens, how many presenters. I'll tell you straight away whether I'm the right fit and what I'd want to see first.
- hello@example.com
- /in/timkloppenburg
- Availability
- Taking bookings
- Lead time
- The earlier the better — phase 01 is the whole point