Operations Runbook

Use this runbook as a starting point for station procedures. Adapt it to local responsibilities and maintenance windows.

Daily Checks

  • Confirm the correct playlists are generated for the next broadcast hours.
  • Check fixed items such as news, commercials, live sources and network joins.
  • Confirm the on-air computer is running the expected Power Studio version.
  • Confirm presenters can log in with the expected permissions.
  • Check that audio routing has not changed on the on-air computer.
  • Review logs or reports for failed playlist items, missing audio or unexpected automation behavior.

Weekly Checks

  • Confirm database backups have completed and can be found.
  • Spot-check that a recent backup can be restored in the agreed test or recovery procedure.
  • Review external content workflows such as news, traffic, commercials and dynamic downloads.
  • Check recurring live sources and streams.
  • Clean up temporary production items where station policy allows it.
  • Review any plugin warnings or recurring support notes.

Monthly Checks

  • Test failover or fallback procedures during a safe maintenance moment.
  • Test remote voice tracking, VPN or Power Sync workflows used by presenters.
  • Review Windows updates, audio driver updates and antivirus changes before applying them to production computers.
  • Check disk space on audio storage, local cache folders and database storage.
  • Review user accounts and permissions.

After Updates

After updating Power Studio or a connected system:

  1. Confirm all production clients use the same intended Power Studio version.
  2. Run the Configuration Tool database update once for the shared database when required.
  3. Restart the updated clients.
  4. Test database connection and login.
  5. Test audio routing, preview routes and recording.
  6. Test Automation Mode and Live Assist Mode with a known playlist.
  7. Test critical plugins and external control systems.
  8. Test remote workflows such as Power Sync or VPN/cache if the station uses them.
  9. Review logs after the first production session.