Format your request descriptions, and write the instructions once

Requests are how you ask crew and suppliers for the thing you need: a certificate, a headcount, a song list, a signed form. The description is where you tell them exactly what “the thing” is, and it was starting to feel cramped.

A real editor, not a code you have to remember

The description field is now a proper rich-text editor. Bold and highlight work the way you’d expect, with no stray markers cluttering the box while you type. You see the formatting as you write it, and what crew see on their card matches what you saw while writing. Nothing dangerous gets pasted in, and the long-standing 500-character limit still applies.

Under the hood we still store plain, safe markup (never raw HTML), so every surface keeps rendering it identically: the crew card, the print, and your own live run of show. The only thing that changed is that you no longer have to think about the markup at all.

Write the brief once with reusable descriptions

If you collect the same thing across several events (public liability cover, a dietary count, an account code), you’ve probably retyped the same instructions more than once. Now a custom contact field can carry its own default description. Map a request to that field, leave the request’s own description blank, and it inherits the field’s wording automatically.

Edit it once on the field, and every request that leans on it stays in step. Override it on an individual request whenever a one-off needs different wording.