Documentation has a discovery problem. It is written carefully, it answers the question, and at the moment someone needs it they are mid-shift with a microphone open and will not go looking.
Help that lives inside the application, one key away, gets used.
What F1 covers
- The full keyboard shortcut reference.
- Playlist management.
- Jingle configuration.
- Playback controls.
- Play history.
- Preferences and customisation.
- Tips and practical guidance.
The shortcut reference is the one that earns its place. Shortcuts are exactly the thing people half-remember, and the cost of checking has to be lower than the cost of guessing.
Why not a website
An external documentation site assumes the studio machine has working internet, that the operator will alt-tab away from the playout system while live, and that they will find the right page.
None of those hold reliably. The studio PC may be deliberately offline; the operator may be mid-link. In-application help has none of those dependencies.
Troubleshooting where it is needed
Common problems are documented alongside the features: audio playback issues, database errors, licence activation problems, playlist loading errors.
These pair with the diagnostics already in the interface. The system health indicator reports licence validity, audio output, database connectivity and AI state, so an operator can often identify the problem before contacting anyone.
"The health indicator says the audio device is unavailable" is a far more actionable support message than "it stopped working".
Small courtesies
Tooltips throughout, and an interface that stays approachable for someone who is not a full-time engineer. Many small stations are run by volunteers who learned the system from whoever ran it before.
Software that assumes a trained operator is software that only works while that person is available.