Changing the words your crew see

The live run of show your crew open is written in 1pm's words. The requests section is headed "Requests all crew", the two free-text panels above it are "Important notes" and "Your notes", the box you ask them to write in is headed "Notes to planner", and the bar that appears when they have answered everything says "All done. / Check, then submit. / Submit".

Those are reasonable defaults and several of them are wrong for a given account. "Requests" is 1pm's word for it rather than your reader's. "Submit" is right for a compliance pack and stiff for "send us your details". And "Notes to planner" is not a label at all, it is a question, so what it asks decides the quality of what comes back.

The Wording tab on an event's settings lets you rewrite all of it, either for one event or for your whole account.

Where it is

Open the event and click the gear beside its name (Event Settings), then the Wording tab. It sits between BEO and Options. From the Events list, the row menu's Settings opens the same form.

The tab has two halves. The top one is Crew, the plural and singular pair covered in renaming crew on an event, which moved here from Options. Everything below it is new.

Two things to know before you go looking:

• The event has to exist first. The fields are keyed to a saved event, so they are not on the create form. Make the event, then reopen its settings.
• Templates do not have them. A template has no crew reading anything, so the section is left off.

Every box is an override

Each field is empty until you type in it, and empty means "use what I would otherwise inherit". The greyed-out text inside each box is exactly that inherited wording, so you can always see the words you are replacing before you replace them.

Clear a box and save, and the inherited wording comes back. There is no way to leave a heading blank: a field with nothing but spaces in it falls through to the default rather than rendering an empty heading.

Reset to default, at the top right of the Requests section, empties every box in one go. It only clears the boxes on screen. Nothing is written until you press Save, so closing the form without saving gets your words back.

What you can reword

The requests section. Its heading (default "Requests all crew", which follows whatever you call crew on this event) and an intro paragraph above the list. The intro is new and has no default, so nothing renders until you write one. It is the right home for "please complete everything below before 1 May": before this existed, that sentence had to go in the event-wide notes, where it reached everyone whether they had requests or not.

The bar that appears once they have answered everything. Three strings: a heading ("All done."), the line under it ("Check, then submit.") and the button itself ("Submit"). Reword the button when Submit is the wrong verb, for instance "Send my details".

Message once they have finished. The confirmation that replaces the default "All required requests completed" once they press the button. This one reaches further than the screen: it also leads the confirmation email. It used to live in the Requests panel on the planner and has moved here.

The two notes panels at the top of the run of show. One is written for everybody on the event ("Important notes") and one is written for that person alone ("Your notes"). Their headings are the only thing telling a reader which is which, so if yours are doing real work, say so: "Everyone read this" and "For you specifically".

What you ask them. The notes box crew write back into: a heading ("Notes to planner"), the question under it ("Anything the planner should know before the day? Arrival, access, parking, drop-off.") and the greyed-out example inside the box ("e.g. I need lift access on arrival"). This section only appears when the event actually collects those notes, which is the Notes to admin toggle on the Options tab. Turn that off and the wording for it disappears too, because there would be nothing on screen to word.

Lengths are generous but finite: 120 characters for the requests heading, 80 for the other headings, 40 for the button, 200 for the example answer, 300 for the question, 1,000 for the completion message, and 2,000 for the intro.

One event, or all of them

Under the fields is a checkbox: Use the wording above on my other events too. It covers everything from Requests down, not the Crew words at the top, which have their own Set as default box.

Ticking it writes your wording to your account, and the account layer is a live fallback rather than a copy. That means it reaches events that already exist, not just new ones, as long as they never set wording of their own. Change what you call requests in March and every event still using the default says the new thing, including the ones you created in January.

Two consequences worth having straight:

• An event with its own words keeps them. Saving this event's wording gives it an override, so it will not follow a later change to the account default. If you want it to follow again, clear its boxes.
• A blank box clears that line's account default too. Ticking the checkbox promotes exactly what is on screen, blanks included, so a field you left empty puts 1pm's shipped words back everywhere that inherits.

This differs from the Crew pair above it on purpose. Crew wording is copied onto new events as they are made and never touches existing ones. The wording below it is inherited live. The two behave differently because they answer different questions: "what did we call crew on that job" is a fact about one booking, while "we call our requests Documents" is a fact about the business.

Where your words show up

Your wording replaces the defaults everywhere the event is read by someone who is not you:

• The live run of show behind a share link, including a client's copy.
• The printed and PDF copy, which carries both your headings so paper and screen agree.
• The public link, for the event-wide notes heading.
• The confirmation email, for the completion message.

Your own planner screens are not renamed. They keep 1pm's labels, so the Requests panel is still headed Requests however your crew read it. The one exception is the Crew pair at the top of the tab, which does relabel your screens as well.

Changes land on the next page load. A crew member with the run of show already open sees the new wording when their page refreshes, which for a live event is usually within seconds.

Related articles

• Renaming crew on an event covers the plural and singular pair at the top of the same tab.
• Renaming events, crew and spaces covers the account-wide renames on your profile: run of show, event, space and crew.
• Requesting documents and info from crew covers the requests themselves, which is what the wording on this tab wraps around.
• Event notes covers the two notes panels whose headings you are editing here.