Your Katapult model holds far more than you need in Cloneable. This is where you decide what comes across: which parts of the model, which details on each one, how they match up to Cloneable's own objects, and how they look on the map for your crews.

It is a guided sequence. Each step asks you to confirm before it will move on, and each step stays locked until you finish the one before it, so you cannot skip ahead. The screen says as much: Complete each step to unlock the next.

Step 1 and the mapping selectors lock behind you. Once you confirm step 1, its three fields stop accepting changes for the rest of the run, and the mapping step's selectors lock the same way once you confirm that step. Treat the other steps the same way in practice: check a step before you confirm it rather than after.

If you get something wrong and only notice later, you are not stuck. Reopening this later, near the end of this article, covers what you can change.

Your own type and attribute names will differ from the examples here. See Why your screens may not match this guide.

You need administrator access to your Cloneable organization. Without it the page tells you that you do not have permission to create or edit configurations, and nothing loads.

Your model also needs to have been sent across already. See Send your Katapult model to Cloneable. If the page is asking you to use the Chrome extension and you know you already have it, that means no model has arrived yet, not that the extension is missing. More on that.

Seven. The extension sends your whole model across, so the sequence always includes the two steps where you choose elements and attributes. Everything below walks through all seven in order.

Three things live here, not just the name.

Configuration Name. There are rules, and they matter more than they look:

On screen: "This name will be used to identify this configuration and as a suffix for generated templates. Only alphanumeric characters, and underscores are allowed. Spaces will be replaced with underscores."

So the name is not just a label. It gets attached to the end of every template this import creates, which is how you will tell one configuration's pole template from another's later. Type anything with a space and it comes back with an underscore instead.

Good names look like Project_Alpha or Q1_2024, which are the examples the screen itself gives. Name it after the work, not the day you did it: you will pick it from a list every time you create a job.

Measurement Unit. Required, and it is the unit your crews will see on their phones. Pick what your crews say out loud and what your engineers expect to receive. If you change it later, that changes how measurements are shown rather than how they are stored, so your earlier measurements show in the new unit too rather than staying in the old one.

Cloneable will ask you for this again in your configuration's settings. It is the same setting in both places.

Enable ground line circumference. A checkbox, described on screen as photo caliper measurement on the pole inspection page. Turn it on if whoever reviews poles in the office needs circumference at the ground line, and they get a measuring tool on the photo.

Then confirm you have reviewed the name, and continue.

Get this step right the first time. All three of these are fixed in this sequence once the configuration exists: if you come back through here later to change your selections, the name, the unit and the checkbox are all shown but not editable. The screen explains the name one itself:

On screen: "Configuration name cannot be changed because existing templates are linked to this name."

The unit and the ground line checkbox both have a way out, because they appear again in your configuration's settings, where you can change them. The name is the one to treat as permanent: this route will not change it, because your templates already carry it.

Cloneable opens by telling you the size of what you sent, in the shape of this model contains 19 node types, 9 connection types, 6 pole annotation types. Those numbers are your model's, so yours will differ.

There is a search box, which you will want, because a real model has more types than fits on a screen.

Three categories, and it is easy to miss the third.

Node Types are things at a single point. They come grouped, so Anchor might hold Existing Anchor, New Anchor and House, while Fiber Callouts holds Slack Loop and Splice. Each group shows how many of its types you have picked, and you can take a whole group at once.

Connection Types are things that run between points, grouped the same way. A real model's group held Aerial Cable, Overlash, Slack Span, Overhead Guy, Pole To Pole Guy, Underground Cable, Reference, Down Guy and Pushbrace.

Pole Annotations are the things recorded against a pole rather than as their own object. One real model's list held Arm, Equipment, Guying, Insulator, Pole Top and Wire. Each shows how many types and how many companies it covers, so you can see which ones your model actually uses before deciding.

Every category has Select All and Deselect All, so you can start from everything and cut, or from nothing and add.

What you leave out does not come across at all, so your crews will never see it. Lean toward including a type you are unsure about. An unused type is a little clutter in your lists. A missing one means coming back through this sequence.

On screen: "Select which attributes to include for each type. Attributes determine which fields appear in the generated templates."

A counter tracks how many of your types have attributes picked so far, so you can see at a glance that you are three of six in rather than discovering a gap at the end.

There is one tab per type you selected, and you work through them. A type can have a lot: one real anchor type carried 60 attributes. There is a search box here too.

Attributes are grouped by what kind of thing they are, and the two biggest groups are worth understanding separately.

Pick lists are the attributes where a fielder chooses from a set of options, and each one shows how many options it has. That count is the useful part: Anchor Was Installed Picklist (2) is a yes-or-no in practice, while Company Picklist (6) is a real choice. Real examples from one model: PCI Failure Type, Anchor Eyes, Cable Was Bonded, Coms As Designed, Down Guy Installed, Existing Aux Eye, Grounding, New Attacher Constructed.

On a span, two fields matter most.

When you are on a connection type such as Aerial Cable or Overlash, look for two attributes. Include validated footage and tree trim if your model has them. Those are the span inputs fielders fill in the field. Your names may differ.

Work through each connection type on its own tab. Pick these two on every type that needs them. The step does not copy your choices from one type onto the others.

Image attachments are the photo slots. One real anchor type offered 24 of them, including Birthmark, Pole Tag, Hallway, Groundline Circumference, Height Marker, Upshot, Note and No Birthmark. Each one you include becomes a place a fielder can put a photo, so this is where you decide what your crews are expected to photograph.

Put midspan height on the span, not the pole.

Midspan Height is a photo slot on the cable, not on a pole or an anchor. Open the tab for that connection type. In a real model the names were Aerial Cable and Overlash. Include Midspan Height there.

If the same slot appears on a pole or anchor tab, leave it off there.

New strand often has no midspan to capture. Overlash and existing strand do. Include the slot only on the connection types that need it.

A clearance type can go with that midspan photo. Include that pick list on the same connection type if crews choose a clearance when they shoot.

Fielders capture the reading with Measure a midspan (High Accuracy).

This is the step worth slowing down on. Every attribute you include becomes a field somebody may have to read on a phone, in the sun, wearing gloves. Too many and your crews scroll past what matters. Too few and the data comes back short and somebody drives out again. The same is true of photo slots: every one you add is another thing a crew has to remember to fill.

On screen: "Map your Katapult node types to standard data objects. Unmapped nodes will be imported as custom data objects."

Three required data objects, each with a one-line description of what it is for:

Cloneable guesses these for you where it can: it looks for a node type called pole or pull, a connection type called aerial cable, and existing anchor or new anchor. When a guess lands, the object shows a green confirmation naming what it matched to, so you can check its work at a glance. Check rather than trust. If your model names its poles something else, nothing matches and you set it yourself.

You can leave Span on its default. Its selector offers None (use defaults) rather than a type from your model, so you do not have to map it. The other two offer that same default, and nothing in the sequence stops you leaving them unset, so the green confirmation is what tells you Pole and Guy Anchor actually matched.

Guy Anchor asks for one extra thing: an export connection type, which is the Katapult connection your anchors go back out as. In a real configuration this was down guy.

Everything you included but did not map is listed under a plain warning that these will be imported as custom data objects. They are split into points and lines, and each has a tick box. Ticked means it comes across as a custom object. Unticked means it does not come across at all.

Points get one more choice: a measurement style of none, pole, or midspan. That decides what happens when a fielder opens one. A reference marker probably needs none. Set a point your crews actually measure to pole or midspan so it behaves like the thing it is. Lines do not get this choice.

Full detail, with a worked example of a real model: How your Katapult types become Cloneable objects.

On screen: "Customize how data objects appear on the map"

On screen: "Review and customize the icons for each data object. Each object can have multiple conditional icons."

This is how a crew reads a job at a glance, so it earns more than a moment.

Your templates are listed with a count of how many icons each one has, which is the quickest way to spot one you have not styled yet. Pick a template and you work on its icons.

Every object starts with a base icon, which is the one shown when no rule matches. Think of it as the resting state: an untouched pole.

On top of that you add rule icons. Each has a label you write yourself, a shape, a stroke color and a fill color, with a live preview of the result. Then you set when it shows, by picking a field and a test, for example measurement_data and has a value. You can stack more than one condition on a rule.

The order matters. You can move rules up and down, and the base icon only appears when none of them match. So put your most specific rule at the top, or a broader rule above it will win first.

Two things worth using: there is an Edit as JSON option if a rule gets fiddly, and a simulator that shows which icon a rule would produce. Use the simulator on every rule, because an icon rule that never fires looks exactly like one you forgot to write.

More on this: Set up your map icons.

On screen: "Configure automation triggers that will handle data synchronization between your system and Katapult. The import trigger processes incoming Katapult data, while the export trigger sends updated data back to Katapult."

Two choices, and they run in opposite directions:

Set both. These are the two automations your account needs, and once they are set every future job uses them. If there is nothing to choose here, your Katapult API key is not stored yet: stop, store it, and come back. See What you need before you start (Katapult).

On screen: "Ready to import! Review your configuration below and click "Complete Import" to finish."

A short summary of what you are about to create: the configuration name, how many data object templates, how many node mappings are configured, and how many workflows.

Check the node mapping count against what you expect. It counts only the objects you actually mapped, so a Span left on defaults does not appear in it. A number lower than you expected here is your last chance to catch a missed match before Cloneable builds anything.

Then press Complete Import. If you came in to change an existing configuration rather than build a new one, the button reads Update config instead.

Saving is not instant, and the page tells you where it has got to: it creates your workflows, then your custom types, then your data object templates, then the configuration itself, and finally stores a snapshot of your model. Cloneable creates them all at save time, which is why your objects and templates lists fill up after an import rather than before. See What your configuration creates in your account.

When it finishes it tells you the import succeeded, and a moment later it takes you to your configurations list.

These steps decide what your crews work on, and they set your units. They do not set everything else: whether crews measure in the field at all, how guy wires get captured, which templates hold your data, and which integration your data exports to are all separate.

See Set up your configuration, stage by stage.

You are not locked out of your choices forever. Your configuration's actions menu offers Edit Katapult selections…, which reopens these same steps so you can change your selections. That is how you fix an element you left out or a type you matched wrongly, and you go through the same sequence, in the same order, with the same confirmations. If that item is not on your menu, ask us.

One part is different, and it is step 1. The name, the measurement unit and the ground line checkbox all appear, grayed out, because the name is now attached to templates that already exist. You acknowledge that step and move on to the ones you came to change.

So the practical rule is: everything from step 2 onwards is revisable, step 1 is not. That is the reason to slow down on step 1 the first time.

This is also the better move when something has come across wrong. Reopening your existing configuration keeps what you already built. Starting a fresh import gives you a second configuration and two sets of templates to tell apart.