NodeOne
NodeOne Group

Deviance Logger Guides

5 guides 90 steps 24 parts Nov 10, 2026

Pick the guide for the job you are doing. Deviances Overview covers the back end, New Service Provider follows one job from assignment through to final sign-off, and New Task Entry is the phone workflow for creating a task and editing a log. New Log Entry is the phone workflow for logging a new deviance and adding notes to it. Introduction covers signing in and finding your way around the app.

Guides
5
Steps
90
Parts
24
Updated
Nov 10, 2026
  1. Introduction cover screenshot
    14 steps4 parts

    Introduction & Login Initiation

    Start here. Sign in, see the home page, understand the Logs Data and analytics dashboards, and find your way around the main navigation.

  2. New Log Entry cover screenshot
    18 steps6 parts

    New Deviance Log Entry

    Log a new deviance on the phone: set the priority, category, severity, type and impact, describe it, pick a resolution date, attach evidence and save. Then review the entry and add a note.

  3. New Task Entry cover screenshot
    18 steps2 parts

    New Task Entry

    The mobile side. Create a task with a title, due date and time, task type, dependency, client details and the linked deviance, then edit a log that is already recorded.

  4. New Service Provider cover screenshot
    21 steps6 parts

    Service Provider Management

    One job, start to finish. Create the portal login, log and approve the deviance, assign it, accept it from the mobile portal, inspect the work and move it to Complete.

  5. Deviances Overview cover screenshot
    19 steps6 parts

    The Deviance Section Overview

    The back-end workflow. Log a deviance, find your way around the Deviance section, read the cards, sort and filter, and add a new deviance.

Five written guides covering the Deviance Logger. Screenshots are frames from the Ep 1, Ep 2, Ep 3, Ep 4 and Ep 5 videos, so names, dates and counts are demo values and may differ in your environment.

Download PDF

How to Use the Deviance Logger: Introduction

14 steps 4 parts 10 November 2026

Watch Episode 1 on YouTube

This guide follows Episode 1 – Deviance Logger: Introduction from NodeOne Group. It covers the sign-in process, home page, Logs Data and analytics sections, and the main navigation menu. All screens featured in this guide are taken from the introductory video.

Parts
4
Steps
14
Helpful Tips
3
Need to Know
2

Things You'll Need

  • The Deviance Logger mobile application installed on your device.
  • Your username, ID number, email address, or phone number.
  • The system password provided by the NodeOne team.
  • Biometric authentication enabled on your device if you wish to use this sign-in method.

Part 1: Sign In

1

Open the Deviance Logger

Open the Deviance Logger application on your mobile device. The welcome screen allows you to enter your login credentials so the application can grant you access based on your assigned role.

In the demonstration, the welcome screen is displayed and ready for the user to sign in.
2

Enter Your Username or ID

Tap the user input field and enter your username, ID number, email address, or phone number. This identifies your account and determines which functions are available based on your role within the platform.

In the demonstration, the user’s details are entered into the input field.
3

Tap Next

Once you have entered your details, tap Next to continue. The application will proceed to the password entry screen.

In the demonstration, tapping Next takes the user to the password prompt.
4

Enter Your Password

Enter the system password provided by the NodeOne team. If biometric authentication is enabled on your device and supported by the application, you may also be able to sign in using facial recognition or another biometric method.

In the demonstration, the user’s credentials are successfully authenticated.

Part 2: The Home Page

5

Access the Home Page

After successful authentication, the application opens the Deviance Logger home page. The layout is clean and organised into clearly defined sections, allowing you to view your data and access key functions quickly and easily.

In the demonstration, the home page is displayed and ready for use.
6

Explore the Three Main Areas

The home page is divided into three main areas: Logs Data, monthly analytics dashboards, and the main function buttons. The NodeOne team can customise the layout to suit your organisation’s specific requirements.

In the demonstration, all three areas are visible on the home page.

Part 3: Logs data and analytics

7

Logs Data

The Logs Data section displays real-time information based on your profile permissions. Standard users can view statistics relating to the deviance incidents they have logged, while managers and supervisors can access data relating to their teams, groups, or business units.

In the demonstration, the Logs Data totals are displayed at the top of the home page.
8

Monthly Analytics Dashboards

The monthly analytics dashboards provide a visual overview of the data. These dashboards display statistics relating to users, types of deviance, groups, priority, impact, and location. Swipe through the available dashboards to explore the different charts and view the latest statistics.

In the demonstration, the dashboards display various charts that users can navigate by swiping.

Part 4: Navigation and functions

9

Main Navigation Menu

The main navigation menu is located at the bottom of the screen. This menu contains icons that provide quick access to the core functions of the Deviance Logger, allowing you to navigate the application easily after signing in.

In the demonstration, the navigation icons are visible along the bottom of the screen.
10

Home

The Home icon is the first option in the bottom navigation menu. Tap this icon at any time to return to the main dashboard.

In the demonstration, tapping Home returns the user to the main dashboard.
11

Logged Deviance

The Logged Deviance function allows you to review previously recorded entries. Use this section to access historical deviance records and review incidents that have already been logged.

In the demonstration, selecting Logged Deviance opens the historical deviance records.
12

Team Meetings

The Team Meetings function supports collaboration and team discussions. Use this section to schedule or view meetings where team members can collectively review and discuss logged deviance incidents.

In the demonstration, Team Meetings provides access to meeting scheduling and viewing functions.
13

Deviance Tasks

The Deviance Tasks function allows you to manage action items arising from logged deviance incidents. This helps ensure that follow-up actions can be tracked, monitored, and reviewed.

In the demonstration, selecting Deviance Tasks opens the list of actionable items.
14

Search

The Search function allows you to quickly locate specific records and information within the platform. Now that you understand the sign-in process, home page layout, and main navigation functions, you are ready to start using the Deviance Logger with confidence.

In the demonstration, the Search function provides quick access to specific platform data.

Helpful Tips

  • Use the login details assigned to you by your organisation, such as your username, ID number, email address, or phone number.
  • Swipe through the monthly analytics dashboards to explore different views of users, types of deviance, groups, priority, impact, and location.
  • Use the bottom navigation menu to switch quickly between Home, Logged Deviance, Team Meetings, Deviance Tasks and Search.

Need to Know

  • Profile permissions: The Logs Data displayed depends on your assigned profile permissions. Standard users can view their own logged deviance records, while managers and supervisors can access data relating to their teams, groups or business units.
  • Customisable interface: The layout presented in this guide represents the standard application view. The NodeOne team can customise the appearance and layout to suit your organisation’s requirements.

Download PDF

How to Use the Deviance Logger: Deviances Overview

19 steps 6 parts Nov 6, 2026

Watch the Ep 5 video on YouTube

The Deviance section of the NodeOne Deviance Logger is where you can view, search for and log deviances: spillage, infrastructure damage, resident falls, water leaks and more. From the home screen, you can browse deviances as cards, in a table, in a calendar or on a map. You can also sort, filter, export to Excel and add a new deviance. This guide follows Ep 5 – Deviance Logger – Deviances Overview from NodeOne Group.

Parts
6
Steps
19
Helpful Tips
5
Need to Know
3

Things You'll Need

  • A Deviance Logger App or Desktop login to view the Deviance section
  • To log a new deviance: a description, its type, category, severity, impact, urgency, location and due date
  • A photo of the deviance (optional)
  • Excel or similar to open exports (.xlsx)

Part 1: Opening the Deviance Section

1

Sign in and view the Dashboard

At the top are four totals: Total Deviances, Open Deviances, Overdue Deviances and High Urgency. Below them are three charts: Deviances per User, Deviance Distribution by User, and Cumulative Deviances over Time.

In the demo, the four totals read 89 (Total Deviances), 89 (Open Deviances), 84 (Overdue Deviances) and 47 (High Urgency).
2

Select Deviance from the left sidebar

The Deviance List opens as a grid of cards, and the total item count shows at the top left. This view can also be accessed from the Dashboard’s Welcome panel by selecting “Manage Deviances”.

In the demo, the list shows Total: 89 items at the top left.

Part 2: Reading a Deviance Card

3

Identify a deviance by the banner colour

It shows the deviance type (for example, Product Spillage) and its unique ID (for example, DEV…). Each deviance type is represented by its own colour.

In the demo, DEV000104 is Product Spillage on a blue banner.
4

View the deviance priority

Each card displays the deviance’s Severity, Impact, Urgency, and creation date.

In the demo, DEV000104 shows Severity Minor, Impact Medium, Urgency Medium and Created At 9/10/2026.
5

Identify the issue quickly with a photo

The photo uploaded for the relevant deviance fills the left side of the card. Cards without a photo display a placeholder image.

In the demo, TRAVEL EMERGENCY DEV000109 shows a placeholder, and ENGINE BREAKDOWN DEV000107 shows its photo.

Part 3: Narrowing the List Quickly

6

Choose a quick-filter tab

Use a pre-configured filter to manage deviances. The tabs above the list are All, Next Day, Next Week, Critical, and Overdue. For example, Next Week shows only deviances due within the next week.

In the demo, Critical is selected and the list shows Total: 17 items.
7

Search by keyword

Use the Search Deviance box in the top-right corner to search. The list of deviances updates as you type your search.

In the demo, typing “rep” narrows the list to matching cards.

Part 4: Switching Views

8

Click Table View to display the deviances as a list

The list contains the columns: Type, Description, Category, Location, Urgency, Severity, Impact, Due Date, State, Logged By and Approval By. The State column indicates each deviance’s current workflow stage: Logged, Accepted, In Progress, Awaiting Final Signoff or Complete. To return to the card view, click the same button, now labelled Grid View.

In the demo, the table shows Total: 89 items, with State values such as Logged, Accepted, Complete and In Progress.
9

Click Calendar to view deviances by due date

The Deviance Calendar opens in Month view. Use the dropdown at the top right to switch to Week or Day. Move between dates with the arrows, or click Today. Click List to go back.

In the demo, November 2026 shows several records, including “this is a demo test” and a Rep Comms item.
10

Click Map to see where deviances occurred

The Deviance Map marks each deviance’s location with a pin. Use + and – to zoom in and out, or click Fit to All to view all pins. The quick-filter and Filters work as well. Click List to return.

In the demo, pins are spread across several countries, with a cluster in South Africa.

Part 5: Sorting, Filtering and Exporting

11

Choose a sort order

Open the Sort dropdown and pick Created Date (the default), Updated Date, Type, Description, Category, Location or Urgency.

The Sort dropdown lists Created Date, Updated Date, Type, Description, Category, Location and Urgency.
12

Open Filters for detailed criteria

Click Filters to open the panel, then filter by Type, Description, Category, Location, Urgency, Severity, Impact, Due Date, State, Logged By, Approval By and Service Provider. Under Type you can select multiple values at the same time, for example, Rep Comms, Infrastructure damage and fire damage.

In the demo, the Filters panel shows all twelve filter fields, from Type to Service Provider.
13

Apply filter criteria

Click Apply to show only the matching deviances. To reset the filters, reopen Filters and select Clear.

In the demo, Type has several values ticked and the list narrows to Total: 1 item.
14

Click Export to download the list

An Excel file is downloaded with a name like Deviance_2026-11-04_11-38.xlsx. In the video, the export came straight after filtering the list down to one deviance

In the demo, the download notice reads Deviance_2026-11-09_11-08.xlsx and Download complete.

Part 6: Adding a New Deviance

15

Click Add Deviance at the top right of the list

Use the button at the top right of the Deviance List. The form has an Information section and an Extra section.

In the demo, Add Deviance is at the top right of the list.
16

Complete the Information section

Required fields in the form are marked with an asterisk (*) : Description, Type, Category, Severity, Impact and Urgency. Severity ranges from Not Severe through Trivial, Minor and Major to Critical.

In the demo, the description is “this is a demo test”, the type is Patient fall, and the category is Health and Safety.
17

Set the location

Use the dropdown in the Location box to select a pre-configured location. A marker will appear on the Map. Drag the marker to the exact location. If applicable, use the dropdown to select a pre-configured area.

In the demo, the location is Sandton and the area is PA1, with the marker placed on the map.
18

Fill in the Extra section

Choose who the deviance was Logged By and set a Due Date (both are required). If available, add Actions Taken, Approval By and a Service Provider.

In the demo, Logged By and Approval By are Demo User, and Due Date is 2026/11/17.
19

Click Save

A green “Saved successfully” message appears, and the new deviance shows up at the top of the Deviance List. Click Close instead if you want to leave without saving.

In the demo, the green “Saved successfully” message appears at the top right.

Helpful Tips

  • Start each day by checking the Overdue and Critical tabs. They highlight the deviances that need attention soonest.
  • To review a single category or team, filter the list first, then export it. You’ll get a focused spreadsheet instead of the full list.
  • Use the map to identify clusters, such as multiple deviances at the same site.
  • When adding a deviance, place the map marker exactly where it occurred. An accurate pin makes the Deviance Map more useful to everyone.
  • Add details to Actions Taken as soon as you know them, so others can see what has already been done.

Need to Know

  • You can't save a new deviance until every field marked with an asterisk (*) is filled in.
  • The State field on the Add Deviance form is read-only. It is set by the workflow, so you can't select or change it yourself.
  • Filters remain active until you clear them. If the list appears short, open Filters and click Clear, or select the All tab.

Download PDF

How to Use the Deviance Logger: New Service Provider

21 steps 6 parts 9 November 2026

Watch Episode 4 on YouTube

This guide follows Episode 4 – Deviance Logger: New Service Provider from NodeOne Group. It explains the complete service provider workflow, including creating portal login credentials, logging and approving a deviance, assigning work to a service provider, accepting the assigned job through the mobile portal, inspecting the completed work, and moving the deviance record to Complete.

The guide includes screens from both the desktop back-end platform and the service provider’s mobile portal.

Things You'll Need

  • Your NodeOne login credentials with access to Service Providers, Deviance, and Kanban.
  • The service provider’s name, email address, and a password for their portal login.
  • The information required to log a deviance, including its description, type, category, severity, impact, urgency, location, and due date.
  • A mobile device that allows the service provider to receive notifications and access the mobile portal.

Part 1: Provider Access

1

Open the Service Provider Record

In the left-hand sidebar, select Service Providers and open the record of the service provider you wish to grant portal access to. This guide uses Demo Service Provider as an example. The Edit Service Provider form displays the provider’s name, description, type, email address, phone number, website, and portal login information.

In the demonstration, Type is set to Pre-Approved Service Provider, and the Portal Access section displays “No portal logins yet for the Service Provider.”
2

Review the Service Provider Details

Before creating a portal login, verify that the Name, Description, Type, and Email fields contain the correct information. The Name, Description, and Type fields are mandatory. Enter a phone number or website address, if available, and use the Notes field to record any additional information that may be useful to other users.

In the demonstration, Name and Description are both set to Demo Service Provider, Type is Pre-Approved Service Provider, and Email is demo@gmail.com. The Username field is being completed.
3

Create the Portal Login

Under Portal Access, enter a Username, the service provider’s Email address, and a Password. Once the required information has been entered, click Create Portal Login. These credentials will allow the service provider to access the mobile portal. Ensure that the login details are shared securely with the intended user.

In the demonstration, Username is entered as demoprovider, and Email is set to demo@gmail.com. The Password field is still empty at this stage.
4

Save the Service Provider

Once the portal login has been created, it appears under the Portal Access section with a green Active status indicator. The system also provides options to Reset Password or Deactivate the login if access changes are required. Click Save in the top-right corner to save the service provider’s details and portal access information.

In the demonstration, the demoprovider login is marked as Active, and Demo Service Provider is available for selection when assigning a deviance.

Part 2: Log and Approve a Deviance

5

Log a New Deviance

Open Deviance and click Add Deviance to create a new entry. Enter a clear Description of the incident, then select the appropriate Type, Category, Severity, Impact, and Urgency. Set the Location using the map, then navigate to the Extra section to complete the Due Date and Logged By fields. Once the required information has been entered, click Save to create the deviance record.

In the demonstration, a new deviance is created with reference number DEV000105, the description “demo deviance”, Type set to Product Spillage, and Severity set to Minor.
6

Receive the Approval Notification

Once a deviance has been logged, the deviance manager receives a push notification through the mobile application. The notification identifies the deviance record and indicates that it is awaiting approval.

In the demonstration, the notification reads “Approval Needed — DEV000020 — Waiting for approval.” The notification reference differs from the desktop record, which displays DEV000105.
7

Approve the Deviance

Open Approvals in the desktop back-end platform and locate the newly logged deviance. Select the relevant record and approve it. Once approved, the deviance card automatically moves from the Logged column to the Accepted column on the Kanban board.

In the demonstration, DEV000105 appears in the Accepted column, which displays a total of 24 items.

Part 3: Assign and Activate the Work

8

Complete the Work Details

Open the accepted deviance card to review and update its information. In the Extra section, enter any relevant details in the Actions Taken field, if applicable. Review the Logged By, Approval By, and Due Date fields to ensure that the information is correct. The Logged By and Due Date fields are mandatory. Supporting photographs can also be attached using the Images upload area located below the Due Date field.

In the demonstration, Logged By and Approval By are both set to Demo User, the State is Accepted and is read-only, and the Due Date is 2026/11/07.
9

Assign the Service Provider

Locate the Service Provider field and open the dropdown menu. Select the service provider created or configured in Steps 1 to 4. For this demonstration, select Demo Service Provider. The dropdown menu also displays other service providers configured within the platform.

In the demonstration, Demo Service Provider appears at the top of the list, followed by SP Security, SP Construction, and SP Cleaning.
10

Move the Deviance to Activated

On the Kanban board, locate the deviance card in the Accepted column. Drag the card from Accepted and drop it into the Activated column. This activates the assigned work and makes the job available to the selected service provider through the mobile portal.

In the demonstration, DEV000105 moves from Accepted to Activated. The Activated column increases from 6 to 7 items, while Accepted decreases from 24 to 23 items.

Part 4: Accept the Assigned Job

11

Receive the Work Assigned Notification

Once the deviance has been activated, the assigned service provider receives a push notification indicating that new work is awaiting attention. The notification identifies the relevant deviance record and its current work status.

In the demonstration, the notification reads “Work Assigned — DEV000020 — Work awaiting.”
12

Sign In to the Service Provider Portal

Open the Deviance Logger mobile portal. Enter the Username and Password created in Step 3, then tap Sign In to access the service provider’s assigned work.

In the demonstration, the username is entered as demoprovider, while the password is displayed as masked dots for security purposes.
13

Open the Assigned Job from Logs Overview

After signing in, the service provider is directed to the Logs Overview screen. Assigned work appears as individual cards displaying information such as severity, title, deviance reference number, creator, and creation date. Locate the relevant job and tap its card to open the detailed view.

In the demonstration, the card displays Minor, PRODUCT SPILLAGE, DEV000105, and indicates that the record was created by demo on 2026-09-15.
14

Add Notes, Images or Documents

On the deviance detail screen, tap Add Info in the top-right corner. A menu appears with three options: Note, Image, and Document. Use these options to document the investigation, record observations, or attach supporting evidence before accepting the assigned work. Adding relevant information helps maintain an accurate record of the incident and any actions taken.

In the demonstration, the Add Info menu displays the options Note, Image, and Document.
15

Accept the Work and Move It to In Progress

Tap Progress at the top of the deviance detail screen. A confirmation dialog appears, asking whether you want to move the log to In Progress. Tap Progress again to confirm the action. The deviance status changes from Activated to In Progress, and the relevant manager is notified of the status change.

In the demonstration, the confirmation dialog displays “Move this log to In Progress?” with Cancel and Progress options. The record remains in Activated until the action is confirmed.

Part 5: Inspection

16

Move the Work to Awaiting Inspection

Once the service provider has completed the assigned work, open the deviance card in the In Progress section. Tap Progress to move the record to the next stage. The deviance moves to Awaiting Inspection, indicating that the work is ready to be reviewed. The available action button changes to Submit for Approval.

In the demonstration, DEV000105 is the only card in the In Progress column. After tapping Progress, the Awaiting Inspection column displays 1 item.
17

Receive the Inspection Notification

When the deviance reaches the Awaiting Inspection stage, the approvals manager receives a notification indicating that the work is ready for inspection. The manager can then review the completed work and assess whether it meets the required standards. Following a successful inspection, the manager can communicate the outcome to the service provider through a note.

In the demonstration, the notification reads “Inspection — DEV000020 — Awaiting Inspection.”
18

Submit the Job for Final Approval

On the deviance detail screen, tap Submit for Approval in the top-right corner. A confirmation dialog appears, indicating that the record will be submitted for final approval. The dialog explains that the deviance is being submitted to Awaiting Final Sign-off and will remain in its current stage until an authorised approver accepts the submission. Tap Submit to confirm.

In the demonstration, the screen displays Awaiting Inspection, and the confirmation dialog provides Cancel and Submit options.

Part 6: Final Sign-off and Completion

19

Review the Provider’s Remaining Work

Once the job has been submitted for final approval, it is removed from the service provider’s active work columns. The deviance no longer appears under Activated, In Progress, or Awaiting Inspection. Authorised management users can continue reviewing the relevant records through the desktop back-end platform.

In the demonstration, the Activated, In Progress, and Awaiting Inspection columns each display 0 items, while the Completed tab remains available.
20

Review the Final Sign-off Requirements

In the desktop back-end platform, open the Kanban board and locate the deviance card in the Awaiting Final Sign-off column. At this stage, the record remains pending while any outstanding requirements are reviewed and finalised. These may include finance, quotations, invoices, documentation, and training. Ensure that all necessary requirements have been completed before moving the deviance to its final stage.

In the demonstration, DEV000105 appears in Awaiting Final Signoff, while the on-screen list identifies Finance, Quotes, Invoices, Documents and Training as items requiring attention.
21

Move the Deviance to Complete

Once the final sign-off requirements have been satisfied, locate the deviance card in the Awaiting Final Signoff column. Drag the card from Awaiting Final Signoff and drop it into the Complete column. This marks the deviance workflow as completed.

In the demonstration, DEV000105 moves to Complete. The Complete column increases from 8 to 9 items, while Awaiting Final Signoff decreases from 6 to 5 items.

Helpful Tips

  • Create portal access before assigning work: Ensure that the service provider has an active portal login before assigning a deviance. Without an active login, the service provider may be unable to access the assigned work through the mobile portal.
  • Manage access when necessary: Use the Reset Password or Deactivate options under Portal Access whenever a service provider’s login credentials or access permissions need to be updated.
  • Attach supporting evidence: Encourage service providers to upload photographs and documents while the work is being performed. This information can assist with inspections, reviews, and final sign-off.
  • Monitor the provider workflow: Use the Activated, In Progress, and Awaiting Inspection columns to track the status of assigned jobs and monitor their progress at a glance.

Need to Know

  • Read-only status field: The State field on the deviance form is read-only and cannot be edited directly. The status changes through workflow actions such as approving the deviance, moving its card on the Kanban board, selecting Progress, or submitting the record for approval.
  • Provider portal visibility: Once a job has been submitted for final approval, it is removed from the service provider’s active work columns. Authorised management users can continue accessing the relevant records through the desktop back-end platform.
  • Final completion: A deviance should only be moved to Complete once all required inspections, approvals, and outstanding administrative requirements have been finalised.

Download PDF

How to Use the Deviance Logger: New Task Entry

18 steps 2 parts 10 November 2026

Watch Episode 3 on YouTube

This guide follows Episode 3 – Deviance Logger: New Task Entry from NodeOne Group. It explains how to create a new task using the mobile application, including entering a task title, setting a due date and time, selecting the task type and dependency, entering client details, and linking the task to a related deviance record.

The final section demonstrates how to edit an existing deviance log. All screens featured in this guide are taken from the mobile application.

Things You'll Need

  • Your NodeOne login credentials for the mobile application.
  • A clear task title, due date, and due time.
  • The task type and dependency classifications used by your organisation.
  • The client’s name and surname.
  • The deviance record to which the task relates.

Part 1: Create a New Task

1

Open Tasks from the Bottom Navigation Menu

Open the Deviance Logger Mobile application and tap Tasks in the bottom navigation menu. The Task List screen opens with All Tasks selected. Additional tabs allow you to view tasks scheduled for Today, This Week, and Later.

In the demonstration, the home screen displays Logs Data totals of New 7, High Risk 7, Completed 0, and Assigned 0.
2

Tap the Plus Button

On the Task List screen, tap the blue plus (+) button in the bottom-right corner to create a new task. This opens the New Task form, where you can enter the relevant task information.

In the demonstration, the Task List displays Thirsti Water Deal, several Deviance Task Test entries, and Meet with plant Manager to design a new process.
3

Open the New Task Form

The New Task form opens in the Task Info section. This form allows you to enter a task title, due date and time, task type, task dependency, client details, and the related deviance record. The SAVE button is located at the bottom of the form.

In the demonstration, all fields are initially empty, and the SAVE button is the only available action on the form.
4

Enter a Clear Task Title

Tap Title and enter a short, descriptive name for the task. Ensure that the title clearly describes the action that needs to be completed so that the assigned person can understand the task without having to open its details.

In the demonstration, the task title is entered as “demo task”.
5

Set the Due Date

Tap Due Date to open the date picker. Select the date by which the task must be completed, then tap OK to confirm your selection.

In the demonstration, Tuesday, 10 November 2026, is selected as the task’s due date.
6

Set the Due Time

Use the time picker to select the required hour and minute, then tap OK to confirm. The selected date and time are stored together in the Due Date field, providing a single deadline for completing the task.

In the demonstration, the time picker displays 10:27, while the Due Date field subsequently displays 2026-11-10 10:28 AM.
7

Select the Task Type

Tap Task Type and select the classification that best describes the task. The available options are based on the task types configured by your organisation.

In the demonstration, Task Type is set to Basic Task.
8

Set the Task Dependency

Tap Task Dependency and select the dependency that applies to the task. This field identifies any requirements or conditions that may affect when the task can be carried out, such as Money or Time.

In the demonstration, Task Dependency is set to Time.
9

Enter the Client Details

Tap Client Name and Client Surname to enter the relevant client’s details. Providing accurate client information helps ensure that the task is associated with the correct person or stakeholder.

In the demonstration, Client Name displays “client name”, while the Client Surname field is being completed.
10

Link the Related Deviance

Tap Related Deviance and select the deviance record associated with the task. Linking the task to an existing deviance record connects the required corrective action to the original incident, helping maintain a clear and traceable audit trail.

In the demonstration, Related Deviance is set to DEV000100.
11

Review the Task Information

Before saving, review all the information entered in the Task Info section. Check the task title, due date and time, task type, task dependency, client details, and related deviance record to ensure that everything is accurate. These details can also be accessed through the Task Info form if changes are required later.

In the demonstration, all relevant fields have been completed and are ready for submission.
12

Save the New Task

Once all required information has been entered and verified, tap SAVE. The button temporarily changes to SAVING… while the application processes the task. Once the task has been saved successfully, a green confirmation banner appears.

In the demonstration, a green confirmation banner displays “Task created”.

Part 2: Edit an Existing Deviance Log

13

Open Logs

To edit a previously recorded deviance, tap Logs in the bottom navigation menu. The Logs Info screen displays a list of deviance entries, including information such as severity, employee, impact, urgency, creator, and creation date. Locate the deviance record you wish to update.

In the demonstration, the Water Damage entry appears at the top of the All Logs list.
14

Open the Log Entry

Tap the relevant deviance entry to open its detailed view. The Log screen displays the attached photograph, description, and recorded information, including severity, impact, urgency, creator, creation date, and due date.

In the demonstration, the entry opens with the title WATER DAMAGE / LEAK, reference number DEV000100, and shows demo as the user who created it.
15

Tap Edit

Tap the Edit icon in the top-right corner of the screen. The application opens the Edit Log screen, allowing you to modify the existing information. Editable fields include priority, category, severity, type, impact, and description.

In the demonstration, the EDIT LOG heading appears above the Log Detail fields.
16

Change the Impact Level

Tap Impact and select the appropriate level from the available options. Update this field when the impact of the deviance has changed since it was initially recorded. Supporting documents, images, and notes can be accessed further down the form.

In the demonstration, Impact displays High, and the available options are Low, Medium, and High.
17

Update the Deviance Log

Once the necessary changes have been made, scroll to the bottom of the form and tap UPDATE. The button temporarily changes to UPDATING… while the application processes and saves the changes to the existing record.

In the demonstration, UPDATING… appears below the Notes section while the update is being processed.
18

Verify the Updated Log

After the changes have been saved, the deviance log reopens in view mode, displaying the updated information. Review the modified field to ensure that the correct value has been saved. Also verify that all other information remains accurate and unchanged.

In the demonstration, the saved log displays Impact as Low.

Helpful Tips

  • Set the due date and time together: Both values are saved in a single field, providing a clear deadline for completing the task.
  • Use descriptive task titles: Write titles that clearly communicate the required action. For example, “Replace damaged pipe in Unit 4” allows the assigned person to understand the task without opening its details.
  • Link tasks to the relevant deviance: Selecting the related deviance record helps maintain traceability between the task and the original incident, which is particularly useful during audits and reviews.
  • Update existing records when necessary: If information relating to a previously recorded deviance changes, open Logs, select the relevant entry, tap the Edit icon, modify the required fields, and tap UPDATE.

Need to Know

  • Mandatory information: All required fields must be completed before a new task can be saved successfully. If the task remains on the form after attempting to save, check for missing information or a possible submission error.
  • Confirmation messages: A successfully created task displays a confirmation banner. Always check that the application has confirmed the task was saved.
  • Editing existing records: Updating a deviance log modifies the stored information rather than creating a separate draft. Carefully review all changes before tapping UPDATE to ensure that the existing record remains accurate.

Download PDF

How to Use the Deviance Logger: New Log Entry

18 steps 6 parts 10 November 2026

Watch Episode 2 on YouTube

This guide follows Episode 2 – Deviance Logger: New Log Entry from NodeOne Group. It explains how to log a new deviance incident in the mobile application, including setting the priority, category, severity, type, and impact; entering a description; selecting a resolution date; and attaching supporting evidence.

The final sections demonstrate how to review a saved entry and add follow-up notes. All screens featured in this guide are taken from the mobile application.

Parts
6
Steps
18
Helpful Tips
4
Need to Know
2

Things You'll Need

  • Your NodeOne login credentials for the mobile application.
  • The priority, category, severity, type, and impact classifications used by your organisation.
  • A clear description of the incident, including what happened and the surrounding circumstances.
  • The date by which the deviance must be resolved.
  • A supporting photograph or document, if available.

Part 1: Open the New Log Form

1

Tap the Plus Button on the Home Screen

Open the Deviance Logger Mobile application and navigate to the home screen. The Logs Data totals are displayed at the top of the screen. Tap the blue plus (+) button in the bottom-right corner to create a new deviance log.

In the demonstration, the home screen displays New 1, High Risk 1, Completed 0, and Assigned 0.
2

Open the New Log Form

The New Log form opens in the Log Detail section. Complete the form in the following order: priority, category, severity, type, and impact, followed by the description, resolution date, supporting documents, and images. Fields marked with a red asterisk (*) are mandatory and must be completed before saving the entry.

In the demonstration, all fields are initially empty, and the form is ready to be completed.

Part 2: Classify the Deviance

3

Select the Priority Level

Tap Priority and select the appropriate level from the available options: Low, Medium, High, or Critical. The priority level indicates how urgently the deviance needs to be addressed.

In the demonstration, the available options are Low, Medium, High, and Critical, with Medium selected.
4

Select the Log Category

Tap Category and select the option that best describes the category of the incident or observation being recorded.

In the demonstration, Environmental is selected from the category list.
5

Select the Severity Level

Tap Severity and select the level that best reflects the seriousness of the deviance. The available severity levels range from Not Severe to Critical.

In the demonstration, the severity options range from Not Severe to Critical, with Minor selected.
6

Select the Deviance Type

Tap Type and select the option that best describes the specific nature of the deviance. The available options are based on the deviance types configured by your organisation.

In the demonstration, Water Damage / Leak is selected.
7

Select the Impact Level

Tap Impact and select the level that best reflects the extent to which the deviance affects operations, people, or outcomes.

In the demonstration, Low is selected from the impact list.

Part 3: Describe the Deviance

8

Enter the Description

Tap Description and enter a clear and detailed account of the deviance. Include relevant background information, what was observed, and the circumstances surrounding the incident. Ensure that the description provides sufficient information for someone who was not present to understand what happened.

In the demonstration, the description reads "this is a demo description".
9

Set the Resolution Date

Tap Resolution Date to open the calendar. Select the date by which the deviance is expected to be resolved. This date serves as the target deadline for resolving the logged incident.

In the demonstration, Wednesday, 9 September 2026, is selected, and the field displays 2026-09-09.

Part 4: Attach Evidence and Save

10

Attach an Image

Tap Upload Images to attach a photograph to the deviance log. You can select an existing image from your device's gallery or grant camera access to capture a new photograph. Visual evidence supports the recorded information and assists with the review process.

In the demonstration, one image is successfully attached and displayed under Images.
11

Attach a Document (Optional)

Tap Upload Documents to attach a supporting file from your device. This could include a report or any other relevant document that provides additional information about the deviance. Attaching documents is optional.

In the demonstration, a document named Deviance_log_report.pdf is successfully attached and displayed under Documents.
12

Save the Deviance Log

Once all mandatory fields have been completed and any supporting documents or images have been attached, tap SAVE. The application displays a "Saving deviance details" message while processing the entry. Once the entry has been saved successfully, the application returns to the home screen.

In the demonstration, a confirmation banner displays "Deviance created", and the home screen updates to show New 2 and High Risk 2.

Part 5: Review the Saved Entry

13

Open Logs from the Bottom Navigation Menu

Tap Logs in the bottom navigation menu to access the Logs Overview screen. Locate the newly created deviance entry in the list of recorded incidents.

In the demonstration, the Water Damage / Leak entry, identified as DEV000100, appears in the list.
14

Open the New Log Entry

Tap the newly created entry to open its detailed view. The screen displays the attached photograph, description, and other information recorded when the deviance was logged.

In the demonstration, the entry opens with the title WATER DAMAGE / LEAK and the reference number DEV000100.
15

Review the Log Details

Scroll down to review the recorded information, including the status, classification, description, and any attached supporting media. The severity, impact, urgency, creator, creation date, and due date are displayed below the photograph. Review these details to ensure that the information has been recorded correctly.

In the demonstration, Severity is Minor, Impact is Low, Urgency is Medium, and the due date is 2026-09-09.

Part 6: Add a Note

16

Tap Add Note

In the top bar of the deviance log, tap ADD NOTE. A note entry field opens, allowing you to record additional information relating to the logged incident. Notes can be used to document follow-up observations, actions taken, or communications received.

In the demonstration, the NEW NOTE TITLE field opens over the deviance log.
17

Enter the Note

Tap the New Note Title field and enter the relevant information. Include any updates that may assist with resolving the deviance, such as actions taken, additional observations, or feedback received from team members.

In the demonstration, the note reads "this is a demo note".
18

Save the Note

Tap Save to attach the note to the deviance log. Once saved, the note appears in the Notes section, along with the name of the user who created it and the date it was recorded. This allows authorised users to review the latest updates and track progress relating to the deviance.

In the demonstration, the Notes section displays "this is a demo note", created by demo and dated 2026-09-07.

Helpful Tips

  • Follow the form sequence: Complete the priority, category, severity, type, and impact fields before entering the description and additional details.
  • Provide a clear description: Write a detailed account that allows someone who was not present to understand the incident. Include relevant background information, observations, and circumstances.
  • Attach supporting evidence: Whenever possible, include photographs or documents that support the recorded information. Visual evidence can assist with understanding and reviewing the incident.
  • Keep the log updated: Use the Add Note function to record follow-up observations, actions taken, and communications received after the initial entry has been saved.

Need to Know

  • Mandatory fields: All fields marked with a red asterisk (*) must be completed before the deviance log can be saved.
  • Supporting evidence: Images and documents can provide valuable additional context when reviewing logged deviance incidents.
  • Follow-up notes: Notes remain attached to the deviance log and can be viewed by authorised users. Use this function to maintain an accurate record of developments and actions taken after the initial entry was created.