nexy

Use case

Confirm who submits a group planning application before deadline

Planning applications need supporting documents from multiple people—site plans, consultation letters, photographs. One person submits, but success depends on everyone delivering their piece on time and the submitter checking everything fits together.

Use one Nexy thread for one agreement: I will collect the application form answers from everyone, chase the architect for the site plan, check all documents match the requirements, and submit by the deadline. 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. Agree who will coordinate the application, collect all required documents, check they meet the published requirements, and submit before the deadline.
  2. List every required document—application form sections, site plans, neighbour letters, photographs—and agree who provides each one and by what internal deadline. The other person receives a message in the chat they already use and needs no new account.
  3. The coordinator sends each person a specific request: what document, what format, what details to include, and the internal deadline at least three days before submission.
  4. As documents arrive, the coordinator checks each one against the requirements, asks for corrections if something is missing or unclear, and confirms receipt to the sender. A reminder is most useful while you could still act, usually the evening before.
  5. The coordinator reviews the complete set the day before submission, confirms to the group that everything is ready, submits the application, and shares the reference number with everyone. 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 happens if someone does not send their document by the internal deadline?

The coordinator contacts that person immediately to find out what is causing the delay and whether the document will arrive in time. If the document will not arrive, the group must decide together whether to submit without it, find someone else to provide it quickly, or accept the deadline will be missed. The coordinator should not submit an incomplete application without the group agreeing that decision, because missing documents usually result in refusal.

How does the group decide who should coordinate the application and collect all the documents?

Choose someone who has time to read the requirements carefully, send clear requests to each person, chase missing documents, and check everything before submission. It helps if they have submitted a planning application before or are comfortable following detailed checklists. The person should volunteer, not be assigned, and the group should agree a backup who receives copies of all documents as they arrive in case the coordinator becomes unavailable close to the deadline.

What should the coordinator check when each document arrives?

Check the document against the published requirements: correct format, correct scale for site plans, all required information included, photographs clear and labeled, letters signed and dated. If something is wrong, contact the person who sent it immediately and explain what needs to change. Do not assume small errors do not matter—planning authorities often reject applications for missing signatures, incorrect scales, or unlabeled drawings. Fix problems as soon as they appear, not the day before submission.

How early should the group set the internal deadline for documents to arrive?

At least three working days before the official submission deadline gives the coordinator time to review everything, ask for corrections, and still submit comfortably. If documents are complex—architectural drawings, environmental reports—allow five days. Receiving everything on the final day leaves no time to fix errors if a site plan is the wrong scale or a consultation letter is unsigned. The internal deadline protects the whole group from last-minute panic.

What if the architect or another external person does not send their document on time?

The coordinator should contact them as soon as the internal deadline passes and explain the submission deadline. If the external person cannot deliver in time, the group must decide whether to delay submission, find another provider, or submit without that document. The coordinator should tell the group immediately so everyone knows the situation. Do not wait until the day before the official deadline to discover a critical document is missing—chase early and chase often.

How does the coordinator confirm to the group that the application has been submitted?

Forward the confirmation email from the planning authority to everyone in the group so they all see the reference number, submission timestamp, and any instructions for what happens next. Write a message in the group chat summarising what was submitted and confirming every required document was included. Save the reference number where everyone can find it. If the authority sends a separate acknowledgment or receipt later, share that too so the whole group has the same information.

Can the group change who coordinates the application after work has already started?

Yes, but only if the handover happens early enough for the new coordinator to understand what has been received, what is still missing, and what the requirements are. The original coordinator should pass over all documents already collected, explain which people have not yet sent their pieces, and confirm the handover to the group. Changing coordinator in the final three days before the deadline is risky unless the new person already knows exactly what is needed and who is providing it.

What happens if the planning authority contacts the coordinator with questions after submission?

The coordinator should share the question with the group immediately so the right person can provide the answer. If the question concerns a site plan, the person who provided it should draft the response. If it concerns consultation, whoever conducted that work should answer. The coordinator reviews the draft response, checks it answers the question clearly, and sends it to the authority. Keep the whole group informed of every question and every response so everyone knows the status.

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.