Most multi-unit Operators start with a single great store and assume the second store will run the same way. It does not. The cultural lift, the Director hire, the layout consistency: everything that worked at store 1 has to be deliberately built at store 2.
One operating playbook. Same Day Part Layouts. Same Training Positions. Same rating rubrics. If the playbook is in someone's head at store 1, it does not transfer.
One performance language. A "3" at store 1 means the same thing as a "3" at store 2. Without that, you cannot move Team Members between stores or compare Leader effectiveness.
One reporting layer. The Operator should see both stores in one view, side by side, with the same metrics defined the same way.
The Multi-Unit tier of OneClick is not a "more seats" upgrade. It is a different product surface that rolls both stores into one Operator dashboard, with cross-store Team Member visibility and standardized reporting.
Day 1 of store 2. The temptation is to let store 2 develop its own playbook because "every store is different" — but the cost of divergent Day Part Layouts, divergent ratings, and divergent reporting is paid every week of the year afterward. Standardize early.
Yes, with the Multi-Unit tier. A Team Member rated at store 1 keeps their Passport progression when they pick up a shift at store 2, as long as the Position name matches. This is why standardizing Position names matters.
Same layout, but rolled up. Labor variance, Director coaching capacity, infraction patterns, and Team Member tier movement are shown side-by-side per store. Click into a store to drop into its single-store view.
Most Multi-Unit Operators do a 10-minute morning glance across both stores, a 30-minute weekly Director sync per store, and a 60-minute monthly cross-store review. The product is built around that cadence.