On this page
Most rollouts are announced, then left alone. Follow-through keeps a priority moving after launch day.
Available now: each priority has a check-in cadence set at publish (once, weekly or monthly). Owners log progress on the web, status is computed from HQ’s conditions, at-risk units are flagged on the rollup, and material edits ask owners to re-acknowledge. The day 7/30/60 cadence, reminders, follow-up lists and peer progress below are Planned.
The day 7/30/60 cadence Planned
Every published priority will carry a follow-through cadence. The planned default is:
| When | What happens |
|---|---|
| Day 1 | A gentle reminder to owners who haven’t acknowledged yet |
| Day 7 | First check-in: has the owner acknowledged and started? |
| Day 30 | Progress check: is the unit on track against its conditions? |
| Day 60 | Result check: did the KPI move against baseline? |
HQ can adjust the days per priority. Each check-in looks at the unit’s acknowledgement, owner steps and metric, then updates its status and decides whether anyone needs a nudge.
What owners see
At each check-in, an owner whose unit needs attention sees a short, specific prompt on the priority: what’s missing, the next step, and the reason it matters. If the priority’s numbers come from an import, there may be nothing to do but read it.
Owners aren’t asked to fill in a form at every step. The aim is the minimum of owner effort for the maximum signal: one tap to acknowledge, a value and one button to update.
The nudge ladder Planned
When a unit falls behind, reminders will step up in a fixed order:
- Push to the owner.
- Email to the owner.
- Flag to the field consultant, who adds the unit to their follow-up list.
Reminders go to owners and field consultants. They never go to franchisee staff. Notifications are batched and respect quiet hours.
Follow-up lists for field consultants Planned
Each field consultant will see which of their units are behind on which priority, ranked so the next call or visit goes where it counts. A unit lands on the list based on its outcome and the owner’s acknowledgement, not on whether someone uploaded a photo.
The list is internal to HQ. Owners see their own status, not a ranking of “behind” units.
When a field consultant follows up, the conversation is with the owner, about the result: what’s getting in the way, whether the priority fits the unit, and whether an exception makes sense.
Stalled units reopen and escalate Planned
If a unit was marked met but its metric slides back past the at-risk condition, the assignment reopens and re-enters the cadence. If it stays at risk, it escalates to the field consultant and the owner. Escalations never land on a staff member’s list.
Every reopen and escalation includes an exception path: sometimes the right answer is that a priority doesn’t fit a unit’s model, and the field consultant can recommend a waiver.
Peer progress Planned
Owners are persuaded more by what peers achieved than by a memo. SignaUnit will be able to show owners how units in their region are moving on the same priority, and it leads with results (“units that did this lifted repeat customers noticeably”) rather than adoption counts.
Peer data is shown only in the form the brand chooses: anonymized bands, “units like yours”, or named comparisons where owners have agreed to it.
The adoption rollup
HQ gets an adoption rollup for each priority by region and by franchisee, with an at-risk list. It shows at a glance where a rollout has caught on and where it hasn’t. Adoption is always shown next to KPI change, so units with low adoption but a good result aren’t chased for no reason, and units with high adoption but no movement prompt a harder question about the priority itself.
Drafted reminders Planned
A later release will suggest nudge wording for HQ and field consultants to edit and approve. A person approves every message before it goes out, and drafts are always addressed to the owner and about the outcome.