How do I coordinate a move when different groups are handling different destinations?
Quick answer
Use one shared overview to assign each group a destination and a named contact, then list the items or tasks that group is responsible for. Give every assignment a clear completion check, such as confirming delivery to the named room. Review the sheet together before moving day, flag anything without an owner or destination, and update the overview if plans change.
The question, the details, the next step.
My move involves several groups: one is taking things to my new home, another is taking some items to storage, and relatives are taking a few things elsewhere. How do I keep everyone from working off separate or incomplete plans?
Make one shared assignment sheet the reference for the whole move. It should show the destination, responsible group, a named point of contact, and how completion will be confirmed for each assignment. Keep the sheet focused on what goes where and who is accountable; individual groups can use their own packing or route notes, but those should not replace the shared overview.
Start by listing destinations as separate entries rather than using vague labels such as “the house” or “storage.” Use clear names like “new home — kitchen” or “storage unit,” and add a destination detail if the group needs it. Avoid putting access codes or other sensitive details in a broadly shared sheet; give those separately to the people who need them.
What should I put in each assignment so people know exactly what they are responsible for?
For each assignment, specify the items or task, the destination, the responsible group, one person to contact, and the completion check. “Take boxes” is too broad if there are several destinations. “Blue-labeled boxes B01–B06 to storage; Sam is the contact; Sam confirms they are at storage” is easier to act on. Use a simple item label or description that everyone can recognize, and keep it consistent on the item and in the sheet.
A compact copyable example:
Assignment: B01–B06, blue labels | Destination: Storage | Group: [Group name] | Contact: [Name] | Confirm by: [Move date/time] | Done when: Contact confirms B01–B06 are at storage | Status: Not started
Use one row or block per destination and assignment. If a group has two destinations, split its work into two assignments so each can be confirmed independently.
How do I catch items or responsibilities that nobody has picked up before the move?
Do a coverage check against the things you intend to move. For each item group or task, ask: Is its destination named? Is a particular group responsible? Is there a contact who can answer questions? Is there a completion check? Mark missing answers visibly as “unassigned” rather than assuming somebody will handle them.
Then review the unassigned entries with the relevant people and agree on an owner before treating the plan as settled. Pay attention to shared or awkward-to-classify items—such as things that might go either to the new home or storage—and state the decision directly. If you are not sure where something belongs, leave it flagged for a decision instead of assigning it by guesswork.
What if a destination or group assignment changes on moving day? How can we avoid two people making different updates?
Choose one person to maintain the shared overview, and ask everyone to send changes to that person or update the same agreed copy. For a change, record what changed, which assignment it affects, who now owns it, and whether the original completion check still applies. Make the revised destination clear to the responsible group; do not rely on a message that only says “plans changed.”
For example: “B01–B06: destination changed from storage to [new destination]. [Group name] remains responsible. [Contact] confirms arrival there. Updated by [name] at [time].” If the update leaves an item without a clear destination or owner, mark it unassigned and resolve that gap before considering it covered. At the end, check each assignment’s status and follow up on anything not confirmed; a blank status is not confirmation.
A practical checklist
List every destination separately, using labels the whole group understands.
For each assignment, name the items or task, responsible group, and one point of contact.
Define a concrete completion check for each destination assignment.
Review the overview for missing destinations, owners, contacts, or confirmation steps.
Choose who maintains the shared copy and how changes will be communicated.
After the move, follow up on assignments that have not been confirmed.
A few more useful answers
Should one group be responsible for more than one destination?
It can be, but write a separate assignment for each destination. That makes ownership and completion easier to check independently.
What counts as a useful completion confirmation?
A direct confirmation tied to the assignment, such as the contact confirming that the listed items reached the named destination. Avoid treating a vague “done” as confirmation if it is unclear what was completed.
What if I have not decided where some items should go?
List them as undecided or unassigned and name who will make the decision and by when. Do not leave the gap hidden inside another group’s assignment.