Everything your crews record becomes an object in your account. This is where you find one, open it, and check it.
Which fields an object carries comes from your organization's own configuration, so the columns and details here will not match the examples. See Why your screens may not match this guide.
Getting there
Open Objects, under the data section of your menu.
If you cannot see it, your role may not include it. Ask whoever manages your organization rather than assuming something is broken.
Finding the one you want
The list gives you a few ways to narrow it down:
Filter by type, which is the fastest cut when you know you are after poles rather than spans.
Filter by time.
Change how many rows you see at once, and page through them.
The app holds filters, sorting and paging in the address of the page, so a filtered view can be bookmarked or sent to a colleague and it will open the same way for them.
The one thing that catches everybody
Clicking the row does nothing. It highlights, which makes it look like it should have worked, but it does not open anything.
Open an object from the view control on its row instead. This is the single most common stumble on this screen, and once you know it you will not hit it again.
What you see when you open one
The top of the object tells you what type it is, when it was created and by whom, and when it was last changed. There is a copy control that copies the object's raw data, including its own reference, which is what to send us if you ever need to ask about a specific object.
Below that are the object's own fields. Which ones exist is your configuration's decision, so two organizations reviewing the same kind of pole can see entirely different pages.
Where an object has a location, there is a control to open it in Google Maps, which is the quickest way to sanity-check that something is where you expect.
An empty-looking object is usually not a lost one
A newly placed object that nobody has filled in yet shows almost nothing. You may see only its location and the job it belongs to.
That is what an object with no captured data looks like. It is not damage, and nobody has dropped anything.
If you expect inspection data and find none, check whether your crew has actually done that work before treating it as missing.
Working out which job an object belongs to
Where your configuration records the job on the object, it is stored as a reference rather than a name, and it is not a link. So to tie an object back to a job you copy that reference and match it in your jobs list.
It is worth knowing in advance, because it looks like something is missing when it is just terse.
Related objects
An object can show what it is connected to, for example the spans attached to a pole. If it says there are none, that is a statement about the connections in your data rather than a fault.
For map files where spans did not attach to poles, the cause is usually the coordinates. See How spans connect to poles.
Archiving one
An object shows either an archive or an unarchive control, never both.
Archiving takes you off the object. Cloneable returns you to where you came from rather than leaving you looking at it, which is easy to read as something having gone wrong. It has not.
An archived object says so plainly when you open it, tells you when it was archived, and offers to restore it. Archiving sets the object's recorded values aside rather than destroying them, so an archived object shows no fields until you bring it back. Unarchive it and the most recently recorded values return, so this is a reversible action rather than a destructive one.