For the line above the button
The title is the first and sometimes only line a visitor reads. Here is how to rewrite vague ones into specific promises, and how to keep that promise consistent everywhere else.
Titles get written for the person who already understands the subject, which is why so many of them say nothing. Your registrant is a stranger with a tab open at lunch and three other sessions competing; they are not trying to work out what you do, they are deciding whether tonight is theirs. A title that needs a second read loses that decision quietly, and you never see it in your list because the person simply did not arrive.
The reliable test is boring and it works: could somebody repeat this title back to a colleague as a reason to attend? Payroll checks that catch mistakes before September passes. Navigating the new landscape of financial operations passes nobody, because there is no noun in it a person would use at lunch.
Same session, two titles. The after version names the subject, the audience or the outcome.
Before: Holistic rota optimisation strategies. After: Night-shift rotas: what to change and what to leave alone.
Before: Grant applications webinar. After: Why your grant application gets refused in the first paragraph.
Before: Pixels and posterity. After: Scanning a photo archive without damaging it.
Before: An introduction to payroll. After: The five payroll checks to run before your next cycle.
Before: Q3 enablement series, session two. After: Expense rules from the first: the claims that will come back.
Before: Masterclass in mailing lists. After: A mailing list people open: what we changed, shown on screen.
No internal project names, no acronyms your own team uses, no abstract nouns standing in for work. If the sentence requires your org chart to decode, rewrite it as the thing people actually do.
A number of checks, a named moment, a decision, an outcome you can point at afterwards. Specific is not the same as grand: the five payroll checks is a promise an hour can keep and a title can be re-read on the night.
Read the title against your chapters. If the promise is the first paragraph of a refusal and the agenda has no worked example in it, the title is advertising a session you have not built.
Choose the words knowing they travel. The same line appears on the page itself, in the confirmation your registrants receive, in the reminder emails before the start, and in every invitation message you post — and a title that mutates between those places reads as three different events to somebody who was forwarded two of them. Write it once, then paste rather than retype.
Two housekeeping notes on length and labels. Keep it short enough to survive a phone screen without wrapping into a block nobody parses, and put the date and the start time in their own fields rather than stuffed into the headline; the page shows the time with its zone beside it, so a title carrying a date is a title that goes stale the moment you move the session. On labels, the product knows two: webinar and workshop. Pick whichever describes the session and leave the invented third category alone.
How it works
Put the subject down exactly as you would say it to a colleague, then mark the words a stranger could not define. Those are the ones to cut.
Say each aloud as a reason to attend. Keep the one that could be repeated at lunch and the one that names what happens afterwards; discard the clever one.
Every promise in the title needs a chapter behind it. Where one is missing, either add the chapter or drop the word.
Enter it on the page and publish. It then carries through the confirmation and the reminders, so the link you post and the email they receive say the same thing.
Questions
It is the same session name throughout: the title on the page is what registrants see in their confirmation and in the reminder emails before the start. That consistency is the reason to settle the wording once instead of rewriting it for each message.
You can edit the page, and the address stays the same, so a retitled session reads correctly for anyone opening the link afterwards. Do it thoughtfully: registrations were made against the earlier promise, so announce the change rather than letting people discover a different evening.
No. The page shows the start time with its zone label beside it and the confirmation email carries the date with a calendar file attached, so a title holding a date only duplicates those fields and goes stale if you move the session.
Sometimes, if it is the question people actually ask. Why does the handover always go wrong works because the reader recognises their own complaint. Can payroll be simplified? does not, because nobody describes their evening that way and the answer reads as a sales pitch.
Whichever it is, and those are the only two labels the product uses. A workshop implies doing something along with the session; if your hour is a presentation with questions at the end, webinar is the honest word and the agenda will confirm it for the reader.
Get Started
Specific, plain, and a promise your agenda can keep. Then let the same line carry through the page, the confirmation and the reminders.
