RiderSmith

A stage plot is one page of a tech rider; the rider is the whole document a venue receives, and for most bands it is a Word file with last year's phone number in it. RiderSmith is an assembler, not another editor: it builds the document from parts your other tools already hold, and it tells the venue which version they are reading.

Who it is for

• Touring and gigging bands who send the same rider to every promoter.
• Tour and production managers who keep one rider per venue and date and need to show what changed since the last one.
• Bands touring abroad who want an English rider from a German interface, or German and English side by side.

What it does

• Sections you switch on and reorder. The contact block sits on top; below it FOH & PA, monitoring, input list, wireless, backline, power, stage plot, schedule, hospitality, merchandise and your own notes. Most sections have a table; all take free text and pictures.
• Standard blocks in the rider's language. Fourteen written clauses for PA, monitoring, changeover, power, hospitality and more. The rider's output language is set per rider, independently of your interface language; your own text stays exactly as typed. More languages print side by side in one PDF or as one PDF per language, with your own translations of the clauses you rewrote — see Send the rider.
• Imports from the suite — the input list from Stage Plot Generator, the wireless plan from FreqSense, the site power total from PowerSense and set lengths from SetlistForge, each through a preview. See Import from your other tools.
• Three ways to send it — a PDF, the input list as CSV, or a read-only Venue link. Every one of them carries a version number, and the next one can list what changed. See Send the rider.
• One rider per situation. Duplicate a rider for the next venue, festival or acoustic set and change only what differs.

Editing

• Clauses in place. ✎ Edit this clause opens its heading and text where the clause stands; Done closes it, Back to the standard text undoes your wording. Changed wording prints exactly as typed and no longer follows the rider language — unchanged clauses still do. With more document languages the clause also takes Your translation per language.
• Clause order. Drag a clause by its handle, or focus the handle and use the arrow keys.
• Undo. Removing a row, a clause or a section shows Undo for a few seconds.
• Rows. A new row takes the cursor straight away. Enter moves to the next row, and in the last row it adds a new one.
• Your own blocks. Save free text as my block keeps your wording — your in-ear setup, your van — under My blocks for every future rider.
• On a phone. RiderSmith works on a phone — updating tonight's venue and date from the van is a phone job. On a narrow screen every table row becomes a card with labelled fields.

Your data

Riders, your own blocks and every attached image sync with your account. Edits from two devices are merged rider by rider, and a new device loads your riders before it saves anything. On a shared computer the riders stay with the account that made them — see Account sync.