Skip to content
QR Codes

One scan to the right control, worker, and asset.

Jobsite QR codes that turn field scans into safety workflows.

Print a code, put it where the work happens, and the phone camera does the rest. The gate code, the machine code, the SDS poster, the meeting board — each opens a different workflow, loaded with the right jobsite, asset, task, language, and worker profile. No app to install, no password to forget, nothing to search.

See one scan launch a workflowSee how Kayden hit 100% adoption with zero training
  • 100% · Zero formal trainingKayden reached 100% adoption across every department with zero formal training - proof that field-friendly safety tools can earn participation instead of chasing it.
  • 5.5 hrs/week · What the hunt for documents costsConstruction professionals lose 5.5 hours a week hunting for project data (PlanGrid/FMI, 2018). One scan puts the document where the worker is standing.

QR codes live on equipment, site gates, and individual floors. The platform meets workers exactly where they're standing.

Phone scanning a QR code on an excavator and instantly loading SWP-042 Trenching & Excavation with a 60-second safety briefing video
No app required
Context-aware workflows
Worker profile connected
Timestamped · GPS-tagged · logged

  1. No app, no password

  2. Context-aware workflows

  3. 21+ languages

  4. Credential checks at the scan

  5. Audit trail by default

Within a month or so of us starting to use SALUS, some of the comments were that if we were to take it away and go back to paper, that they would quit.

Kelly Kursteiner · Director, Occupational Health & SafetyWestUrban Developments
01Act 1 · In the field

Remove the first barrier to participation.

Scan without friction

Point the camera. The workflow is already open.

Workers aren't going to navigate a five-screen app menu to find a procedure - they're going to skip it. But QR codes are the low-friction entry point. One scan can open the right orientation, procedure, equipment check, SDS answer, toolbox talk, form, or corrective action workflow.

Worker at the jobsite scanning a QR code with a phone camera — verified with no password required, no app required, no navigation through menus, no clicks
→

No app

Reduce login and download friction.

→

Context

Open the workflow for the place or asset.

→

Record

Attach the scan to the safety record.

Participation starts with one scan.

See one scan launch a workflow
Scan everything

Context-aware QR codes.

In SALUS, a QR code at the gate, on a machine, in a zone, or on a poster can open a different workflow based on the jobsite, asset, task, language, credential, or worker profile.

Scan is simple. Context is powerful.

QR code scanned on a CAT 320 GC excavator boom, pulling up the senior operator's credential card, the asset's operational status and hours, and a completed pre-operational inspection
01 ·
Gate
Checks the worker into that site — day-one paperwork included.
02 ·
Machine
Opens that exact asset's pre-use inspection — see Equipment.
03 ·
Zone
That floor's hazards and forms, not the generic site pack.
04 ·
Poster
The SDS for the chemical stored behind it — see Searchable SDS.
02Act 2 · The record

Every scan becomes part of the record.

Worker profile

The profile travels with the scan.

One scan connects to the worker's portable profile. The worker is verified in seconds instead of re-onboarded for an afternoon.

New site, new gate. Same scan, same worker.

Worker profile for an HVAC technician with active certificates, a work permit, and a portable profile verified across three companies' projects
01 ·
Certificates
Active credentials with expiry dates, on the profile.
02 ·
Training status
Current, and checked at the scan.
03 ·
Access documents
Work permits and clearances, one scan deep.
04 ·
Forms
Every form they've signed, attached to the worker.
Every scan leaves proof

One scan in the field. One row in the audit trail.

Every scan is a timestamped, GPS-tagged, worker-identified event: who opened what, where they stood, when it happened, and which workflow followed. Gate entry, zone scan, dock check — each lands in the record the moment it happens. Nobody writes it down, because nobody has to: the audit trail is a byproduct of the work, not a second job after it.

Scanned. Stamped. Stored. Provable.

Audit trail listing a main hub entry scan, a warehouse zone scan, and a loading dock scan — each completed with a timestamp and GPS coordinates
03Act 3 · In the office

The office deploys the codes - and watches adoption increase.

Bundle builder

One QR code. A whole workflow behind it.

Behind every code is a bundle the office controls: open a form, play a briefing video, surface an asset profile, run a sign-in — stacked in the order the job needs. Build it in seconds, then deploy it yourself: generate, print, place. Under five minutes per code, no hardware, no IT ticket. When the workflow changes, update the bundle — the printed code never moves.

QR code creation screen building a Safety Asset Bundle from a site safety orientation, an equipment maintenance form, a forklift training video, and an asset profileGloved hand placing a printed QR code on a concrete column in less than 5 minutes, above three step cards: generate, print, place
▦

Form

Pre-targeted to the site, zone, or asset it hangs on.

▶

Briefing video

A 60-second briefing plays before the form opens.

⚙

Asset profile

The machine's full record, one tap deep.

✓

Sign-in

Attendance at the meeting board — see Toolbox Talks.

Bundled in seconds. Placed in minutes.

High visibility

Scanning creates adoption.
Adoption creates visibility.

When the entry point is one scan, participation stops depending on reminders and starts showing up as live data. Each scan is contextualized by worker, site, asset, task, GPS, timestamp, credential status, language, and workflow, so the office sees adoption as it happens and can trace every signal back to the source.

Every live signal traces back to the source scan.

Site operations dashboard showing 95% field adoption, 3,122 active workers, 134 subcontractors, and a timestamped scan log where one worker's certification status reads expired
01 ·
Live scan feed
Every site's scans, landing on one screen as they happen.
02 ·
Rosie flags
Expired certs and unopened briefings, surfaced from the stream.
03 ·
Adoption by site
Participation the office can see, not hope for.
04 ·
Source trace
Each signal ties back to the worker, asset, place, and scan that created it.
Business impact

More participation with less training.

The most expensive minutes on a jobsite are the ones nobody bills: walking to the trailer, hunting for the binder, asking the foreman where the procedure is. When information is hard to reach, workers wing it - and the office can't prove anything either way. A scan-first platform flips both: participation climbs because the cost of taking part collapses, and proof accumulates because every scan records itself.

Reclaim the search time

5.5 hours per worker per week goes to hunting for project data. One scan ends the hunt.

Kill the 'wing it' decision

When the procedure is one scan away instead of a trailer walk away, workers actually consult it.

Make proof automatic

The audit trail is a byproduct of the field workflow, not a separate documentation process.

Feature grid

What a jobsite QR code should have behind it.

01 ·

QR codes everywhere

Equipment, site gates, zones, individual floors — the code lives where the work is.

02 ·

No app, no password

The phone camera is the whole install. Access in one scan.

03 ·

Context-aware workflows

The same scan opens the right workflow for that site, asset, and task.

04 ·

Automatic translation

Rosie renders the workflow in the worker's preferred language — 21+ languages.

05 ·

Portable worker profiles

Certificates, training, and documents travel with the worker, site to site.

06 ·

GPS + timestamp audit trail

Every scan is a worker-identified, geo-tagged data event.

Connected workflows

What one scan can launch.

→

Orientations

Scan to clear workers at the gate.

→

Equipment

Scan assets for inspection and readiness.

→

Searchable SDS

Scan posters for SDS answers.

→

Toolbox talks

Scan to verify attendance.

Go deeper

From scan to workflow.

QR codes are strongest when the workflow behind the scan is already connected.

Request a demoSee orientationsSee equipment
FAQ

QR code, jobsite QR codes, scan workflow, participation, and audit trail FAQ

What are QR codes used for on construction sites?
Construction teams post QR codes on equipment, gates, zones, and posters to give workers instant phone access to safety workflows: inspection forms, safety data sheets, meeting sign-ins, site check-ins, and procedures. Each scan is logged with a timestamp and location, so access, attendance, and participation become verifiable records instead of paperwork.
Do workers need to download an app or create a password?
No. The QR code opens in the phone's camera — no app, no password, no menu navigation, no clicks. If they can use a phone camera, they can use SALUS. That's also why no training is required: the first scan is the onboarding.
How can the same QR code open different workflows?
Each code is tied to a place or asset, and each scan is tied to a worker profile. SALUS combines the two: the code on a machine opens that machine's workflow, in the scanning worker's language, with their credentials checked on the way in. Same gesture at the gate, the zone, or the poster — a different workflow, decided by the context.
Can QR codes track who is on a jobsite?
Yes — as a record, not a turnstile. Gate and zone scans create timestamped, GPS-tagged, worker-identified events, so the office can answer who scanned in, where, and when — live on the dashboard. Physical access control stays with your site setup; SALUS makes the record of it automatic.
Are QR codes secure enough for jobsite use?
A printed code is just a pointer — the security lives in what it points to. Static codes that link to open documents can be copied or swapped; codes that open managed workflows attach identity at the scan and log every access. In SALUS, the office controls what each code opens, and every scan is worker-identified and audit-trailed.
What happens if a worker's certification is expired?
It's caught at the scan. The credential check runs before the workflow opens, and the expired ticket is flagged before work starts — not discovered in a records review weeks later.
What languages does SALUS support?
21+ languages, on any device. Rosie, the AI Admin & Risk Assistant, detects the worker's preferred language and renders the workflow in it automatically — no settings to hunt for.
Does it work for subcontractors who move between sites?
Yes. One scan and the worker has a profile that travels with them — certificates, training records, access documents, and signed forms follow them from site to site, GC to GC.
How long does setup take?
Under five minutes per code: generate, print, place — on equipment, gates, and floors. No hardware installation, no IT project. When a workflow changes, you update the bundle, not the printed code.
How is SALUS different from a generic QR code generator?
A generator creates a code. SALUS connects the scan to safety workflows, worker profiles, jobsites, assets, languages, credentials, GPS, timestamps, and audit trails.
What should we bring to a QR code demo?
Bring one poster, asset tag, gate sign, SDS station, meeting sign-in, or field workflow. SALUS can show what the scan should open and what proof it should leave behind.
Can QR codes support equipment tracking?
Yes. QR codes can open asset profiles, pre-use inspections, operator verification, deficiencies, and fleet readiness workflows.
Verified compliance resource

Need the rule behind the workflow?

Use the dated OSHA for Construction field guide for current penalties, inspection steps, recordkeeping, and heat-rule status.

Explore the OSHA field guide
Scan demo

Show us one field workflow.
We will show what the scan should open.

Map the QR entry point, worker profile, context, language, and audit trail for one workflow.

See one scan launch a workflow

Bring the current workflow. We will map the live version from field action to proof.