The Checklists page (HQ dashboard → Checklists, at `/app/hq/[orgId]/checklists`) is where a franchisor sets one org-wide checklist standard — separately for Shop Staff and Installers, and separately for each of the four checklist types (Daily Opening, Daily Closing, Weekly, and Monthly) — and pushes it down to whichever shops should be running it. This is an HQ-level page. It lives under your organization's HQ dashboard, not inside an individual shop's own SalesThumb account, and it's built for the franchisor side of a multi-location org. Shop staff fill out and complete the actual checklist from their own shop's screen, not from here.
Set the org standard (Push & Manage tab)
The Push & Manage tab lays out a card per audience — Shop Staff, Installers — and, under each, one card per checklist type. Every card shows how many of your shops are currently on it ("X/Y shops on this standard"). If you haven't saved anything for that combination yet, the card carries a Using defaults badge, meaning you're looking at SalesThumb's built-in starter list rather than a blank editor.
If you're an ORG_OWNER or ORG_ADMIN, you can edit the list directly on the card — change an item's wording, delete an item, or click Add item to append a new one. Any other org member with HQ access can still open this same page and read the current list, but the edit fields and the push button aren't shown to them; it's a read-only view for everyone else.
Push it to shops
Push to Shops… on a card opens a dialog scoped to that one audience/checklist-type combination. It lists every shop in the org, pre-checked, with a badge where relevant: On standard means that shop is currently synced to your org template for this combo; Customized means the shop has its own saved checklist here that never came from HQ.
Below the list, an Overwrite shops with their own customized version toggle is off by default. With it off, pushing skips any shop marked Customized, and afterward the dialog names which shops were skipped and tells you to turn on overwrite and push again if you want to force it. A shop that's already On standard is never skipped, toggle or not — since staying in sync with HQ is what being on the standard means, a push always brings that shop's copy current. Turning overwrite on removes the skip protection entirely, so a shop's own customized list gets replaced without a second warning.
Pushing does two things in one action: it saves your edited items as the org's standard for that audience and checklist type, and it writes that list out to every shop you didn't skip. There's no separate "save without pushing" — you need at least one shop selected to push at all.
See who's actually using it (Adoption tab)
The Adoption tab is a grid: one row per shop, one column per checklist type, with a toggle at the top to switch between Shop Staff and Installers. Each cell shows whether that shop has completed the current period's checklist — a green checkmark and the name of whoever submitted it, or "Not done" — plus a small icon marking whether that shop's checklist is currently on the HQ standard or customized locally. "Current period" is computed in each shop's own local timezone, so a shop in a different timezone than HQ starts a new day, week, or month on its own clock, not HQ's.
Not the same as Brand Standards Audits
This page and HQ dashboard → Audits/Compliance (see Scheduling and running a brand-standards audit) both send checklist-shaped content out to shops, but they solve different problems. Checklists here are routine, recurring operational lists — a shop marks each item done or not, nothing is scored, and nothing here creates a corrective action. Brand-standards audits are scored compliance visits: each item is graded Pass/Fail/N/A, a numeric score is derived automatically, and a failed item is tracked as a corrective action until it's resolved. If you need a score, a sign-off, and a paper trail for a compliance visit, that's the Audits/Compliance workflow — this page is for the day-to-day daily/weekly/monthly routine instead.
Things to know
- Viewing either tab requires being a member of the org with HQ dashboard access (the org needs the HQ add-on, and your own account needs HQ dashboard access — the same gate every other HQ page in this dashboard uses). A member whose HQ access was restricted at invite time won't see this page even if they hold an Admin role.
- Editing a checklist's items and pushing it to shops additionally requires the ORG_OWNER or ORG_ADMIN role.
- A shop's own customized checklist (one that never came from an HQ push) is protected from being overwritten unless you explicitly turn on the overwrite toggle in the push dialog.
- A shop already on the HQ standard is always brought current on the next push — the overwrite toggle only matters for shops that customized independently.
- The adoption count and the "On standard" badge reflect whether a shop has ever been synced to this checklist slot, not necessarily whether it has your very latest edit. If you edit the items and then push to only some shops, a shop you leave out keeps its older copy but still shows as on-standard until you push to it again.
- Adoption is computed in each shop's own local timezone, so "today's" or "this week's" completion status can flip at a different moment for shops in different timezones.
- This feature has no scoring, sign-off, or corrective-action tracking — for that, use Audits/Compliance instead.
Related
Frequently asked questions
Q: Who can push a checklist standard to shops?
A: Anyone who's an ORG_OWNER or ORG_ADMIN on an org with the HQ add-on and HQ dashboard access. Other org members with HQ access can view the same page — the current items and the adoption grid — but the edit fields and Push to Shops button don't appear for them.
Q: What happens if a shop already customized its own checklist?
A: It's protected by default. Pushing skips it and, afterward, names it as skipped for being customized. Turn on "Overwrite shops with their own customized version" in the push dialog and push again to force it.
Q: What happens to a shop that's already on the HQ standard?
A: It's always overwritten on the next push, overwrite toggle or not — staying in sync with HQ is what being "on standard" means, so there's nothing to protect there.
Q: Does editing a checklist's items save automatically?
A: No. Editing only takes effect once you push. Pushing updates the org's saved standard for that audience and checklist type and writes it to whichever shops you selected — you need at least one shop selected to push at all.
Q: Is this the same as HQ's brand-standards Audits/Compliance pages?
A: No. This page is for routine operational checklists — items marked done or not, no scoring. Audits/Compliance is a separate, scored compliance workflow with Pass/Fail/N/A results, a derived score, and corrective-action tracking for failures.
Q: Do individual shop owners see this page?
A: No. This page lives under the HQ dashboard for your organization, not inside a shop's own account. Shop staff complete their checklist from their own shop's screen, not from here.