Every other check in this product compares the configuration against itself. Readiness asks whether the stores we know about have someone to alert; import validation asks whether your file parses. Neither can catch the error that matters most here, because the information simply isn't in the system.
So we ask them. The first time a manager signs in, their store list is shown at the top of the dashboard and they either confirm it or say what's wrong.
- It's asked of managers with a defined territory — the only people who have independent knowledge to contribute. Someone who sees every store is not asked, because "are these the right stores?" has no meaning when the answer is "all of them".
- It doesn't block anything. The dashboard renders underneath, so a live alert is never behind a piece of paperwork.
- A confirmation vouches for the list they actually saw. Change someone's territory afterwards and they're asked again — they never agreed to the new list.
If they flag a problem — a store missing, a store that isn't theirs, or something else — it goes to a queue for whoever manages the dashboard, with who reported it and when.
- The report appears under Territory reports, and in the top navigation while any are open.
- A missing store is treated as critical on Readiness, because until it's fixed nobody is alerted about that restaurant.
- You fix the territory, then close the report — optionally noting what you did, which is kept in the audit trail.
- Closing it asks the manager to confirm their list again. Closing a report claims the territory is now right, and only they can verify that.
In the dashboard: Territory reports — Managers reporting that their store list is wrong — a store missing, or one that isn't theirs.