Automatic run of show updates
The live run of show updates without anyone clicking refresh. When you change something in the planner, your crew see the change within a second or two on their phones. This article explains what triggers an update, how it reaches your crew, and what to expect when the connection is patchy.
How updates flow
1pm uses a one-way live connection from the server to each open browser tab. When you open the planner or a crew member opens their live link, the page subscribes to updates for that event. Any change the server records triggers a push to every open subscriber.
There is nothing to set up. Real-time updates are on by default whenever both the planner and the run of show are open anywhere.
What triggers an update
Most things that touch the event push an update:
Adding, editing, or deleting a timeline item.
Reordering items in the planner.
Changing an item's responsible crew member.
Updating an item's start time, duration, title, details, or location.
Editing the event header (name, date, status, space, PAX).
Changing event notes.
Adding or removing attachments.
Generating or revoking share links.
Crew see most of these within a second or two. Some inputs in the planner update intelligently after you stop typing, not on every keystroke.
Please be aware that updates are designed to show immediately where possible (without in some cases pressing the enter key).
How long the update takes
A typical update reaches a crew member's open page in about one to two seconds. Times can stretch under poor network conditions, but the system is designed to keep working over standard venue Wi-Fi and mobile data.
Crew connection states
On the crew view, a small connection indicator near the top of the page shows one of three states.
Online. The live connection is active and updates are flowing.
Offline. The browser cannot reach 1pm. Updates are not flowing.
Syncing. The connection has just come back after an offline period and queued actions are catching up.
If a crew member's connection drops mid-event, they keep seeing the run sheet as they last saw it. Any action they take while offline (Start, Mark finished, Done) is queued locally. When the connection returns, the queue drains automatically.
Multiple devices, multiple tabs
You can have the planner open in multiple tabs at the same time. Each tab gets its own live connection and stays in sync with all the others. The same applies to crew: if a crew member opens their link on a phone and a tablet, both update.
Edits you make on one device propagate to every other open tab immediately, including your own other tabs. You do not need to refresh after saving.
When the connection fails
If your browser tab loses the live connection, the changes you make are still saved to the server. The next time the connection comes back, your tab catches up automatically. Live updates are the delivery channel; the database is the source of truth. Edits never depend on the connection being open.
If something looks out of date and the connection indicator says Online, a hard refresh (Ctrl+R or Cmd+R) re-fetches the current state. You should not need this in normal use.
