Fixing mistakes: what can be corrected, and how

LakeOps treats finished work as a record: completion is stamped, the price is snapshotted, receipts are frozen. That is what makes last year’s question answerable — and it means fixing a mistake is rarely an edit. Each fix here moves the record forward instead of rewriting it, which is also what keeps you credible in a dispute. Worst phone call first.

The job was closed too early

The lift got marked done from the boat, the job completed itself, and the canopy is still on the trailer. Open the job and press Reopen — it goes back to in progress, the crew finishes the real work, and it completes again when everything is resolved. Reopening is its own permission, so you decide who on the team can do it.

The price came out wrong

The price on a job is snapshotted when it completes, from your price list as it stood that day. If the snapshot is wrong — a rate was mistyped, a dock’s section count was off — the fix depends on one question: has money moved?

Nothing paid yet: fix the cause (the rate on the price list, the item’s spec), reopen the job, and complete it again. Completing re-prices it, and the page behind the customer’s link shows the new number. The same move covers a job that completed unpriced because sales tax wasn’t configured for that property — the app refuses to guess at tax, so the job waits, loudly, until you set the jurisdiction and re-complete.

Already paid: the number is locked — a figure a customer has paid against is history, not a draft. If they were over-charged, refund the difference from the payment itself, with a reason; the refund is its own record and shows beside the payment everywhere. If the whole thing was wrong, refund the payment in full — that lifts the lock, so you can reopen, re-complete at the right price, and the customer pays the corrected bill from the same page.

The wrong item got ticked

An item marked done stays marked — there is no un-ticking it from the screen, because who marked what, and when, is exactly the record the crew’s day is built from. What you can do: if the item that actually got done is still pending, mark it (or skip it, with the reason); and if the stray tick reached the bill, treat it as a price problem and use the section above. Write what happened in the notes — a note on the record beats a corrected memory in November.

The job is on the wrong property

While nothing has been recorded on a job, you can simply edit it and change the property. Once a crew has worked an item or run the clock against it, that door closes — the recorded work describes equipment at one shoreline and cannot honestly move to another. Cancel the job and create the right one; the canceled job stays in the record as a stop that didn’t happen.

The clock ran wrong

A clock left running gets stopped like any other. An entry that shouldn’t exist at all — the clock started against the wrong stop — is voided, with a required reason, rather than edited or deleted. The minutes that were real stay; the void is itself part of the record.

A payment was recorded wrong

A cheque recorded by hand with the wrong amount is corrected the same way a card payment is: refund it — in part, or in full — and record it again correctly. A refund of a by-hand payment doesn’t touch any card; it is a record that money went back. The receipts stay frozen as they were issued, which is the point: each one says what was true when it was sent, and the customer’s payment history shows the whole corrected story in order.

What never changes, and why that helps you

Receipts don’t change. Completed seasons don’t reopen. Canceled jobs and plans stay in the record. A voided timer says who voided it and why. Every fix above adds a correcting record instead of rewriting the original — so when a customer, a bookkeeper or an insurance company asks what happened, you have the mistake and the correction, in order, with names and dates. That is a better position than a clean-looking record nobody can vouch for.