Back to Blog
Blog

How should a platform behave when integrations are delayed by third party IT approvals?

How should a platform behave when integrations are delayed by third party IT approvals?

Integration approvals often take months, so a platform that cannot deliver value until every integration is live can stall a project before it starts…

Integration approvals often take months, so a platform that cannot deliver value until every integration is live can stall a project before it starts. The platform should be able to run with manual imports or simple file transfers in the meantime and switch to the live integration once it is approved, so the work of getting crews onto the system and improving procedures can begin while the paperwork is still moving.

The delays usually have little to do with the technology itself, since connecting to a maintenance system, an identity provider or a document store often requires security reviews, change board approvals, firewall changes and sign off from teams that own those systems and have their own priorities. Each of those steps can be reasonable on its own, but together they can add months to a timeline, and a project that waits for all of them tends to lose momentum, budget and the attention of the people who championed it.

In practice the interim approach can be quite simple, such as a scheduled export of work orders or asset lists from the maintenance system as a spreadsheet that someone uploads each morning, or a weekly file of completed jobs sent back the other way. It is more manual than a live connection and someone needs to own it, but it lets the field teams work with real data and it shows which fields actually matter before the integration is built, which often makes the eventual integration simpler and easier to get approved.

It helps if the data formats used for the manual imports match what the live integration will use, so that switching over later is a configuration change rather than a rework. Watch for duplicate records and stale data during the interim period, since a file uploaded late can mean a crew works from yesterday’s list, and agree who checks the import each time and what happens if it fails.

That way the field teams can start using the system and the business can see results while IT works through its process. It also helps to plan pilot milestones that do not depend on integrations outside the vendor’s control, which keeps the project moving even when approvals are slow and means the pilot is judged on whether the tool works rather than on how long another team took to approve a connection.