Accept an office map before handing it to a host

A map builder and a session host can have different ideas about what finished means. The builder may see complete furniture; the host needs a layout they can explain and use. Review the handoff explicitly before someone sends invitations. This is a team acceptance process, not a built-in approval workflow.

Agree on acceptance criteria

Ask the host for the activities the map must support and write a short list of observable results. For example, a workshop layout should have a recognizable arrival area, an accessible presentation corner, and an unambiguous return route. Separate required results from decorative preferences. Decide who can accept the layout and who can authorize changes, rather than interpreting a positive comment on a screenshot as final approval.

Identify the version under review

Use the saved layout the host will actually receive, not an unsaved editor arrangement. Record the map context and the date of the review in your existing notes. After authorized changes, follow the available save workflow and inspect a fresh visit. Keep an appropriate recovery copy before substantial revisions. This gives both people a shared reference if the office later looks different.

Compare evidence with each criterion

Have the builder explain the intended layout, then let the host check it against the agreed results. Record which observations are visual and which interactions were actually tested. A complete board-shaped object establishes appearance, not drawing support. Where collision or object controls are available, inspect relevant configuration in the authorized editor context. Do not describe an untested feature as accepted merely because its artwork looks convincing.

Resolve blockers before preferences

Classify findings as an invitation blocker, an accepted limitation, or an optional improvement. A blocked presentation approach is different from a request for another plant. Give each required correction an owner and repeat its acceptance check after the change. If two proposed fixes conflict, return to the original activity rather than letting the latest aesthetic preference silently redefine the layout.

Hand over an honest operating note

Give the host the office location, accepted version context, destination descriptions, and limitations relevant to the invitation. Include where the recovery copy is managed and whom to contact about map changes. Ask the host to explain the main destination in their own words. If they cannot, clarify the handoff before calling the map ready. Keep later session-device checks separate from this layout acceptance decision.