Service logs

A service log is one completed visit: the filled-in form, the photos, the notes, the timestamp, and the worker who did it. It is the record you keep and the record you show a client. Everything else in Opzaco exists to produce good ones.

How a worker submits one

The worker scans the asset, reads the instructions, and taps Start service. They move through the form a step at a time — your sections and their questions, then notes and wrap-up photos — and land on a review screen where every answer can still be changed. Then they submit. The app and the web browser break the steps up slightly differently, but ask for the same things — section by section, then notes, wrap-up photos, and review.

A worker who finds something wrong ticks Flag for review on the way through. Flagged logs are called out on your dashboard rather than sitting in the pile.

What gets recorded

Log number: A sequential number for the log. Easy to reference on a phone call.
Who and when: The worker who submitted it and the exact submission time.
Answers: Every checklist tick and question answer, against a frozen snapshot of the form as it stood that day.
Photos: Everything the worker photographed, stored privately. Photos are re-encoded to remove location data on the way in; a small number of older logs predate that processing and may still carry it.
Notes: Free-text observations, issues found, parts used.
Duration: How long the visit took.
Flag: Whether the worker marked it as needing attention.

Bad signal is expected

Every submission carries a unique identifier generated on the worker’s device. If the connection drops and the worker retries, the server recognises the identifier and updates the existing record — it can never create a duplicate visit. See Mobile app for what happens with no signal at all.

Logs cannot be edited

Once submitted, the content of a log is fixed. There is no edit button — not for workers, not for supervisors, not for owners. A correction is a new log, not a rewrite of the old one.

A log can be deleted by an owner if it was genuinely submitted in error. That is a soft delete: it disappears from your views immediately, and a nightly job removes it permanently after 7 days. Within that window recovery is possible, but only through Opzaco support — there is deliberately no self-serve undo.

This is what makes a log worth keeping. A record that anyone could quietly edit afterwards proves very little.

Working a flag

A flag is not just a marker — it has a state you move it through, so nothing quietly sits unattended:

Open: The worker flagged it and nobody has picked it up yet. Filter the logs list to flagged entries to find them.
Seen: You tapped Acknowledge. The log records who acknowledged it and when, so a client asking “did anyone even look?” has a dated answer.
Resolved: You tapped Mark resolved once the problem was dealt with. Also dated and attributed, and you can Reopen if it turns out it was not fixed.

The worker’s original flag itself never changes — acknowledging and resolving are recorded alongside it, not on top of it.

If the asset is assigned to a client in the portal, flagging also emails them automatically when the log is submitted. They find out from you, in writing, rather than on their next site visit. See Client portal.

Finding logs

Logsin the sidebar lists everything, with filters for date range, property, worker, and flagged entries, plus a search over notes. The dashboard surfaces the three things you usually want without filtering: today’s logs, flagged logs, and overdue assets. A staff member’s profile shows their recent submissions, and an asset’s page shows its own service history.