SCOPE safety platform
Demonstration build. All people, incidents and vehicles are synthetic; no real employee data appears anywhere in this system.
Client demos
Rule book
Rule mappingBeta (beta)
/rulesOpen asWhich rules in the client's own book, which of their courses and which corrective actions follow from an incident, each link with the words that made it. Approve, reject or add, with a reason on the record; see the training the catalog is missing; test the rules on any incident.
Sal decides, Paul reads. Try IN-20260922-001, the slip on ice: the rules point at the ice-cleat clause and Slip, Trip and Fall Prevention, not the lifting course it was given.
Rule book
/policyOpen asThe client's own safety rules book, searchable, with each section showing which checklist lines quote it.
Reached from a checklist line in an observation. Everyone can read it, drivers included: the book itself is issued to every employee.
Capture
DVIR: vehicle inspection
/dvirOpen asPre-trip and post-trip inspection on a tablet. Installable, works with no signal, uploads when it can.
The offline surface. Show it in Airplane Mode.
Observation
/observationOpen asBehavior-based observation: what was safe, what was at risk, and the corrective action per unsafe line.
No driver pill: an observation is one person watching another work, and the database refuses a driver outright.
Incident report
/incidentOpen asFirst notice from the field: who, where, what, injury and vehicle detail.
Investigation and follow-up
Incident investigation
/investigationOpen asPick up a reported incident, work it to root cause and contributing factors, attach photos and documents, raise corrective action.
No driver pill: this is supervision, and a driver is not shown the investigation behind his own report.
Requests for input
/requestsOpen asThe owner of an investigation keeps the file and sends a piece of it out (two witness statements, a maintenance history) and it comes back for them to accept or send back. Every step is on the record.
No driver pill: a driver is not shown the investigation behind his own report, so he is not asked to work on one either. Sal has one to review, Kyle one to answer.
Dashboards and reports
Safety dashboard
/dashboardOpen asWhat each level is responsible for, and the watchlist of who and what is heading for trouble, with the signals behind every row rather than a score.
One screen, three compositions: Kyle sees one site, Paul six, Sal all ten. No driver pill: a driver who reaches it another way is refused.
Reports
/reportsOpen asOne tab, five record types, and the grid changes its columns with the type. Filter by site, person, truck and date; every row opens the record behind it; the whole grid comes out as CSV.
No driver pill: reporting is supervision, and a driver's own records are on their home screen. Kyle sees his site, Sal all ten, and neither query mentions a site: RLS does it.
Comparison bands
/benchmarksOpen asThe numbers an outside body publishes, BLS and the like, that the dashboard colors rates against. Entered rows, not constants, so a revised band is a form and not a deploy.
Not targets. A VP writes, everyone signed in reads, and the database enforces both. Enter one for AFR and that tile stops being a bare number.
SpotterBeta (beta)
/spotterOpen asAsk about the company in your own words: "drivers out of compliance", "sites with a TRIR over 5". It reads the question into the filters you would have set, shows them as chips, and answers from the same rows as Reports.
Sal only: an add-on, VP only. When it is not sure it asks, at most twice; when it cannot answer, it says why. Also a box on Sal's dashboard.
Questions askedBeta (beta)
/spotter/logOpen asEvery question typed into Spotter, exactly as it was typed. The ones it could not answer come first: they are the list of what to build next, written by the people using it rather than by us.
Sal only: the log is VP-read in the database. The only screen in SCOPE whose clock is the real one.
Training and qualifications
Driver qualification files
/dqOpen asOne person's file as 49 CFR 391.51 asks for it: every line the job requires, what is held against it, since when, until when, and what is missing. Download it as CSV or print it.
A driver opens their own and may file a card; only a supervisor and above can check one. Daniel is one overdue course short of a clean file.
Training (LMS)
/trainingOpen asThe course library, the material each course teaches, the sessions that deliver it and the outside training somebody brings in. A session signed off is the record of who trained whom, when, and with what.
A driver browses the library and submits an outside certificate; a supervisor schedules and signs sessions; a GM or VP also edits the catalog.
Working documents
Rendered from the repository at each deploy, so they are never older than the app.
SOC 2 and security3 new
The readiness board, the work outside the code and the control calendar.
Clients and demos2 new
What a client costs us, what we ask them for, and how a demo runs.
Progress and questions1 new
Where the work stands, the questions waiting on an answer, and the rules to comment on.
Architecture and CI/CD1 new
How the code is organized, branched and shipped, and the checks every change passes on the way.
Tablet testing
Testing the tablet app on a real device, offline, and watching its inspections arrive.
The data model
Every table, its keys, rules and access, generated from the database as it stands.
Database review
Rebuilt from the repository at each deploy.
Download
Read online
Cover note: start here/hub/docs/dbaWhat the pack holds, the database in brief, what loading the schema elsewhere needs, and what the files cannot show.Review findings/hub/docs/dba-findingsPerformance, indexes, concurrent writes and access controls as measured, and the questions they raise.Hand-written. Measured 6 October 2026.Database inventory/hub/docs/dba-inventorySizes and row counts, every table, unindexed foreign keys, functions, triggers, grants, and every piece that is Supabase rather than PostgreSQL.Generated by scripts/db/gen_dba_pack.py. Re-run before sending.Architecture briefing for Patrick and Kylehttps://claude.ai/code/artifact/103009af-9305-44cd-8917-afd647b2eddbWhere SCOPE is today, three-tier against what we built, the decisions to agree before design starts, fit to the new client, risks and the open questions.A Claude doc. Private until shared from its own page.Reference documents
Who may see and do what, every table and column as built, and the sample data set.
Not built yet
So nobody looks for these in the launcher. In the order they will arrive.
- 1Incident capture offlineThe incident form still writes straight to the server. Photos from the yard will queue as separate upload jobs.