Skip to main content

Day-To-Day Operations

This page summarizes the normal daily workflow for operators and admins. It is intended as the practical runbook for routine operation rather than deployment or deep troubleshooting.

Daily Operating Cycle​

For most teams, daily work follows this pattern:

  1. confirm the system is healthy
  2. review any planned content changes
  3. update assets or schedules as needed
  4. validate results in preview
  5. monitor the live state through the dashboard
  6. use logs or escalation paths if something looks wrong

Start-Of-Shift Checks​

At the start of a shift, operators should check:

  • the dashboard for target, player, and system health
  • whether Quick Play is enabled or disabled as expected
  • whether any screens or players look degraded
  • whether any planned schedule changes are pending review

Start Of Shift Dashboard Stub screenshot: start-of-shift dashboard view showing target health, Quick Play state, and systems status. Save final image at packages/docs/screenshots/operations-start-of-shift-dashboard.png.

If the system already looks degraded at the start of a shift, move into the relevant troubleshooting workflow before making new changes.

Routine Content Workflow​

The normal content workflow is:

  1. upload or review assets
  2. organize assets with tags or asset blocks if needed
  3. edit or create events
  4. confirm the targeted screens
  5. review the calendar placement
  6. use preview to validate the generated result
  7. publish when ready

See Content Publishing.

Schedule Validation Workflow​

Operators should treat preview as a standard part of daily work, especially when:

  • multiple events overlap
  • timing matters
  • Quick Play was recently used
  • a screen serves high-visibility content

The safest sequence is:

  1. confirm the selected screen
  2. confirm the intended time window
  3. review preview
  4. compare with the calendar if anything looks unexpected

Quick Play Usage Boundaries​

Quick Play should remain a temporary override tool.

Use it for:

  • urgent overrides
  • short manual takeovers
  • controlled testing on selected screens

Do not use it as a replacement for normal scheduling unless the site has a deliberate operational policy for doing so.

Before ending a shift or handoff, always confirm whether Quick Play is still active.

What Operators Should Escalate​

Operators should escalate to admins or deeper support when they see:

  • repeated player or output instability
  • degraded systems that affect operation
  • schedule results that do not match preview or documented behavior
  • upload or processing problems that affect multiple assets
  • authentication or license issues

What Admins Usually Handle​

Admins usually own:

  • preferences and defaults
  • users and access changes
  • extensions and schema changes
  • system integrations and restart controls
  • deployment-level recovery actions