This screen answers one question: how much gets done, and where does the rest of the time go.

Field Efficiency is a tab on the Analytics dashboard. Open the account dropdown, choose Analytics, then open the Field Efficiency tab. See The Analytics dashboard for the other tabs on that screen.

You can also reach it from a day replay, which links back here.

Organization admins and workforce managers see every fielder. Everyone else sees only their own activity, and the page says so when that is what happens.

The page also describes itself differently depending on which of those you are, so if a colleague quotes a heading at you that does not match yours, that is why.

There is a panel on this page explaining how the figures are worked out. It is closed unless you open it, and it is the best explanation of these numbers that exists anywhere, better than this article.

Open it once, read it properly, and most of what follows will not need explaining again.

This is the thing that will confuse you, so take it first.

One of these numbers appears three times on this page under three different names. Depending on where you look, the rate that excludes time when a crew was not collecting is called poles per hour while collecting, while working, or just working.

They are the same number. Nothing is inconsistent about your data. The screen is inconsistent about its labels.

What to hold onto instead of the names is the relationship, which is the product's own:

On screen: "Poles / hr ≤ At job ≤ Working"

Each is the same output measured against a narrower slice of time. Poles per hour is against everything. At job takes out getting there. Working also takes out the time on site when nobody was collecting. So the third is always the flattering one, and the first is the honest one for planning.

Cloneable measures a day from a crew's first capture to their last capture. Not a shift, not a timesheet.

So every percentage on this page is a share of that window, not of somebody's day. A crew that captured between nine and one has a four-hour day here. If you read those percentages as portions of an eight-hour shift you will draw the wrong conclusion about all of them.

This makes the figures good for comparing shape between crews and bad for anything to do with hours paid.

When the app saves everything about an object in one go, which happens on roughly a fifth of them, the recorded time comes out around twenty seconds regardless of how long the work actually took.

So treat time-per-pole as the shortest it could have been, never as what it was.

That is the page declining to calculate a rate it cannot calculate honestly. Each row needs enough from that fielder in the window you look at before its numbers mean anything. Nothing is broken. See Field Efficiency only shows dashes.

Cloneable will flag some days as having thin GPS coverage, with a note that stopped time could not be measured.

Take that seriously rather than reading past it. On those days the time breakdown is incomplete, so the split between working, traveling and stopped is not reliable. The capture counts are still fine. It is the time analysis that is not.

You can change the window between one week and ninety days, and organization admins and workforce managers can narrow to one fielder. You can also group the view by day or by fielder depending on whether you ask "what happened on Tuesday" or "how is this crew doing".

Dragging across a lane zooms into it, and each day offers to replay itself on a map. See Replay a fielder's day.

Compare a crew against itself over time, not against another crew. Terrain, job type and access vary far more than technique does, and this page cannot see any of that.

If a number looks wrong, check the GPS warning and the date window before concluding anything about the crew.