For fielders and analysts collecting data with UtilityScout.

In this guide

This collection covers the complete field data collection workflow: get a job into Cloneable, collect pole, attachment, guy, and midspan data with the UtilityScout app, sync and review it, then export back to Katapult for annotation and design. It is one continuous loop:

Access and device. You need access to both Katapult and Cloneable before you start, on the right team with a role that covers your part of the work. The usual choice is Analyst / Fielder, which can import jobs and export data; in organizations where the back office handles importing or exporting, a field user still needs collection access on the job's team (see Start here). Use a supported iPhone (a recent Pro model with plenty of storage is best). On first launch, allow the app's Location, Camera, and Photos permissions; denying Photos will block photo syncing.

Getting Started as a Setup Admin / Implementer covers how the Katapult round trip works. Almost every Cloneable-to-Katapult problem comes from an action that breaks or bypasses that link. Here is what to avoid.

Do not delete or re-create a node in Katapult after you import the job. Once you export, Cloneable stores each object's Katapult ID and keeps updating that exact record. If you delete the pole, span, or underground run in Katapult (for example, cleaning up the Katapult map mid-project), that ID no longer exists, that object fails to export (its stored Katapult record is gone) and shows up in the Export Issues panel. Your completed field data for it never lands, even though the overall export may still report success. The link is broken, and re-exporting will not fix it on its own. Instead: do any Katapult-side cleanup before you import the job, or do the removal in Cloneable and leave the Katapult node in place. If a node was already deleted after import, there is a self-service fix from the portal: open the flagged object on the map, clear its Katapult ID field, then run Export Data > Force Export All to create a fresh Katapult record. If that does not resolve it, contact Cloneable support with the job name so they can re-link or re-push those objects.

Do not assume that deleting a pole in Cloneable removes it from Katapult. Deletions are one-way; Cloneable never deletes from Katapult. A pole you delete in Cloneable still exists in Katapult, and because that object may still carry its original Katapult ID, it can even reappear on a later export. Instead: if you remove a pole, delete it in both places, and re-check the Katapult job after each export. Do the Katapult-side deletion carefully, per the point above about deleting exported nodes.

Do not edit data in Katapult after import and expect it to appear in Cloneable. The link is not a live two-way sync. The import is a one-time snapshot; nothing reads Katapult changes back into Cloneable afterward, and your next export can overwrite a value you typed in Katapult. Instead: once a job is imported, make all edits in Cloneable (the app or the web portal), and do office corrections in the web portal before you export.

Do not re-import a job into a new Cloneable job to "start fresh," and do not fire off several imports at once. As a rule, import a given Katapult job one at a time and let it finish before starting another. Re-importing into a brand-new Cloneable job creates fresh objects that still carry the original Katapult IDs, so two Cloneable jobs end up writing back onto the same Katapult records. Firing multiple imports back-to-back before each finishes produces half-imported, failed jobs. Instead: to refresh a job, re-import into the same existing Cloneable job (it relinks and updates in place, with no duplicates, so this is safe). Import one job at a time and wait for it to finish. To truly start over, archive or delete the previous Cloneable job first.

Do not export before every device shows "Synced." Field values and photos upload on separate queues, and photos lag on weak signal. The export only sends what has reached the cloud, so exporting early silently leaves out un-synced poles, measurements, and photos. This is the most common cause of "the export missed some data." Instead: before exporting, confirm every device that worked the job shows Synced and the Unsynced Files warning has cleared. If something was missed, a re-export catches it (it is incremental), or open the specific object and use Force Export All (under Export Data), which re-sends all of its fields regardless of what changed.

Do not trust a "Completed" export at a glance, or click Export over and over. An export can report Completed while individual objects sit unresolved in the Export Issues panel, and repeated clicking just re-queues work and can trip Katapult rate limits. Instead: after an export, open the Export Issues panel and work each flagged object using its on-screen guidance. The export is resumable, so a single re-run sends only what did not go through.

(For administrators: see Getting Started as a Setup Admin / Implementer for the round-trip attribute rule when a field goes missing after export.)