Skip to main content
All CollectionsHelp ArticlesMaintenance and Lubrication
Proof of Presence (POP) Facility and Route Level Settings
Proof of Presence (POP) Facility and Route Level Settings

Enforce completing tasks at the applicable asset with Proof of Presence

Kyle Bryant avatar
Written by Kyle Bryant
Updated over a week ago

Redlist Proof of Presence allows Supervisors to require that technicians scan a tag in order to complete the tasks for a given asset or group. It enables technicians to show, especially during downtime events, that preventative maintenance has been performed on that asset.

Proof of Presence is controlled in two areas

To set up Proof of Presence for your Facility:

Go to Settings > Lubrication Routes > Task Completion

Under the 'Require Asset Scan (Proof of Presence)' there are four options:

  1. Select (Default)- Proof of Presence will not be required for task completion. Additionally, in Route setup, the Proof of Presence setting will indicate that no POP has been selected at the facility level.

  2. Do not require Proof of Presence- Proof of Presence will not be required for task completion. Additionally, in Route setup, the Proof of Presence setting will indicate that the facility has elected to NOT require POP to complete tasks.

  3. Require POP of individual assets- This will require POP for tasks on each asset that you want to complete.

  4. Require POP on per asset or asset group- Allows technicians to scan either an asset or a group tag for a group that asset is in to complete tasks.

To set POP on Specific Routes:

Lubrication Routes > Route Setup / Templates > Select a route or click 'Create' to enter route setup

At the bottom of the page is the Require Asset Scan (Proof of Presence) setting

  1. Select (Default)- Proof of Presence will remain linked to the facility POP requirements. The Facility Setting will show in the parentheses next to Select

  2. Do not require Proof of Presence- Proof of Presence will not be required for task completion.

  3. Require POP of on individual assets- This will require POP for tasks on each asset that you want to complete.

  4. Require POP on per asset or asset group- Allows technicians to scan either an asset or a group tag for a group that asset is in to complete tasks.

Note: A warning will appear when a supervisor is selecting an option on the route that differs from the facility selection and once the route is moved off of the default, it will maintain the selection if the facility setting is changed.

Did this answer your question?