Day replay plays back one crew member's day on a map: where they went, and each capture appearing at the moment it was actually taken.

It is the drill-down from Field Efficiency. When a number there looks odd, this is how you find out why.

We would rather you heard this from us than discovered it.

A replay shows one named person's location trail for one day, alongside every object they captured and when. It is built from the location UtilityScout reports under your organization's location policy: while the app is open, and, if your organization has turned background reporting on, during its set work hours as well. It draws the route between captures.

It covers the last ninety days. Days older than that cannot be replayed at all. Cloneable says so rather than showing you an empty map. The location trail has its own start date: Cloneable began collecting location history on July 13, 2026, so a day inside the window but earlier than that replays its captures with no route drawn between them. Cloneable tells you when a trail is missing, and its own message names a second possible reason: the device may not have reported its location that day.

Your role decides who can watch whose day. Organization admins and workforce managers can replay any fielder's day. Everyone else can replay only their own.

If you introduce Cloneable to a crew, this is worth telling them directly rather than leaving it to be found. It is a normal capability for this kind of work, and it lands far better said out loud than discovered.

Start from Field Efficiency and pick a day. Each day offers to replay itself.

Do not try to build the link by hand. It needs both the person and the date in a particular form, and if either is wrong the page tells you the parameters are invalid rather than guessing. Open it from the timeline instead.

The controls are icons rather than words, so the fastest way in is the keyboard:

There are three playback speeds, from a gentle ten times real time up to three hundred, which is the one for skimming a whole day. There is also a control to follow the fielder as it plays, and one to fit the entire day's travel on screen.

You can zoom the timeline down from the whole day to five minutes, and further still by dragging, down to about a minute across. That is the resolution to use when you try to understand what happened at one pole, rather than what happened all morning.

The header tells you how many objects were captured and the mix of them, how long the day ran, how much of it was travel, and, when there is a location trail, how far was covered.

The page also breaks down where the day went.

Times on individual objects are floors, not measurements. When the app saves everything about an object at once, the recorded time comes out at about twenty seconds no matter how long it took. Cloneable says so in its own tooltip. See Field Efficiency, and what each number means for why.

You can also jump from a capture straight into its inspection view. See Work in the pole inspection view.

No activity found for that person on that day usually means what it says: they did not capture. Check the date before assuming the feature is broken, and remember a crew's day here starts at their first capture.

If it is somebody else's day, this message can also mean your role does not include replaying it. Only organization admins and workforce managers can replay other people's days, and anyone else gets this same message even when that person was out working.

A warning that something could not load means part of the picture is missing, most often the location trail or the photographs. The captures are still real. The route between them may not be complete.

Replay is for understanding, not for auditing. It shows where the app reported location, which is not the same as where somebody was or what they did. Gaps in coverage are common and normal, and the product itself flags days where the location data is too thin to draw conclusions from.

If you look at a replay to answer "why did this take so long", it is very good. If you look at one to answer "was this person working", it will mislead you.