Review an imported office with a teammate

Write down the intended result

Before importing, record what the map is meant to provide: arrival point, meeting destination, usable furniture, and any areas participants must avoid. Identify the source file and its expected scope. A teammate should be able to compare the result with that description without guessing why the layout exists. These are review practices, not a claim that importing automatically validates every interaction or design choice.

Preserve the current layout first

With the necessary editing permission, make an appropriate recovery copy of the current map before using the available import controls. Confirm that the file belongs to the office or experiment you intend to change. Do not import a file into a shared workspace simply because it opens successfully. Coordinate the change with whoever is responsible for the map and choose a suitable review context.

Inspect the editor result together

After the import, compare the important objects and areas against the intended description. Look for missing pieces, unexpected overlaps, unclear entrances, and surprising collision arrangements. Have one person explain the map's purpose while the other checks the result. For example, a meeting layout may contain the correct desks yet place a storage cabinet across the only obvious route from the entrance.

Walk independently in normal play

Leave editing mode and ask the teammate to complete the main journey without continuous directions. Test the interactions required for the planned activity where they are available. A successful file parse does not prove that a chair works, a whiteboard is usable, or a participant can reach the presentation area. Also check a smaller-screen view if that reflects how people will join.

Decide whether to keep or recover

Write a short list of blocking issues and optional improvements. Fix the blockers with authorized edits, then repeat the relevant walk. If the result differs too much from the intended map, use the known recovery path instead of layering uncertain changes on top. Keep the accepted file and review notes together so the next teammate knows which version was checked and which limitations remain.