A fix is not a checklist you finish, it is a system you put in place and keep running. So Bar Cop does not ask you to tick boxes. For the work it can see, it reads your real data and shows whether the system is actually happening.

1. Open your Revenue Systems

Open Revenue Recovery → Revenue Fix. Each system is one revenue lever. The ring and status read off live data, how many of the watched steps are on track. Open one and its fix expands in place, so you move between systems without leaving the page. A system reads On track only while every watched step is current; the moment one lapses it tells you how many steps are slipping or behind.

2. Know watched steps from guidance steps

Watched steps are the work Bar Cop can verify: building the schedule, logging a server check, logging a price change, running a dog test, confirming a week, opening the weekly reviews. Steps like repricing read your live numbers, any menu item still over its target cost. Guidance steps, a signed server standard, the pre-shift briefing, the table-visit audit on the floor, are the things Bar Cop cannot see; they matter, but are never counted as proof.

3. Read the Watch Out For notes

At the bottom of each system are the mistakes that quietly break its numbers, the things Bar Cop itself cannot catch for you. Worth a read before you chase a number that looks off.

4. Let it measure from your baseline

There is no start button. The moment you do the first tracked step, Bar Cop logs that day and measures from there, taking your own first few weeks as the baseline, so the recovery number reads against where you started.

Early on there is not enough logged to call anything recovered, and Bar Cop says so plainly instead of inventing a figure.