Use case
Agree who updates the group after a site visit
After a site visit, the rest of the group needs to hear what was found and what happens next. Agreeing one person to deliver that update by a specific time means everyone gets the same information without repeated questions.
Use one Nexy thread for one agreement: I will send the site visit update to the group chat by six o'clock this evening. 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
YouCan you send the site visit update to the group chat by six o'clock this evening?
ThemYes, I will send the site visit update to the group chat by six o'clock this evening.
NexyOne agreement: I will send the site visit update to the group chat by six o'clock this evening.
ThemDone—I have sent the site visit update to the group chat.
NexyDone. There will be no more reminders for this completed task.
An example of people making one clear agreement and confirming when it is done.
How to do it
- Start one Nexy thread for the agreement. Decide what the update needs to include: findings from the visit, photographs if useful, decisions made on site, and any actions or next steps for the group.
- Choose one person who attended the visit to write and send the update—usually whoever took notes or has the clearest view of what was agreed. The other person receives a message in the chat they already use and needs no new account.
- Agree the deadline for sending the update, allowing enough time to gather thoughts and photos but soon enough that people can act on the information.
- Confirm where the update will be sent: the main group chat, a specific thread, or a message to named individuals who need to know. A reminder is most useful while you could still act, usually the evening before.
- When the update is sent, the person confirms it is done so others know to look for it and no one else duplicates the effort. Once the task is done, there are no more reminders for that completed task.
Why it works
Where it stops
Keep the agreement narrow and let the people involved make the decisions.
Questions people ask
Who should send the update if more than one person attended the site visit?
Choose whoever has the clearest overall picture or took the most complete notes during the visit. If responsibilities were divided on site, one person can still gather input from the others and send a single combined update. That way the group receives one coherent message rather than several partial reports. If two people have distinct areas to cover, agree who sends which part and make clear in the update that a second message will follow, so the group knows to expect both.
What should the update include if nothing significant was found during the visit?
Send the update anyway, confirming that the visit happened, what was checked, and that no issues were found or no changes are needed. The group still needs to know the visit is complete and that silence does not mean something was missed. Include any observations that might be useful later, such as general condition, access details, or minor points that do not need immediate action. Reporting a clear outcome prevents others wondering whether the visit actually took place or whether bad news is being delayed.
How soon after the visit should the update be sent?
Agree a specific time that gives the visitor enough time to travel back, review notes or photographs, and write a clear summary, but is soon enough that people can act on any urgent points the same day. For a morning visit, early evening is often realistic. For an afternoon visit, the following morning might be more practical. If decisions depend on the findings, the update becomes more urgent. Always state the deadline clearly when making the agreement so everyone knows when to expect the information.
What happens if the person who agreed to send the update cannot do it by the deadline?
They should tell the group as soon as they know there will be a delay, explain why, and give a new time when the update will arrive. If the delay is significant or they cannot complete the update at all, they can ask someone else who attended the visit to take over, passing on their notes or photographs. The group then knows the update is still coming and can plan around the new timing. Silence past the deadline leaves everyone uncertain whether to wait, chase, or assume the worst.
Should photographs be included in the update or sent separately?
Include photographs in the same message if they help explain the findings or show something the group needs to see, such as damage, layout, progress, or items that were checked. Keep the number manageable—select the most useful images rather than sending everything taken on site. If there are many photographs or large files, mention in the update that they are available and explain how people can request or access them. The update itself should still be readable and clear without needing to open every image to understand the main points.
What if the site visit revealed a problem that needs immediate action?
Send a brief message to the group or to specific people as soon as the problem is discovered, so urgent action can start without waiting for the full update. Then send the complete update at the agreed time, including context, details, and any further steps beyond the immediate response. That way the group gets both speed when it matters and a proper record afterwards. Make clear in both messages which is the urgent alert and which is the fuller report, so nothing gets confused or missed.
Can someone who did not attend the visit send the update if they gather the information afterwards?
Yes, if the person who attended the visit passes on their notes, photographs, and observations clearly enough for someone else to write an accurate summary. This can work if the visitor has other commitments immediately afterwards or if one person coordinates all group communications. The update should make clear who attended the visit and who is reporting, so the group knows where the information came from and who to ask if there are follow-up questions. Accuracy matters more than who sends the message.
How should the update handle actions or decisions that still need group input?
State clearly in the update which points are confirmed findings and which are recommendations or questions for the group to discuss. Separate factual observations from opinions or options, and identify any decisions that need to be made by a certain time. If the update includes a question for the group, say when you need responses by and who should coordinate the answers. That way the update both informs and moves things forward, rather than leaving people uncertain whether they need to reply or just read and note the information.
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 freeNo app needed to begin, and nothing at all for the other person.
Related use cases
- Get an electrician to call when scaffold is removed
Building work often runs to unpredictable schedules, and you need the electrician to reconnect overhead cables only after the scaffolding comes down. A fixed callback date risks the electrician arriving too early or you missing the window entirely.
- Confirm who checks venue accessibility before an event
Someone needs to visit the venue ahead of time to check accessibility features like ramps, lifts, accessible toilets and parking. The person who checks reports back specific details so attendees with access needs know what to expect.
- Confirm handouts printed the night before training
Training sessions rely on printed handouts being ready at the venue when participants arrive. Printing the night before gives time to fix problems without delaying the session start.
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.