ACCESSPUBLICFORConference organisers, churches, speaking events

Conferences & churches

Two very different rooms with the same underlying problem: a person at the front who cannot see a clock, and a room that will not tell them.

The problem

The speaker has twenty-five minutes and no clock. At thirty-eight minutes somebody starts waving from the back of the room, which everybody sees, and the session after theirs loses its Q&A.

What NextSet does

A stage timer the speaker can see and the audience cannot, counting down their own time. A wrap-up call one tap away. Nobody waves.

Conferences

Build the agenda as sessions with lengths — twenty-five minutes is the default session, five the default gap. Speakers go on the agenda so the room screen can say who is next without anyone typing during the day.

Surface	Faces	Shows
Room screen	The audience	Current session, next session, and the clock.
Stage timer	The speaker	Their own time remaining, and your calls to them.
Green room	The next speakers	Who is on, who is next, and how long is left.

Your presets are Q&A NOW and BREAK — 15 MIN, plus the universal timing and safety ones.

Churches

The order of service is the running order: fifteen-minute items with three-minute gaps by default. Worship, announcements, offering, message, closing. Your team sees the same plan, and a service that is running eight minutes long is a fact on a screen rather than an argument afterwards.

Presets are OFFERING and CLOSING SONG. The platform and green room screens exist here, because these rooms do have them.

Multi-service Sundays

If you run the same service twice, build it once and reuse it. The second service is a copy with its own clock — including its own honest record of where it ran long, which is the only reliable way to find out that the announcements are always the problem.

Streaming

Both rooms stream more often than they used to. The clock and current item can be composited into your stream as a browser source with a transparent background — see Screens and displays.