01 / 05
Capture
Describe what happened in plain language.
Screenshot needed: Capture step
Show the floor note composer.
02
Check-ins
Turn a floor note into structured work.
A check-in starts with plain language. The manager writes or speaks what they saw on the floor. They do not need to know the right category first.
SANDR reads the note, identifies likely signals, lets the user choose the right scope, and prepares the blocks of work that match. The user reviews the draft before it becomes part of the operation.
Screenshot needed: Capture step
Show a note field with an example floor note about a rough rush, a late person, unclear handover, and backed-up drinks.
What the user does
The screen appears when the conversation needs detail.
The point is not to make managers fill out more forms. The point is to stop useful floor reality from disappearing after the rush.
A short note can become evidence, a signal read, and a plan the team can actually work from.
01
Capture
The user describes what happened, where, when, and who was involved.
02
Read
SANDR maps the note into confident signals and signals worth confirming.
03
Scope
The user chooses how much work should be created: light, medium, or full.
04
Plan
SANDR suggests the operating blocks and layers that match the signals.
05
Commit
The user reviews and saves the check-in, creating the assessment, selected signals, plan, and tasks.
Screenshot needed: Capture step
Show the note field with the example floor note and voice/text controls.
Screenshot needed: Read step
Show confident and suspected signal cards with clear review states.
Screenshot needed: Scope step
Show light, medium, and full scope options with plain explanations.
Screenshot needed: Plan step
Show recommended blocks with L1, L2, and L3 rows.
Screenshot needed: Commit step
Show the final summary with signals, blocks, scope, and a save confirmation.
Five check-in steps
A manager note becomes reviewed work.
Outcome
What the user knows by the end.
By the end, a messy floor note has become evidence, a signal read, a scoped plan, and reviewed work the team can act on.
Walkthrough
Bring one real operating day.
We will map how SANDR would open in the conversation, show the right context, prepare the work, and keep confirmation with the user.