
QR codes for equipment maintenance: make fault reporting easier
ON THIS PAGE
- Define the report before you print the label
- Give each machine a clear identity
- Ask for details the maintenance team can use
- Make the scan instruction specific
- Keep fault reporting as the main action
- Separate scans from maintenance results
- Choose the setup that matches the number of machines
- Common questions
Staff see a fault at the machine, but reporting it means finding a form, identifying the equipment and explaining where it is.
A staff member hears a new rattle from a shared machine. They can read its asset label and take a useful photo. This is the best time to report it. Returning to a desk to find a general form adds work and may lose useful detail.
A QR label lets them open the right page while the equipment is still in front of them, describe what they observed and report it through the maintenance team’s existing tool.
Real facilities teams use this approach. At the University of British Columbia, technicians scan QR labels on university-owned equipment or infrastructure through the Planon Mobile Field Service App. Authorized users can view asset information and associate it with a work order.
Kennesaw State University uses machine-level QR labels for campus laundry equipment. If a washer or dryer needs repair, the reporter scans the QR code on that machine, enters the printed machine identifier, adds the building and unit, describes the issue and submits a service request. In both cases, the maintenance system remains responsible for the work after the scan.
Define the report before you print the label
A good equipment label supports a short, predictable sequence:
- A staff member sees or hears a problem.
- They scan the label on that machine.
- The destination confirms which equipment they are reporting.
- They describe what they observed and attach a photo if useful.
- The existing form, help desk or CMMS accepts the request and provides a confirmation.
Decide what happens at step three before creating the QR code. The best destination may be a direct request form, an equipment page with a prominent Report a fault button, or an authenticated asset record for technicians.
Keep emergency reporting outside this routine. The University of Sussex, for example, uses building-specific QR requests for routine facilities work but publishes phone numbers for emergencies. Put the urgent number and a short instruction on the physical label where staff can read it without scanning.
Give each machine a clear identity
A generic maintenance homepage adds identification work back into the process. A label on Chiller 2 should lead to the Chiller 2 reporting path, or at least make that asset unmistakable when the page opens.
Use one QR code per machine when you need a distinct destination or distinct scan count. Print a human-readable asset ID beside it. Include the location if similar equipment sits in several rooms or buildings.
If your form tool supports a prefilled asset ID in its URL, create that URL in the form tool and test it before using it as the destination. If it does not, show the asset ID on the label and tell the reporter where to enter it. Kennesaw State’s laundry instructions use this practical fallback: the machine identifier appears beneath the QR code.
A Graklink dynamic QR code opens the URL you set. Your form or CMMS handles asset prefill, request creation, assignments and maintenance records.
Ask for details the maintenance team can use
Keep the mobile form short enough to complete while standing beside the equipment. Confirm the machine name and asset ID near the top. Then ask for the observed problem, when it was noticed, a photo and whether the equipment is still operating. Collect reporter contact details only when your process needs them.
Avoid asking staff to diagnose the failure. “Grinding sound during startup” is more useful than forcing someone to select a technical cause they cannot verify.
After submission, the maintenance tool should show a clear acknowledgement. If it provides a request number or email updates, tell the reporter what to expect.
Make the scan instruction specific
Many staff members can scan without installing another app. On an iPhone, Apple supports scanning through the Camera app. Camera from Google can scan in QR mode or the default photo mode on selected devices.
A short label instruction is enough: Open your camera, scan the QR code, then tap the link. Test it on the phones people actually carry, including managed devices with camera or browser restrictions.
Some maintenance systems require their own app or an authenticated account. Say so on the label. UBC’s equipment page tells technicians to use its Planon mobile app and gives everyone else a service-centre contact.
Add a readable short link as a fallback when practical. It helps someone with a damaged camera, a device that cannot scan, or a label installed at an awkward angle. Keep the asset ID and urgent phone number readable without any device.
Keep fault reporting as the main action
Operators may also need a manual, startup checklist or vendor contact. If those resources share one destination, put Report a fault first and label the other links clearly. Do not make someone search a long instruction page for the reporting form.
A Graklink hosted page can provide a mobile destination with the report link and approved equipment information. The form or CMMS receives the report, assigns the work and records what happened.
Separate scans from maintenance results
Basic scan counts can tell you whether a machine label is being opened. They cannot tell you that a fault was submitted, accepted, repaired or closed. Someone may scan and leave. Someone else may use the printed short link or call the service number without scanning.
Compare each label’s scans with the actual requests recorded in your form or maintenance system. A label with no scans may be hard to see or placed where staff do not pause. Many scans and few requests may mean the form is difficult to finish, the destination requires an unexpected sign-in, or people also use the page for equipment information. Check the workflow with staff before deciding why.
Use the maintenance system for submitted and completed job totals. Separately coded machines or placements let you compare scan activity. Use a controlled placement comparison when you change label position or wording, and keep ticket and repair results in the maintenance system.
Choose the setup that matches the number of machines
For one machine or a small pilot, one dynamic QR code is the direct fit. Each includes destination editing, unlimited scans and basic scan counts. If the form provider, vendor or equipment page changes, update the destination without replacing the printed label.
For several machines or locations, use separate QR codes to compare label scans while your existing equipment register and maintenance tool keep the operational records.
Start with a few shared machines. Install the labels, scan each one from a normal standing position, submit test reports and confirm they arrive in the correct system with the expected machine information. Then review the actual reports. If people still omit the location or choose the wrong asset, fix the destination form or label before adding more equipment.
Common questions
Can one QR code cover several machines?
It can open a general equipment list, but the reporter must still identify the machine. A separate QR code for each machine gives each one its own destination and scan count. Multiple copies of the same QR code share both.
Does scanning a Graklink QR code create a work order?
No. The scan opens the destination URL you set. Your form, help desk or CMMS must create and manage the request.
Should the QR code open a manual or a fault form?
For staff reporting problems, make the fault form the primary action. If operators also need approved instructions, use a mobile page with a clear Report a fault button and secondary links to the relevant information.
Do staff need a QR scanner app?
Often they can use the phone camera. Apple supports scanning through the iPhone Camera app, and Camera from Google supports QR scanning on selected devices. Test the phones used at your site and label any app or sign-in requirement.
Sources and verification dates
Source links, check dates and available archived copies are listed below.
- UBC Facilities: Urban assets QR code
view asset information, associate the asset to a work order
Checked September 19, 2026.
Public scan destination for equipment or infrastructure owned and operated by UBC Facilities; no login was needed to read its instructions in the indexed result.
The operational page gives no publication date, rollout size or maintenance outcome data.
- Kennesaw State University: Laundry maintenance
Scan the QR Code located on the machine that needs repair.
Checked September 19, 2026.
The page lists the machine-level reporting steps and displays an example laundry maintenance QR code.
The example covers campus laundry equipment served by an outside provider.
- University of Sussex: Scan a QR code to request maintenance support
Each QR code is tailored specifically to the building it’s in
Checked September 19, 2026.
Dated October 2, 2025; the page separates routine QR requests from emergency phone calls.
The example covers building-level facilities reporting rather than one QR code per machine.
- Apple Support: Scan a QR code with your iPhone or iPad
Use your Camera app or Code Scanner to quickly access websites, apps, tickets, and more.
Checked September 19, 2026.
Published September 14, 2026.
The instructions apply to supported iPhone and iPad software; other devices vary.
Make your QR code in a minute
$7.99 once. Unlimited scans. 30-day money-back guarantee.
