Skip to content

Operations

Generate run of show PDFs from your data

A run of show is read one row at a time, often in a dark room by somebody who is already late. Times down one edge, the cue beside them, and the contingency written down before it is needed.

3 designs, each a separate take on the same document rather than a recolour of one layout: Minimal, type-led, Boxed form planner and Framed ceremonial. Every preview below is the actual compiled output, not a mock-up.

Open one in the editor and render it from your own JSON over the API — 1 page of A4 portrait, the same engine either way.

Designs
3
Page size
A4 portrait
Length
1 page
Document family
Analytical report

Run of show designs

How the run of show designs differ

Same document, same data model, 3 different arguments about how it should look on paper. Pick on layout and typography — the content behaves identically.

Design Layout Palette Typefaces Pages
Call Board Minimal, type-led Bark & saffron Inter only 1 · A4 portrait
Cue Sheet Boxed form planner Ink & magenta JetBrains Mono + Inter 1 · A4 portrait
Stage Black Framed ceremonial Slate & violet Playfair Display + EB Garamond 1 · A4 portrait

What your data drives in a run of show

Each design is authored against an explicit reflow contract, so it is defined up front which blocks are emitted once per record and which fields absorb longer content. That is what stops the layout falling apart at a hundred rows.

Design Repeats per record Grows with your data
Call Board one call per row, its time and the people called hung in the margin; the standing notes every call's instruction; the standfirst; any standing note
Cue Sheet cue rows down the sheet; the fact cells across the head band; the contingency boxes any cue's item, cue or note text; the contingency lines
Stage Black programme items down the axis, each with its credit and its running time; the credit lines any item title or credit that wraps; the note under the interval

Start from one of these run of show designs

Open a design in the editor and the agent reshapes it around your schema — then render it from your own data over the API, or let your users edit it in the embedded editor.