Guide
Vendor check-in methods compared: which ones actually prove presence?
The check-in method you choose decides what record you'll have when an invoice, a service-level agreement or an audit asks whether a vendor was really there. A keypad phone tree proves a call, a QR scan proves a scan and a photo proves a photo; only location-based methods place the technician at the site. The strongest record ties who, where, when, how long and what was done to the work order, for every vendor, captured during the visit.
By David Torchiano, Co-Founder
Last updated · 6 min read
Why does the check-in method matter to your business?
A check-in isn't just a status change. It's the evidence you'll reach for later, often months later, when someone asks whether a visit happened the way it was billed and reported:
- Invoice approval. Billed labor can only be checked against time on site if arrival and departure were captured independently of the vendor's invoice.
- Contract and SLA compliance. Response-time and scheduled-service terms need a verified arrival time. Without one, a missed SLA looks the same as a met one.
- Audits and inspections. Recurring services that a landlord, insurer or inspector may ask about, such as hood cleaning, fire system checks or backflow testing, need a record that the visit happened, when and by whom.
- Site security and incidents. When something goes wrong at a location, you need to know which technicians were on the premises, from which company, and when they arrived and left.
- Vendor performance. Scorecards and contract renewals are only as fair as the data behind them. Self-reported times reward the vendors who report generously.
How do the vendor check-in methods compare?
| Method | What it proves | Technician effort | Spoofing risk | Needs an app? | Best for |
|---|---|---|---|---|---|
| Keypad phone tree (IVR) | That someone called with a work order number, and when | Medium: menus and long numbers to key in | High: the call can come from anywhere | No | Logging a call against a work order when location doesn't matter |
| GPS geofencing app | The device's location while the app is running, often arrival and departure | High to start (install, log in, permissions), low after | Medium: mock-location tools work on some phones | Yes | In-house technicians, or a vendor that has standardized on one app |
| Texted location link | The device's location at the moment of check-in | Low: one tap that opens in the phone's browser | Medium: location can be declined, or faked on a modified phone | No | Many vendors and subcontractors who won't install an app |
| QR code or NFC tag at the site | That the tag was scanned | Low to medium | QR: high, since a photo of the code scans anywhere. NFC: lower, but tags can be removed or cloned | Usually | Sites where you control the tag and want proof at a specific room or asset |
| Timestamped photo | That a photo was taken at a time; the place is unclear unless location data is kept | Low | Medium: older photos can be reused and metadata edited | No | Showing the condition of the work, alongside another check |
| Voice AI call + texted location link (spryggAIVR) | Who called, the device's location at check-in, check-in and check-out times, and a spoken record of the work | Low: a phone call and one tap | Medium for location (same limits as a texted link); off-site and unverified visits are flagged | No | Multi-site operators with many vendors who need one process for all of them |
What data does each check-in method leave you with?
When a dispute or an audit comes up, what matters is the record each method actually produces. Here is what you can expect to have on file after a visit:
| Method | Who | Where | Arrival time | Time on site | Work performed | On the work order? |
|---|---|---|---|---|---|---|
| Keypad phone tree (IVR) | A phone number, sometimes a PIN | No | Yes, the call time | Only if they call again to check out | Rarely, a resolution code at most | Usually, when the IVR belongs to your work order system |
| GPS geofencing app | The logged-in user | Yes, while the app runs | Yes | Yes, from leaving the geofence | Depends on the app | Only if the app connects to your system |
| Texted location link (alone) | The phone the link was sent to | Yes, once at check-in | Yes | No | No | Depends on the provider |
| QR code or NFC tag | Often anonymous | The tag's location, if it wasn't copied | Yes, the scan time | Only if scanned in and out | No | Depends on the provider |
| Timestamped photo | No | Only if location data is kept | Only if metadata is kept | No | The condition of the work | If someone uploads it |
| spryggAIVR | Caller ID matched to the technician and their company, or the company's PIN | Yes: the phone's location at check-in, compared with the site address | Yes | Yes, from the check-in and check-out calls | A completion report from the technician's own words (work performed, parts, follow-up) plus texted photos | Yes: ServiceChannel, spryggCMMS and Google Sheets, plus email |
A record that only exists in a vendor's app or a separate portal is one your team has to request, export and match by hand. A record written to the work order is there when the invoice is approved and when an auditor asks. See what syncs to each system.
What makes a check-in record hold up in an audit or a dispute?
- It was captured during the visit. Times and location recorded when the technician was there carry more weight than a timesheet filled in afterwards.
- It names the person, not just the company. Contracts often say who may work on site. A record of the individual technician shows whether an unknown subcontractor did the job.
- It doesn't depend on the vendor's word. Arrival, departure and location come from the check-in itself, not from the invoice the record is meant to check.
- Every vendor gets the same check. A standard only one vendor follows can't be audited across a portfolio. One process for every site and vendor makes records comparable.
- Failures are recorded, not hidden. An off-site location or a declined location request should show on the record, so the visits that need a second look are easy to find.
- It lives where your team works. Records on the work order in your CMMS or spreadsheet can be found by work order, site or vendor when the question comes.
What are the limits of a texted location link?
A texted link removes the app, which is why vendors actually use it. It also has limits worth knowing before you rely on it:
- It needs permission. The technician has to allow location access in their browser. If they decline, spryggAIVR marks the visit unverified and shows only the approximate area the phone number is registered to.
- It checks once, not continuously. The link confirms location at check-in. It doesn't track the technician afterwards; time on site comes from the check-in and check-out calls.
- It needs a smartphone. A technician on a basic phone can still call in, but without the tap the visit can't be location-verified.
- Location can be faked on a modified phone. Like any phone-based location check, it can be fooled by mock-location tools. spryggAIVR's link is single use, tied to that call and expires shortly after, and a location outside the site's radius is flagged off site.
No phone-based method is tamper-proof. For compliance, what matters is that every visit gets the same check, and that the visits that fail it are flagged rather than silently accepted.
How do you choose the right check-in method?
- List the questions you'll need to answer later. Was the invoice accurate? Was the SLA met? Did the required service happen? Who was on site? The method has to capture the data each answer needs.
- Count who has to adopt it. In-house technicians will install an app; a long list of vendors and subcontractors mostly won't. A gap in adoption is a gap in your records.
- Check what happens when it fails. Declined location, no smartphone, a copied QR code: does the visit get flagged, or does it pass?
- Check where the record goes. Proof that never reaches the work order your team approves invoices from doesn't get used.
- Combine methods where it helps. A photo of the finished work adds to a location check; it doesn't replace one.
If all of your technicians are your own employees and already run a field service app with GPS check-in, that app may be enough. For the full criteria to compare providers, see how to choose a vendor verification service.
Frequently asked questions
What is the most reliable way to verify that a vendor checked in?
Capture identity, location and time at the moment of check-in and tie them to the work order. A location check from an installed app or a texted link does this; a phone tree, QR scan or photo on its own does not.
What records do I need to show a vendor met its SLA?
A verified arrival time for each visit, captured independently of the vendor, on the same work order as the dispatch or due time. With both on one record, response time is a comparison rather than an argument.
Can technicians fake a GPS check-in?
On some phones, yes: mock-location tools can fool any phone-based location check, app or link. Single-use links tied to the call, a radius around each site and flagging off-site or unverified visits make it much harder to do quietly.
Is a keypad phone tree enough to prove a technician was on site?
No. It proves that someone called with the work order number and when. It can't tell where the caller was standing.
Do QR codes at the site prove presence?
Only if the code can't be copied. A photo of a QR code scans just as well from a parking lot, so QR codes are best for proving which room or asset was visited, alongside another check.
Does spryggAIVR need an app?
No. Technicians call one number, and the only tap is a texted link that opens in the phone's browser to confirm location.
Try spryggAIVR on your own work orders
Every plan starts with a 30-day free trial. No credit card required.