One weekly number.
What a group of two to ten locations reconciles every week, why the unit report and the group report disagree, and what to standardize before the second lease.
Daniel M. Ortiz · September 2026
The Sunday-night ritual is familiar to anyone running more than one room: the logins, the spreadsheet, and an owner deciding which of two disagreeing totals to believe. A second location doubles the logins and adds a third total.
One weekly number is the third of the three things a group run as one operation has, beside one book and one guest record. This is what it is, what it is for, why the reports disagree without it, and what has to be standardized before the second room opens.
What should a multi-location restaurant group reconcile every week?
One view of sales, labor, payroll and the software bill across every site, built from the same sources the P&L is built from, with the same cut-offs, readable in one sitting, with a named owner for each source system. Four figures per site, one page, one person who can say where each figure came from. If the group cannot produce that page in an hour on a Monday, the number is not one number yet; it is several, waiting to disagree.
The decision the number supports.
A weekly number earns its page by deciding something. Three decisions come up every week in a group and cannot be made well from a monthly statement that arrives after the month is over: who works next week, and where; whether the next opening is being funded by the rooms that exist; and which room's workaround has quietly become policy.
The third is the one a single-site owner never has to make. When two rooms close differently, the group inherits both closes, and whichever one the manager who trained the new team preferred becomes the standard by accident. The weekly number is where that shows up, because the two rooms stop agreeing.
Why the unit report and the group report disagree.
The unit report is what each room's POS says about itself. The group report is what the spreadsheet, or the accounting file, says about all of them. They disagree for reasons that are boring one at a time and expensive together: one room closes at midnight and the other at the end of the last check; one room's modifiers carry a price and the other's do not; an invoice was keyed into the books with a different date from the one on the delivery slip; a guest who booked in one room and dined in the other was counted twice.
None of those will be found by staring at totals. They are found by reading the definitions: what counts as a sale, when a day ends, which system is the source for each figure. Written down once, the definitions turn the disagreement from a mystery into a list.
What does “ties to the P&L” mean?
It means the weekly figure and the monthly statement are built from the same sources, with the same cut-offs, so that when they differ the difference is a finding and not a mystery. Sales on the weekly page come from the same POS close the bookkeeper uses. Labor comes from the same scheduling and payroll exports. The software bill comes from the same invoices. If the weekly number is built from a manager's text message and the P&L from the bank feed, they will never tie, and no amount of reconciling on a Sunday will make them.
This is an operating signal, not accounting advice. Have your accountant read the definitions before you rely on the number.
Tying is a property of the sources, decided when the page is designed; it cannot be recovered afterward by working harder on Sunday. Write the source and the cut-off beside each figure on the page itself, so that is what your accountant reads.
One guest record, one system owner.
Two things make the weekly number possible, and both are decisions before they are software. The first is one guest record: the regular from the first room is not a stranger at the second, the party of twelve that booked in one room and dined in the other is one guest and one cover count, and the history rides with the guest in a system you control. Without it the group counts the same person twice and calls the difference growth.
The second is one named owner per system, across the group rather than per room. The person who owns the POS owns its close in every room and can say why the cut-off is what it is. When a figure on the weekly page is wrong, there is one phone number to call, and it is not yours.
What should be standardized before a second restaurant location?
Before the lease is signed: one book and one order-queue policy, one guest record, written permissions per room, and the software bill priced line by line. Before opening week: the weekly number defined, with its sources and cut-offs, and produced once from the first room alone. After opening: a manager who can run either room from the written record. Standardize in that order, because the first room is the only place the definitions can be tested before they are copied.
Before the lease
- One book and one order-queue policy, written, that either room will run under
- One guest record, in a system the group controls, with the first room's history already in it
- Permissions per room, written: who can see, who can change, who can void, in each system
- The software bill priced line by line, so the second room does not inherit a line the first one should have cancelled
Before opening week
- The weekly number defined on paper: four figures, the source system for each, the cut-off for each, the owner for each
- The page produced once from the first room alone, and argued from, before a second room's figures are added to it
After opening
- A manager can run either room from the written record, without the owner's phone number as the fallback
- The weekly page reads in one sitting, and both rooms' figures come from the same definitions
The blank weekly page.
One row per site, with the definitions that make the figures comparable: the system each figure comes from, who owns it, and when its day ends. Where a site's figures come from more than one system, add a row per system. The rows stay blank on purpose; the first fill should be from your own first room.
| Site | Sales | Labor | Payroll | Software bill | Source system | Owner | Cut-off |
|---|---|---|---|---|---|---|---|
The group as one operation.
The page for groups says what the other two of the three things look like, one book and one guest record, and how the fee follows system stacks and sets of books rather than doors.
The rebuild that gets a group there runs under written rules: nothing changes during service, one change at a time, the old way runs beside the new until it has proven itself, and a written rollback the manager on duty can pull. The Operations Assessment is where the definitions get written and the bill gets priced, for two to ten locations at once.
If the second lease is signed or circling and the Sunday-night ritual is still two totals that disagree: