🔧 Any Tech Can Now Log Service Through Your QR Code — No App Required

Here is a situation every building manager and HVAC contractor has dealt with at some point: you hire a one-off tech to handle a repair, they do the work, they leave, and the maintenance log never gets updated. Maybe they scribbled something on a work order that ended up in a filing cabinet. Maybe the verbal summary you got over the phone was the last you heard about it. Either way, your digital records are now out of date.

That gap is exactly what we closed with this update. Starting today, any technician who scans the Link Mode QR code on a piece of equipment can submit a service or repair record directly through their phone browser — no Equipment Tracker account required, no app to install.

How It Works for the Guest Tech

When a guest technician scans the Link Mode QR tag on a unit, they land on the public specification page — the same read-only page they have always been able to see. The difference now is a "Log Service / Repair" button at the top of the maintenance history section.

Tapping it opens a full service submission form right in their phone browser. They fill out the service date, pick the type of work (Preventive Maintenance, Repair, Inspection, Installation, Emergency, or Other), enter their name and company, describe what was done, list any parts replaced, and optionally attach a before photo and an after photo from their camera roll.

Hit submit. Done. The whole thing takes about two minutes, and it requires nothing from them beyond a phone with a camera.

What You Receive as the Account Holder

The submission lands in your Transfer Inbox in real-time. It shows up as a guest record with the technician name, company, service type, description, parts used, and any photos attached. You have two options: Accept, which imports it directly into the equipment maintenance history including any photos, or Decline, which permanently deletes the submission and removes the photos from storage.

This is important: guest submissions are not automatically merged into your records. They come in as pending inbox items that require your explicit approval before they become part of the equipment history. That keeps your data clean and gives you a chance to verify the details before they are permanently logged.

The before and after photos are stored in our secure Firebase cloud storage and attached to the record, so you get the full visual documentation whether or not the tech is standing in front of you.

Why We Built It This Way

The design goal was to remove every possible obstacle for the person submitting the service. If they have to download an app, they probably will not do it. If they have to create an account, forget it. The QR code is already on the unit. The form opens in their browser. That is the entire workflow from their side.

At the same time, the account holder stays in control. Nothing gets added to your database without your review. You either accept it as submitted or decline and delete it. The guest never touches your actual equipment records directly.

The Vendor Field Is Now Separate on All Records

As part of this update, we also separated the technician name from the contracting company across all maintenance records — not just guest submissions. Previously both landed in a single "Technician" field, which made records like "John Smith / Apex Mechanical LLC" harder to filter and report on.

Now there are two distinct fields: Technician Name and Company/Vendor. Both show up independently on service lists, in generated PDF reports, and in the maintenance history view. The vendor field is included in all exports, imports, peer-to-peer pushes, backups, and cloud syncs — so your records stay properly attributed no matter how the data moves.

Jonathan Curtis

HVAC Technician & Founder · Equipment Tracker Pro

Jonathan Curtis is an HVAC technician and the founder of Equipment Tracker Pro. He built the app to solve real problems he encountered in the field — including the frustration of service calls that never made it into the maintenance log.