Skip to main content

Event Control

Event Control is the live log for the show. It is built for speed first: capture the issue, keep the stack moving, then add detail as the situation develops.

DesktopEvent Control workspace desktop view
MobileEvent Control workspace mobile view
The quick log form, live stack, and connection status are visible together on desktop and collapse into focused panes on mobile.

Start a log​

Use the quick log form at the top of Event Control.

  1. Pick a category.
  2. Add the caller.
  3. Write a short title or initial description.
  4. Add the first action if you have it.
  5. Select Start Log.

The category is searchable. Type a few letters, pick the best match, and Nexus applies the category defaults such as priority and lead agency where the setup allows it.

Best practice

Start the log as soon as the control room has enough information to act. A short, accurate first log is better than waiting for a perfect description.

Work the stack​

The stack is the list of logs for the event. It shows log numbers, status, category, priority, title, timing, and visible indicators such as closed state. Select a row to open the detail pane.

The live connection status tells you whether browser updates are connected. When it is live, updates from other users should appear without a manual refresh.

caution

If the live connection is not connected, keep working but be careful before making duplicate logs. Refresh once connectivity is back if the stack looks stale.

Update a log​

DesktopEvent Control log detail desktop view
MobileEvent Control log detail mobile view
Open a log to update category, state, agencies, location, comments, and attachments.

The detail pane is where the log becomes useful for handover.

  • Change the State as work progresses.
  • Adjust Priority and Category if the first choice was wrong.
  • Set lead and additional agencies so ownership is clear.
  • Add comments for actions, decisions, and updates.
  • Add attachments when the log needs evidence or a related file.
  • Close the log when the issue is finished.

Keep comments factual. Write what changed, who owns the next action, and any decision that someone might need later.

Attachments​

Attachments are stored against the log. Where preview generation is enabled, image-style thumbnails may appear after upload processing. Use attachments for evidence, plans, photos, and other supporting files. Do not use them as the only record of an important decision; add a comment as well.

Close a log​

Close a log when the situation is done and no one needs to act on it. Closed logs can still be searched and exported.

note

Nexus keeps closed logs available because they are often needed during handover or after-show review. Hiding them from the live stack is for focus, not deletion.