Guide
Check-in add-on or CMMS replacement? Fixing vendor check-in without switching systems
If the problem is that vendors skip check-in or that check-ins can't be trusted, a verification layer that plugs into your existing CMMS can fix it without a migration, because the gap is in how visits are captured, not in how work orders are managed. Replacing the CMMS is the right call when the system itself falls short: it can't handle core work order, asset or invoice work, it can't share data with other tools, or you're moving off it anyway. spryggAIVR is a verification layer that adds voice check-in and check-out, a location check and a completion report to the work order in ServiceChannel, spryggCMMS or a Google Sheet, with Corrigo and Accruent coming soon.
By David Torchiano, Co-Founder
Last updated · 5 min read
Who provides check-in verification that plugs into an existing CMMS?
You have a few options that don't involve changing your CMMS:
- Your CMMS's own check-in tools. Many CMMS platforms, ServiceChannel among them, include their own check-in options. If every vendor uses them and they give you the proof you need, start there.
- A vendor's own field service app. Some vendors run apps with GPS check-in for their technicians. The record helps if it reaches your work order, which depends on that vendor's integration.
- A verification layer. A separate service that every vendor uses the same way, that checks presence at the site and writes the result back to your work orders. spryggAIVR is one: technicians call one number and tap one texted link, with no app.
Whichever you choose, the test is the same: does it produce trusted visit data for every vendor, on the work order your team approves invoices from?
Is your check-in problem a CMMS problem?
Start with the symptom. Many check-in problems sit in the moment a technician arrives and leaves, which a new CMMS doesn't change on its own if vendors still have to adopt a new tool. Others are real limits of the system.
| What you see | Where it usually comes from | Where to fix it |
|---|---|---|
| Vendors skip check-in | Check-in depends on an app or a phone tree vendors won't use | The check-in layer |
| Check-ins can't be trusted | Nothing confirms the technician was at the site | The check-in layer |
| Work orders close with no detail | Nothing captures the work performed when the visit ends | The check-in layer |
| No-shows are found days later | No live view of who has arrived | The check-in layer, with monitoring and alerts |
| Every site and vendor checks in differently | Each vendor follows its own process, or each client's | The check-in layer, with one process for all |
| Preventive maintenance is missed | Scheduling and PM plans | The CMMS |
| No reliable history per asset | Asset records and work order structure | The CMMS |
| Invoices can't be approved in the system | Invoice and approval workflows | The CMMS, or your AP system |
| Data can't get in or out | No API or import and export | The CMMS |
When should you add a verification layer, and when should you replace the CMMS?
| When to add a verification layer | When to replace the CMMS |
|---|---|
| Your CMMS handles work orders, dispatch and invoices well, and the gap is proof of the visit | The CMMS can't do core work you need, such as preventive maintenance, asset records or invoice approval |
| Vendors resist installing another app or using a phone tree | Your team struggles with the system across the board, not just at check-in |
| You need one check-in process for vendors and sites that work in different systems | You've already decided to consolidate several systems into one |
| Your CMMS can share data with other tools, or you work from a spreadsheet | The system can't send or receive data, so nothing can be written back to it |
| Your work order history, reports and vendor setup live in the CMMS and would be costly to move | The system is being retired, or its contract is ending and you'd be moving anyway |
| You want verified visit data without retraining your team | The cost of the system's gaps is greater than the cost and disruption of moving |
These aren't mutually exclusive. If you're replacing your CMMS, check that your check-in layer works with the new one. A layer that works across systems keeps check-in the same for vendors during the move, and a new CMMS doesn't by itself solve vendor adoption.
What changes for your team and your vendors in each case?
| What changes | Add a verification layer | Replace the CMMS |
|---|---|---|
| Your team | Keeps working in the same system; verified data shows up on the work order | Learns a new system and new workflows |
| Your vendors | Call a number and tap a link, with nothing to install (in English or Spanish on Scale and Enterprise plans) | Learn the new system's check-in and invoicing steps |
| Your data | Stays where it is; new visit records are added to it | Has to be migrated, mapped and checked |
| Other integrations | Unchanged | Rebuilt for the new system |
| When results start | Once the systems are connected and vendors have the number | After migration, training and vendor onboarding |
| What it doesn't fix | Gaps in the CMMS itself | Vendors who don't check in, if the new system's check-in has the same adoption problem |
What should a verification layer write back to your CMMS?
A layer only pays off if its data lands where decisions are made. Use this as a checklist: ask any provider which of these it writes to your work orders in your system, since the answer can differ from one system to the next, and check what each one drives:
| Data on the work order | What it drives |
|---|---|
| Verified check-in time | SLA response-time reporting on verified arrivals, not times the vendor entered |
| Location result: verified, off site or unverified | Which visits need review before the invoice is approved |
| Check-out time and time on site | Comparing billed labor with the visit |
| The technician, and the company they work for | Who was on site, and where subcontractors are used |
| Completion report: work performed, parts, follow-up | Closing the work order, scheduling follow-ups and checking billed parts |
| Photos | Confirming the result, and evidence if an invoice is questioned |
| Work order status | A live picture of open and in-progress work, without calling sites |
A record that stays in a separate portal has to be exported and matched by hand, which is the work a layer is supposed to remove.
How does spryggAIVR work alongside your CMMS?
spryggAIVR reads open work orders from your system, so technicians can check in against them by phone. It then writes the check-in and check-out, the completion report, status and photos back to the work order (photos are attached in ServiceChannel and spryggCMMS, and counted with a link to the visit record on a Google Sheet). Today it connects to ServiceChannel, spryggCMMS and Google Sheets, and sends check-in and check-out emails, and check-in alerts to Slack. Corrigo and Accruent connectors are coming soon. If you run another system, spryggAIVR doesn't offer a public API or webhooks yet; in the meantime visits can go to a Google Sheet, an inbox or Slack. See integrations for what syncs to each.
If your platform's built-in check-in already gives you trusted, location-checked visits from every vendor, you may not need a layer at all.
Frequently asked questions
Do I need to replace my CMMS to verify vendor check-ins?
No. A verification layer adds check-in and proof of presence to the CMMS you already use and writes the results back to each work order. Replace the CMMS only if the system itself can't do the work you need.
Will a check-in add-on create duplicate records?
It shouldn't. A good layer writes to the existing work order rather than keeping its own copy you have to reconcile. When your work orders come from ServiceChannel, spryggCMMS or a Google Sheet, spryggAIVR writes each visit back to that work order (on a sheet, as a row on its Check-ins tab).
Can we add a verification layer now and replace our CMMS later?
Yes. Visit records written to your current CMMS stay there as part of each work order's history. Before you move, confirm the layer supports the new system so vendors can keep the same check-in process.
Is a new CMMS the answer if vendors won't check in?
Not on its own. If vendors skip check-in because it needs an app or a portal, they'll likely skip the new system's version too. Fix adoption at the check-in step, whatever system sits behind it.
What if we don't have a CMMS?
You can still verify visits. spryggAIVR can read work orders from a Google Sheet, write every visit back to it, email check-ins and check-outs, with the completion report, to an inbox, and post check-in alerts to a Slack channel.
Try spryggAIVR on your own work orders
Every plan starts with a 30-day free trial. No credit card required.