Safety Intelligence

Note: This analysis is based entirely on the self-reported description provided by the author. No independent verification, historical data, or third-party sources are available.

The description states that Safety Intelligence is an AI-powered workplace safety investigation assistant. It supports a workflow from incident input to report generation and includes:

• Local PII masking before OpenAI processing
• Structured analysis of direct causes and contributing factors
• Recommendation of corrective and preventive actions
• Retrieval of historical cases
• Human review and approval steps
• Generation of structured HTML, ODT, and PDF reports
• Multilingual output support

The system is built using FastAPI, Docker, OpenAI GPT-5.6, RAG, function-calling, structured outputs, and SQLite.

Inference: The product appears to be a prototype or proof-of-concept for an AI-assisted safety investigation tool, not a commercial-grade solution yet.

The author states that the product was created to help safety professionals investigate incidents more consistently, identify root causes, and generate professional reports with AI assistance. It positions itself as an assistant that improves upon inconsistent, time-consuming, experience-dependent investigations.

It also claims to be built with privacy in mind, using local PII masking and structured workflows to ensure compliance and control over outputs.

Claim: The system is designed for safety professionals to improve consistency and reduce reliance on individual investigator expertise.

Inference: This is a self-positioning statement; no evidence of actual adoption or impact is provided.

The description states that the tool is intended for safety professionals who investigate workplace incidents. It aims to support their workflow by automating parts of the analysis and report generation process.

Inference: The target customer segment is likely safety managers, compliance officers, or incident investigators in industrial, manufacturing, or regulated environments.

Not evidenced: No specific industry, company size, or job role details are provided.

No evidence of pricing, monetization strategy, or business model is present in the description.

Not evidenced: There is no mention of licensing, subscription models, SaaS offerings, or any commercial revenue mechanism.

The system uses:

• FastAPI for backend
• Docker for containerization
• OpenAI GPT-5.6
• Structured outputs and function-calling
• RAG (retrieval-augmented generation)
• PII masking
• SQLite for local storage
• JavaScript, Python, privacy, safety, workplace-safety tags

It is designed with modularity in mind, separating components like masking, analysis, and report generation to allow future replacement or integration.

Inference: The architecture suggests a modular, scalable approach that could support commercial deployment.

Not evidenced: No details on scalability, performance, or production readiness are provided.

The project is described as a hackathon submission and was built during Build Week. It uses synthetic data only and does not contain real company or employee incident information.

Key accomplishments mentioned include:

• 100 synthetic incident cases
• 13,931 regression tests with zero failures
• No confidential data in the submission repository

Not evidenced: No real-world usage, customer feedback, or adoption metrics are provided. The system is not demonstrated to be used beyond a demo.

No evidence of competitors or market positioning is provided in the description.

Not evidenced: There is no mention of existing tools or platforms in the safety investigation space.

• The system is described as a hackathon prototype, not a production-ready product.
• It uses synthetic data only; no real-world testing or validation is evident.
• No commercial deployment, customers, or revenue are mentioned.
• The use of GPT-5.6 implies reliance on a proprietary model with potential limitations in enterprise settings.
• The system’s architecture suggests it may be difficult to scale without significant rework.

Inference: The project has not yet demonstrated real-world utility or commercial viability.

1. Has the system been tested on real incident data, or is it limited to synthetic examples?
2. What specific safety regulations or compliance standards does it aim to support?
3. How is the structured output validated in practice? Is there a feedback loop for improving accuracy?
4. What are the plans for integrating with existing enterprise safety management systems?
5. Are there any plans for multi-tenancy, private cloud deployment, or data sovereignty features?
6. What is the expected timeline to move from prototype to commercial product?