Do Not Copy Location One Into a Different Room

Location two can carry the same menu, service promise, and visual identity while needing a different operating method. The entrance faces another direction. The bar storage sits farther from the service well. The pickup point is visible from one section and hidden from another. A copied checklist cannot make those conditions identical. The expansion job is to preserve the outcomes that define the restaurant while translating the path used to produce them. Without that distinction, consistency becomes a collection of copied instructions that fight the new address every service.

1. Name the promise that cannot drift

Begin with the invariant, the condition a guest or operator should experience at either address. A reservation handoff should preserve the current table state. A menu hold should reach every ordering point. A finished plate should arrive at the correct pickup position with its table context intact. A close should leave the next opening a legible room.

The invariant should avoid describing location one's method. If it says the host marks the paper floor plan beside the front door, it has already copied an address-specific path. If it says the active table state must be visible at the reservation handoff, location two can select a method that fits its own entrance and sightlines.

2. Put the old path and new condition together

For each critical service sequence, place four fields on one page: the invariant outcome, the method used at location one, the physical condition that changes at location two, and the translated method. The sheet should follow the movement of work through the room rather than the departments on an organization chart.

Guest arrival may move from a host stand with a direct view of the dining room to an entry around a corner. Beverage service may move from shared backbar storage to separated storage and service points. Kitchen pickup may change from one pass to two distinct landing points. Receiving may enter through a route that does not lead directly to the same holding area. Each change needs a deliberate handoff, not an assumption that the old instruction will stretch.

3. Walk the information through the room

A floor plan shows where objects sit. The translation sheet shows what information must travel with them. Follow a reservation from arrival to table state. Follow a menu availability change from the kitchen to every ordering surface. Follow a beverage order from entry to production to pickup. Follow an unfinished close item into the next opening record.

At every transfer, ask what the next operator needs to know and where that state becomes visible. If the answer depends on a sightline that exists only at location one, the method is address-bound. If it depends on local shorthand, the language is address-bound. The translated path must replace that hidden condition with an explicit handoff.

4. Resolve the contradictions the building creates

The sheet becomes valuable when two desired outcomes conflict. The second bar may need product close to production, while the close standard needs one visible record of what remains. The new entrance may need a distinct arrival flow, while the restaurant wants one shared reservation state. Writing both outcomes on the same page forces the operating choice into view before the room begins improvising around it.

A translated method does not need to match the original action. It needs to protect the same operating promise and leave evidence that can be inspected. That gives the second address permission to fit its room without drifting into an unrelated version of the restaurant.

5. Rehearse the translated path

Walk the translated sequence in the actual room with the real records and service points available. Carry the information as the work moves. Stop when a handoff requires memory, an unavailable sightline, or a record that lives somewhere else. Revise that line on the sheet, then walk the sequence again from its beginning.

The standard is not speed and it is not visual similarity. The standard is continuity. The final state of one step should become the visible starting state of the next. When that chain holds, the restaurant has translated a system. When it breaks, copying more of location one's checklist will only give the break a familiar name.

A second address should feel like the same restaurant to the guest without pretending it is the same room to the operator. The address translation sheet protects both truths: the promise remains stable, and the operating path is allowed to change where the building demands it.