Applies to: All customers.
In this guide
Who handles the end-of-day steps? Collecting data and syncing the device is always the field crew's job. The web-portal steps that follow, reviewing, exporting, and verifying (Steps 12 through 15), may be done by the field crew or by a back-office analyst, depending on how your organization is set up. If your organization has no back office, the field crew does them too. The instructions are the same either way, and from here on "you" means whoever on your team owns that step. One rule never changes for the field crew: do not treat a job as finished until the device shows fully synced. Everything after this point depends on it.
Step 12: Sync and review
Two things happen at end of day: sync the phone, then review the data in the Cloneable web portal before the job is exported.
End-of-day sync
Get back to Wi-Fi (hotel, rental, anywhere with good internet).
Toggle sync back on (top left of the app). Let it run; give it thirty minutes to an hour.
Confirm it reads fully synced, including photos (remember data and photos sync in separate queues). Do not export until the phone is fully synced.
Review in the Cloneable web portal
Before exporting, review the job in the portal to catch problems while you can still fix them cheaply.
Open the job and its map. Confirm poles collected and data present. Use the Layers panel to check counts per object type.
The office can fix text, number, date, dropdown/status, and yes/no fields inline from a pole's detail panel, and can upload or replace files and photos. (A measurement itself cannot be edited inline; it opens the photo-measurement view.)
Some things cannot be fixed from the portal and need the device: running AI detection and replacing a measurement photo. Attachment markers can be added, dragged, and reclassified in the portal's photo-measurement view.
A bad pole height often does not require a return trip. If a measurement is wrong, the portal can re-measure the pole from its photo (Calibrate or Re-calibrate: place the two targets, align the pole, set top and base, save). This works only on a high-accuracy photo, not a Standard/AR photo. Fix it, then re-export.
Check the Unsynced Files indicator before exporting. If a fielder's files have not finished uploading, the portal shows which crew member still has pending files; have them finish syncing first, or the export will be incomplete.
Step 13: Export back to Katapult
Open the job's map and use the Export Data button. It offers four targets:
Katapult: the write-back to Katapult (the only true round trip).
PDF report: choose which data types to include and optionally bundle all photos into a ZIP.
KMZ: a zipped file for Google Earth or GIS.
CSV (ZIP): a ZIP of separate CSV files per object type, for spreadsheets or analytics.
Then complete the Katapult round trip:
Choose Export to Katapult and step through the export screens.
Watch the status. The Katapult export runs as Pending, then Running, then Success or Issue (the error state is labeled "Issue"). Click Export only once; large jobs can take from a few minutes to a couple of hours. If it sits on Pending for more than about 30 minutes, contact support with the job name and how long it has been running.
The export is resumable. Cloneable tracks what did and did not make it to Katapult, and a re-run only sends what was not delivered before. An object counts as delivered only when its attributes and all of its photos have uploaded. Re-running on unchanged data is harmless. To re-push a single object, open it and use its History > Exports tab: Export Updates sends only new data, while Force Export All re-sends everything (and can create duplicates). This is the same export activity administrators monitor from the dashboard's Exports tab (see Analytics and export operations).
If an export has problems
Symptom | Most likely cause and fix |
A field you filled in is missing in Katapult | The round-trip attribute rule (see Start here): the attribute was not selected when the configuration was imported, so it never exports. Your data is not lost; it just was not in the export set. This is an administrator configuration fix, not a re-collection. |
Export stuck on Pending (over ~30 min) | Contact support with the job name and elapsed time; they can restart it. Do not keep clicking Export. |
Export shows "Issue" (check the error text in the Export Issues dialog) | Usually missing required fields or an orphan midspan (a midspan not tied to a span). Fix the flagged records and re-export. |
Photos not appearing / file not yet saved | Photos are still syncing from a device. Finish syncing (see Unsynced Files), then re-export. |
API errors during export | Often transient. Re-run the export; it only retries what did not go through. |
Step 14: Verify the data in Katapult and fix any issues
This is a two-person quality-control step. The field tech verifies their own work first; a field supervisor does a second pass before the job moves on.
Note: Steps 14 and 15 involve detailed Katapult work that goes beyond Cloneable itself. Treat this as a reference; your supervisor should walk you through it before you run a job independently, and your organization's Katapult reference guide covers the full Katapult-side detail.
Geometry and pole changes to verify
Added poles: make sure the original line is not hiding behind the new pole. You should see two new line segments, not the old single line underneath.
Removed poles: deletions are one-way. If you delete a pole in Cloneable, the matching pole is not removed from Katapult, so clean up removed poles in Katapult by hand. This is intentional. Two things to watch: a pole deleted in Cloneable can reappear in a later export (Cloneable still carries its original Katapult ID), so check the Katapult job after exporting; and if something was deleted on the Katapult side, a re-export may flag an error, which the export issues panel helps you resolve.
Moved poles: confirm anything you repositioned in Cloneable moved correctly in Katapult. It does not always translate perfectly.
Attributes to check
Field-complete checkmark: Cloneable can now send the field-complete status to Katapult, so completed poles flip to complete in Katapult automatically (the field-complete checkmark turns them from red to blue there) when your configuration is set up for it. This is the Katapult-side completion state, separate from the pole color in the app. If your configuration does not export it, set the checkmark manually on completed poles. Confirm with your administrator whether field-complete export is enabled for your configuration.
Connection type and span type: the broad span type does export, but the overlash-versus-new-attach designation may not carry over reliably, and whether it carries over depends on your configuration. After exporting, check the affected spans in Katapult and correct them by hand if needed.
The third-party photo approval prompt
When you work with Cloneable photos in Katapult, Katapult flags them as coming from a third-party source and asks for approval. This is because Cloneable uploads photos through Katapult's API as an external tool, not because of anything wrong with the photos.
The first time you go to a pole height photo, Katapult asks whether to use the third-party photos. Choose Do It Anyway. This accepts Cloneable photos for that photo type across the whole job.
Do the same at the first midspan. You only need to do this once per photo type per job (once for poles, once for midspans).
How to fix issues
Most geometry and attribute fixes are done directly in Katapult.
If the issue is a missing photo or a bad height calibration, fix it in Cloneable (re-calibrate from the photo in the portal, or re-capture on the device) and re-export.
Step 15: Confirm height photos are starred
A "starred" photo in Katapult is the primary pole height photo. It opens in the trace view where annotation happens, and the calibration captured in Cloneable is tied to it, which is how Katapult converts pixels to real-world heights.
Cloneable is intended to upload measured pole photos to Katapult already starred as the height photo, but do not assume it: confirm the correct height photo is starred on each pole and midspan, and use the manual tool below whenever one is missing its starred height photo or has the wrong photo starred. If your photos are not auto-starring, check that your Cloneable Katapult integration is up to date and flag it to your administrator.
Fallback: the Star Height Photos tool
Open the job in Katapult. On the far-right toolbar, click Tools, switch from Aerial Design to Office Tools, and click Star Height Photos (the yellow circle with a star).
In the pop-up, check Star the first photo if no height photo is found, then click Star.
For midspans (usually one photo), it stars correctly every time. For poles, it stars the first photo, which is not always the right one, so go through each pole and confirm.
Fallback: correcting a pole height photo by hand
Click the pole, click the pencil edit button, and click Photos.
Identify the pole height photo (taken from a distance, showing the full pole with the High Accuracy Stick targets visible). Hover over it and click the star icon in the top right.
If you get the third-party photo prompt again, choose Do It Anyway.
Why this matters
The starred photo opens in the trace view where the annotation team works. The calibration from Cloneable (the yellow-line alignment) carries over and is tied to that photo, so when the annotation team places a point, Katapult uses the calibration to compute the real-world height. Photo classification also comes over automatically. Getting the right photo starred is the final handoff prep.
If you do not use Katapult
Applies to: Non-Katapult customers.
There is no Katapult round trip, so Steps 14 and 15 above do not apply to you. Your end of the loop is simpler: sync, review, then export a file. Step 12 (end-of-day sync and review in the web portal) is exactly the same as described above, so do that first.
Before you export, confirm every device shows Synced and the Unsynced Files warning has cleared. An export made while photos are still uploading will be incomplete.
Export the job. Open the job's map and use the Export Data button. Skip the Katapult target and choose the output you need:
PDF report: choose which data types to include, and optionally bundle all photos into a ZIP.
KMZ: a zipped file for Google Earth or GIS.
CSV (ZIP): a ZIP of separate CSV files per object type, for spreadsheets or analytics.
Verify and finish. Open the downloaded file and confirm the poles, spans, and photos you expect are all there. When the output looks right, archive the job to keep your active list clean. Archiving is reversible and frees up device space.
Related: Once a job is exported, ongoing work like reviewing the Data Objects table or monitoring exports happens in the Cloneable web portal.