A job is the container your crews work inside. Everything they capture belongs to one.

Start from Add Job on your dashboard. It is not in the side menu, so if you look for it there, that is why.

From Katapult, which brings pole and span data across from a Katapult project. This is the recommended route if you use Katapult.

Empty, where you name the job and crews add everything on the map themselves.

From a map file, if your data is arriving as KML, KMZ or GeoJSON. Choosing this one takes you out of the job wizard and into the map-file import, which is a different flow with its own article. Going back afterwards will not return you to where you were. See Bring your map file in as a job.

It depends on your route, and on what your organization already has stored.

So the step count tells you something useful: if Cloneable asks you to connect to Katapult, your organization has no Katapult credential stored yet. That same missing credential is behind the most common failure on this screen. See Store the credentials your integrations need.

If you need a configuration you do not have, build it before you start the job. Leaving the wizard part-way through loses what you have entered, and you will start the wizard again from the beginning.

The last step confirms what you are about to make. For a Katapult job, creating it also starts the import.

The app returns you to your dashboard afterwards, not to the new job. The job is there in your list, and you open it from there.

This is the one thing on this screen that catches people out, and it costs a day when it does.

A Katapult job can be created successfully while its import fails to start. When that happens Cloneable tells you, but it tells you gently: the message looks like an ordinary success, and it differs from the real success message by a single word.

On a Katapult job you may get a second message that says your job was created but the import trigger failed to start, and that you can trigger the import later.

Cloneable shows the ordinary success message either way, so it does not tell you the import started. Read past it rather than stopping at the first two words, because a job created without its import is an empty job.

If you see the failure message, tell us before sending a crew out.

If poles never arrived and you are not sure which message you saw, treat it as this until proven otherwise.

If the wizard says it cannot load jobs and offers to retry, retrying will not help. Check for a missing Katapult credential first. See "Error loading jobs" when I import from Katapult.

That failure appears in the wizard rather than as a message that slides away, so you will not miss it. Try again, and if it keeps failing tell us the name you gave the job.