Your crew lead scans a QR code taped to the wall of the third-floor restroom. The timestamp logs. The system marks the zone as serviced. Everything looks clean in the dashboard — except the crew lead is sitting in his car in the parking lot, scanning a photo of the QR code he took last Tuesday.

This is not a hypothetical. Static QR codes — the kind printed on a sticker and stuck to a wall — can be photographed, shared, and scanned remotely. If the system treats the image alone as proof, it cannot tell the difference between a scan of the original code and a scan of a photo.

If you are using tag-based check-ins to prove your team was on site, the technology behind those tags matters more than most contractors realize. The difference between a QR code and an NFC tag is not just a hardware detail. It determines whether your proof of presence holds up when a client questions it.

Key Takeaways

Static QR codes can be photographed and scanned remotely, making them unreliable as standalone proof of presence.
NFC tags require physical proximity (typically within a few centimeters), which makes remote spoofing far harder than scanning a static QR image.
QR codes are still useful for public-facing displays and low-risk applications — they are not obsolete, just insufficient for accountability.
The tag itself is only one layer of proof. Timestamps, photos, zone mapping, and client-facing reports are what turn a scan into evidence.
When choosing a proof-of-presence system, evaluate tamper resistance, data ownership, and whether the records are shareable with clients.

How Tag-Based Proof of Presence Works

The basic concept is straightforward. A physical tag — QR code or NFC chip — is installed at a specific location inside a facility. When your crew arrives, they scan the tag with a mobile device. The scan creates a timestamped record that ties a specific person to a specific place at a specific time.

This record serves two purposes. First, it answers the "did they show up?" question without requiring anyone from the client side to be present. Second, it creates an audit trail that accumulates over time, building a documented pattern of consistent service.

The idea has been around for years. Some janitorial systems use QR codes to let the public view when an area was last cleaned. But the question is not whether the concept works — it is whether the implementation holds up under scrutiny.

And that depends almost entirely on the tag technology.

The QR Code Problem: Why Static Codes Get Gamed

A QR code is an image. That is the core vulnerability. It encodes a URL or an identifier in a visual pattern that any camera can read. Once that pattern exists in the physical world, it can be captured and reproduced.

The most common fraud vector is simple: a crew member takes a photo of the QR code on their first visit and scans that photo on subsequent visits without being on site. The system has no way to distinguish between a scan of the physical tag and a scan of a photograph of that tag.

Other vulnerabilities include:

Photo sharing. One crew member photographs the code and texts it to another who is not on site. Both log a "visit."
Screenshot reuse. A screenshot of the QR code stored in the camera roll can be scanned weeks later.
Code duplication. A QR code can be reprinted and placed anywhere. Without additional verification, scanning a copy is indistinguishable from scanning the original.

None of this requires technical sophistication. A crew member who wants to cut corners does not need to hack anything. They need a phone camera and five seconds.

For contractors, this creates a dangerous situation: you believe your check-in system is generating reliable proof, but the underlying data may be compromised. If a client requests an audit and you cannot demonstrate that your check-in records are tamper-resistant, the documentation you built to protect your business becomes a liability.

What NFC Changes About Verification

NFC (Near Field Communication) tags operate on a fundamentally different principle. Instead of encoding a visual pattern, an NFC tag contains a small chip that communicates with a mobile device via radio frequency — but only when the device is very close to the tag.

That physical proximity requirement is what changes the accountability equation. You cannot scan an NFC tag from across a parking lot. You cannot photograph it and scan the photo later. You have to be there, holding your phone against the tag, at the moment of the scan.

Some NFC implementations can add stronger tamper resistance through features like:

Unique identifiers. Many NFC chips expose a factory-set identifier that can help distinguish one tag from another.
Encrypted authentication. Some secure NFC products support challenge-response verification so the system can confirm the tag is authentic.
Dynamic or single-use tokens. More advanced implementations can rotate the value associated with a scan so replay attacks are harder.

The result is a check-in record that can be significantly harder to fabricate. It does not make fraud impossible — no system does — but it raises the bar well above "anyone with a phone camera."

For cleaning contractors, the practical difference is this: when a facility manager asks how you know your crew was on site, a well-implemented NFC-based record is usually a stronger answer than a QR-only one. It is the difference between "they scanned a code" and "they were physically at the tag location within arm's reach."

When QR Codes Are Good Enough

NFC is not always the right choice. QR codes have legitimate advantages in certain contexts:

Public-facing displays. If you want building occupants to scan a code and see when an area was last cleaned — a transparency feature, not a proof-of-presence feature — QR codes work well. The purpose is information, not verification.
Low-risk sites. For contracts where attendance is not disputed and the client relationship is strong, the fraud risk of QR codes may not justify the cost of NFC tags.
Budget constraints. QR codes can be printed for pennies. NFC tags cost more per unit. For a contractor deploying tags across dozens of zones in multiple facilities, the cost difference adds up.
Visitor-facing applications. QR codes are familiar to the general public in a way that NFC is not. If your workflow includes a public scan step — for example, allowing a facility manager to check service status from their phone — QR is often the more accessible format.

The key distinction is purpose. QR codes are useful for information sharing and low-stakes logging. NFC is often the better fit when the scan record needs to function as proof — when someone might challenge it, audit it, or use it to resolve a dispute.

What to Look For in a Proof-of-Presence System

The tag is only one component. A scan without context is just a timestamp. What turns a tag scan into meaningful proof is the system around it.

When evaluating a proof-of-presence system for your cleaning operation, consider:

Tamper resistance. Can the check-in be faked? If the system relies solely on QR scans with no additional verification, the answer is yes.
Contextual data. Does the system capture more than just the scan event? Timestamps, zone identification, and optional photo attachments create a richer record.
Client accessibility. Can your client see the records without asking you for them? A proof-of-presence system that only you can access is documentation, not transparency. The value multiplies when the client can verify service independently.
Data ownership. Who owns the service records — you or the facility? Some systems lock your data inside the client's quality management platform. If you lose the contract, your proof-of-work history disappears with it. Look for systems where the contractor retains access to their own records.
Zone-level granularity. A single check-in for an entire building is weaker proof than zone-by-zone scans. If your crew cleans six zones per shift, six scan events tell a more complete story than one.
Report generation. Raw scan data is useful for audits but hard for clients to interpret. Systems that generate automated service reports — pulling from scan events, photos, and completion data — turn your proof into a professional deliverable.

Whatever system you use, the goal is the same: tie check-ins to zone-level records, photos, and client-facing reports so the contractor retains usable proof of service.

How This Plays Out in a Client Dispute

Here is where the technology choice becomes concrete.

A facility manager contacts you on a Monday morning. They say the fourth-floor break room was not cleaned over the weekend. Your crew lead says it was. The facility manager says there were coffee rings on the counter and a full trash can when staff arrived.

With a QR-based system: You pull up the check-in log. It shows a scan at 10:47 PM Saturday. The facility manager asks how you know the scan was not done from outside the building. You do not have a good answer. The conversation stalls. The burden of proof is on you, and a QR scan alone does not carry it.

With an NFC-based system: You pull up the scan record showing a tap at 10:47 PM Saturday from the NFC tag mounted inside the fourth-floor break room. You also have a time-stamped photo taken at the time of the scan showing the cleaned counter and empty trash can. The system confirms the tag UID matches the registered tag for that zone. You share the report link with the facility manager.

The dispute does not escalate. The facility manager can see the evidence. If the break room was messy on Monday morning, it happened after your crew left — and you have the documentation to establish that timeline.

This is the scenario where your method for proving your team cleaned either holds up or falls apart. The technology behind the tag determines which side of that line you land on.

Making the Right Choice for Your Operation

For most cleaning contractors running multiple sites, the decision is not NFC or QR — it is knowing where each one fits.

Use QR codes where transparency and accessibility matter more than verification: public-facing scan stations, low-stakes sites, visitor-facing features. Consider NFC where the scan needs to function as stronger proof: high-value contracts, sites with a history of attendance disputes, or clients who require audit-ready documentation.

The technology is the foundation. But the real value comes from what you build on top of it — consistent documentation, client-accessible reports, and a proof-of-work record that follows your business from one contract to the next.

Elijah Weske is the founder of CleanScan, a platform that helps cleaning contractors document their work with verifiable service records and client-facing reports.

NFC vs QR Codes for Cleaning Proof of Presence