Contractors HSE Passport brings the training and certification status of employees, contractor workers and visitors onto one platform and returns a live Go / No-Go decision for every person. The prototype below mirrors the real application flow.
Today training and certification records live in folders and spreadsheets, and nobody can tell at the gate who is actually compliant. The application automates that decision.
A unique QR-coded passport for every worker. Overall Go / No-Go status visible at a glance on the front screen.
The mandatory training set is derived from the person's role and site; a missing or expired document turns the passport red instantly.
Workers upload certificates from their phone, the HSE team verifies them in the console, and every decision is logged.
Workers and their line managers are notified before certificates and medical certificates expire.
The passport can be shown without connectivity; queued actions sync automatically once the device is back online.
Compliance for each contractor company is consolidated on one screen, with gaps reported per company.
Tap the buttons and the bottom tab bar to move through the real flow. Switch roles to compare the worker, manager / HSE and site security views.
Status is never expressed by colour alone — colour, icon and text always travel together. Click any screen to open it in the prototype.
A four-step core flow, continuously re-evaluated in the background by the compliance engine.
The worker registers through an invitation link and completes their profile and personal information.
Training certificates and the medical certificate are uploaded from the phone; the system pre-checks them.
Line manager and HSE review the documents and approve, reject or request a revision.
The system issues the QR passport, sets the Go / No-Go status and it is scanned at the gate.
The mandatory training set is calculated from the person's role and the site they will work on, then every item is checked individually.
The scope file asks for an application that behaves like the digital safety passport solutions already deployed on industrial sites. We reviewed the alternative applications in use in the field, together with the reference screenshots supplied with the requirements, kept the patterns that work — and closed the gaps the scope explicitly asks for.
| Aspect | Alternative apps in the field | This project |
|---|---|---|
| Profile structure | Employee Profile with collapsible sections: Personal Information, Work Locations, Position Courses, Certificate, FPE, Status of Duty, Matter of Personal Safety Information. | The same section structure is retained so the experience stays familiar to users of existing apps, plus emergency contacts and profile photo.KEPT |
| Passport identity | Passport Card ID and Employee ID, an Active badge, Creation Date and Expired Date on the passport itself. | The same identity model, plus a signed QR token that can also be validated offline.EXTENDED |
| Course status | Courses grouped under categories (DOJO Induction, PPE Awareness, BST, Medical Certificate); each row is green when completed and red when not. | The same grouping and colour logic, plus an amber “awaiting verification” state and an expiry countdown.EXTENDED |
| Overall status | Status has to be read from the individual course rows; a single overall indicator on the front screen is usually missing. | Front screen shows the overall Go / No-Go status and a compliance score, as required by scope item 12.ADDED |
| Verification | Records are maintained centrally; safety induction is typically handled by a separate kiosk application. | A single web console for HSE: verification queue, approve / reject / request revision, full audit trail.ADDED |
| Scanning | QR codes are scanned from documents and the user's details are displayed. | QR scanning for gate control plus document upload with automatic reading of validity dates.EXTENDED |
| Points | The profile commonly carries a points balance (370 in the reference screenshots). | Included in the prototype as an optional element — scoring rules to be confirmed.TO CONFIRM |
| Language | Course names are commonly bilingual (local language _ English), with the interface in English. | Bilingual course naming supported; application language set to be confirmed.TO CONFIRM |
| Offline use | Rarely supported; offline behaviour is generally not documented. | Offline passport display and queued actions, as required by scope item 6.ADDED |
Topics to decide together on top of the prototype. Each one directly changes how the application behaves.
Which trainings are mandatory for which role? Who defines the matrix, and on which screen?
How long is each training valid? Is a grace period allowed once it expires?
Two states (Green / Red) or three (Green / Yellow / Red) on the front screen? The scope currently uses both.
Is validation done by reading the document, by a QR-coded certificate, or through an LMS integration?
Single-step approval, or line manager and HSE in sequence?
Will security staff scan with a phone, or is turnstile / kiosk integration expected?
Can a contractor company register and manage its own workers?
Corporate SSO for company employees? Is a separate identity pool acceptable for contractors?
Is the medical certificate stored, or only its validity status and fitness result?
Comparable applications carry a points balance on the profile. Is scoring in scope, and what earns points?
Do visitors install the app, or is a temporary link / QR sufficient?
Will historical training records be migrated? In what format and to what extent?
