How SANDR connects observations, decisions and results.

Facts

What was observed, when and where it happened, and the source. A reported incident remains a report; it does not become an established cause just because it sounds plausible.

Pattern

Whether similar observations recur. Repetition can make a situation worth investigating, while differences between shifts or venues still matter.

Problem

The proposed explanation for the pattern, with supporting evidence and what is still uncertain. The team can challenge or correct this reading.

Response

A possible intervention drawn from the operating knowledge. The relevant conditions, constraints and prerequisites explain why it might fit.

Work

The approved actions, their sequence, the people responsible and when they will be reviewed. Reading a suggestion does not approve a plan.

Proof

Evidence that an action happened: a completed handover, a working routine, a reviewed document or another appropriate record.

Result

What changed after the work. Completing a task and reducing a recurring problem are separate things to check.

Learning

What should be retained, adjusted or investigated next, using the result and the limits of the evidence.

The library connects recurring operating problems with practical responses. A Block describes one intervention: when it applies, what needs to be ready, the order of work, its owner, useful Tools and the evidence to review.

A Tool helps carry out part of that intervention, such as a checklist, template or tracker. An Article explains the subject and supports the team's judgement. An approved Plan adapts the work to a particular venue and gives it owners and review points.

SANDR considers the venue context alongside this knowledge. A useful response for one business can be too early, too demanding or unsuitable for another. The person reviewing it needs to see those conditions before deciding what to do.

Several afternoon shifts report missing the same information from the morning team. First, the manager checks the accounts and the existing handover process. The question is whether the information is missing, the routine is unclear or nobody owns the transfer.

If the evidence supports a handover problem, SANDR can propose a small response. The manager reviews the fit, agrees on what needs to be passed over and assigns responsibility. The plan might begin with one short handover routine that the team can actually keep during a busy shift.

Completed handovers provide evidence that the routine is being used. Later check-ins ask whether the same information is still missing. If the handovers are complete but the problem continues, the team revisits the explanation or changes the response.

The original observations, the decision, the work and the later result stay connected. The team can see what it tried and why, rather than start the investigation again from a blank conversation.

SANDR can read permitted sources, explain relationships and prepare proposed work. People review the interpretation, decide whether a response fits and approve consequential changes within their product permissions.

• Evidence: keep reported facts separate from inferred causes and make missing information visible.
• Capacity: review who can carry the work and what must happen first.
• Access: use only the information allowed by the person's role and workspace.
• Privacy: an employee's private Frontline conversation remains separate from the summary they approve for sharing.
• Follow-through: check the effect of the work before treating an issue as resolved.

A structured recommendation can still be wrong. The method provides a way to inspect and revise it; it does not remove the need for local judgement or make an outcome certain.