Running Event Signage From a Browser Tab
The hard part of event signage is handover, not design. How a Share link moves a finished banner to whoever is holding the screen, and what goes wrong on site.
An event is not one sign. It is the same screen saying different things at 9am, at noon, and during the closing session, usually held by different people who were not in the room when you set it up.
That is the actual problem at an event, and it is not a design problem. It is a handover problem.
Share is how a banner survives handover
The Share link carries the Text and every appearance setting inside the URL itself. Open it on another device and you get the identical banner — same words, same colours, same speed.
This matters more than it sounds. It means you can build the day's banners in advance, at a desk, and send each one to whoever needs it. A steward on the door gets the door link. Registration gets the registration link. Nobody has to be talked through the controls over the phone while a queue builds.
Nothing is stored on a server, so there is no account to share and nothing to expire. The link is the banner. Keep them in whatever you already use — a pinned message, a note, a shared doc.
Build the day's set before the day
Write each banner once, share each one to itself, and keep the links in order:
Five minutes at a desk beforehand replaces twenty distracted minutes on site. The links do not go stale and they cost nothing to prepare.
Held signs and mounted signs want different things
A held sign — a pickup at the entrance, a name at a station — is read from a few metres by one person scanning for it. Short line, tall letters, and landscape. Adding a greeting to a name halves the letter height and buys nothing.
A mounted sign on a stand is read by many people at varying distances, often while walking past. It can carry a longer line, but it needs a slower scroll, because a walker gets one pass and no second chance.
The rule underneath both: work out where the reader stands, and let that decide how many words you are allowed. Every centimetre of capital-letter height buys a bit over a metre of comfortable reading distance, so a phone in a hand covers an entrance, not a hall.
Practical things that go wrong on site
The screen sleeps. A device left on a stand will lock unless you stop it. Sort this before the doors open, not while somebody is waiting.
Battery. Fullscreen Play on maximum brightness for a whole day needs a charger, not a full battery at 9am.
Venue lighting. A hall lit for a stage eats contrast. What looked fine in the office looks grey under lighting rig spill, so bias brighter than you would at a desk.
Someone edits the wrong thing. If a helper has the link and starts typing, they change their copy, not yours. That is usually what you want, but it is worth saying out loud so nobody assumes a change propagates to the other screens. It does not.
When to reach for something else
If the content needs to change automatically — a live schedule, a feed, results updating themselves — this is the wrong tool. It shows what you typed until somebody types something else.
And if the screen is a projector running from a presentation deck, keep it in the deck. Introducing a browser tab into a running AV setup at a live event is a risk with no reward.