Part of the Product series on the Mobtag platform.

In short: The first screen after a scan is where trust is won or lost. Templates that surface safety- and job-critical data first, with the right validation, beat another report nobody opens on site.

A template is the contract between what the business must know and what a human can act on in 10 seconds in rain, with gloves, on a shaky connection. The failure mode is not a missing field once—it is partial history, three field orders across sites, and an auditor who sees a different “official” shape every time.

What to put on scan one

  • Identity before commentary: serial, site, status, and contract so nobody updates the wrong line.
  • The job block next: PPM, statutory, or return flags—before optional “nice to have” marketing fields.
  • Tight pick lists where you can: free text is how one part number becomes three.
Principle What you avoid
One template per equipment class Mixed, incompatible questions on one form
Validation in-app A cleanup project the week before an audit
Aligned to your SOP Training drag when every site has its own “version” of the truth

Roles, contractors, and the same record

HSE may need photos; a contractor may be limited to a subset. Field visibility by group is how you get one system of record without a data fight—everyone still lands evidence on the same asset. The point is not one beautiful universal screen; it is one coherent profile under the tag.

flowchart TB Z[User scans] --> T[Template for asset class] T --> C[Show critical + identity block] C --> R[Sign-off / photos as policy requires] R --> L[Record saved to asset]

Summary: The first screen is your cheapest insurance against wrong-part work, late evidence, and the assumption that “someone else updated the record.”