Completing works

Completing a works order seals a remediation record — the same evidentiary posture as finalising a survey, with the assigned operative’s own on-site photo and GPS fix as the default path, and an honestly-labelled portal fallback for when that isn’t possible.

What it is

The field app’s Complete job action is the primary route: at least one fingerprinted after-photo and a GPS fix acquired on the device, sealed the moment both are present. The portal’s works-order drawer offers a second, secondary route — a manager or coordinator recording completion on the operative’s behalf — for when the assignee genuinely couldn’t do it themselves; this is always marked as a proxy entry, never disguised as the operative’s own submission.

Before you start

Completing a job from the field app needs an assigned-scope Edit grant on Work orders for that specific job. Recording completion from the portal needs organisation-scoped Edit access to Work orders on either the landlord or the contractor side of the job.

How to do it

1. In the field app, open the job and tap Complete job. Add at least one after-photo; the app acquires a GPS fix automatically.
2. If your organisation requires a photo (the default) and none is available, an explicit I confirm no after-photo is available checkbox plus a completion note stand in — this marks the record Notes Only — No Photo Evidence rather than blocking you outright.
3. If photos are still uploading when you tap Complete, the app queues sealing automatically once they land — you can close the app and walk away; a permanently blocked upload (a device security check, a rules rejection, storage at capacity) is surfaced plainly instead of being silently retried forever.
4. From the portal, open the works order and use Record completion on the operative’s behalf — choose after-photos if available, or confirm the no-photo skip and add a completion note. This path never captures GPS at all, since a coordinator’s own location isn’t the job site’s; the record is honestly marked No Presence Data instead.

How it integrates

Completing a job writes a remediationRecords entry — hash-chained back to the source survey’s own record hash where one exists, using the same sealing machinery as finalising a survey. This is the evidentiary floor a works order needs to reach Works Complete on the case lifecycle rail; verifying it is a separate, optional step layered on top — see Verifying works. A cancelled works order can never be completed through either route.

Common problems

• Complete job is greyed out or won’t submit. Check the GPS fix acquired — a blocked location permission shows its own reason and a retry button; on desktop, or where location genuinely can’t resolve, use the portal’s proxy-completion route instead.
• I completed a job with no photo and want that visible later. It is — a Notes Only — No Photo Evidence chip stays on the record wherever it’s shown.
• A coordinator completed a job and I want that clearly distinguished from the operative’s own work. It is — proxy completions are marked with who entered them and, optionally, why, and never carry a GPS fix.