Request a Team’s Input on a Proposed Office Move Date

Before you write

Use this example when a workspace move is being planned and the coordinator needs concrete operational conflicts before confirming the date. Gather the details below so the recipient can act without asking you to reconstruct the situation.

• Proposed move window
• Affected teams and systems
• Deadline for dependency reports

An email you can adapt

The subject “Operational check for proposed move on [date]” identifies the request. Replace each bracketed field with a checked detail and remove any sentence that does not describe your situation.

Subject: Operational check for proposed move on [date]

Hello team,
We are assessing [window] for the proposed move to [location]. Please identify any critical activity, access need or equipment dependency that would make that window impractical. Send the specific conflict and responsible owner by [date], rather than a general preference alone. The move is not yet confirmed. [Coordinator] will review the responses and issue one agreed plan with arrangements for any necessary continuity work.
Best, [sender]

Check the boundary

A planning inquiry should not be interpreted as a final instruction to relocate equipment or interrupt services.

What a useful reply should settle

The replies should expose specific dependencies and identify who can help resolve each one.

Confirm the final plan through the designated coordinator and withdraw superseded draft dates clearly.