nexy

Use case

Agree who closes the venue after an event

After a community event, someone needs to lock up, turn off lights, check windows and complete a closing checklist. The organiser wants a named person to accept this responsibility for a specific evening without sharing access codes in a group conversation.

Use one Nexy thread for one agreement: I will close the venue after the concert on Saturday and complete the checklist. 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. The organiser describes what closing involves: which doors to lock, what to check, where to leave keys, and roughly what time the handover will happen.
  2. One volunteer accepts responsibility for that specific evening and confirms they can meet for a handover at the agreed time. The other person receives a message in the chat they already use and needs no new account.
  3. The organiser meets the volunteer before leaving, hands over keys, walks through the checklist together and answers any questions about locks or alarm codes.
  4. The volunteer works through every item on the checklist after the last attendees leave, checking each room and securing the building. A reminder is most useful while you could still act, usually the evening before.
  5. The volunteer messages the organiser when closing is complete, listing what was done and confirming where keys were left. 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

How does the organiser share a closing checklist without it getting lost in group chat?

The organiser sends the checklist directly to the person who accepted closing responsibility, either during the handover meeting or immediately after someone volunteers. This keeps the checklist with the person who needs it and avoids confusion about which version is current. If the checklist changes, the organiser sends an updated version and asks for confirmation that the volunteer has seen the changes before the event.

What happens if the volunteer who agreed to close has to leave the event early?

The volunteer tells the organiser as soon as they know they cannot stay. The organiser asks the remaining attendees if someone else can take over, explains what is involved, and does a handover with the new person. If no one can stay, the organiser closes the venue themselves or postpones any non-urgent checklist items until the next day. The important thing is that someone confirms they are responsible before the original volunteer leaves.

How does the volunteer confirm closing is complete without sharing access codes in messages?

The volunteer lists what they completed from the checklist without mentioning specific codes or key locations. They might say which doors were locked, that the alarm was set, and where keys were returned, but avoid writing down the actual alarm code or describing exactly where the hidden key safe is located. If the organiser needs more detail, they can ask a specific question privately rather than requesting sensitive information in a group conversation.

What should the organiser include in the closing checklist?

The checklist should cover every task needed to secure the building: which lights to turn off, windows to close, doors to lock, heating or equipment to switch off, bins to put out, and where to return keys. The organiser includes rough timings if certain tasks must happen in order, and notes anything unusual like a temperamental lock or a fire exit that needs checking twice. The checklist should be complete enough that someone unfamiliar with the building can follow it without guessing.

How does the handover work if the organiser needs to leave before the volunteer finishes closing?

The organiser meets the volunteer while attendees are still present, hands over keys, walks through the entire checklist together, and answers questions about anything unclear. The organiser explains what to do if something goes wrong, such as a door that will not lock or an alarm that will not set. The volunteer confirms they understand everything and knows who to contact if they encounter a problem. The handover happens face-to-face so the volunteer can ask about anything uncertain before the organiser leaves.

What if something on the checklist cannot be completed, like a window that will not close?

The volunteer tries reasonable solutions, such as checking if something is blocking the window or if a different latch works. If the problem cannot be fixed quickly, the volunteer messages the organiser to explain what is wrong and asks whether to proceed with closing anyway or wait for help. The organiser decides whether the issue is urgent enough to return, whether someone else should be called, or whether it can wait until morning. The volunteer does not leave the building unsecured without confirmation from the organiser.

How does someone volunteer to close if they have never done it before?

The person tells the organiser they can stay but have not closed the venue before. The organiser decides whether to pair them with someone experienced for this event, spend extra time during the handover explaining everything, or simplify the checklist for a first-timer. Many organisers appreciate a new volunteer and will make sure the handover is thorough. The volunteer should ask about anything unclear during the handover rather than guessing later when they are alone in the building.

How does the organiser know the building is definitely secure if they have already left?

The volunteer sends a message when closing is finished, confirming each major task from the checklist: doors locked, alarm set, keys returned. The organiser can ask a follow-up question if anything is unclear, such as whether a specific door was definitely locked or whether the back gate was closed. If the organiser does not receive a completion message within a reasonable time after the event ended, they contact the volunteer to check everything is finished. Some organisers drive past later to visually confirm the building is dark and locked.

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.