Checks

Checks define what needs to be verified, when, and how evidence is captured.

Photo centreline targets

A centreline target can be a photo. The operator compares the machine with the target photo and records Matches or Doesn't match. Target photos are stored per format when a check uses format-specific targets; optional evidence photos remain separate from the target.

Authorized users can create photo centrelines in either the portal or the mobile app. On mobile, each target photo can be captured with the camera or selected from the photo library.

The portal's Checks area has three tabs: Activity (individual check instances), Definitions (the check library), and Proposed Changes (the review queue for suggested edits).

Who Can Do This

Owners, Admins, and Managers can create and edit checks.

Check Types

Centreline Checks

Centreline checks verify that a machine or process is running within a defined target range. They are used for ongoing in-process monitoring — confirming that a value (speed, weight, temperature, label position, etc.) meets the expected standard.

• Targets are required: text, numeric value, numeric range, or photo.
• A result is passed if the entered value matches the target; failed if it does not.
• When a reading is outside target, the Operator records whether they corrected it, left it for follow-up, or believe the target should change. Leaving it for follow-up raises or updates a deviation action; a later passing result closes that action automatically.
• Targets can vary by machine format, so the same check can have different acceptable values depending on what is currently running.

CIL Checks (Cleaning, Inspection, Lubrication)

CIL checks are task-based checks for maintenance and inspection activities. They confirm that a specific task was carried out — not that a value fell within a range.

• No target is required; the result is a simple pass/fail based on whether the task was completed.
• A failing CIL check raises a defect action automatically. Defects require explicit resolution and verification before they close.
• CIL checks are suited to tasks like "Wipe down conveyor belt", "Check oil level", or "Inspect safety guard".

Choosing the right type: Use Centreline for measured process parameters; use CIL for discrete maintenance tasks.

Restricting Who Can Execute A Check

A Manager can restrict a check to a specific function — Production, Maintenance, Quality, or Engineering — for example a CIL lockout task that only Maintenance should carry out. A restricted check is never hidden: everyone on the line still sees it in their list, but only members of the required function can complete it; everyone else sees it read-only. Compliance is unaffected by the restriction — a missed restricted check still counts against the line the same as any other missed check. This is set per check from the check's Location & Identity settings, either when creating it or editing it later. Only functions that somebody in your organisation belongs to are offered — a check restricted to a function with no members could never be completed — so add people to a function first if you do not see it listed.

Before You Start

• Ensure your factory, Line or Group, and machine structure is set up.
• For machines on production Lines, define Line and machine formats if you plan to use format-specific targets.

Create A Check In The Portal

1. Go to Operations -> Checks -> Definitions.
2. Select the factory, Line or Group, and machine.
3. Click Create Check to open the wizard.

Step 1: Location And Identity

• Choose the Line or Group and machine for the check.
• Select the check kind: Centreline or CIL.
• Add a clear title and optional description.
• Decide whether photo evidence is required.
• Optionally restrict execution to a function. A restricted check stays visible to everyone on the line — read-only — and a miss still counts against line compliance.

Evidence photos are always captured live with the device camera — operators cannot attach an existing photo from the gallery. This is deliberate: evidence exists to show the machine at the moment the check was completed, not a photo taken earlier. This is different from photo centreline target photos (see Photo Centreline Targets above), which an authorized user can capture or choose from the photo library when defining the standard operators check against.

Step 2: Scheduling

Choose the trigger type:

Periodic

Runs on a recurring schedule regardless of production state. Choose Hourly, Daily, Weekly, or Monthly, then select the interval, day, and time shown by the schedule picker.

• The schedule is evaluated in the factory's configured timezone.
• Hourly intervals can run every 1, 2, 3, 4, 6, 8, or 12 hours at minute :00, :15, :30, or :45.
• Daily and weekly schedules use 24-hour local time.
• Monthly schedules use days 1–28 so every selected date exists in every month.

Examples include every hour at :00, every four hours at :15, daily at 06:00, every Monday at 09:00, or monthly on day 1 at 07:30.

Set the factory timezone before creating checks. Schedule times follow that local timezone, including daylight-saving changes. Avoid scheduling safety-critical work during a repeated or skipped daylight-saving transition hour; use a shift-start trigger or another unambiguous time instead.

On Format Change

Fires once every time the active line format changes. Use this for checks that need to be performed whenever a changeover happens — for example, verifying that a machine is set up correctly for the new product.

Available only for machines on production Lines.

• The check instance is created immediately when an operator records a format change in the portal or mobile app.
• Format change checks are not subject to a periodic schedule; they depend entirely on when changeovers occur.

At Shift Start

Fires once at the start of each production shift. Use this for checks that should happen at the beginning of every shift — for example, pre-start safety inspections or startup parameter verification.

Choose all configured shifts or select individual shifts. Configure factory shifts before creating this type of check.

Manual

Available for production-line machines and Group assets. It generates no instances on a schedule. Instead, the check becomes due when an operator chooses Trigger all checks on the machine or asset in the mobile app, which immediately makes every active check on it due and completable, manual checks included. Use this for ad-hoc checks that only apply on some occasions — for example, pre-start checks for equipment that is only turned on some days.

• Manual checks stay due until they are completed; they are not marked missed and do not count against timeliness metrics.
• Triggering is idempotent: if a manual check already has an open occurrence, triggering again does not create a duplicate.
• A single trigger starts every active manual check on the selected machine or asset; operators cannot choose just one from that set.

See Manually Triggered Checks for the complete configuration and mobile workflow.

Grace Period

The grace period is the window of time after a check becomes due in which it can still be completed and count as on time. A check completed within the grace period is counted as on time in timeliness metrics; one completed after the grace period has elapsed is still recorded but is counted as late. A check that is never completed becomes missed after the grace period ends.

New checks inherit the factory's default grace period. Review that default under Settings -> Factories before creating checks. Set it long enough for realistic shift constraints but short enough to identify genuine non-compliance.

Scheduling Decision Guide

Need	Trigger
A check at a regular time or interval	Periodic
A check whenever a production Line's product or setup changes	On Format Change
A check at the beginning of one or more shifts	At Shift Start
An ad-hoc check started by the operator on a machine or asset	Manual

Step 3: Target Configuration

Choose the target type:

• Text: A condition written out, which the operator confirms or disputes — for example All gauges in green zone. The operator sees the target and chooses Setting is correct or Setting is deviated; they do not retype it. Write the target as the condition you want to be true, not as a question. Use Number or Range instead when the operator should record an actual reading.
• Number: The operator enters a numeric value compared against a target number.
• Range: The operator enters a numeric value compared against a minimum and maximum.
• Photo: A reference photo of the correct state. The operator compares the machine with it and chooses Matches or Doesn't match. When the photo itself is wrong, the operator can propose a replacement photo from the mobile deviation flow, which can be reviewed or trialled like any other target change.

For a Group asset, enter one Target. For a production-line machine, apply one target to all formats or set targets per format when different products have different acceptable values.

Note: CIL checks do not require targets — they are pass/fail task confirmations.

Step 4: Reference Media

• Upload photos or videos that show the expected outcome.
• Add captions to reduce ambiguity for operators.

Step 5: Review And Create

• Confirm the schedule, targets, and evidence requirements.
• Create the check and verify its order in the machine sequence.

Time Tracking

Continual records how long each operator takes to complete a check — from tapping Start to submitting the result. On the check detail page you can see the median completion time (Typical time) and a distribution of times across recent submissions. The same metrics appear in Analytics -> Insights -> Completion, including a slowest-checks ranking and typical-time columns in the completion breakdown table.

Check instance CSV exports include Time Spent (s) and Completed At columns when a result is linked.

Ordering Checks

Checks are executed in sequence for each machine. Reorder checks to match the flow on the floor.

Editing And Archiving

Use the check detail panel to update schedules, targets, or evidence requirements. Archive checks that are no longer active.

See Check Lifecycle for version history, proposed changes, and archival guidance.

Proposed Changes

Any user can propose changes to a check without applying them immediately — including Operators proposing from the mobile app. A Manager, Owner, or Admin reviews the proposal from the Proposed Changes tab (Operations -> Checks -> Proposed Changes) and either approves or rejects it. Reviewers can also edit a proposal before approving it. Approved proposals are applied and create a new version of the check, preserving the full history of changes.

Proposals linked to failed centreline readings are marked Fail-linked in the queue. Use the Source filter to show only these proposals, then expand a row to review its readings, original targets, Operator notes, photos, and recurrence count before deciding whether to edit, approve, or reject it.

Eligible fail-linked target proposals can also be accepted temporarily for 1 to 14 days. The proposed target takes effect during the trial and a review action records the later keep/revert verdict. See Deviations And Temporary Target Trials for the complete workflow.

This workflow lets floor-level observations feed back into check configuration without requiring direct admin access for every update.

Check History

Recorded results can be browsed on the floor from the mobile app's History screen, as a list or as a grid of result photos, with each result shown against the target it was judged against at the time. See Check History In The Mobile App.

Best Practices

• Use action-oriented titles like "Check oil level" or "Verify label alignment".
• Keep targets aligned with the current machine format.
• Set grace periods that reflect real shift constraints.

Related Pages

• Factories, Lines, Groups & Machines
• Formats
• Check Lifecycle
• Deviations And Temporary Target Trials
• Manually Triggered Checks
• Complete Checks In The Mobile App
• Check History In The Mobile App
• Troubleshooting