This article explains how to mark a job as unable to complete in the BriqSafe mobile app. It is intended for engineers working on-site who need to record jobs that cannot be done, providing reasons and evidence so the back office can follow up effectively.
NoteRequired role: Engineer
Mark a Job as Unable to Complete
Use this process when a job cannot be performed because the outlet or asset is inaccessible, missing, or broken during a visit.
- Open the job you want to mark as unable to complete.
- Tap Unable to Complete.
- In the Reason field, enter a free-text explanation of at least 3 characters describing why the job cannot be done.
- Optionally, add a note and attach an evidence photo to support your reason.
- Tap Submit.
The job will then be recorded as Skipped, and the visit continues.
Important Details on Asset Absence
If you tick The asset is not present at this location, the system’s response depends on your role:
| Role | Effect on Asset Status | Job Status |
|---|---|---|
| Inspector | The asset is marked missing immediately. | Job is skipped. |
| Lower-tier Field Worker (e.g., Engineer) | The missing asset request is logged as a draft requiring approval. | Job is still skipped. |
Job Status and Visit Workflow
Choosing Unable to Complete sets the job status to Skipped with your reason included. There is no separate status labeled "unable to complete."
If you sign off a visit with jobs still open, those jobs are automatically skipped by the system with an automatic reason to distinguish them from deliberately skipped jobs.
Additional Notes on Signing Off a Visit
Before signing off a visit, review all jobs to ensure they are either completed or skipped intentionally. On the Sign Off tab:
- Review the JOB SUMMARY to see counts of completed, unable to complete, and not completed jobs.
- Either draw a signature on the signature pad or tick the confirmation checkbox (mutually exclusive).
- Optionally, add a comment about the visit.
- Tap Close Visit and confirm by tapping Sign off.
Any jobs left open at sign off will be automatically marked as skipped for back-office review. Note that signing off locks the visit on your device and prevents further edits to jobs within that visit.
If all jobs in a visit end up skipped or cancelled and none are completed, the visit is recorded as Skipped rather than Completed.
Working Offline
You can mark jobs as unable to complete while offline. Open the visit while online initially to cache the data. Offline entries, including notes and photos added during the unable to complete process, will queue and sync automatically when connectivity returns.
Summary
- Mark a job as unable to complete by entering a reason and optionally attaching notes and photos.
- The job records as skipped, allowing your back office to track and act on it.
- If the asset is missing, marking this triggers different workflows depending on your user role.
- Visits can be signed off without completing every job; pending jobs are auto-skipped with automatic reasons.
- Work offline safely and rely on auto-sync to update the system once reconnected.
