How do I know a job was completed by a sensor?

This article explains how sensor readings complete scheduled jobs, how to identify an automatic completion in the compliance record, and what the device timeline does and does not show. It also explains why some readings have no visible action and how threshold breaches become draft Technical Recommendations.

How sensor readings complete jobs

BriqSafe checks scheduled jobs that are due today or earlier in the Location's own day.

1. The job must have a status of To do or In Progress.
2. The job must contain a parameter measured by a mapped sensor.
3. The sensor's latest reading is used if it is younger than the mapping's staleness threshold, which is 24 hours by default.
4. When every parameter has a value, including values already entered by hand, the job becomes Done.

If only some parameters have values, the job becomes In Progress. If no sensor fills a value, the job keeps its current status. Each automatic fill stores one reading with its value, unit and time, rather than the sensor's history.

• A job that is not due yet is not auto-filled.
• An early reading is skipped if it becomes older than the staleness threshold before the job is due.
• An unmapped parameter, including an optional parameter, keeps the job at In Progress until someone fills it in.
• The Automatic Job Execution setting on a Structure can switch auto-filling off for every job under that Structure.

Identify a job completed by a sensor

The Organisation Logbook provides the specific record that distinguishes an automatic completion from a manual one.

1. Open Organisation Logbook from the main menu.
2. Find the job event recorded as Task auto-completed.
3. Select the row to open its details.

The event has no person as its actor. Its byline shows Unknown where a person's name would normally appear. This entry and its unnamed actor are the only indication that the sensor pipeline completed the job automatically. The job otherwise behaves like a manually completed job.

A Location's Timeline tab lists the event under the same title as a manually performed job. Open the event to see the details that identify it as Task auto-completed. If the job is later performed by hand, the manual completion supersedes the automatic entry.

What the device timeline shows

The device's activity timeline is not the record of sensor-completed jobs.

1. Open the device from the IoT Devices list.
2. Scroll to the Device Timeline card at the bottom of the page.

Device Timeline records the device's lifecycle and connectivity, such as registration, provisioning, placement, moves, offline periods, return to connectivity and battery warnings. Readings are not timeline events. To review readings, use the device's readings chart higher on the page.

If the device has more than its first twenty events, select Show all. A device with no events shows No events yet.

When a reading needs no job

If a reading arrives when no due job needs that parameter, BriqSafe records it silently:

• No job changes status.
• No recommendation is created.
• No notification is sent.

The reading remains available on the device's readings chart. A job created after the reading can still use it if the reading is younger than the mapping's staleness threshold. Older readings remain on the chart as history.

What happens when a reading breaches a threshold

A reading that is outside a rule's threshold does not create a direct alert. It fills the scheduled job and can complete it, while the server evaluates the reading separately.

When the Location has an active Risk Assessment and the reading matches a risk rule, BriqSafe creates a draft Technical Recommendation. It does not create a Case or automatically escalate the issue.

1. Open the Location's Recommendations.
2. Under Filters, set Status to Needs Approval.
3. Select Apply Filters.
4. Open the draft recommendation to review its problem, solution, priority and triggering values.

The draft appears under Drafts (auto-generated) and carries an Auto-generated pill. It remains a proposal until someone approves or dismisses it. A draft from a sensor breach follows the ordinary recommendation review process; there is no separate IoT review queue.

Do not use device status as proof of compliance

Device status describes connectivity, not compliance. An Online device is not evidence that a job passed, and an Offline device is not a compliance issue by itself.

Compliance is recorded on jobs and their parameters. Use the job record and Organisation Logbook to establish whether a job was completed automatically or by a person.