Your crew works in places with no signal, and they can complete jobs offline. When those actions sync back and disagree with what the server already thinks, ClippingCash does not guess. It flags the job for you.
Jobs Needing Review is that queue. Two things land here: an offline action that conflicts with the server state, and a worker who overrode the on-site location check.
1 Open the queue
Go to Needs Review from the left menu. When it is empty you get No jobs need review, which is where you want it to sit.
2 Resolve an offline conflict
A conflict row shows the customer (as a link to their record), the worker action and when it happened, and the server status the job currently holds. That is everything you need to see which version is right.
You get two buttons and they are a straight choice:
- Accept worker’s action takes what the crew did in the field as the truth. Confirmed with Worker action accepted.
- Keep server state discards the offline action and leaves the job as the server has it. Confirmed with Server state kept.
Default to accepting the worker’s action. They were standing at the property. The usual cause of a conflict is somebody in the office also touching the job while the crew was out of signal, and the person on site is the one who knows whether the lawn got cut.
Keep server state when the offline action is clearly stale, for example a job the customer cancelled by phone after the crew had already lost signal.
3 Resolve a location override
The other kind of row is a worker who completed the on-site check while not at the property’s recorded pin. That is not automatically wrong: the pin might be in the wrong place. It is flagged so a human looks.
These rows have a single Acknowledge button, which clears the flag once you are satisfied. Confirmed with Override acknowledged.
Before acknowledging, use Review on map. It opens a map right there in the row with the property pin, and where the worker actually was shown as a second marker labelled Worker.
Now you can see the answer. If the worker’s marker is sitting on the property and the pin is out on the road or on the wrong lot, the pin is wrong, not the worker. There is a button for exactly that case: Use worker’s location drops the pin onto where the worker actually stood, and you can save it straight from this panel.
That is the highest-quality address correction you will ever get, because it comes from someone physically standing at the property. Repeated overrides at the same address are a pin problem, not a crew problem.
4 Keep it short
Nothing in this queue blocks work, so it is easy to ignore, and then a month later you have forty rows and no memory of any of them. Resolve it while you can still remember the day: a minute at the end of the afternoon.
Overrides that keep recurring at one property are telling you to fix the pin permanently. See how to fix a property’s map pin.