Cloneable has three parts, and which of them you use depends on your job.
UtilityScout is the app your crews carry. It is where the work is captured.
The Cloneable web portal is the browser side. It is where work is set up, reviewed and sent onward.
Your configuration is the part that makes Cloneable yours rather than generic. More on that below, because it explains most of what people find confusing.
The shape of the work
1. Somebody sets up a configuration. This decides what kinds of thing your organization records, what they are called, which details go with each, and how they appear on a map. Somebody does this once at the start and adjusts it occasionally afterwards.
2. Somebody creates a job. A job is the container everything else lives in. It is the unit of work you hand to a crew. Every pole, span and photograph belongs to one.
3. A crew captures in the field. They open the job on their phone and complete whatever that job requires for each object. That may include locating or placing it, filling details, taking photographs, correcting guy data or measuring. Not every crew does every action.
4. The work reaches the office. The app holds captures on the phone first and sends them when there is a connection. Nothing depends on being online at the moment of capture.
5. Somebody reviews it. Somebody reviews it in the browser, on the map, or object by object, to check that what came back is what was needed.
6. The data leaves. Somebody exports it to whoever needs it, in whatever shape they take it.
That is the whole of it. Everything in this guide is one of those six things in more detail.
Why your Cloneable is not identical to anyone else's
This is the idea worth spending a minute on, because it explains more confusion than anything else here.
Cloneable does not arrive with a fixed set of poles and spans. Your organization decides what kinds of thing it records, and what to call them. It also decides which details each one carries, which are required, and what they look like on a map. That collection of decisions is your configuration.
One consequence matters more than the rest. Two organizations using Cloneable can see screens with almost nothing in common, while doing exactly the same job. If your company calls its poles structures, the app says structures.
So this guide describes what you do rather than reading out what is on your screen. When the words do not match, look for the step that matches what this guide describes. See Why your screens may not match this guide.
Where things live once they are captured
Two words come up constantly and are worth separating now.
An object is a thing your crew recorded: one pole, one span, one anchor. A template is the shape it landed in, which is what decides the details it carries.
Your configuration builds the templates. Your crews create the objects. See What your configuration creates in your account.
A complete object is defined by the job
Worth knowing before anyone goes out, because it prevents a whole class of worry.
Placing an object records where it is. Filling details, taking photographs and measuring are separate actions that may happen at the pole, later in the office, or not at all, depending on the job.
That means neither a sparse object nor a detailed object is universally "finished." Your organization's crew card should say what completion means for the job. See Your field shift: start ready, complete the record, finish synced.
Getting data out is a step, not an afterthought
Work sitting in Cloneable is only half the point. Exporting is what puts it in front of whoever pays for it, and it is worth understanding before you have a deadline rather than during one. See Export your data.
Now go to the part that is yours
You are unlikely to need the whole guide. See Which guide is for you.