QR Inspector Portal
The inspector at the gate does not want a phone tree; they want the record. Read-only access is how they get it without anyone handing over the keys. The QR inspector portal is that answer made physical: a code that opens the site's compliance record for the person standing in front of it — read-only, no phone tree.
What is a QR inspector portal?
A shortcut from the jobsite to the record. On the platform, site-specific QR codes and view-only links make providing view-only access to others easy. The code is the doorway — the visitor lands in the site's record with exactly the access the client decided to give.
The code itself is worth posting where visitors already look: the gate, the posted-notice frame, the trailer window. A doorway does its job best when it stands where people knock.
How the access works
Each project gets its own doorway. The platform has view-only links and automatically generated QR codes for each site that can be shared. People who need standing access get it by name. View-only users can be added to any site at any time for controlled access. And what any of them can do once inside is bounded. Access to stored documents is controlled through the platform's view-only capability. Read-only is the operative phrase — the visitor sees the record; the record does not become theirs to change.
Who must be able to see the record
The audience for a stormwater record is written into the rules, and it is wider than the project team. The SWP3 must be made readily available at the time of an on-site inspection to the executive director; a federal, state, or local agency approving sediment and erosion plans; local government officials; and the operator of the municipal separate storm sewer receiving the discharge. The clock matters too. If the SWP3 is retained off-site, it must be made available as soon as reasonably possible — in most instances within 24 hours of the request. A code at the gate beats that clock by definition — the record is available in the time it takes to point a camera at a sign. The obligation to show the record was never optional; the only question was whether showing it would be graceful or a scramble, and the code decides that in advance.
The scramble this replaces
Everyone who has run enough projects has lived the other version. The inspector arrives, the plan is in a truck that is at the concrete plant, the super's phone goes to voicemail, and a routine visit turns into a retrieval exercise with an audience. Nothing was actually wrong — but the site spent its credibility on logistics, and the visit report reads that way.
The portal deletes the logistics. The record is at the gate because the gate is where the code is. The visit starts with the record open instead of ending with a promise to send it, and the impression left behind is the one the site earned: current paperwork, produced instantly, nothing to chase.
The platform behind it
Terradyne's SWPPP Compliance Hub runs on the cloud inspection platform behind our field program — it carries reports, corrective action items, and distribution lists. The portal is one face of that platform: the same record the project team works in, shown to outside eyes in a form they can read but not touch. There is no separate inspector system to maintain — the visitor reads the same record the team maintains, scoped to their purpose.
Frequently Asked Questions
Who can use the QR code?
Whoever the client decides should see the record — a municipal inspector at the gate, a reviewer, an owner's rep. The code opens a view of the record; it does not hand out the ability to change anything.
Can a visitor change or delete anything?
No — the access is view-only by design. Visitors see the record; the record does not become theirs to edit. Working access stays with the project team.
Why does on-demand access matter?
Because the record must be available to inspectors and agencies when they ask, and an off-site record runs on a clock. A code at the gate answers the request on the spot instead of starting a retrieval scramble.
Is each site's code unique?
Yes — codes are generated per site, so the gate code at one project opens that project's record and nothing else. Access is scoped to the site it belongs to.
What does a visitor actually see?
The site's compliance record in read-only form — the reports, the documents, the trail. What they cannot do is edit, reassign, or reach into any other project. Seeing and touching are different permissions, and visitors get exactly one.
Request a bid
Ask bids@terradynegroup.com or call (214) 878-7392 to see the portal on a live project record. The record behind the code lives in Cloud Records, the findings inside it in Digital Action-Item Logs, and the whole system under the SWPPP Compliance Hub.