All guides

Help Center · RiderSmith

Send the rider

Export a PDF, send the input list as CSV or give each venue its own link to read and answer — each with a version number, a list of what changed, and a Sent panel that shows who got which version.

Open RiderSmith

On this page
  1. Versions and what changed
  2. The PDF
  3. More than one language
  4. The input list as CSV
  5. Venue links: one per recipient
  6. How the venue answers
  7. Sent versions and responses (full version)
  8. Before you send

A venue reads a rider once, in a hurry, and usually not the newest one. RiderSmith puts a version on everything you send so nobody has to guess.

Versions and what changed

Every PDF, CSV or venue link you send becomes a version: Version 1, Version 2 and so on, with the date. Next to the export options RiderSmith shows where you stand — "Not sent yet", "Version 3 · sent … — nothing changed since", or how many changes the next export will carry. What changed lists them: a section added, two channels more, a new power line.

Tick Print what changed on page 1 to put that list at the top of the next PDF and the venue link, so the house tech sees at a glance what is new since the rider they already have.

Duplicating a rider starts the copy at version 1.

The PDF

Export PDF builds the document with your logo in the header, the band photo after the contact block and the pictures you attached. Every page carries the band, version, date and your phone number in its footer (the email address when there is no phone number), with "Page x of y". Dates are written with the month spelled out — "5 Nov 2026" — so a venue abroad can't read them the wrong way round. The file is named band · "Tech Rider" · venue · date · version, for example "Velvet Nova - Tech Rider - Molotow - 2026-11-05 - v3.pdf". Under the footer sits a small Assembled with RiderSmith · squaresmile.de line; untick "Assembled with RiderSmith" line in the PDF footer to leave it out (full version).

Print sends the live preview to the browser's print dialog instead.

The PDF export covers the Latin, Greek and Cyrillic languages. For a Japanese, Korean or Chinese rider RiderSmith explains the other way: Print, then choose "Save as PDF" in the print dialog — the browser has the fonts for those scripts.

More than one language

Under Also in these languages tick every language the venues need — English and Spanish next to a German rider, for example. Then choose how they print:

  • Side by side in one PDF (one extra language): every section heading and standard clause prints twice — "Kanalliste / Input List", the German clause followed by the English one.
  • One PDF per language (always, from two extra languages on): each language becomes its own document — headings, labels, dates and standard clauses all in that language. Export PDF then asks which one: a button per language, or All languages (ZIP) for all of them in one download. Every file is the same version of the rider, named like "… - v3 - ES.pdf". Preview and print in picks the language the preview and Print show.

Your own translations

RiderSmith never translates what you wrote yourself — not your own blocks, not a standard clause whose wording you changed. Instead, when you open such a clause with ✎, it offers Your translation (English) for each extra language: a heading and a text, in your words. The clause shows a small badge per language — ✓ translated, — not yet.

If you change the original after translating it, the translation stays and says The original changed since you translated this — check it (badge ⚠). Fix the translation, or press Still right if it still fits.

A clause without a translation for a language prints as you typed it in that language's document — and the export tells you first: "1 of your clauses have no Spanish translation — they will appear in German". Your translations are part of the rider and sync with it like the rest of it; nothing is sent anywhere to be translated.

The input list as CSV

Input list (CSV) saves the input list as a spreadsheet file that opens in Excel, Numbers or LibreOffice — for the engineer who wants to copy it into their own sheet or console file. Languages that write decimals with a comma get a semicolon as the separator.

Venue link (full version) opens Venue links: one per recipient. Each venue, promoter or crew gets its own link. They open it without an account, read the version you sent and can accept it, with or without changes.

  1. Press Link for another recipient. RiderSmith asks Who gets this link? — prefilled with the venue and city. Name the recipient, so you know whose answer is whose: "Docks Hamburg — Promoter".
  2. Create link. The link appears in the list with its recipient, "Version 3 · updated … · works until …", how often it was opened, and Answered once the venue has answered.
  3. Copy the address and send it however you like.

After you change the rider, the link's button reads Send version 4: the same address then shows the new version, so the venue never has to look for a new link. While the version hasn't changed the button reads Update link — it sends the same version again, for example after you ticked the contact details.

  • Contact details stay out unless you tick Include contact details (phone, email). The contact person and web address are always shown.
  • The page shows the rider language — with the second language beside it when you print side by side. With one PDF per language it shows the rider language only; send the venue its own language as a PDF.
  • Stop sharing (press twice) ends a link at once; the page then says "Link expired". You can also delete it under Share links on your account page.
  • A link works for 90 days after the last update, or until 30 days after the show date if that is later — never longer than a year. An account can hold 50 live links.
  • The page is closed to search engines, but anyone who has the link can read it. Send it only to people who need it.

The venue link needs you to be signed in; the rider itself works without an account.

How the venue answers

On its link the venue reads the rider and, if something is outside their limits, switches on Mark changes: they strike a line through or add a short note to it. Then they enter their name, role and email, confirm they answer for the venue or promoter, and press Accept or Accept with changes (which needs at least one marked line). A plain Accept works even without JavaScript.

Each version takes one answer. After that the page shows it read-only — "Accepted with changes by Jo Berger, Promoter on …". When you send a newer version to the same link, the page says "Version 4 replaces version 3. Please review it again.", keeps the old answer visible and takes a new one. An answer is a record of agreement for that version, not an e-signature.

You get one email per answer, with replies going straight to the venue. Turn it off on your account page with Email me when a venue answers.

Sent versions and responses (full version)

Sent in the header opens, for the open rider, every version that went out. A number on the button counts responses you haven't looked at yet. At the top it says where the rider stands: "Draft — changes since version 3", or "This is version 3, as sent."

  • Every version with its number, date and What changed, and every send under it: to whom, how (link, PDF, CSV or ZIP), when, how often the link was opened, and its status — Sent, Opened, Accepted, Accepted with changes, Replaced, Stopped or Expired.
  • Copy and Stop sharing for every live link.
  • Compare versions — pick an older and a newer version and see which rows, clauses and texts were added, removed or changed.
  • View response shows the venue's answer over exactly the version they answered: who, their email, the struck lines and notes.
  • Start a new version from this response takes the struck lines out of your draft and turns the notes into Venue notes. You can undo it for 10 seconds. Then send the next version.
  • Download agreed version (PDF) prints the version as the venue answered it — struck lines crossed out, notes under their lines, and "Accepted (with changes) by … on …" in the document. The file name ends in "- agreed.pdf".

Venue notes at the top come from responses. They are not printed; mark each one Done when you've dealt with it.

The record of sent versions and answers is deleted twelve months after the show date, when you delete the rider, or with your account. Deleting a sent rider warns you first — download the agreed PDFs before, if you need them.

Before you send

  • Keep health details out of the rider: allergies, intolerances, religion, passport numbers and dates of birth. "On request" is enough — tell the promoter or caterer directly. RiderSmith reminds you in the hospitality section.
  • Check the Rider language — the venue's language, not yours.

Was this page helpful?