Marking items done, and skipping the ones you cannot do

This is the only thing the crew genuinely has to do, and it is one tap per item.

One item at a time, as you go

Every item on the stop has its own Mark done button. Press it when that thing is actually finished. The item shows as queued for a moment and then as done.

Do not save it all for the end of the day. The whole value of per-item status is that the office and the next crew can see what was finished while the day is still happening — and a memory reconstructed in the truck at six o’clock is worth much less than a tap at the dock.

Skipping what you could not do

Not everything gets done, and pretending otherwise is how billing arguments start. Skip the item and write the reason. LakeOps requires the reason — a skip is a billing exception and it has to say why.

Good reasons look like:

• “Water too low at this end — cannot float the sections in.”
• “Needs the crane; fork barge cannot lift this one.”
• “Customer asked us to leave the canopy up another two weeks.”

A skipped item is not billed. It also stays visible to the office, which is how somebody decides whether to send the crane crew back.

What else is on a stop

• Access notes, in an amber box at the top, because the time to read them is before you tie up.
• The item’s notes for this job — install notes in spring, removal notes in fall, never both.
• Reference photos showing where the item goes or how it stacks, opened by default on anything still pending.
• The clock. See running the clock.

Closing the job is a separate decision

If items are left pending, leave the job open. That is not an unfinished chore, it is the accurate state, and the property will read as partly done on the map for whoever comes next.

With no signal

Identical. The tap is stored on the device with the time it happened and sent when the bars come back. A resend cannot create a second completion. See working with no signal.

Fixing a mistake

A completion recorded in error is corrected from the office, by a person, on purpose. The server never quietly un-completes work on its own — that rule is what makes the record worth trusting six months later. See why work is tracked item by item.