The stage plot is spatial
The stage plot communicates positions and relationships: where the drummer sits, which side the keyboard rig occupies, where wedges point, how risers fit, and which microphones belong to each source. It should be understandable at a glance.
The technical rider is operational
The technical rider explains what the production needs in order to deliver the show. It can include audio system expectations, console and stage-box requirements, backline, lighting, video, power, rigging, staffing, schedule, contacts, hospitality, and commercial terms. Not every show needs every category.
The input list connects them
An input list translates visible sources on the stage plot into console channels and connection requirements. It often sits directly after the plot in the technical pack. Monitor mixes, outputs, and equipment lists add the next layer of detail.
When one page is enough
A solo artist or small club act may communicate everything important with a stage plot, compact input list, and a short notes section. A touring production with special infrastructure should use a full rider. The test is whether the receiving crew can plan staff, inventory, patching, stage space, and changeover without guessing.
Keep one revision across the pack
The most common failure is not missing design polish; it is inconsistent information. A revised plot paired with an old input list creates more work than a simple but accurate document. Generate the pages from one working project and put a revision identifier on the exported pack.
Build the working document on your Mac.
Stage Plot Forge keeps the visual plot, production lists, notes, and exports together in one local project.
Download Stage Plot Forge