Continual

Appearance

Check Lifecycle ​

Checks move through a lifecycle from draft configuration to daily execution, review, and eventual archival.

In the portal, the Checks area is split into three tabs — Activity, Definitions, and Proposed Changes — which map to the stages below.

Create ​

Managers, Admins, and Owners can create checks from Operations -> Checks -> Definitions.

Each check belongs to one machine and includes:

  • Type: Centreline or CIL.
  • Trigger: periodic, at shift start, on format change, or manual (started on the machine in the mobile app).
  • Grace period.
  • Target configuration, for centreline checks.
  • Evidence requirement and reference media.
  • Sequence order on the machine.

Execute ​

When a check becomes due, operators complete it in the mobile app. Each occurrence is stored as a check instance. Scheduled checks create occurrences automatically; manually triggered checks create an occurrence only after a mobile user triggers them on the machine.

Operators can:

  • Submit passing or failing results.
  • Enter numeric, text, selection, pass/fail, or photo responses.
  • Add notes and evidence.
  • Skip a check with a reason when it cannot be completed.

Review Activity ​

Use Operations -> Checks -> Activity to review due, completed, missed, and skipped check instances.

Use this view for daily supervision:

  • Find checks that are currently due.
  • Investigate missed or skipped checks.
  • Confirm whether late work was still completed.
  • Filter by factory, line, machine, status, and date range.

Update ​

Use Operations -> Checks -> Definitions to edit an existing check.

Common updates include:

  • Changing the schedule or grace period.
  • Updating target values.
  • Adding or replacing reference media.
  • Changing evidence requirements.
  • Reordering the machine sequence.

Continual preserves history so previous results remain tied to the definition that existed when they were submitted.

Proposed Changes ​

Operators can propose changes from the mobile app without directly editing live configuration. Managers, Admins, and Owners review proposals from Operations -> Checks -> Proposed Changes.

Proposals are useful when operators notice:

  • A target no longer matches reality.
  • A description is unclear.
  • Reference media is missing or stale.
  • A new check should be added.
  • The sequence order does not match the floor route.

Approved proposals apply the change and create a new version. Reviewers can adjust a proposal before approving it. Rejected proposals remain in history with reviewer notes.

Archive ​

Archive checks that should no longer create new work. Do this instead of deleting when the check has historical results.

Archived checks:

  • Stop creating new check instances.
  • Remain visible in historical reporting.
  • Preserve past results and actions.

Create a replacement check when the task has changed enough that comparing future results to past results would be misleading.

Version History ​

Check detail views include version history so managers can see what changed over time.

Use version history when investigating sudden metric changes, operator confusion, or a new pattern of failed results after a check was updated.