How It Works

The weekly rhythm that closes the loop

Five days. One pulse on Monday. One report on Wednesday. Documented resolution by Friday. Repeat every week.

The Weekly Rhythm

Five days. One closed loop.

MON
Operational Signal
Staff receive a unique encrypted link by text. 12 questions across rotating organizational health categories. Under 90 seconds.
TUE
AI Pattern Analysis
The Tuesday window closes overnight. Pattern Intelligence groups responses into named themes by wing, shift, and category.
WED
Action Report
9 AM: administrators receive the Wednesday Morning Action Report. Top three signals. Named owner. Required action. 72-hour clock starts.
THU
Managers Execute
Stay conversations, supply audits, shift huddles, new-hire check-ins. Managers also receive a daily micro-prompt tied to this week's theme.
FRI
Loop Closes or Escalates
Managers log what was done. Unresolved items escalate automatically to the administrator. Every resolution is documented for QAPI.
Question Architecture

12 questions per week. Rotating coverage. No survey fatigue.

Two to three CREATOR categories are active each week, with three to four questions per category. Rotation prevents fatigue and builds a comprehensive signal picture across every dimension of organizational health over time — instead of measuring the same things repeatedly.

Once per month, staff receive an additional open-ended comparison question: have you seen any improvement or changes you want to comment on over the past month? Analyzed separately to give the AI a baseline-versus-trend view weekly questions alone cannot produce.

Staffing adequacy — was there enough coverage to do the job safely
Role clarity — did I know what was expected of me this week
Supervisor communication — was I getting the information I needed
Psychological safety — could I raise a concern without fear
Supplies and resources — did I have what I needed to do my job
Shift handoff — was the transition complete and useful
Workload and safety — was my assignment manageable
Recognition — did I feel valued this week
Voice and respect — did I feel heard
Intent to stay — am I planning to still be here in six months
The Daily Manager Micro-Prompt

Five small actions a week. One behavioral pattern a month.

Every day Monday through Friday, managers receive a short micro-prompt tied to the current week's signal theme. Not a training module — one specific, actionable thing to notice, try, or say today. The manager logs whether they did it. Tomorrow's prompt arrives shaped by what happened.

Example week — theme: psychological safety gap on North Wing
MON
Before your first interaction with a staff member today, ask one genuine question and say nothing for 30 seconds after they answer.
Logged: tried with night-shift CNA. She mentioned the linen cart issue.
TUE
If someone raises a concern today, acknowledge it by name before you respond to it.
Logged: used with two staff during morning huddle.
WED
Pick one of yesterday's concerns. Tell that person what you did with it. Even if the answer is 'I escalated it.'
THU
(prompt arrives Thursday morning, shaped by what you logged Wednesday)
FRI
(prompt arrives Friday morning)
Manager Voice — Upward Pulse

The middle of the sandwich also gets a channel.

Once a month, managers complete a separate pulse that faces upward — toward administration and ownership. Individual manager responses are grouped before ownership sees them. This is the signal that usually only surfaces when a good manager quits.

Decision access
Can I get answers from administration when I need them? Are decisions being made in time for me to act?
Resource adequacy
Do I have what I need to meet the standards being asked of me?
Psychological safety upward
Can I raise a concern with my administrator without fear of consequences?
Meeting effectiveness
Are our meetings producing decisions or just discussion? Do I leave with clarity or more questions?
Execution friction
What is the one thing administration could change that would most improve my ability to lead my team?

See the full weekly rhythm running in the demo.