One service, start to finish
A Sunday with LogosPilot
Not a feature list. One ordinary Sunday, in order, showing where LogosPilot participates — and, just as deliberately, where it stands aside and lets your existing tools do their job.
Earlier in the week
Someone prepares. Passages that are known in advance are prepared as slides, composed for the display they are going to. Existing presentation files can be rendered and driven alongside Scripture content, so material you already have does not need rebuilding.
Not here: the order of service
LogosPilot does not plan services, schedule volunteers or hold a run sheet. That work stays where your church already does it. It is not a missing feature — it is a boundary, and it does not change with plan or scale.
Arrival
The desktop host in the booth is switched on. LogosPilot runs on that machine — not in a browser, and not on someone else’s server. Displays are listed, the certified production software is connected, and the license is active.
If the building’s internet is down this morning, none of the above changes. Licensing operates on a signed lease and does not need to reach us during a service.
The service starts
Songs begin. LogosPilot is not involved. Lyrics, the song library and CCLI reporting belong to your worship software, and LogosPilot works alongside it rather than replacing it.
At the desk, the volunteer is watching rather than typing. Nothing is on the congregation display that should not be.
The message
This is the part LogosPilot exists for. The speaker says a reference, in the middle of a sentence, the way they were always going to say it.
| Step | What happens | Who can intervene |
|---|---|---|
| It listens | Audio from the room is transcribed as it is spoken. Nothing is displayed and nothing has been decided | Stop automation at any time |
| It finds the passage | The reference is matched against the translation your church selected. This produces a candidate, not a decision. Confidence is assessed before anything moves toward a display | Search and select manually — a manual choice supersedes automation |
| It prepares the slide | The text is retrieved from the licensed provider you configured, or from local text when the network is unavailable, and composed for its display | Clear output |
| It displays | The passage appears | Clear output |
If it is not sure, nothing happens
Low confidence produces no slide and no display change. A blank screen is recoverable. Wrong Scripture in front of a congregation is not.
The text is never generated. It is retrieved and shown exactly as published.
What each screen is doing
Each output carries independent content, composed for that surface rather than scaled from one master.
| Surface | Carrying |
|---|---|
| Congregation display | The passage |
| Stage display | Content for the person speaking |
| Confidence monitor | What is current and what is next |
| Lobby and overflow | Independent content per output |
How many run at once is limited by the graphics hardware in the desktop host, not by LogosPilot.
Broadcast and recording
Program content is sent to your production software — OBS Studio or vMix, at the certified versions — which does the switching, encoding and streaming. LogosPilot is not an encoder and does not host video. Connection health is reported and reconnection is attempted.
Audio recording runs locally on the desktop host, and the finished file is written there with its checksum.
When something goes wrong
| Failure | What the congregation sees |
|---|---|
| The audio source is lost | Nothing. Detection suspends; manual control continues unaffected |
| The internet drops | Nothing. The service runs to the end |
| A component stops responding | Nothing. A watchdog restarts it rather than leaving the service without output |
| A license condition becomes true | Nothing. It is recorded and applied after the service ends |
The common thread: a condition that becomes true during an event is recorded and dealt with afterwards, and never appears on a display a congregation can see.
End of service
Output is cleared. The recording is finalized on the desktop host with its checksum. Anything that was deferred during the service — a license condition, a background check — is applied now, when nobody is watching a screen.
The machine is shut down. Nothing needs to be uploaded, reconciled or synchronized before it can be turned off.
Where it was not involved
Worth stating plainly, because it is the shape of the product: for most of that Sunday, LogosPilot did nothing at all.
| Part of the morning | What owns it |
|---|---|
| Planning the service, scheduling volunteers | Your church management system |
| Songs, lyrics, CCLI reporting | Your worship software |
| Switching, encoding, streaming, hosting video | Your production software and encoder |
| Attendance, membership, giving | Your church management system |
| Writing or shaping the message | The person speaking |
LogosPilot runs the room, not the office. It participates in one part of one hour, and it is built to do that part without being noticed. The complete list of boundaries, and the reasoning behind them, is on About.