Greppers Capstone
In progress
A Prototype for the SFI Foundation
Today is a prototype review. We'll walk the build, compare it to SFI's current public system, and invite your direction on where the real system should go next.
Current System
SFI's current site holds the right standards — but they're buried. There's no search, no way to sign in, no way for a driver, inspector, or staff member to see anything tailored to them, and every standard change has to route through someone who can edit the page by hand.
Prototype System
A working prototype of what an SFI-run system could look like: sign-in with profiles, plain-English search, a photo identifier for safety gear, light quizzes for learning, and a dashboard that lets your staff update the site directly. It's a preview — and an invitation to shape where it goes from here.
Prototype Build
Plain-English Search
Find any of 140+ safety standards by name or description — no memorizing numbers, and typos are fine.
Identify Equipment by Photo
Photograph a piece of gear and the prototype tells you the standard it's meant to meet — right on the phone, nothing uploaded.
Sign-In That Knows You
Drivers, inspectors, and staff each sign in and see the tools and information relevant to their role.
Staff Dashboard, No Code
Your team updates standards, manages roles, and keeps the site on-mission — without a developer in the loop.
Three Focus Areas
The people, the features, the foundation.
Three lenses to read the prototype through — who uses it, what's new about it, and how the foundation stays in charge of every word on the page.
Who It's For
- Drivers, inspectors, and staff all sign in
- Each person sees the tools that fit their role
- Profiles remember history and preferences
- A place for inspectors and staff to talk
What's New
- Search in plain English — not by standard number
- Point a camera at gear, get a standard back
- Learn through short quizzes and checkpoints
- Photo checks happen on the phone, nothing uploaded
Your Control
- Edit a standard; the site reflects it the same day
- Decide who can see and do what
- Keep content on-mission — moderation is built in
- Every change leaves a record
Prototype in Practice
Three moments, three people.
What the prototype feels like in the hands of a driver, an inspector, and your own staff.
Type it the way you'd say it.
A driver's parent types "fire suit for my son" — not a standard number. The right junior rating comes up first, with close alternatives right behind it.
Point the phone at the gear.
An inspector at the track aims a phone at a helmet, suit, or harness. The prototype names the standard it's meant to meet — without sending a photo anywhere.
Your staff, in charge.
A staff member updates a standard from a simple dashboard. The site reflects the change the same day — no email to a developer, no waiting, no deploy.
Three roles, one prototype, one foundation in control.
Every path through the prototype begins with someone signing in, passes through the features they need, and ends at the dashboard where your staff keep the whole thing accurate and on-mission.
Who signs in
What they use
Who stays in control
Discussion Agenda
Your direction from here.
The prototype is a starting point. We'd like your take on which pieces matter most — and whether the work continues in the fall with 3rd- and 4th-year students on the real system.
Prototype Direction
- Which features are most important to the foundation?
- What's missing that you'd expect at launch?
- Where should further prototype work focus?
- Which role — driver, inspector, staff, fabricator — needs attention first?
Beyond the Prototype
- Fall engagement with 3rd- and 4th-year students
- Shape the real system — data, hosting, ownership
- Roadmap from capstone prototype to launch
- How the foundation wants to steer longer-term work