Safety observation logging

What problem does it solve? Near misses and unsafe conditions often go unreported because reporting feels risky or pointless, so organisations lose their cheapest safety data and only learn after someone is injured. ## Core Features & Use Cases - Structured Capture: Records what was observed, where, when, worst-case potential, contributing conditions, and immediate actions taken. - Blameless Framing: Describes conditions rather than naming individuals, keeping reporting channels open. - Potential-Based Rating: Rates events by what could have happened, not by the actual outcome. - Closed-Loop Accountability: Assigns every observation an owner and a date, or records why no action is warranted. - Use Case: A warehouse supervisor spots a pallet stacked above the marked line in aisle 4 and logs it as a high-potential near miss with an assigned corrective action instead of letting it become a statistic. ## Quick Start Log a safety observation for a near miss I witnessed on the factory floor, including location, worst-case potential, contributing conditions, and a corrective action with an owner and due date.