Multi-Unit Restaurant Management: Give Each Location Clear Ownership
When you cannot be present at every restaurant, a useful management system must make the next decision clear. Who investigates an unexpected labor change? Who explains a comp? Who follows an unmatched deposit through to the bank?
Start with ownership and evidence. More notifications alone will not answer those questions.
Standardize definitions before targets
Write down what each measure includes. Does labor contain manager salaries and employer costs, or only clocked wages? Are sales net of discounts? Does the trading day follow the calendar day or the POS business date? Use the report source and evidence fields to make sure managers are responding to the same period and measure.
Use consistent definitions across locations, then set targets that reflect their formats and demand. A shared reporting method does not require every location to carry an identical staffing target.
Give managers authority with boundaries
For each exception, specify who receives it, what they may change, and when they should escalate. A GM can investigate a schedule variance; a finance lead may need to resolve a bank match. Sensitive employee issues need an appropriate review process, not an accusation in a group message. The manager action log provides fields for recording the owner, next action, review date, and result after authority is agreed.
Have a backup owner for days off. An escalation that depends on one person always being available is a fragile process.
Keep the daily review focused
Use the daily check to identify incomplete records, unresolved cash items, unexpected hours, and transaction adjustments that require context. A missing source feed belongs on the list even if the report otherwise looks normal.
Ask managers to explain the evidence and proposed next step. A percentage outside a target is a prompt to investigate; it does not tell you whether volume, rate mix, training, or a record error caused the change.
Use the weekly conversation to remove repeated problems
Review recurring exceptions instead of replaying every alert. If closing hours are consistently above plan, inspect the closing workload and schedule assumptions. If discounts repeatedly need explanations, check the policy, reason codes, and approval flow.
Before adopting another tool, inspect capabilities already enabled in your stack. For example, 7shifts documents overtime notifications whose delivery depends on settings, time-clocking, and supported connections. The operating task is to confirm whether the right managers receive and use them. 7shifts documentation.
Verify the action worked
Closing an item requires more than “done.” Keep the supporting record: a corrected menu setting, a matched deposit, or a later comparison showing whether the recurring variance changed.
Separate an explanation from a recovery. If a bank timing difference explains an apparent shortage, the work improved clarity; it did not create new cash. If an operating change improves a measure, account for sales and other relevant changes before claiming savings.
Put authority next to the assignment
Use this illustrative authority matrix as a starting point. Replace the roles with named people and your actual approval policy; it is not a claim about a customer organization.
| Issue | Primary owner | Backup | Decision authority | Escalation trigger | Closure evidence |
|---|---|---|---|---|---|
| Repeated unplanned closing hours | GM | Area manager | Adjust future coverage within policy | Agreed review date missed or issue repeats | Later punches, demand, and service context |
| Invoice price dispute | Purchasing lead | Finance lead | Request correction within purchasing policy | Supplier response overdue | Posted credit or documented explanation |
| Unmatched deposit | Finance lead | Controller | Reconcile records; operating changes require assigned approval | Missing record beyond agreed check date | Bank match and custody trail |
Set due dates around the next decision or source availability. “Urgent” without an owner and review time is not an escalation rule. If the primary owner is absent, the backup needs access and authority before the issue arrives.
Make accountability repeatable across locations
Marty is a managed profit-control layer for multi-unit restaurants. It connects the systems you already use, finds what changed, alerts the right manager, follows up on the action, and verifies whether the number improved.
Find → Assign → Follow up → Verify. Find a change against the location baseline. Assign the manager who has the information and authority to act. Follow up and escalate a missed action through the agreed chain. Verify whether the measure improved so ownership includes the result, not just the task.
The paid Cash Recovery Plan establishes the baseline that tells Marty what to watch first.
Optional Managed Profit Control adds monitoring, alerts, follow-up, escalation, and verification for the agreed controls across locations and their responsible managers.
Sources checked September 15, 2026: linked 7shifts documentation and Marty's Review offer.