When you import a map file, Cloneable has to work out which spans belong to which poles. Nothing in your file says so directly: it holds points and it holds lines, and Cloneable has to infer the relationship between them.
The rule, in Cloneable's own words
On screen: "Lines will automatically link to point objects based on matching endpoint coordinates. Make sure your KML data has properly aligned coordinates for accurate relationships."
A line finds a pole because the end of the line is where the pole is. Coordinates are what Cloneable tries first. If your file also carries attributes naming or identifying the point at each end of a line, Cloneable can fall back to those.
Which means the quality of your coordinates is not a tidiness concern. It is the thing Cloneable builds the connection from.
Why this catches people out
People make map files in all sorts of ways, and some of them produce lines that look right and are not.
If your lines were drawn by hand over an aerial image, the ends will be near the poles rather than on them. Cloneable does not need the line end to sit exactly on the pole. It matches an exact coordinate first, and if that fails it looks for a point close by, so ends that are close still attach. Ends that are a long way out, or in a different place entirely, are what fails.
Files exported from a system that already knows which span attaches to which pole are usually fine, because the system placed the endpoints from the same data as the poles.
What to check before you import
Roughly how far out are the line ends? Ends drawn close to their poles are fine. What causes trouble is ends a long way out, or in a different place entirely. This is the single most useful question to ask whoever produced the file.
Do the poles and the lines come from the same source? Two sources merged into one file is where mismatches come from, especially if one has been through a coordinate conversion.
Spot-check a few ends. Pick a pole with several spans and look at whether the line ends land on or close to it, rather than somewhere else on the map.
After the import, check the map
The reliable check is visual, and it takes a minute. Open the job on the map and look at whether spans are attached to poles or sitting on their own.
Do that before crews go out rather than after. A span that did not attach is a five-minute fix in the office and a wasted trip in the field.
Do not rely on the object count for this
When the import finishes, Cloneable tells you how many objects it created, and you should check that against the points and lines it found. Twenty points and twelve lines should give you thirty-two objects.
That check catches missing objects, not unlinked ones. Both numbers can reconcile perfectly while your spans are attached to nothing, because an unattached line is still an object. Counts tell you whether everything arrived. Only the map tells you whether it arrived connected.
If things did not link
Fix the file rather than the import. Get the line endpoints onto the point coordinates in whatever produced the file, and import again into a fresh job. Correcting coordinates at source is quicker than reconnecting spans one at a time afterwards, and it means the next batch from the same source works too.