nexy

Use case

Confirm who checks sound levels before broadcast starts

A broadcast cannot be restarted once live, so confirming sound levels just before transmission is a one-off task with no margin for error. The person checking must finish in time to report the result before the broadcast opens.

Use one Nexy thread for one agreement: I will check the sound levels in the studio ten minutes before we go live and confirm they are correct. The other person receives a message in the chat they already use, without installing anything or creating an account; reminders stop for a task that is already done.

Try this in Nexy, freeStarts on the web. The other person installs nothing.

What it looks like

An example of people making one clear agreement and confirming when it is done.

How to do it

  1. Start one Nexy thread for the agreement. Ask the group who is available to check sound levels in the studio ten minutes before the broadcast time.
  2. Agree on exactly what counts as correct: which channels to check, what levels are acceptable, and whether a spoken test phrase is needed. The other person receives a message in the chat they already use and needs no new account.
  3. Confirm the person knows where to stand, which equipment to check, and who to tell if something is wrong.
  4. Remind the person two hours before the broadcast so they can plan to be in position. A reminder is most useful while you could still act, usually the evening before.
  5. Once the person reports the levels are correct, confirm with the group that the broadcast can proceed. Once the task is done, there are no more reminders for that completed task.

Why it works

One clear agreementOne agreement per thread keeps this specific commitment separate from the rest of the conversation.
People choose the ownerAn unclaimed task is announced to the whole group. Nexy does not choose a person or assign it for you.
Done means no remindersA person who has already completed the task is left alone. Finishing is different from receiving another reminder.

Where it stops

Keep the agreement narrow and let the people involved make the decisions.

One agreement per threadUse this thread for the specific agreement, rather than treating it as an entire project.
No automatic assignmentNexy announces unclaimed tasks to the group; the people decide who will act.
No reminders after doneCompleted tasks are not a reason to keep reminding someone.

Questions people ask

What if the person checking sound finds a problem just before broadcast?

Agree in advance who the person reports to if levels are wrong or a channel is silent. That named person must have authority to delay the broadcast or fix the problem. Write down a backup plan: if the main contact cannot be reached, who else can make the decision? The person checking sound should know how much time remains before going live, so everyone understands how urgent the problem is and whether a delay is possible.

Should the same person check sound for every broadcast?

You might choose the same person each time if they know the equipment well and are always present before broadcasts. Alternatively, you might ask whoever arrives earliest to take responsibility that day. Either approach works as long as everyone knows who is checking on each specific occasion. If you rotate the task, confirm in advance that the new person understands what to check and has been shown the equipment at least once before.

How detailed should the sound check report be?

The report must confirm that the check is finished and whether the broadcast can proceed. A short message naming each channel and stating levels are acceptable is usually enough. If something is wrong, the person should describe what they found, which channel or microphone is affected, and whether they attempted to adjust it. Agree in advance what detail is helpful and what is unnecessary: too much information at the last minute can cause confusion.

What if no one volunteers to check the sound?

Describe the task clearly to the group: what needs checking, where the equipment is, how long it takes, and exactly when it must be done. If no one offers, ask each person in turn whether they can do it, starting with those who have checked before. If everyone declines, you may need to check the sound yourself or accept that the broadcast carries more risk. Agree as a group how to prevent this situation recurring for future broadcasts.

Should the person checking sound arrive early or wait until ten minutes before?

Arriving slightly early means the person can deal with an unexpected problem without the pressure of an imminent broadcast. However, sound levels can change if equipment is adjusted or people move around the studio, so checking too early may produce an inaccurate result. Ten minutes before is usually a sensible compromise: recent enough to be reliable, but leaving a short window to report a problem or make a quick adjustment if needed.

What counts as completing the sound check?

Completion means the person has physically tested the levels, confirmed they are within the agreed range, and reported that confirmation to the group or the named contact. Simply being present in the studio is not enough: the person must perform the check and communicate the result. If the broadcast begins and the person has not yet confirmed levels are correct, the check is incomplete and the broadcast carries unnecessary risk of audio failure.

Can someone else check the sound if the first person is delayed?

Yes, if the agreed person is unexpectedly delayed, ask the group whether someone else can step in. The replacement must know what to check and where the equipment is. If no one else knows the procedure, consider delaying the broadcast or asking the delayed person to talk someone through the check remotely. Agree in advance whether a backup person will be named for every broadcast, or whether you will find a replacement only if needed.

How do you remind the person without sounding like you do not trust them?

Send a brief reminder two hours before the broadcast that acknowledges their agreement and confirms the time: for example, a short message saying you are looking forward to their confirmation at ten minutes before going live. This gives the person a chance to mention any new conflict without feeling accused of forgetting. A reminder is a practical prompt, not a test of memory, and most people appreciate a helpful note when timing is critical.

Do this with Nexy

Start free on the web. Tell Nexy what the two of you agreed on and it takes it from there: it asks, reminds whoever still has to act, and tells everyone when it is done.

Start free

No app needed to begin, and nothing at all for the other person.

Related use cases

New here? How Nexy works explains the whole thing in a minute, and the index lists every use case.

Stay posted on Nexy

We add a new use case most days and test what actually works. Get the short version by email, or a notification the moment something ships. No account, and one click to stop.

Agree who checks sound levels before broadcast starts