Getting Started

Introduction

Everything you need to install, launch, and start working in FidentraOS.

This manual explains how to install and get started with FidentraOS, based on the official setup package (FidentraOS-Setup, version 0.1.0, build 14).

This manual is being built up module by module from real screenshots. My Place (Dashboard), Asset, Log Book, Load Record, Job Request and Files are documented — the rest of the sidebar fills in as screenshots are supplied.
Getting Started

System Requirements

What the target machine needs before installing.

The setup package is a Windows installer (32-bit PE executable, built with Inno Setup 6). At minimum, the target machine should meet:

Confirm exact minimum RAM, disk space, and supported OS versions against FidentraOS's official specification before distributing this manual.
Getting Started

Installing FidentraOS

FidentraOS uses a standard Windows installation wizard.

  1. Locate the downloaded file, FidentraOS-Setup-0.1.0(14).exe, and double-click it to launch the installer.
  2. If prompted by Windows User Account Control, select "Yes" to allow the installer to run.
  3. On the Welcome screen, review the introductory text and click "Next" to continue.
  4. Read the License Agreement. Select "I accept the agreement", then click "Next".
  5. Choose the destination folder where FidentraOS will be installed, or accept the default location, then click "Next".
  6. Choose the Start Menu folder for shortcuts, then click "Next".
  7. Select any additional tasks, such as creating a desktop icon, then click "Next".
  8. Review the installation summary and click "Install" to begin copying files.
  9. Wait for the progress bar to complete. This may take a few minutes depending on your system.
  10. On the final screen, click "Finish" to exit the installer. Leave "Launch FidentraOS" checked if you want to open the application immediately.
Exact wording of each screen may vary slightly depending on how the installer was configured. Confirm against the live installer and adjust step text if needed.
Getting Started

First Launch

What to expect the first time FidentraOS opens.

The first time FidentraOS starts, you may be asked to complete initial setup steps such as account sign-in, license activation, or configuration of basic preferences.

Placeholder — describe the actual first-run experience (login screen, license key entry, initial configuration wizard, etc.) once available.
Module 1

Dashboard (My Place)

The landing screen after signing in — a company-wide, at-a-glance summary.

Module Overview

The My Place dashboard provides a quick overview of important system information, including Assets, Log Books, Job Orders, Users, Recent Activity, and Synchronization Status — enabling users to monitor daily operations efficiently from a single screen.

Objective

To provide users with a centralized view of key operational information, enabling them to monitor system activity, track outstanding tasks, and access important data quickly and efficiently.

Purpose

To simplify daily operations by presenting essential system information in a single interface, helping users improve productivity, make informed decisions, and stay on top of maintenance activities.

Basic Workflow

  1. Start
  2. User logs in
  3. My Place dashboard opens automatically
  4. View summary cards — Asset, Log Books, Job Order, Users
  5. Check Recent Activity
  6. Check Sync Status and items pending upload
  7. Check Alerts & Notifications
  8. Navigate to another module if required
  9. End

Screen Walkthrough

My Place dashboard with numbered callouts
Figure 1 — My Place dashboard, numbered callouts explained below.
#ElementDescription
1Menu iconToggles/collapses the left navigation panel.
2My Place (active)Highlights the page currently open in the navigation panel.
3Page titleShows the name of the current screen ("My Place").
4Sync statusShows whether the app is synced ("Synced just now"), with a manual refresh icon beside it.
5NotificationsBell icon for system notifications.
6User accountSigned-in user's name and role, with a drop-down for account options.
7Greeting & date/timePersonalised greeting with the current day, date, and time.
8Date rangeSelects the period the dashboard's figures are calculated over.
9ExportExports the dashboard's data for the selected period.
10Asset cardTotal active assets.
11Log Books cardLog books created in the current period.
12Job Order cardOpen job orders.
13Users cardActive users.
14Recent ActivityFeed of recent actions, with a link to view the full history.
15Sync Status panelConfirms all changes are synced, with a details button.
16Items pending uploadCount of items still queued to sync.
17Alerts & NotificationsOutstanding items needing attention (e.g. a draft log book).
18Account / Log OutSigned-in user shown at the bottom of the sidebar, with Log Out below it.
19Copyright footerPublisher and copyright notice.

Dashboard Components

Asset Card

Displays the total number of active assets available in the system.

Log Books Card

Displays the total log book entries created in the current period.

Job Order Card

Shows the number of open job orders requiring attention.

Users Card

Shows the total number of active users registered in the application.

Recent Activity

Displays the latest actions performed in the system, such as log book entries.

Sync Status

Indicates whether application data has been successfully synchronized with the server, and how many items are still pending upload.

Alerts & Notifications

Lists items that need attention, such as an unfinished log book draft.

Export

Lets users export the dashboard's data, for the selected date range, for reporting and record-keeping.

Dashboard Navigation

Login → My Place → Select Required Module → Asset / Log Book / Job Order / Job Request / Load Record / Fatigue / Maintenance Policy / Files / Learning / User / Setting → View Information → Perform Required Action

Dashboard Features

Rules & Regulations

Benefits & Advantages

Quick overview Saves time Easy to navigate Faster decisions Real-time updates Quick module access
This module (Dashboard / My Place) is fully documented from the supplied screenshots. The remaining modules can each be added in this same format as their screenshots are provided.
Module 1

Dashboard — KPI & Troubleshooting

Key figures shown on My Place, and what to do if something looks wrong.

Dashboard KPI Summary

KPIDescriptionPurpose
AssetTotal active assets in the system.Monitor asset availability.
Log BooksLog books created in the current period.Track log book activity.
Job OrderOpen job orders.Track outstanding maintenance tasks.
UsersActive users.Monitor user activity.
Recent ActivityLatest actions performed in the system.Track recent updates.
Sync StatusWhether data is synchronized, and items pending upload.Ensure data is up to date.
Alerts & NotificationsItems needing attention (e.g. drafts).Prompt timely follow-up.

Error Handling and Troubleshooting

IssueSolution
Login failedCheck username and password.
Dashboard figures look out of dateWait for auto-sync, or use the manual refresh icon next to the sync status.
Dashboard not loadingRefresh the application.
Export failedCheck your internet connection and try again.
Items stuck pending uploadConfirm an internet connection is available, then allow sync to complete.
Module 2

Asset — Groups & Asset Creation

Create the asset-group hierarchy, then create assets under the right group.

ModuleAsset
Main ScreenAsset Register
Primary PurposeCreate, organise, view and maintain fleet asset records.
Training OutcomeUser can create an asset group, create an asset, open Asset Details and understand each related tab.

Training Objective

Overall Asset Process Flow

  1. Create Asset Group — define the parent/child grouping.
  2. Create Asset — select group and enter asset details.
  3. Asset Register — verify the new asset in Tree View / list.
  4. Open Asset Details — select View to open the asset.
  5. Review Related Tabs — checklist, jobs, logbooks, requests, documents, readings and maintenance.

Step 1 — Create an Asset Group

Asset Groups organise assets into a logical hierarchy. The Asset Register uses Tree View to display these groups and their child groups, making it easier to classify and locate assets.

  1. Select Asset → Asset Register.
  2. In the Asset Groups panel, select Add Group.
  3. Enter the Group Name.
  4. Enter a short Description, if required.
  5. Select Create.
  6. The new group becomes available in the Asset Groups Tree View.
Asset Group creation with numbered callouts
Asset Group — Create: Name, Description and Create button.

Step 2 — Create an Asset

After the required group is available, create the asset under the appropriate group. The New Asset form captures the asset's identity, registration, technical information, vehicle configuration and business information.

  1. Select Add Asset from the Asset Register.
  2. Select the Asset Group.
  3. Enter Asset Name and Asset No. as required.
  4. Enter registration/fleet information and vehicle identification details.
  5. Enter make, model, year and engine number where applicable.
  6. Enter VIN/Chassis Number, GCM, GVM, odometer and tare weight.
  7. Select Vehicle Type and then the relevant Axle Group.
  8. Set Status and complete description, department, customer and contractor where applicable.
  9. Select Create to save the asset.
New Asset form with numbered callouts
Asset — Create: identity, vehicle/technical data, status and business details.
The example counts, names and statuses shown in screenshots represent the application state at the time the screenshots were captured. Use actual customer/company data for live training where appropriate.
Module 2

Asset — Asset Register & Tree View

Find, filter and open the assets that have been created.

Step 3 — Asset Register and Tree View

Once the asset is created, it is available in the Asset Register. The left side is the Asset Groups Tree View, while the right side contains the asset list. The user can expand groups to see child classifications and use search/filter controls to locate a specific asset.

Asset Register showing Tree View and asset list
Asset Register — Tree View (left) and asset list with search, filters and actions (right).
Module 2

Asset Details — Overview

The main summary page for a selected asset.

Step 4 — Asset Details: Overview

Selecting View opens Asset Details. The Overview tab is the main summary page. It combines general information about the asset with its vehicle configuration.

Asset Details Overview tab with numbered callouts
Asset Details → Overview: general information and vehicle configuration.
Module 2

Asset Details — Related Tabs

Where each tab's information comes from, and what it shows for the asset.

The Asset Details page acts as a consolidated view for the selected asset. Related information is shown in separate tabs. The records are generated or maintained in their respective modules and, when linked to the selected asset, become visible here.

Asset Details TabSource / OriginWhat appears for the asset
OverviewAsset moduleCore asset information and vehicle configuration.
ChecklistSettings → Checklist templatesThe checklist configured in Settings can be associated with the asset and displayed here.
Job OrderJob Order moduleJob orders created/managed for the asset are reflected here.
Logbook HistoryLog Book moduleLog books recorded against the asset are reflected here.
Job RequestJob Request moduleRequests created for the asset are reflected here.
DocumentsAsset / Documents areaDocuments uploaded/attached to the asset are listed here.
ReadingsAsset ReadingsReadings created for the selected asset are shown here.
Maintenance PolicyMaintenance Policy moduleA maintenance policy assigned to the asset is available here for asset-specific maintenance tracking.

Checklist — Asset Safety Checks

The Checklist tab shows the checklist assigned to the asset. In the supplied screen, both Pre-Start and Post-Trip checklists are displayed. Checklist templates are configured in Settings and the relevant checklist can then be associated with the asset.

Asset Safety Checks screen with numbered callouts
Asset Details → Checklist: Pre-Start and Post-Trip checks.

Job Order — Asset Work Orders

The Job Order tab provides the asset-level history of work orders. Status tabs allow the user to focus on specific stages. Job orders originate in the Job Order module and are linked to the relevant asset.

Asset Work Orders screen with numbered callouts
Asset Details → Job Order: status tabs and work-order history.

Logbook History — Asset Log Books

The Logbook History tab shows log book records associated with the selected asset. Log books are created through the Log Book module; the asset's history provides a quick reference to submitted records.

Asset Log Books screen with numbered callouts
Asset Details → Logbook History: date/time and status.

Job Request — Asset Requests

The Job Request tab shows requests associated with the asset. A request can be Open, Approved or Declined. Requests are created in the Job Request module and linked to the selected asset.

Asset Requests screen with numbered callouts
Asset Details → Job Request: Open, Approved and Declined states.

Documents — Asset Documents

The Documents tab provides asset-specific document storage and retrieval. When a document is uploaded and associated with the asset, it becomes visible in this list.

Asset Documents screen with numbered callouts
Asset Details → Documents: name, type, metadata, size and actions.

Readings — Asset Readings

The Readings tab records measurements or readings against the selected asset. The + button is used to create a new reading, and View Timeline provides the historical sequence of readings.

Asset Readings screen with numbered callouts
Asset Details → Readings: add a reading and view the timeline.

Maintenance Policy — Asset-Level Assignment

Maintenance Policy is a separate module used to define maintenance rules or service intervals. When a maintenance policy is assigned to an asset, the applicable policy information becomes available in the asset's Maintenance Policy tab. This connects the asset to its maintenance schedule and supports tracking of service requirements.

Placeholder — a screenshot of the Maintenance Policy tab was not supplied with this training set.
Module 2

Asset — Relationships & Roles

How other modules connect to the asset, and who is typically responsible for what.

Module-to-Asset Relationship Diagram

The key concept for training: the Asset record is the central reference, while related operational information comes from the corresponding module or configuration area.

Settings
→
Checklist Template
→
Asset Details
Job Order
→
Job Order for Asset
→
Asset Details
Log Book
→
Log Book for Asset
→
Asset Details
Job Request
→
Request for Asset
→
Asset Details
Asset / Documents
→
Document attached to Asset
→
Asset Details
Asset Readings
→
Reading for Asset
→
Asset Details
Maintenance Policy
→
Policy assigned to Asset
→
Asset Details

User / Person Responsibility Flow

For training, the workflow can be explained by role. The exact permissions depend on the user's configured access.

RoleTypical Responsibility
Company Admin / Asset AdminCreates groups, creates assets, maintains master/default data and controls access.
Operations / Fleet UserReviews asset status, job requests, job orders, log books and operational history.
Driver / Field UserCreates or completes log book and checklist-related activities against the assigned asset.
Maintenance UserReviews readings, maintenance policy, job requests and job orders for the asset.
Module 2

Asset — Training & Checklist

A recommended demonstration sequence, a completion checklist, and important notes.

Trainer Demonstration — Recommended Sequence

  1. Open Asset → Asset Register and explain the Asset Groups Tree View.
  2. Select Add Group and demonstrate entering Name and Description.
  3. Create the group and show where it appears in Tree View.
  4. Select Add Asset and explain each major field in the New Asset form.
  5. Create the asset and return to the Asset Register.
  6. Use the asset list to confirm Asset No., Asset Name, Group, Registration and Status.
  7. Select View and explain the Asset Details → Overview page.
  8. Move through each tab and explain where the related information originates.
  9. Demonstrate the checklist relationship with Settings.
  10. Demonstrate how Job Orders, Log Books and Job Requests created for the asset become visible under Asset Details.
  11. Upload/attach a document to the asset and show it under Documents.
  12. Create a reading and show it under Readings.
  13. Assign a Maintenance Policy and show the asset-specific policy under Maintenance Policy.
  14. Finish by explaining the full Asset relationship flow to the trainee.

Training Completion Checklist

No.Training RequirementStatus
1Can create an Asset Group.☐ Not Checked
2Understands Tree View and parent/child asset-group structure.☐ Not Checked
3Can create an Asset under the correct group.☐ Not Checked
4Can explain the main New Asset fields.☐ Not Checked
5Can locate the asset in the Asset Register.☐ Not Checked
6Can use View and Edit actions appropriately.☐ Not Checked
7Can explain the Overview tab.☐ Not Checked
8Can explain the Checklist tab and its Settings relationship.☐ Not Checked
9Can explain Job Order and its source module.☐ Not Checked
10Can explain Logbook History and its source module.☐ Not Checked
11Can explain Job Request and its source module.☐ Not Checked
12Can explain Documents and asset-specific attachments.☐ Not Checked
13Can create/review Readings for the selected asset.☐ Not Checked
14Understands Maintenance Policy assignment to an asset.☐ Not Checked

Important Training Notes

Module 3 · Log Book · Introduction

Log Book — Overview & Workflow

Create a driver's daily heavy-vehicle log book, submit it for review, and turn an approved one into a Load.

ModuleLog Book
Main ScreenLog Book list (left menu → Log Book)
Primary PurposeCreate and manage a driver's daily heavy-vehicle log book — from pre-trip vehicle checks through to post-trip checks, fatigue self-assessment and driver certification.
CoversNavigating the Log Book list, creating a new Log Book, completing all Section, submission, review (approve / reject), and creating a Load from an approved Log Book.

Overview

The Log Book module in FIDENTRA OS is used to create and manage a driver's daily heavy-vehicle log book — from pre-trip vehicle checks through to post-trip checks, fatigue self-assessment and driver certification. Once submitted, an office administrator reviews the Log Book and either Approves or Rejects it. An Approved Log Book can then be used to create a Load record for that trip.

This guide walks through the module in the same order a user works through it: opening the Log Book list, creating a new Log Book, completing each of its Section, submitting it, and finally reviewing / approving it.

Tip — every screenshot in the Log Book pages can be enlarged. Click a screenshot to open it full size; use the arrow keys to move between screenshots and Esc to close.

Where to find it

The Log Book module is opened from the left-hand navigation menu:

Overall Workflow

The diagram below summarises the complete Log Book lifecycle, from creation to submission, review, and (for approved Log Books) creating a Load. Click any step to jump to its page.

If approved
If rejected
↩ Returns to step 10 — back to the Submitted tab for another review

What is in this module guide

GroupPageWhat it covers
IntroductionMain List ScreenThe landing screen of the module: status tabs, filters, search and the table of every Log Book.
IntroductionCreating a New Log BookPick a vehicle group and vehicle, then start the Log Book.
Section1. Driver / VehicleWho is driving, for which customer, and which vehicle / trailer combination is being used.
Section2. Shift & BreaksThe driver's working hours and breaks, checked against fatigue-management rules.
Section3. Fitness for WorkA self-assessment declaration the driver completes before starting duty.
Section4. Pre-Start CheckA vehicle safety inspection completed before starting the trip.
Section5. Fault ReportFormally log any vehicle or equipment fault found during the trip.
Section6. Post-Trip CheckMirrors the Pre-Start Check, completed once the trip is finished.
Section7. CertificationThe driver certifies that everything entered is accurate, and signs on screen.
Review & approvalDraft Preview & DetailsCheck a Draft before submitting, and open the full detail view of any Log Book.
Review & approvalSubmit, Approve & RejectWhat an admin can do with a Submitted Log Book, and what happens to Approved and Rejected ones.
Review & approvalCreate a Load & Asset StorageUse an Approved Log Book to start a Load record, and find every Log Book stored against a vehicle.
ReferenceNavigation Quick ReferenceHow to get to each screen and action in the module.
Module 3 · Log Book · Introduction

Log Book — Main List Screen

The landing screen of the module: status tabs, filters, search and the table of every Log Book.

This is the landing screen of the module. It lists every Log Book created in the system and lets you filter, search, and jump into creating a new one.

Log Book main list (status tabs, filters and table)
Figure LB-2 — Log Book main list (status tabs, filters and table)

Status Tabs

Every Log Book sits in exactly one of four tabs, shown as a count next to the tab name:

TabMeaning
AllEvery Log Book regardless of status.
DraftLog Book created but not yet submitted — can still be edited freely.
SubmittedSent for review; awaiting Approve / Reject by an admin.
ApprovedReviewed and accepted; read-only, and a Load can be created from it.
RejectedSent back to the driver; must be corrected and resubmitted.

Filters and Search Bar

Above the table is a row of filters used to narrow down the list:

ControlWhat it does
Search boxSearch by Log Book No., Asset or driver.
All AssetFilter to a single vehicle / asset (dropdown lists every registered asset).
All DriversFilter to a single driver.
All CustomersFilter to a single customer / client company.
Any dateOpens a calendar to filter by a date or date range.
Flagged onlyShow only Log Books with a Red Flag (e.g. a fatigue rule breach).
ExportExport the current filtered list.
Create Log BookBlue button — starts a new Log Book (see Creating a New Log Book).
"All Asset" filter dropdown
Figure LB-3 — "All Asset" filter dropdown
"All Drivers" filter dropdown
Figure LB-4 — "All Drivers" filter dropdown
"All Customers" filter dropdown
Figure LB-5 — "All Customers" filter dropdown
Date range picker ("Any date")
Figure LB-6 — Date range picker ("Any date")

Table Columns

ColumnWhat it shows
Log Book No.Unique reference, e.g. LB-00022. A red flag icon appears next to it if a fatigue rule was breached.
AssetVehicle / asset ID and description.
DateDate and time the Log Book was created / last updated.
StatusDraft / Submitted / Approved / Rejected, plus a Red Flag badge if applicable.
Created ByThe user who created the Log Book.
ActionsView (eye icon), Edit (pencil), and, for Submitted rows, Approve (green tick) / Reject (red cross).
Module 3 · Log Book · Introduction

Log Book — Creating a New Log Book

Pick a vehicle group and vehicle, then start the Log Book.

1

Click the blue “Create Log Book” button on the main list screen.

New Log Book screen (before a vehicle is selected)
Figure LB-7 — New Log Book screen (before a vehicle is selected)
2

Click the “Vehicle Group” dropdown and pick the group the vehicle belongs to (e.g. Kenworth K200, Dog Trailer, Mack, Low Loader, etc.).

Vehicle Group dropdown list
Figure LB-8 — Vehicle Group dropdown list
3

Select the specific “Vehicle” from that group. The “Start Log Book” button becomes active once both fields are set.

Vehicle selected; ready to start
Figure LB-9 — Vehicle selected; ready to start
4

Click “Start Log Book”. The Log Book opens on the first of seven tabs: Driver / Vehicle.

Note — the seven tabs across the top (Driver / Vehicle, Shift & Breaks, Fitness for Work, Pre-Start Check, Fault Report, Post-Trip Check, Certification) can be completed in any order. A blue tick appears on each tab once it is filled in.
Module 3 · Log Book · Section

Section 1 — Driver / Vehicle

Who is driving, for which customer, and which vehicle / trailer combination is being used.

Captures who is driving, for which customer, and which vehicle / trailer combination is being used.

Driver / Vehicle tab, completed
Figure LB-10 — Driver / Vehicle tab, completed

Driver & Trip Details

FieldWhat to enter
Driver NameThe logged-in / assigned driver.
Company NameThe transport company operating the vehicle.
Customer NameThe customer the trip is being run for.
Product TypeWhat is being carried, e.g. Ore.
Start Location / End LocationTrip origin and destination.
Date / Day of WeekTrip date; day of week is auto calculated.
Fuel Added / AdBlue AddedOptional fuel (Diesel – L) and AdBlue (L) top-up quantities.

Vehicle & Trailer Configuration

FieldWhat to enter
Asset IDThe selected vehicle and its registration.
Truck RegoRegistration plate.
Start KM / Finish KMOdometer readings at the start (and later, end) of the trip.
Trailers / Dollies AttachedAdd a trailer or dolly (“Add Trailer”) or select a saved combination (“Use Combination”).

Click “Next: Shift & Breaks” to continue.

Module 3 · Log Book · Section

Section 2 — Shift & Breaks

The driver's working hours and breaks, checked against fatigue-management rules.

Records the driver's working hours and breaks for fatigue-management compliance.

Shift & Breaks tab, no time blocks logged yet
Figure LB-11 — Shift & Breaks tab, no time blocks logged yet

Shift Configuration

FieldWhat to enter
Shift TypeDay Shift or Night Shift.
Off-Road TripTick if the shift did not use public roads (e.g. stayed within a farm or yard).
Shift Start Time / Shift Finish TimeEstimated or actual shift boundaries.

Adding Time Blocks

1

Click “+ Add Time Block Segment”.

Time segment type list: Driving / Break from Driving / Non-Work Time
Figure LB-12 — Time segment type list: Driving / Break from Driving / Non-Work Time
2

Choose the Type, set Start and Finish times, add an optional note, then click “Add”.

Add Time Segment dialog, filled in
Figure LB-13 — Add Time Segment dialog, filled in

Repeat this for every driving, break, and non-work period in the shift. Each entry appears in the “Logged Time Blocks” table on the right and on the 24-hour visual timeline (Driving = blue, Break = orange, Non-Work = grey).

Shift & Breaks tab with logged segments and a fatigue warning
Figure LB-14 — Shift & Breaks tab with logged segments and a fatigue warning

Example: logged time blocks in the screenshot above

ActivityStartFinishDuration
Driving06:0007:001 hr 00 mins
Break from Driving07:0007:200 hrs 20 mins
Driving07:2012:305 hrs 10 mins

Shift Summary & Fatigue Rule Warning

As time blocks are added, FIDENTRA OS automatically calculates:

If the entries breach a fatigue rule (e.g. insufficient break time, insufficient rest in a 72-hour or 14-day window), a red “Fatigue Rule Warning” box lists exactly which rule(s) are not yet met. This is informational while editing, but a breach at submission time is what causes the Red Flag shown on the Log Book list.

Shift Summary Metrics — example
  • Total Shift Duration: 0 hrs 00 mins (Shift Start and Finish are both 06:00 in this example)
  • Logged Work / Driving: 6 hrs 10 mins
  • Logged Rest Breaks: 0 hrs 20 mins
Fatigue Rule Warning — example
  • Breaks From Driving: 0 min of breaks so far, below the required 30 min in the last 5h of work.
  • Non-Work Total (72h): only 60 min, below the required 1620 min.
  • Long-Rest Count (72h): only 0 qualifying rest(s), below the required 3 qualifying rest(s).
  • 14-Day Work & Rest Cycle — Rest Count: only 0 24h rest(s), below the required 2 24h rest(s).

Click “Next: Fitness for Work” to continue.

Module 3 · Log Book · Section

Section 3 — Fitness for Work

A self-assessment declaration the driver completes before starting duty.

A self-assessment declaration the driver completes before starting duty.

Fitness for Work self-assessment questions
Figure LB-15 — Fitness for Work self-assessment questions

The driver answers Yes / No to nine compliance questions, covering rest hours, days off, fatigue, medication, alcohol/drugs, and correct sleeper-berth use. A progress indicator (e.g. “Answered 9 of 9”) confirms when the section is complete.

The nine questions

“Please answer all questions honestly before commencing duty.”

  1. Have you had at least 7 continuous hours of stationary rest in the last 24 hours?
  2. Have you had at least 24 hours off-duty in the last 7 days?
  3. Have you had at least 2 nights of stationary rest in the last 14 days?
  4. In the last 12 days, have you complied with all required rest conditions?
  5. Are you free from fatigue and fit to commence this shift?
  6. Have you had adequate sleep in the last 48 hours?
  7. Are you taking any medication that may affect your ability to drive safely?
  8. Have you consumed any alcohol or a drug that may impair your driving in the last 24 hours?
  9. Have you used a sleeper berth, and if so, was it used correctly as required?

Click “Next: Pre-Start Check” to continue.

Module 3 · Log Book · Section

Section 4 — Pre-Start Check

A vehicle safety inspection completed before starting the trip.

A vehicle safety inspection completed before starting the trip.

Pre-Start Check checklist
Figure LB-16 — Pre-Start Check checklist
ElementWhat it does
Checklist itemse.g. engine oil, coolant, tyre condition, brake system, lights and indicators — set as Pass / Fail or answered as free text depending on the item.
What is wrong?Appears when an item is marked Fail — free text description of the defect.
Photo uploadAttach a photo as evidence for an item (green check confirms it uploaded).
Add to Fault ReportTick to automatically carry a failed item into the Fault Report tab.
All Items CheckedProgress badge (e.g. 5 / 5) confirming every item has been answered.
Pass allShortcut to mark every remaining item as Pass.

Checklist items in the screenshot above

  1. Check engine oil level
  2. Check coolant level
  3. Check tyre condition
  4. Check brake system
  5. Check lights and indicators

See also: Asset Details — Related Tabs shows the Pre-Start and Post-Trip checks for an asset.

Click “Next: Fault Report” to continue.

Module 3 · Log Book · Section

Section 5 — Fault Report

Formally log any vehicle or equipment fault found during the trip.

Used to formally log any vehicle or equipment fault found during the trip.

Fault Report tab
Figure LB-17 — Fault Report tab
FieldWhat to enter
DescriptionWhat is wrong with the vehicle / equipment.
Prioritye.g. “B — Not Serious”, used to set urgency of repair.
StatusOpen / In Progress / Closed.
Repair ByTarget timeframe for the repair, e.g. 1 Week.
Maintenance NotesFree text notes for the maintenance team.
+ Add Fault EntryAdd another fault if more than one was found.
Delete FaultRemove a fault entry.
Description, Priority, Status and Repair By are marked as required (*) on the screen, and Description and Maintenance Notes each accept up to 500 characters.

If this section is empty, no faults are recorded and it can be skipped.

Click “Next: Post-Trip Check” to continue.

Module 3 · Log Book · Section

Section 6 — Post-Trip Check

Mirrors the Pre-Start Check, completed once the trip is finished.

Mirrors the Pre-Start Check but completed once the trip is finished.

Post-Trip Check checklist, all items checked
Figure LB-18 — Post-Trip Check checklist, all items checked
ElementWhat it does
Check vehicle for damage / fuel levelPass / Fail toggle.
Check tyre condition / warning lightsFree-text confirmation.
Record any faultsAttach a photo / file as supporting evidence.
All Items CheckedProgress badge, e.g. 5 / 5.

Checklist items in the screenshot above

  1. Check vehicle for damage
  2. Check fuel level
  3. Check tyre condition
  4. Check warning lights
  5. Record any faults

Click “Next: Certification” to continue.

Module 3 · Log Book · Section

Section 7 — Certification

The driver certifies that everything entered is accurate, and signs on screen.

The final step, where the driver certifies that everything entered is accurate.

Certification tab, signature captured
Figure LB-19 — Certification tab, signature captured
ElementWhat it does
Declaration statementConfirms the Log Book information is true, accurate and complies with Australian heavy-vehicle fatigue management requirements.
“I confirm the above statement...” checkboxMust be ticked to proceed.
Driver SignatureCaptured on-screen; “Re-sign” clears it and lets the driver sign again.
CompleteFinishes the Log Book. It remains in Draft until it is submitted from the list screen.

Declaration wording on screen

“I declare that the information recorded in this driver log book is true and accurate and complies with applicable Australian heavy vehicle fatigue management requirements.”

Please review and confirm — by confirming below, you are declaring that all entries are accurate and complete.

☑ I confirm the above statement is true and correct *

Module 3 · Log Book · Review & approval

Log Book — Draft Preview & Detail View

Check a Draft before submitting, and open the full detail view of any Log Book.

Reviewing a Draft Before Submitting

Opening a Draft Log Book from the list (eye icon) shows a read-only preview of everything entered so far, including the shift summary, Fitness for Work answers, and certification status.

Draft preview: summary, Fitness for Work answers, and Certification status
Figure LB-20 — Draft preview: summary, Fitness for Work answers, and Certification status

If the Certification step has not been completed, the preview shows “Declaration not confirmed / Not signed” and offers a “Continue editing draft” button to go back in and finish it.

Viewing Log Book Details

Clicking the eye (View) icon on any row opens the full detail view of that Log Book — useful for admins reviewing a Submitted entry, or for anyone checking a Log Book after the fact.

Log Book detail view header, showing a Fatigue Rule Breach and Red Flag
Figure LB-21 — Log Book detail view header, showing a Fatigue Rule Breach and Red Flag

The header repeats the Log Book No., status badges (e.g. Red Flag, Draft / Submitted / Approved / Rejected), and key trip facts: Asset, Vehicle, Date, Inspection type, fit to drive, and Work Time. Below it, the Checklist and Driver / Vehicle details are shown read-only.

Shift & Breaks detail, including the 24-hour timeline
Figure LB-22 — Shift & Breaks detail, including the 24-hour timeline

Scrolling down shows the Shift & Breaks summary (Start, Finish, Total Work Time) and the same 24-hour timeline used during data entry, plus a breakdown of every logged segment.

Module 3 · Log Book · Review & approval

Log Book — Submitting and Reviewing

What an admin can do with a Submitted Log Book, and what happens to Approved and Rejected ones.

Once Certification is complete, the Log Book is submitted for review and moves to the Submitted tab.

Submitted tab: rows show green Approve and red Reject action icons
Figure LB-23 — Submitted tab: rows show green Approve and red Reject action icons

From the Submitted tab, an admin can:

Approved Log Books

Approved tab: one Approved Log Book, with a Load-creation icon in Actions
Figure LB-24 — Approved tab: one Approved Log Book, with a Load-creation icon in Actions
Approved Log Book detail view, with Print, Download and "Create Load Plan Sheet"
Figure LB-25 — Approved Log Book detail view, with Print, Download and "Create Load Plan Sheet"

An Approved Log Book becomes read-only. From here it can be Printed, Downloaded, or used to “Create Load Plan Sheet” (see Creating a Load).

Rejected Log Books

Rejected tab: the entry keeps its Red Flag
Figure LB-26 — Rejected tab: the entry keeps its Red Flag
Rejected Log Book detail, with "Edit and resubmit"
Figure LB-27 — Rejected Log Book detail, with "Edit and resubmit"

A Rejected Log Book can be reopened with “Edit and resubmit”. The driver corrects the flagged information, re-confirms the declaration, re-signs, and completes Certification again — after which it returns to the Submitted tab for another review.

Module 3 · Log Book · Review & approval

Log Book — Creating a Load & Asset Storage

Use an Approved Log Book to start a Load record, and find every Log Book stored against a vehicle.

Creating a Load from an Approved Log Book

Once a Log Book is Approved, the truck icon in its Actions column (see Figure LB-24 on Submit, Approve & Reject) opens the Load Record module, pre-linked to that Log Book's vehicle and trip.

Load Details screen (Load Record module), Step 1 of 4
Figure LB-28 — Load Details screen (Load Record module), Step 1 of 4

The Load Record is completed over four steps:

  1. Load Details — load date / type, driver, customer, source and destination, truck / prime mover and trailer configuration.
  2. Axle & Mass Capture
  3. Documents
  4. Review & Confirm

This Load is created specifically against the Log Book it was launched from, keeping the trip, vehicle configuration and load information linked together.

Log Books Stored Against an Asset

Every Log Book is associated with the vehicle / Asset selected when it was created. To see all Log Books for a specific vehicle, go to Asset in the left-hand menu, open the vehicle, and view its Log Book history from there — instead of filtering the main Log Book list by asset.

See also: Asset Details — Related Tabs (Logbook History).

Module 3 · Log Book · Reference

Log Book — Navigation Quick Reference

How to get to each screen and action in the module.

Screen / ActionHow to get there
Log Book listLeft menu → Log Book
Filter by statusLog Book → tabs: All / Draft / Submitted / Approved / Rejected
Filter by asset / driver / customer / date / flagLog Book → filter bar above the table
Create a new Log BookLog Book → “Create Log Book” → Vehicle Group → Vehicle → “Start Log Book”
Fill in the 7 sectionsLog Book (open) → tabs: Driver / Vehicle, Shift & Breaks, Fitness for Work, Pre-Start Check, Fault Report, Post-Trip Check, Certification
Submit a Log BookComplete Certification → Complete (from the list, status becomes Submitted)
View detailsLog Book list → eye icon on any row
Edit a Draft / Rejected Log BookLog Book list → pencil icon
Approve / RejectSubmitted tab → green tick / red cross
Create a LoadApproved tab → truck / Load icon → Load Record (4 steps)
View Log Books for one vehicleLeft menu → Asset → select vehicle → Log Book history

End of the Log Book training guide.

Training & User Workflow Guide

Fatigue Management Module

Practical day-to-day training for scheme configuration, driver logbook activity, fatigue warning evaluation and breach review.

Key distinction: A warning shown on the device is informational. The backend independently evaluates fatigue and creates the authoritative BreachEvent used in the formal review workflow.
End-to-end fatigue evaluation flow
1Driver time segmentsDriving, breaks, work and non-work
→
2Resolve active schemeAssigned active scheme or company Default
→
3Evaluate supported rulesLocal checks from available logbook data
→
4Driver warningLive / submit-time information
→
5Backend evaluationAuthoritative BreachEvent
→
6ReviewEvidence, actions, comments, close/reopen
Fatigue Rules & SchemesCompany Admin defines fatigue limits and policy settings.
Dashboard / LogbookDriver records driving, breaks, work/rest and Fitness for Work information.
Active BreachesRead-only breach events; drivers see their own records.
ReviewsCompany Admin investigates, records actions, closes or reopens incidents.
Fatigue › Introduction

Roles & Permissions

Who can view, configure, drive, review and approve.

CapabilityCompany AdminDriverMechanicMaster Admin
View Fatigue / Active BreachesYesOwn onlyYesNo company scope
See Reviews / perform reviewYesNoNoNo in role table
View Fatigue RulesYesRead-onlyRead-onlyNo in role table
Create / edit / activate / delete / default schemeYesNoNoNo in role table
Fill own Shift & Breaks / Fitness for WorkN/AYesN/AN/A
Approve / reject submitted logbookYesNoNoNo in role table
Training note: The source guide records an internal inconsistency for Master Admin permissions. Train against the permissions actually presented by the deployed environment.
Fatigue › Introduction

Navigation Map

Exact paths to Fatigue, Rules, Logbook and Fitness for Work.

Main navigation map
1Sign inChoose role / company
→
2DashboardMain workspace
→
3FatigueActive Breaches / Reviews
→
4SettingsFatigue Rules / scheme editor
→
5LogbookShift & Breaks / Fitness for Work
ScreenNavigation pathWhat happens there
Fatigue homeSidebar / bottom nav → FatigueActive breach list; admins may also have Reviews.
Active BreachesFatigue → Active BreachesRead-only BreachEvent list.
ReviewsFatigue → ReviewsReview queue and status filters.
Review detailReviews → open a rowEvidence, timeline, actions, comments, close/reopen.
Fatigue RulesSettings → Fatigue RulesView schemes; admins manage lifecycle.
Scheme editorFatigue Rules → New Scheme / open rowConfigure details, regulatory and operational rules.
Shift & BreaksLogbook → day entry → Shift & BreaksRecord time blocks and review metrics/issues.
Fitness for WorkLogbook → day entry → Fitness for WorkComplete self-assessment and acknowledgements.
Fatigue › Admin & Scheme Setup

Create, Activate & Assign a Fatigue Scheme

Administrator setup workflow
1Settings → Fatigue RulesOpen scheme list
→
2New SchemeCreate mode
→
3Configure details & rulesName, cycle, policies
→
4SaveNew scheme is Inactive
→
5Make ActiveActivate from row menu
→
6Set as DefaultOptional fallback
→
7Assign to driverUser → Edit → Fatigue Scheme + Start Date
StepActionExpected result
1Settings → Fatigue RulesScheme list opens.
2Select New SchemeEditor opens in create mode.
3Enter a scheme name and configure settingsBlank name cannot be saved.
4SaveNew scheme is created as Inactive.
5Row menu → Make ActiveStatus becomes Active.
6Optional: Set as DefaultUsed when a driver has no active direct assignment.
7Users → driver → Edit → Fatigue SchemeSelect scheme and enter Scheme Start Date.
Operational policy: Daily Driving Cap, Night Hours, Night Rest and Long Hours are off by default and must be deliberately enabled.
Fatigue › Admin & Scheme Setup

Scheme Details

Start at Settings → Fatigue Rules → New Scheme → Details. Use the left-hand section menu to move through the policy.

Fatigue Scheme — Details screen
Fatigue Scheme — Details screen
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.
Field / ControlMeaning / Training guidance
Fatigue SchemeName of the scheme. Use a clear business name for assignment and reporting.
Schedule / Rest OptionSelect either 14-Day Cycle or 28-Day Cycle. Only one is binding at a time.
Recording TypeReal Time or Retrospective.
Fleet IDOrganisational scope for reporting and alert routing where used.
Daily Window AnchorControls how 24-hour window rules are anchored.
Notes CompulsoryEnable when the organisation requires notes as part of the record.
Fatigue › Admin & Scheme Setup

Regulatory Rules

Breaks From Driving

Breaks From Driving — short-break requirements
Breaks From Driving — short-break requirements
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

The supplied configuration shows a 5-hour work period, 20 minutes total break, including at least one continuous 10-minute break.

Work & Rest Cycle

Work & Rest Cycle — qualifying long-rest requirements
Work & Rest Cycle — qualifying long-rest requirements
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

The supplied screen shows 7 hours minimum continuous rest and 17 hours maximum between qualifying rests.

72-Hour Rest Requirements

72-Hour Rest Requirements — total non-work and long-rest checks
72-Hour Rest Requirements — total non-work and long-rest checks
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.
ControlSupplied value
Non-Work Hours Required27 hours
Required Long Rests3
Assessment Period72 hours
Minimum Qualifying Non-Work Event30 minutes
Qualifying Single Long Rest Duration420 minutes / 7 hours
Fatigue › Admin & Scheme Setup

Choose the Binding Cycle: 14-Day or 28-Day

The Schedule / Rest Option on Details determines which cycle is binding. The other cycle can remain configured for later use.

14-Day Cycle — active / binding cycle example
14-Day Cycle — active / binding cycle example
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.
28-Day Cycle — configured but not binding in the supplied example
28-Day Cycle — configured but not binding in the supplied example
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.
CycleSource guide summary
14-Day Cycle14-day assessment period; 168-hour work limit; 2 required 24-hour rests; advisory thresholds 150 / 156 / 162 hours.
28-Day Cycle28-day assessment period; 144-hour work limit per 14-day sub-window; 4 qualifying 24-hour rests.

Shift-Change Rest

Shift-Change Rest — rest required when shift patterns change
Shift-Change Rest — rest required when shift patterns change
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

The supplied screen uses a 5-day threshold and requires 24 hours rest between shift changes. An optional practicability override can be recorded when enabled.

Fatigue › Admin & Scheme Setup

Operational Policies

Daily Driving Cap

Daily Driving Cap — optional operational cap
Daily Driving Cap — optional operational cap
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

Operational cap. The guide's defaults are 16 hours per day and a 6-hour major break; this control is off by default.

Night & Long Hours

Night & Long Hours — optional night-hours, night-rest and long-hours controls
Night & Long Hours — optional night-hours, night-rest and long-hours controls
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.
ControlSupplied defaults / engine scope
Night Hours Cap00:00–05:00; 5 hours allowed. Backend-only; off by default.
Night Rest Check22:00–06:00; minimum 7 hours rest. Backend-only; off by default.
Long Hours CapStarts after 12 hours worked; 2 hours excess allowed. Evaluated by the on-device warning engine; off by default.
Fatigue › Admin & Scheme Setup

Corrective Action Defaults

Corrective Action — automatic action defaults and breach-type overrides
Corrective Action — automatic action defaults and breach-type overrides
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

This page controls whether the system automatically creates a first corrective action when a breach occurs.

  1. Enable Automatically create a corrective action on breach when required.
  2. Choose the Default Action Type and enter a useful description.
  3. Optionally configure a different action for Regulatory breaches.
  4. Optionally configure a different action for Company Policy breaches.
  5. Leave an override blank when it should fall back to the default action.
Fatigue › Admin & Scheme Setup

Additional Company Rules

Additional Company Rules — custom rules layered over the regulatory scheme
Additional Company Rules — custom rules layered over the regulatory scheme
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

Additional Company Rules allow company-defined controls to be layered over the regulatory scheme.

FieldTraining guidance
Rule NameUse a human-readable policy name, e.g. Yard Shunting Max Hours.
EnabledTurns the custom rule on/off.
Assessment PeriodWindow used to assess the rule; supplied default 1440 minutes.
Maximum WorkOptional; may be blank for no cap.
Minimum Total RestSupplied default 600 minutes.
Minimum Continuous RestSupplied default 420 minutes.
Rest Must Be StationaryEnable only when company policy requires stationary rest.
Warning ThresholdOptional advance-warning threshold; may be blank.
Fatigue › Driver & Compliance

Driver Daily Workflow

Driver Duty Card workflow
1Dashboard → Start DrivingVehicle selection opens
→
2Select vehicle → StartDuty Card = Driving
→
3Take BreakDuty Card = On Break
→
4Resume DrivingDuty Card = Driving
→
5Finish DrivingOpen segment closes
→
6Complete Log BookFinish required sections
→
7SubmitSubmission / warnings as applicable

Shift & Breaks

Fitness for Work

Fatigue › Driver & Compliance

Understanding Fatigue Warnings

The device evaluates the assigned active scheme, or the company Default scheme when no active direct assignment can be used. The backend independently re-checks and is authoritative for BreachEvent records.

Where warning appearsWhat the user sees
Dashboard Duty CardLive warning while an active segment is running; refreshes on a roughly 30-second ticker.
Shift & BreaksWork-hours-limit red flag in the metrics area.
Submit-time dialogAfter submission, current fatigue warnings may be listed in a Fatigue rule warning dialog.
Active Breaches / ReviewsBackend-authoritative breach events and formal review workflow.
Severity: Warning-only results use amber. If any result is breach-tier, the banner switches to red/danger. When no warnings remain, the banner disappears.
RuleOn-device?Training summary
F01 Breaks From DrivingYesRequired break in work period.
F02/F04 Long-Rest SeparationYesQualifying rest and maximum gap.
F03A/B 72-Hour RestYesTotal non-work and long-rest count.
F05 14-Day CycleYesWork cap and 24-hour rests.
F07 28-Day CycleYesSub-window cap and 24-hour rests.
F08 Shift-Change RestNoBackend only.
Daily Driving CapYesOperational cap.
Night Hours / Night RestNoBackend only.
Long Hours CapYesOperational cap.
Fatigue › Driver & Compliance

Breach Review Workflow

Active Breaches and Reviews are separate records. Active Breaches shows the read-only BreachEvent; Reviews contains the linked investigation record.

Breach review workflow
1Fatigue → ReviewsOpen queue
→
2Open reviewReview detail
→
3Start Review / Assign to MeClaim New review
→
4Check evidence & timelineActual vs required; events
→
5Add action / commentAssign, due date, notes
→
6Close incidentAcknowledge open actions if needed
→
7Reopen if requiredReason required

Review Queue

AreaWhat to do
EvidenceReview evaluation rows, actual vs required values, forecast where available, severity and override details.
Driver TimelineCheck driving, break, non-work and work events; unconfirmed events are highlighted.
Corrective ActionsAdd action, assign it and set due date. Completion needs a note; cancellation needs a reason.
CommentsComment and optionally apply an action tag. Blank comments are blocked.
Close While ActiveExceptional path; record override reason and resolution outcome.
ReopenClosed reviews can be reopened with a reason.
Fatigue › Driver & Compliance

Offline & Sync Behaviour

Fatigue schemes are cached locally, so rules and supported on-device checks can continue offline. An offline-created scheme receives a local ID first; the backend server ID appears after sync.

SituationExpected behaviour
Create scheme offlineScheme appears locally; server ID is not yet available.
Reconnect and revisit Fatigue RulesRemote changes are pulled; scheme syncs and server ID becomes available.
Assign unsynced offline-created schemeApplication should show a clear error instead of using a non-existent backend ID.
Remote pull failsCached schemes remain available; list should not crash or become blank.
Driver edits logbook offlineSupported fatigue checks use local driver, scheme and recent logbooks and should compute as online.
Fatigue › Reference & Training

Quick Rule Reference

CodePlain-language ruleDefault / key values in the training guide
F01Breaks From Driving5h work period; 20min total break; 10min continuous break.
F02/F04Long-Rest Separation7h minimum continuous rest; 17h maximum gap.
F03ANon-Work Total (72h)27h non-work in 72h.
F03BLong-Rest Count (72h)3 long rests of at least 420min in 72h.
F0514-Day Work & Rest Cycle168h work limit; 2 qualifying 24h rests; advisory 150/156/162h.
F0728-Day Work & Rest Cycle144h per 14-day sub-window; 4 qualifying 24h rests.
F08Shift-Change Rest5 consecutive shift-day threshold; 24h required rest.
Daily Driving CapOperational16h/day and 6h major break; off by default.
Night HoursOperational00:00–05:00; 5h allowed; off by default.
Night RestOperational22:00–06:00; 7h minimum rest; off by default.
Long HoursOperationalStarts after 12h worked; 2h allowed excess; off by default.
Fatigue › Reference & Training

Practical Training Scenarios

Scenario A — Admin creates a scheme

Trainer asks learner to…Success check
Create “Training Scheme” in Settings → Fatigue Rules.Scheme saves as Inactive.
Activate and set Default.Status shows Active / Default.
Enable Daily Driving Cap and set a test-friendly value.Setting persists after save/reopen.
Assign to a driver with Scheme Start Date.Assignment saves successfully.

Scenario B — Driver completes a shift

Trainer asks learner to…Success check
Start Driving and select a vehicle.Duty Card shows Driving.
Take a break, then resume.Duty Card changes state correctly.
Finish Driving.Segment closes; Complete Log Book is available.
Review Shift & Breaks timeline/issues.Blocks and metrics match recorded activity.
Complete Fitness for Work with a risky answer and acknowledgement.Risk and acknowledgement are recorded.

Scenario C — Admin reviews a breach

Trainer asks learner to…Success check
Open Fatigue → Reviews and claim a New review.Review becomes assigned.
Inspect Evidence and Driver Timeline.Learner can explain actual vs required values and identify events.
Add corrective action and comment.Both appear in history.
Close then reopen with a reason.Status changes correctly and reason is captured.
Fatigue › Reference & Training

Troubleshooting & Trainer Sign-Off

Question / issueWhat to check
Driver sees no fatigue warningsConfirm an active assigned scheme exists, or an Active Default scheme is configured.
F08 / Night Hours / Night Rest has no live client warningExpected from source: these are backend-only checks.
Cannot delete a schemeActive schemes cannot be deleted; deactivate first.
Cannot save driver scheme assignmentScheme Start Date is required when a scheme is selected.
Cannot approve a red-flagged logbookA comment on the red flag and action taken is required.
Warning disappears after Finish DrivingThe live Duty Card projection ends when the active segment closes; other checks may still appear later.
Offline scheme cannot be assignedIt may not have a backend server ID; reconnect and sync first.

Trainer sign-off checklist

Maintenance Policy › Introduction

Maintenance Policy — Overview & Workflow

Define scheduled maintenance rules once; let Fidentra OS raise the work when it is due.

The Maintenance Policy module defines scheduled maintenance rules for assets. A policy controls the service interval, scheduling method, hierarchy behaviour, meter-trigger behaviour, lead time and grace period.

After a policy is saved, the required assets are assigned with baseline information. Meter readings are then recorded against the asset. Fidentra OS uses those readings and the configured interval to calculate the next due point and raises a maintenance job when the configured condition is met.

ItemDetail
AudienceMaintenance planners, administrators, mechanics, testers and developers.
Navigation pathMain Menu → Maintenance Policy
Policy tabs8 — Policy Details & Scheduling, Assets Assigned, Documents, Materials, Worklist, Instructions, Work Time, Job Orders
Service typesA, B, C and D Service (intervals set by your approved maintenance schedule)

End-to-End Workflow

The eight steps below take a policy from creation to sign-off. Click any step to jump to its page.

Guide Map

Creating a PolicyPolicy details, scheduling fields, save and assign assets.
Eight Scheduling ConfigurationsFixed and Variable Cycle screens, with and without hierarchy and meter trigger.
Meters & ReadingsCreate a meter and record readings.
Policy TabsDocuments, materials, worklist, instructions, work time, job orders.
Scheduling EngineHow due points, triggers, hierarchy and duplicates are decided.
Training & ReferenceScenarios, knowledge check, checklists, cheat sheet.
Maintenance Policy › Introduction

Learning Outcomes & Service Structure

What you will be able to do, and the four services a policy can describe.

Learning Outcomes

After this training you will be able to:

Service Structure

An asset can have four maintenance services: A, B, C and D. The actual interval for each service must be configured according to your company’s approved maintenance schedule.

ServiceIntervalPurpose
A ServiceConfigured intervalRoutine scheduled maintenance
B ServiceConfigured intervalHigher-level scheduled maintenance
C ServiceConfigured intervalPeriodic major maintenance
D ServiceConfigured intervalPeriodic major / overhaul maintenance
Maintenance Policy › Creating a Policy

Create a New Maintenance Policy

Open the module, start a policy and complete the Policy Details.

Steps

  1. Open the Maintenance Policy module from the left navigation.
  2. Click New Policy.
  3. The Policy Details & Scheduling page opens.
  4. Complete all required Policy Details fields before moving to Asset Assignment.

Policy Details

FieldWhat to enter
Policy NameName of the maintenance policy.
Policy CodeA unique policy code / reference.
StatusActive or Inactive.
Job TypeThe applicable maintenance / job type.
Policy CategoryThe appropriate policy category.
Service Checklist TemplateSelect the required checklist template from the dropdown.
DescriptionA short description of the policy / service.
TipPolicy Name, Policy Code and Job Type matter most when you build a four-service hierarchy — see Hierarchy — Service Matching Rule.
Maintenance Policy › Creating a Policy

Scheduling Configuration

The fields that decide when maintenance becomes due.

FieldWhat to enter
Schedule MethodFixed Cycle or Variable Cycle.
HierarchyEnabled when the policy uses hierarchy levels; otherwise Not Applicable (off).
Trigger Meter (Reading Trigger)Tick the checkbox when meter readings should trigger the maintenance calculation.
Hierarchy LevelShown when hierarchy is enabled; enter / select the required level.
Interval TypeMeter-based: KM (Kilometer), Hours. Period-based: Days, Weeks, Months, Years.
Policy IntervalThe interval value used for the policy (for example 10,000 KM).
Lead TimeHow early the system prepares / raises the requirement before the due point.
Grace PeriodAllowed grace after the due point, where applicable.
Add Secondary IntervalUse when an additional scheduling interval is required (see Primary & Secondary Intervals).
Configuration note
“Not Applicable / Off” means hierarchy is not used for that policy. Trigger Meter is enabled by ticking the Reading Trigger checkbox.
Type 1 — Policy Details & Scheduling with Scheduling Configuration fields
Type 1 — Policy Details & Scheduling with Scheduling Configuration fields
Maintenance Policy › Creating a Policy

Save the Policy & Assign Assets

Attach the policy to assets with a baseline reading and date.

  1. After completing Policy Details & Scheduling, click Save.
  2. Open the Assets Assigned section.
  3. Click Assign Asset on the right side.
  4. Select the required Asset Group.
  5. Select the asset that must follow this maintenance policy.
  6. Enter the Baseline Reading.
  7. Enter the Baseline Date.
  8. Click OK / confirm and then Assign.
  9. Verify that the asset appears in the Assigned Assets list with its baseline, current reading, next due and job status.
Assets Assigned — asset with baseline, current reading, next due, due date, remaining and job status
Assets Assigned — asset with baseline, current reading, next due, due date, remaining and job status
Do not skip the baseline
Automatic generation must not begin until the required anchor is known: Baseline for Fixed Cycle, Last Done for Variable Cycle.
Maintenance Policy › Eight Scheduling Configurations

The Eight Scheduling Configurations

Three independent choices combine into eight practical policy set-ups.

The Maintenance Policy design supports eight practical combinations of Schedule Method, Hierarchy and Trigger Meter. Each configuration page shows the policy form and the Assets Assigned list for that set-up.

TypeSchedule MethodHierarchyTrigger MeterWhere to find it
1Fixed CycleNoDisabledFixed Cycle Types 1–4
2Fixed CycleYesDisabledFixed Cycle Types 1–4
3Fixed CycleNoEnabledFixed Cycle Types 1–4
4Fixed CycleYesEnabledFixed Cycle Types 1–4
5Variable CycleNoDisabledVariable Cycle Types 5–8
6Variable CycleYesDisabledVariable Cycle Types 5–8
7Variable CycleNoEnabledVariable Cycle Types 5–8
8Variable CycleYesEnabledVariable Cycle Types 5–8
How this relates to the engine
The scheduling-engine pages describe the same eight combinations as “Concepts 1–8”. The Concept Map page shows how each Type matches a Concept.
Maintenance Policy › Eight Scheduling Configurations

Fixed Cycle Configurations — Types 1 to 4

Due points stay anchored to the planned baseline.

Fixed Cycle reminder
Next Due = Baseline + Policy Interval
State advances at Job generation, from the planned due point.

Type 1 — Fixed Cycle + No Hierarchy + Trigger Disabled

Use a fixed maintenance interval without hierarchy and without meter-trigger behaviour. The policy follows the configured fixed cycle.

Type 1 — Policy Details & Scheduling
Type 1 — Policy Details & Scheduling
Type 1 — Assets Assigned
Type 1 — Assets Assigned

Type 2 — Fixed Cycle + Hierarchy Enabled + Trigger Disabled

Use a fixed cycle where hierarchy is required. Configure the applicable hierarchy level. Meter reading trigger remains disabled.

Type 2 — Policy Details & Scheduling
Type 2 — Policy Details & Scheduling
Type 2 — Assets Assigned
Type 2 — Assets Assigned

Type 3 — Fixed Cycle + No Hierarchy + Trigger Enabled

Use a fixed cycle and allow meter readings to drive the maintenance calculation. Hierarchy is not used.

Type 3 — Policy Details & Scheduling
Type 3 — Policy Details & Scheduling
Type 3 — Assets Assigned
Type 3 — Assets Assigned

Type 4 — Fixed Cycle + Hierarchy Enabled + Trigger Enabled

Use a fixed cycle with hierarchy and meter-trigger behaviour enabled. Configure the hierarchy level and record readings against the assigned asset.

Type 4 — Policy Details & Scheduling
Type 4 — Policy Details & Scheduling
Type 4 — Assets Assigned
Type 4 — Assets Assigned
Maintenance Policy › Eight Scheduling Configurations

Variable Cycle Configurations — Types 5 to 8

Due points move from the actual last-done completion.

Variable Cycle reminder
Next Due = Last Done + Policy Interval
State advances at Job completion, from the actual completion reading / date.

Type 5 — Variable Cycle + No Hierarchy + Trigger Disabled

Use a variable cycle without hierarchy and without meter-trigger behaviour.

Type 5 — Policy Details & Scheduling
Type 5 — Policy Details & Scheduling
Type 5 — Assets Assigned
Type 5 — Assets Assigned

Type 6 — Variable Cycle + Hierarchy Enabled + Trigger Disabled

Use a variable cycle with hierarchy, while leaving the meter trigger disabled. Configure the required hierarchy level.

Placeholder — a screenshot for this exact combination (Variable Cycle + Hierarchy Enabled + Trigger Disabled) was not supplied with this training set. Set Schedule Method = Variable Cycle, Hierarchy = Enabled, leave Trigger Meter unticked and enter the Hierarchy Level.

Type 7 — Variable Cycle + No Hierarchy + Trigger Enabled

Use a variable cycle without hierarchy and allow meter readings to trigger the maintenance calculation.

Type 7 — Policy Details & Scheduling
Type 7 — Policy Details & Scheduling
Type 7 — Assets Assigned
Type 7 — Assets Assigned

Type 8 — Variable Cycle + Hierarchy Enabled + Trigger Enabled

Use a variable cycle with hierarchy and meter-trigger behaviour. Configure the hierarchy level and maintain current meter readings for accurate due calculations.

Type 8 — Policy Details & Scheduling
Type 8 — Policy Details & Scheduling
Type 8 — Assets Assigned
Type 8 — Assets Assigned
Maintenance Policy › Meters & Readings

Create a Meter

For meter-driven maintenance the asset needs a meter, created from its Readings section.

  1. Open the required asset and select View.
  2. Open the Readings section.
  3. Click Add Readings / Create Meter as provided by the screen.
  4. The asset is normally carried into the meter form. Select / confirm the Meter Type.
  5. Enter the Meter Name and Unit.
  6. Set Average Using Last N Readings — the number of readings the system averages for usage analysis and forecasts.
  7. Enter the Last End Reading or applicable starting value.
  8. Click Create Meter.
Asset Details → Readings, with the Add Readings button
Asset Details → Readings, with the Add Readings button
New Meter form: Asset, Meter Type, Meter Name, Unit and Average Using Last N Readings
New Meter form: Asset, Meter Type, Meter Name, Unit and Average Using Last N Readings
Maintenance Policy › Meters & Readings

Record Readings

Keep readings current so due calculations stay accurate.

  1. Open the created meter to view the Timeline / Graph.
  2. Click Record Reading.
  3. Enter Date & Time and the current reading.
  4. Continue recording readings as the asset operates, according to actual readings.
Meter timeline listing each recorded reading with date and value
Meter timeline listing each recorded reading with date and value
Reading Required
If no valid matching reading exists for a usage-based policy, no meter-based Job Order is generated and the status is set to Reading Required.
Maintenance Policy › Policy Tabs

The Eight Maintenance Policy Tabs

Complete the sections in order, then save.

A Maintenance Policy is organised into eight sections along the top of the screen. Complete Policy Details first, then configure assigned assets, documents, materials, worklist, instructions, work time and job orders.

Recommended completion flow
Complete the sections in order and review the policy summary at the top before saving: Policy Details & Scheduling → Assets Assigned → Documents → Materials → Worklist → Instructions → Work Time → Job Orders → Save.

Tabs 1 and 2

TabPurpose
1. Policy Details & SchedulingPolicy Code, Job Type, Policy Category, Service, Description, Scheduling Method, Service Cycle, Variation, Trigger, Interval Type and related values.
2. Assets AssignedSelect the assets the policy applies to. Confirm the correct asset or asset group before continuing. The assigned-asset count appears in the policy summary at the top of the screen.
Maintenance Policy › Policy Tabs

Documents & Materials Tabs

Attach the service manual and list the parts required.

Documents

Attach the manual or service document related to the policy. The uploaded document shows its file name and link.

Documents tab — Manual / Service Document
Documents tab — Manual / Service Document

Materials

Records the parts or materials required to complete the service.

Materials tab — Name, Part No. and Qty
Materials tab — Name, Part No. and Qty
Maintenance Policy › Policy Tabs

Worklist & Instructions Tabs

The checklist and the tasks technicians follow on the Job Order.

Worklist

Contains the checklist items that must be completed during the service. Each item appears as a numbered task and can be marked Required.

Worklist tab — numbered checklist items
Worklist tab — numbered checklist items

Instructions

Tasks that technicians or workers should follow when the policy creates a Job Order.

Instructions tab — Add Task
Instructions tab — Add Task
Maintenance Policy › Policy Tabs

Work Time & Job Orders Tabs

Planned labour, and the Job Orders the policy has generated.

Work Time

Defines planned labour for the policy. For each role, specify Workers Required and Planned Hours. The summary shows planned hours per role on every Job Order.

Work Time tab — roles, workers required and planned hours
Work Time tab — roles, workers required and planned hours

Job Orders

Shows Job Orders generated from the policy. Filter by status — All, Open, InProgress, Completed, SignedOff, Cancelled, Forecast — and by date range.

Job Orders tab — status filters and date range
Job Orders tab — status filters and date range
Maintenance Policy › Engine Architecture

The Engine in One View

The five building blocks and the order in which the engine thinks.

Core principle
The Schedule Policy defines the rules. The Asset-Policy record stores the current schedule state. The Reading Module supplies usage readings. The scheduling engine evaluates eligibility. The Job Order is the transaction created by the engine.
  1. Calculate Next Due for every configured interval.
  2. Evaluate Primary and optional Secondary intervals independently.
  3. Use OR logic: the first satisfied interval makes the shared cycle eligible.
  4. Apply Meter Trigger rules to a reading interval when enabled; the calendar interval remains independently active.
  5. If hierarchy is enabled, rank only policies that are independently eligible.
  6. Check for an existing active Job Order for the shared cycle.
  7. Generate one Job Order and update state according to Fixed Cycle or Variable Cycle rules.
Maintenance Policy › Engine Architecture

Four Scheduling Methods & Schedule State

Two schedule bases, with or without hierarchy — and the fields that hold the state.

MethodSchedule anchorHierarchyState moves
Fixed CyclePlanned BaselineNoAt Job generation, from planned due point
Variable CycleActual Last DoneNoAt Job completion, from actual completion
Fixed Cycle HierarchyPlanned BaselineYesGenerated + covered lower baselines advance at generation
Variable Cycle HierarchyActual Last DoneYesGenerated + covered lower Last Done values update at completion
Do not confuse the dimensions
Meter Trigger is not a fifth scheduling method. It changes only the meter-side generation condition. Hierarchy is an optional selection layer, and dual intervals are an interval model.

Essential Schedule State

FieldTraining meaning
Baseline Date / ReadingDriving planned anchor for Fixed Cycle methods.
Last Done Date / ReadingActual completed-work anchor for Variable Cycle methods.
Next Due Date / ReadingCalculated due point for the Asset + Policy pair.
Current Reading / Reading DateLatest valid accumulated matching reading from the Reading Module.
Schedule Cycle IDShared due-cycle key used to prevent duplicate generation.
StatusExamples: Waiting, Due Soon, Due, Job Raised, Suppressed, Reading Required.
Per-asset state
A policy can be assigned to many assets. Schedule state therefore belongs to the Asset + Policy relationship, not only to the reusable policy.
Maintenance Policy › Intervals, Readings & Triggers

Dual-Interval Scheduling — OR / Whichever Occurs First

One required Primary Interval and one optional Secondary Interval.

A policy has one required Primary Interval and may have one optional Secondary Interval. Each interval is evaluated independently, but both represent the same maintenance requirement and share one Schedule Cycle ID.

Eligibility formula
PolicyDue = Interval1TriggerSatisfied OR Interval2TriggerSatisfied
ExampleReading sideCalendar sideResult
Configuration10,000 KM3 Months10,000 KM OR 3 Months
Fixed baseline100,000 KM01-Jan-2026–
Next Due110,000 KM01-Apr-2026–
Forecast trigger108,000 KM30-Mar-2026Whichever trigger is reached first

If 108,000 KM is reached on 20-Mar-2026, the reading side generates the one Job Order for the shared cycle. The later calendar trigger must not create a duplicate. If the calendar trigger is reached first, it generates the one Job Order instead.

Maintenance Policy › Intervals, Readings & Triggers

Reading & Calendar Rules

Which readings count, and what happens when none exist.

Maintenance Policy › Intervals, Readings & Triggers

Forecast Mode vs Meter Trigger

Same policy, two ways of deciding when the reading side fires.

ConditionMeter Trigger OFFMeter Trigger ON
Reading intervalCurrent Reading >= Forecast Trigger ReadingNew valid Reading >= Next Due Reading
Average usageUsed to calculate meter forecastIgnored for meter generation
Calendar intervalCurrent Date >= Trigger DateCurrent Date >= Trigger Date
Overall dual policyReading condition OR Calendar conditionActual meter condition OR Calendar condition

Forecast formulas

Usage forecast
NextDueReading = ScheduleAnchorReading + PolicyInterval
ForecastLeadUsage = AverageDailyUsage x LeadTimeDays
TriggerReading = NextDueReading - ForecastLeadUsage
Calendar forecast
TriggerDate = NextDueDate - LeadTime

Meter Trigger event rule

When Meter Trigger is ON for a reading interval, generation is event-driven. On a new valid matching reading, calculate Next Due and continue only when NewAccumulatedReading >= NextDueReading. Forecast usage is not used for that meter condition.

Important
Meter Trigger does not disable a configured calendar interval. The calendar side remains independently active and the overall policy still uses OR logic.
Maintenance Policy › Schedule Basis

Fixed Cycle

Future due points stay anchored to planned cycle values.

Fixed Cycle keeps future due points anchored to planned cycle values. Actual completion is recorded for history but does not move the schedule.

Due calculation
NextDueReading = BaselineReading + PolicyInterval
NextDueDate = BaselineDate + PolicyInterval
StepExample
StartBaseline 10,000 KM; interval 10,000 KM; Next Due 20,000 KM
GenerationJob Order generated for the 20,000 KM cycle
State updateBaseline advances to planned 20,000 KM; Next Due becomes 30,000 KM
Actual completionWork completes at 21,350 KM
OutcomeNext Due stays 30,000 KM, not 31,350 KM
Developer rule
Advance from the planned due point, not from the actual completion point.
Maintenance Policy › Schedule Basis

Variable Cycle

The next cycle moves from the actual completion point.

Variable Cycle scheduling moves the next maintenance cycle from the actual completion point of the previous completed Job Order.

Due calculation
NextDueReading = LastDoneReading + PolicyInterval
NextDueDate = LastDoneDate + PolicyInterval
StepExample
StartLast Done 11,000 KM; interval 10,000 KM; Next Due 21,000 KM
GenerationJob generated; Last Done remains 11,000 KM while work is open
CompletionJob completes at 21,500 KM
State updateLast Done becomes 21,500 KM
OutcomeNew Next Due becomes 31,500 KM
Developer rule
Do not advance Last Done at Job generation. Advance only at completion using the actual completion reading / date.
Maintenance Policy › Hierarchy & Suppression

Hierarchy — Rules, Window & State

A higher eligible service covers the lower services — but only after eligibility is proven.

Hierarchy groups related service policies so a higher eligible service can cover lower services. The critical order is: calculate eligibility first, then rank. A higher policy that has not reached its own trigger must not be pulled forward.

LevelPolicyInterval
1A Service10,000 KM
2B Service30,000 KM
3C Service60,000 KM
4D Service120,000 KM

Expected Fixed Cycle sequence: 10K A, 20K A, 30K B, 40K A, 50K A, 60K C, 70K A, 80K A, 90K B, 100K A, 110K A, 120K D.

No early pull-forward
Each hierarchy policy must first become independently eligible using its own interval(s). Only independently eligible policies enter the candidate list.

Hierarchy window

Window formula
HierarchyWindowPercent = (LowestInterval / HighestInterval) x 100
Example: (10,000 / 120,000) x 100 = 8.33%
HierarchyWindowReading = 10,000 KM
Suppression comparison uses Difference < HierarchyWindow, not <=

The strict boundary preserves the 110K A Service before the 120K D Service because the difference is exactly 10,000 KM, and 10,000 < 10,000 is false.

Fixed vs Variable Cycle hierarchy state

SituationFixed Cycle HierarchyVariable Cycle Hierarchy
Higher service generatedAdvance generated + covered lower planned baselinesKeep Last Done unchanged; mark covered lower policies suppressed
Higher service completedRecord actual completion onlyReset generated + covered lower Last Done to actual completion point
Higher service cancelledKeep / recreate same cycle; do not advance twiceRelease suppression and re-evaluate; Last Done remains unchanged
Maintenance Policy › Hierarchy & Suppression

Hierarchy — Service Matching Rule

Four services only form a Hierarchy when three details match.

When four services are created under a Maintenance Policy and the Service Schedule Method is set to Hierarchy, the services must be identified as belonging to the same policy and the same type of work. Three details are checked across all four services: Policy Name, Policy Code and Job Type.

Requirement
Hierarchy works only when all four services have a matching Policy Name, Policy Code and Job Type. If any one differs, the Hierarchy is not accepted and does not work. The check is all-or-nothing: one mismatched service rejects the whole Hierarchy.
ServicePolicy NamePolicy CodeJob Type
Service ASameSameSame
Service BSameSameSame
Service CSameSameSame
Service DSameSameSame

Each service still keeps its own level and interval within the Hierarchy (A lowest, D highest).

SituationResult
All four services match on all three detailsAccepted — Hierarchy works
Policy Name differs on any serviceNot accepted — Hierarchy does not work
Policy Code differs on any serviceNot accepted — Hierarchy does not work
Job Type differs on any serviceNot accepted — Hierarchy does not work
More than one detail differsNot accepted — Hierarchy does not work

How to set up a valid Hierarchy

  1. Create the first service and note its Policy Name, Policy Code and Job Type.
  2. Create the remaining three services using exactly the same three details.
  3. Set the Service Schedule Method to Hierarchy.
  4. Give each service its own level and interval (A lowest, D highest).
  5. Save. If any detail differs, the Hierarchy is rejected — correct the mismatch and save again.
Developer / tester rule
HierarchyValid = (PolicyName A=B=C=D) AND (PolicyCode A=B=C=D) AND (JobType A=B=C=D)
If HierarchyValid is false: reject the Hierarchy — no covering or suppression of lower services is applied.

Test checklist

#TestExpected result
1Create Services A–D with identical Policy Name, Policy Code and Job Type; set method to HierarchyAccepted and works
2Change the Policy Name on one service onlyNot accepted
3Change the Policy Code on one service onlyNot accepted
4Change the Job Type on one service onlyNot accepted
5Change all three details on one serviceNot accepted
6Correct the mismatch so all four services match againAccepted and works
Maintenance Policy › Job Order Generation

Initialising an Asset on a Policy

What happens when an asset is first placed under a policy.

  1. Check whether valid service history exists for the policy.
  2. If history exists, derive Baseline or Last Done according to the scheduling method.
  3. If no history exists, an administrator establishes the initial scheduling anchor.
  4. Calculate Next Due.
  5. Read current meter / date state.
  6. Set schedule status and activate the assignment.
Activation rule
Do not begin automatic generation until the required anchor is known: Baseline for Fixed Cycle, Last Done for Variable Cycle.
Maintenance Policy › Job Order Generation

Job Raised → Job Order

How a due service becomes completed, signed-off work.

How the service becomes due

Once the policy, asset baseline and meter readings are configured, Fidentra OS uses the configured interval and current reading to calculate the maintenance position. When the configured service threshold is reached, the system can show the maintenance status and raise the corresponding job according to the policy configuration.

Working the Job Order

  1. Open Job Order and locate the maintenance job.
  2. Review the asset, service and due information.
  3. Add the required Instructions.
  4. Add the required Work List items.
  5. Add Materials where required.
  6. Enter Work Time.
  7. Attach Documents, Work Logs / Audit Logs and Certification where applicable.
  8. Perform the maintenance work.
  9. Complete the required checklist / work information.
  10. Complete and Sign Off the Job Order / service.

End-to-end example

Example
A maintenance policy is configured for an asset with a 10,000 km interval. The asset is assigned with a valid baseline reading. Meter readings are recorded as the asset operates. When the calculated reading reaches the configured service point, Fidentra OS updates the maintenance status and, where the configured rule is satisfied, raises the maintenance job. The job is then handled in Job Order, completed and signed off.
Maintenance Policy › Job Order Generation

Job Order Lifecycle & Duplicate Prevention

One shared cycle produces one Job Order.

EventFixed CycleVariable Cycle
Policy eligibleGenerate if duplicate / cycle checks passGenerate if duplicate / cycle checks pass
Job generatedAdvance Baseline to planned due pointDo not change Last Done
Job openBlock same-cycle duplicateBlock same-cycle duplicate
Job completedRecord actual completion onlyUpdate Last Done from actual completion
Job cancelledKeep / recreate same cycle; no double advanceRelease suppression and re-evaluate; Last Done unchanged
Mandatory duplicate key
AssetID + PolicyID/HierarchyGroup + ScheduleCycleID + Active/Outstanding State

Both intervals in a dual-interval policy resolve to the same Schedule Cycle ID. Once the first interval generates the Job Order, the second condition may later be recorded as reached but must not generate another Job Order for that cycle.

Maintenance Policy › Job Order Generation

Edge Cases & Required Behaviour

Conditions to train and test.

ConditionRequired behaviour
No matching valid readingNo meter-based Job Order; status = Reading Required
Reading jumps over due pointUse >= so the due cycle still generates
Wrong frequency typeIgnore for that policy
Meter replaced / resetUse accumulated reading; do not restart from raw meter
Policy inactive / asset not in useDo not evaluate or generate
Existing Job for due cycleDo not create duplicate
Variable Cycle Job remains openDo not update Last Done; block same-cycle duplicate
Higher hierarchy policy not independently eligibleExclude it; never pull it forward
Hierarchy difference equals windowDo not suppress because the comparison is strict <
Maintenance Policy › Eight Scheduling Concepts

Eight Scheduling Concepts — Concept Map

Three independent dimensions, one scheduling engine.

The eight concepts are combinations of three independent dimensions: Schedule Basis (Variable Cycle or Fixed Cycle), Hierarchy (off or on) and Meter Trigger (off or on). They are combinations of one scheduling engine, not eight separate engines.

ConceptSchedule BasisHierarchySuppressionMeter TriggerScreen Type
1Variable CycleNoNoneOFFType 5
2Fixed CycleNoNoneOFFType 1
3Variable CycleYesSuppressionOFFType 6
4Fixed CycleYesSuppressionOFFType 2
5Variable CycleNoNoneONType 7
6Fixed CycleNoNoneONType 3
7Variable CycleYesSuppressionONType 8
8Fixed CycleYesSuppressionONType 4
Terminology
The specification uses Variable Cycle as the preferred term for the legacy term Variable. Fixed is referred to as Fixed Cycle.

Rules that apply across all eight concepts

Maintenance Policy › Eight Scheduling Concepts

Concepts 1 to 4 — Meter Trigger OFF

Forecast generation: the reading side can fire before the actual due point.

Concept 1 — Variable + No Hierarchy + Meter Trigger OFF

Variable Cycle schedule, individual policy, forecast generation, no suppression.

Concept 2 — Fixed + No Hierarchy + Meter Trigger OFF

Fixed Cycle schedule, individual policy, forecast generation, no suppression.

Concept 3 — Variable + Hierarchy + Meter Trigger OFF

Variable Cycle with hierarchy, forecast generation, and suppression of covered lower services.

Concept 4 — Fixed + Hierarchy + Meter Trigger OFF

Fixed Cycle with hierarchy, forecast generation, and suppression of covered lower services.

Maintenance Policy › Eight Scheduling Concepts

Concepts 5 to 8 — Meter Trigger ON

Actual-reading generation: the reading side fires on a new valid reading at or past Next Due.

Concept 5 — Variable + No Hierarchy + Meter Trigger ON

Variable Cycle schedule, individual policy, actual-reading Meter Trigger, no suppression.

Concept 6 — Fixed + No Hierarchy + Meter Trigger ON

Fixed Cycle schedule, individual policy, actual-reading Meter Trigger, no suppression.

Concept 7 — Variable + Hierarchy + Meter Trigger ON

Variable Cycle with hierarchy, actual-reading Meter Trigger, and suppression.

Concept 8 — Fixed + Hierarchy + Meter Trigger ON

Fixed Cycle with hierarchy, actual-reading Meter Trigger, and suppression.

Maintenance Policy › Training & Reference

Scenario Workshop

Practical scenarios for trainers and learners.

Use these scenarios during training. Ask the learner to state: (a) whether the policy is eligible, (b) which policy / interval wins, (c) whether a Job Order is generated, and (d) which state values change.

ScenarioExpected result
Fixed: 20K cycle completes at 21.35KNext due remains 30K.
Variable Cycle: Last Done 11K, completes at 21.5KLast Done = 21.5K; next due = 31.5K.
Meter Trigger ON; next due 30K; reading 29.9KNo Job.
Meter Trigger ON; next due 30K; reading 30.0KJob eligible.
Fixed hierarchy at 60K: A/B/C due; D not dueGenerate C; suppress A/B; D untouched.
Dual interval 10K KM OR 3 Months; date reaches trigger firstGenerate one Job from calendar side even if KM is below trigger.
Meter Trigger ON; KM below due; calendar trigger reachedGenerate from calendar side.
Fixed dual interval generated by KM sideAdvance both Baseline Reading and Baseline Date to planned due points.
Completion of dual interval at 111.2K on 24-MarSet both Last Done anchors to actual completion values.
Hierarchy: A meets an interval; higher B meets neitherOnly A is independently eligible; do not pull B forward.
Maintenance Policy › Training & Reference

Knowledge Check & Answer Key

Ten questions, then the model answers.

Questions

Answer Key

#Answer
1The policy defines reusable rules; the Asset-Policy record stores the current state for that specific asset assignment.
2OR / whichever occurs first. The first satisfied interval makes the shared cycle eligible.
3No. Meter Trigger changes only the reading-side generation condition; the calendar side remains independently active.
4At Job generation, from the planned due point.
5At Job completion, from the actual completion reading / date.
6No. Each hierarchy policy must first be independently eligible.
7To ensure the second interval cannot generate a duplicate Job Order for the same maintenance requirement.
8Do not generate the usage-based Job Order; set Reading Required.
9Strict less-than: Difference < HierarchyWindow.
10Next due points; whether Primary OR Secondary reached its generation condition; Meter Trigger / calendar interaction; hierarchy winner among independently eligible policies; whether the shared cycle already generated a Job Order.
Maintenance Policy › Training & Reference

Maintenance Policy — User Checklist

What a trainee should be able to confirm unaided.

Validation checklist

No.Training RequirementStatus
1Policy name and code are correct and unique.☐ Not Checked
2Status is set correctly.☐ Not Checked
3Job Type, Policy Category and Service Checklist Template are correct.☐ Not Checked
4Schedule Method is correct: Fixed Cycle or Variable Cycle.☐ Not Checked
5Hierarchy is correctly enabled or not applicable.☐ Not Checked
6Trigger Meter checkbox is correctly enabled / disabled.☐ Not Checked
7Interval Type and Policy Interval are correct.☐ Not Checked
8Lead Time and Grace Period are correct.☐ Not Checked
9Asset Group and Asset are correctly assigned.☐ Not Checked
10Baseline Reading and Baseline Date are correct.☐ Not Checked
11Meter is created with the correct type, name and unit.☐ Not Checked
12Readings are recorded with the correct date / time and value.☐ Not Checked
13Next Due / Remaining / Job Status values are reviewed.☐ Not Checked
14Raised maintenance job appears in Job Order.☐ Not Checked
15Instructions, Work List, Materials, Work Time, Documents / Logs / Certification are completed as required.☐ Not Checked
16Job Order is completed and signed off.☐ Not Checked

Final review of the eight tabs

No.Training RequirementStatus
1Policy details and scheduling values are correct.☐ Not Checked
2The correct assets are assigned.☐ Not Checked
3The required manual / service document is attached.☐ Not Checked
4All required materials have Name, Part No. and Qty.☐ Not Checked
5The worklist contains the required service checks.☐ Not Checked
6Instructions are clear and actionable.☐ Not Checked
7Roles, worker requirements and planned hours are correct.☐ Not Checked
8Generated Job Orders and scheduled dates are reviewed.☐ Not Checked
Maintenance Policy › Training & Reference

Trainer Quick Reference

One page for the trainer.

Remember the architecture
Two Schedule Basis behaviours + optional Hierarchy + optional Meter Trigger + Primary interval with optional Secondary interval joined by OR. This is one scheduling engine, not separate engines.
QuestionRule
How is Next Due calculated?Fixed = Baseline + Interval; Variable Cycle = Last Done + Interval.
When is a dual policy eligible?When Primary OR Secondary reaches its generation condition first.
What changes with Meter Trigger ON?Reading generation waits for a new valid reading >= Next Due; calendar remains active.
How is hierarchy applied?Only after independent eligibility; highest eligible policy wins under suppression rules.
How are duplicates stopped?Shared Schedule Cycle ID + active / outstanding Job check.
When does state move?Fixed at generation from planned due; Variable Cycle at completion from actual values.
Module 4 · Files · Introduction

Files — Purpose & Overview

A central place to create, upload, organise, search, view, manage, delete and restore files.

ModuleFiles
Main ScreenFiles (left menu → Files)
Primary PurposeA central location to create, upload, organise, search, view, manage, delete and restore files.
CoversPurpose, overview, navigation, file management, search & filters, folder management, trash & restore, and the end-to-end workflow.

Purpose and Scope

The Files module provides a central location to create, upload, organise, search, view, manage, delete and restore files. It supports common file categories such as Documents, Images, Spreadsheets, PDFs and Other file types.

Module Overview

The Files main page provides access to the user's file library and folder structure. The main areas are:

Files main page: left panel, search and filters, and the Folders / Files tabs
Figure FL-1 — Files main page: left panel, search and filters, and the Folders / Files tabs
Tip — click any screenshot to enlarge it. Use the zoom button in the viewer to read small text, the arrow keys to move between screenshots and Esc to close.

What is on the main screen

Elements visible in the screenshot above:

ElementWhat it shows
Left panelAll Files, My Folders (labelled “My Folders” on screen) and Trash. Under FILE TYPES, each type is listed with its file count, e.g. Images (2).
Search box“Search files and folders ...”
Type filterDrop-down that limits the list to one file type (“Images” is selected in this example).
Sort menuDrop-down for the sort order (“Name (A-Z)” in this example).
View toggleTwo icons beside the sort menu: a list view and a grid view.
Folders / Files tabsSwitch between the folders and the files in the current area, each with a count (Folders 5, Files 2 in this example).
New FolderButton at the top right. See New Folder.
Folder rowsEach folder has a three-dot menu on the right (example folders: SC, test, module, QA_Temp_Folder, Test).
Module 4 · Files · Introduction

Files — File Types, All Files & My Folder

How files are grouped by type, and the difference between All Files and My Folder.

File Type Organisation

Uploaded files are presented according to their file type. Typical categories include:

File TypeExamples
DocumentDOC / DOCX and similar text documents
ImageJPG, JPEG, PNG and similar image files
SpreadsheetXLS / XLSX and similar spreadsheet files
PDFPDF documents
OthersFile formats not covered by the main categories

On screen, the FILE TYPES section of the left panel lists the types that currently contain files, each with a count — for example Documents (1) and Images (2).

My Folder and All Files

All Files is used to view the complete file collection available to the user. My Folder is used to navigate through the user's folder structure and view folders.

On the screen, the left-panel entry reads “My Folders” (plural). The guide calls it “My Folder” — they are the same area.
Module 4 · Files · Managing files & folders

Files — Create / Upload Files

Add new content to the Files module.

Use the Create option on the Files module main page to add new content. Users can create or upload supported file content such as images, documents, spreadsheets and PDFs.

  1. Open the Files module.
  2. Click Create.
  3. Select the required create/upload option.
  4. Choose the file to upload or complete the required file details.
  5. Confirm the action.
  6. The file is stored in the appropriate file area/type and becomes available from the Files list.
Inside a folder: New Folder, Camera and Upload buttons, with the file list below
Figure FL-2 — Inside a folder: New Folder, Camera and Upload buttons, with the file list below

In this screenshot, the buttons at the top right of the folder screen are New Folder, Camera and Upload. The uploaded file (a .docx in this example) appears in the file list, and its type is added to the FILE TYPES panel on the left.

Follow the button labels on your screen. The steps above use the guide's wording (“Create”), while the folder screen shown here offers Upload and Camera — see the note in Training Notes.
Module 4 · Files · Managing files & folders

Files — New Folder

Create a folder to keep related files together.

The New Folder option allows users to create a folder for organising files.

  1. Click New Folder.
  2. Enter the Folder Name.
  3. Click Create.
  4. The new folder appears in the folder/file area.
  5. Use the three-dot menu beside the folder to access Edit Folder when available.
New Folder dialog on the Files main page
Figure FL-3 — New Folder dialog on the Files main page

The dialog is titled New Folder. It has one field, Folder name, and two buttons: Cancel and Create.

Module 4 · Files · Managing files & folders

Files — Working Inside a Folder

Open a folder and use the same tools on its contents.

Click a folder to open it. The folder name is displayed at the top of the page. The same search, type-filter and sorting controls are available inside the folder.

Inside the folder called test: breadcrumb, actions, filters and file list
Figure FL-2 — Inside the folder called test: breadcrumb, actions, filters and file list

What is on the folder screen

ElementWhat it shows
Folder nameShown as the page title (“test” in this example).
Breadcrumb“Home › test” — click Home to go back up.
New Folder / Camera / UploadButtons at the top right for adding folders and files to the current folder.
Folders / Files tabsFolders 0 and Files 1 in this example.
File listName, Type, Size, Modified On and Actions columns.
Module 4 · Files · Managing files & folders

Files — Delete & Restore

Deleted items go to Trash first, and can be restored from there.

When a file or folder is deleted, it is moved to Trash rather than being permanently removed immediately.

  1. Select the required file or folder.
  2. Use the available Delete action from the item's action or more-options menu.
  3. The deleted item is moved to Trash.
  4. Open Trash to locate the deleted item.
  5. Use Restore to return the item to its available file/folder location.
Trash screen: a deleted folder with Restore
Figure FL-4 — Trash screen: a deleted folder with Restore

The Trash screen lists each deleted item. In this example the deleted folder Test is shown with a blue Restore link and a red bin icon on the right.

The guide describes Restore only. It does not explain the red bin icon next to it, so confirm what it does on the live screen before training users on it.
Module 4 · Files · Reference & training

Files — End-to-End Workflow

The full journey from opening Files to deleting and restoring an item.

The ABC flow: A – Access Files → B – Create/Upload → C – Organise → D – Search/Filter → E – Manage → F – Delete/Restore. Click any step to open its page.

Typical file lifecycle
Upload / CreateStore in FolderSearch / FilterOpen / ManageDeleteTrashRestore
Module 4 · Files · Reference & training

Files — Quick Reference

Find the right control for each goal.

User GoalUse
See every available fileAll Files
See foldersMy Folder
Find a file by nameSearch bar
Show only PDFsType filter → PDF
Show recent filesSort → Newest
Show oldest filesSort → Oldest
Sort names alphabeticallyA to Z / Z to A
Create a folderNew Folder
Edit a folderThree dots → Edit Folder
Recover a deleted itemTrash → Restore
Module 4 · Files · Reference & training

Files — Training Checklist & Notes

What a trainee should be able to do, and how to treat the guide.

User Training Checklist

No.Training RequirementStatus
1Open the Files module and identify All Files, My Folder and Trash.☐ Not Checked
2Create a new folder and edit the folder name/details.☐ Not Checked
3Upload an image, document, spreadsheet and PDF.☐ Not Checked
4Search for a file by name.☐ Not Checked
5Apply the file-type filter.☐ Not Checked
6Apply A to Z, Z to A, Newest, Oldest and Largest sorting where available.☐ Not Checked
7Open a folder and create a sub-folder.☐ Not Checked
8Open and manage a file using the available actions.☐ Not Checked
9Delete a test file and confirm that it appears in Trash.☐ Not Checked
10Restore the deleted file from Trash.☐ Not Checked

Training Notes

Use the current approved application screen as the source of truth for exact button labels, permissions and validation behaviour. The visible options may vary according to user role and system configuration.

Files Module – Training Guide | Internal User Guide

Module 5 · Load Record · Introduction

Load Record — Overview & Workflow

Plan, command, wait and track every trip.

Module Purpose

The Load Record module is used to create and manage trip/load information. From a single workflow you can filter existing records, manage supporting Customers and Locations, create a new load, capture vehicle/trailer and axle-mass information, upload documents, certify the record, review the details, and save the final load for future tracking and management.

ItemDetail
AudienceOperations users, dispatch / load planners, administrators, and anyone responsible for maintaining load information.
Navigation pathMain Menu → Load Record → Load Records
Stages to create a load4 — Load Details & Vehicle, Axle & Mass, Documents, Review & Confirm

End-to-End Workflow

The eleven steps below cover a load from opening the module to managing it after it is saved. Click any step to jump to its page.

A Load Record can also be started from an Approved Log Book — see Create a Load & Asset Storage. The four stages are identical.
Module 5 · Load Record · Introduction

Load Records Main Page

Where existing loads are found, filtered and managed.

The Load Records page lists every created load and gives access to the actions required to create and manage them.

Load Records main page with numbered annotations
Figure LR-1 — Load Records main page, with each control numbered
Click the screenshot to open it full size

Filters and Search

Filter / OptionPurpose
DateFilter load records by date.
LocationFilter records using configured locations.
VehicleFilter records using the relevant vehicle / asset.
StatusFilter by Planned, Dispatch, In Transit, Complete or Cancelled.
SearchSearch by Load ID, name or asset name.
More FiltersNarrow the results by Customer, Priority and Load Type.

Page Actions

ActionDescription
ExportExports the displayed Load Record information (Excel / PDF).
Show Menu (three dots)Provides additional management actions.
Manage CustomerOpens the Customer configuration page — create, edit, delete and search customers.
Manage LocationOpens the Location configuration page — create, edit, delete and search locations, including loading and unloading points.
Create New Load RecordStarts the new Load Record creation workflow.
View icon (eye)Opens the load record details.
The Status column shows the current position of each load in its lifecycle, so the list doubles as a live tracking board.
Module 5 · Load Record · Creating a load — 4 stages

Stage 1 — Load Details & Vehicle Configuration

The basic trip information, then the truck and trailer combination.

Select Create New Load Record to open the Load creation panel. The workflow is completed through four stages:

Stage 1Load Details + Vehicle / Trailer Configuration
Stage 2Axle and Mass Capture
Stage 3Documents + Terms & Conditions + Certification
Stage 4Review and Confirm

1.1 Load Details

Enter or select the basic load information required for the trip.

1.2 Vehicle & Trailer Configuration

Select the required truck, prime mover, trailer or other configured assets from the available dropdowns. Where a Road Train combination has been configured in Settings, that combination can be selected as a predefined configuration instead of picking each unit.

After selection, the chosen vehicle / trailer configuration can be previewed with the related asset image.

Load Details screen, step 1 of 4
Figure LR-2 — Load Details screen, Step 1 of 4, with Road Train combination selected
Click the screenshot to open it full size
Select Next to continue to Axle & Mass Capture.
Module 5 · Load Record · Creating a load — 4 stages

Stage 2 — Axle & Mass Capture

Axle masses, bucket distribution and the load summary.

Axle and Mass Capture screen, step 2 of 4
Figure LR-3 — Axle Group Mass Entry, Load Bucket Distribution and Total Load Distribution Summary
Click the screenshot to open it full size
Use Recall where the workflow requires the record to be recalled, then select Submit and Next to continue.
Module 5 · Load Record · Creating a load — 4 stages

Stage 3 — Documents, Terms & Certification

Attach evidence, accept the terms and sign the record.

  1. Upload the relevant documents and photographs required for the load.
  2. Review and agree to the Terms & Conditions.
  3. Use the Sign option to provide the required signature.
  4. Select Save to store the signature.
  5. Complete the certification step so the record is marked Certified.
  6. Select Submit and Next to proceed to Review & Confirm.
Documents and certification screen, step 3 of 4
Figure LR-4 — Documents page before signature, the Sign-to-certify popup, and the signed / certified state
Click the screenshot to open it full size
The load cannot be saved until the Terms & Conditions are accepted and the signature has been captured and certified.
Module 5 · Load Record · Creating a load — 4 stages

Stage 4 — Review & Confirm

The last check before the Load Record is created.

Review all information entered during the previous stages. Confirm the load details, configuration, mass information, documents, terms, signature and certification before saving the load.

Review and Confirm screen, step 4 of 4
Figure LR-5 — Review & Confirm screen, Step 4 of 4, with the Save Load action
Click the screenshot to open it full size
Final action — select Save Load to create the final saved Load Record.
Module 5 · Load Record · After the load is saved

Saved Load Record — Available Actions

What you can do with a load once it exists.

ActionPurpose
SyncSynchronise the saved load record where applicable.
Offline SyncUse the available offline-sync option where supported.
PrintPrint the saved load record.
EditModify permitted load information.
Status ChangeUpdate the load status — Planned, Dispatch, In Transit, Complete or Cancelled — as permitted.
Three DotsProvides additional actions such as Edit, Delete and other load-related actions.
Saved load record detail view and change status menu
Figure LR-6 — Saved load record detail view, and the Change Status options
Click the screenshot to open it full size
Load status lifecycle
PlannedDispatchIn TransitCompleteCancelled
Module 5 · Load Record · After the load is saved

Load Record List — Ongoing Management

How saved loads are tracked day to day.

All created load records are listed on the main Load Records page. Users can open a record to view its details and use the available actions.

Load information may also be generated or stored as part of related operational workflows, including loads associated with approved Logbook processes — see Create a Load & Asset Storage in the Log Book module.

Use the status filter on the list to run the day: Planned for what is booked, Dispatch and In Transit for what is moving, Complete for what is closed out.
Module 5 · Load Record · Reference

Load Record — Quick Reference

Find the right control for each goal.

TaskSteps
Find a loadUse Date, Location, Vehicle, Status, Search or More Filters.
Create a loadCreate New Load Record → complete all four stages → Save Load.
Manage customersShow Menu → Manage Customer.
Manage locationsShow Menu → Manage Location.
Track statusUse the available load status values and the Load Records list.
Review a saved loadOpen the record → review details → Sync / Print / Edit or other permitted actions.
Module 5 · Load Record · Reference

Load Record — User Checklist

What a trainee should be able to do unaided.

No.Training RequirementStatus
1Confirm Date, Load Type, Driver, Customer, Loading Point and Unloading Point.☐ Not Checked
2Select the correct vehicle / trailer or configured Road Train combination.☐ Not Checked
3Verify the Load Panel and Axle & Mass Capture information.☐ Not Checked
4Check payload, gross load, legal payload and utilisation values.☐ Not Checked
5Upload the required documents and photos.☐ Not Checked
6Agree to the Terms & Conditions and complete signature / certification.☐ Not Checked
7Review all information before selecting Save Load.☐ Not Checked
8After saving, use the available Sync, Print, Edit, Status and additional actions.☐ Not Checked
Use the current approved application screen as the source of truth for exact button labels, permissions and validation behaviour. Visible options may vary by user role and system configuration.

Load Record Module – Training Guide | Internal User Guide

Module 5 · Job Order

Job Order — User Guide

A topic-based guide to creating, assigning, tracking, completing and signing off maintenance work.

PurposeThe Job Order module is used to create, assign, track and close maintenance work carried out by drivers, mechanics and admins. A Job Order records what work needs to be done, who it is assigned to, when it is scheduled, and the actions taken until the work is completed and signed off.

Find a Job Order topic

Overall Workflow

The module follows a simple lifecycle: create the Job Order, assign it, edit the work setup, track work, update status, then sign off completed work. Maintenance Policy and Forecast are linked where applicable.

Job Order lifecycle — overall workflow from creation to sign-off and Forecast
Job Order lifecycle — overall workflow from creation to sign-off and Forecast
Click the screenshot to open it full size
↓
↓
↓
↓
↓
Job Order › Navigation Map
Module 5 · Job Order · Introduction

Navigation Map

Where each screen and option sits inside the Job Order module.

Job Order module — navigation map
Job Order module — navigation map
Click the screenshot to open it full size
Job Order structure
  1. Main Menu → Job Order opens the Job Order List page.
  2. The list page contains Filter/Search controls, the New Job Order action and row-level actions.
  3. View Details opens the Job Order detail screen and its work-tracking tabs.
  4. Edit is used to update the job and add Service Checklist/Parts.
  5. Change Status moves the Job Order to In Progress, Complete or Cancelled.
  6. Completed Job Orders can be signed off using the configured Job Order Sign Off process.
Job Order › Filter & Search
Module 5 · Job Order · Find work

Filtering and Searching Job Orders

Use the controls above the list to locate the work you need.

  1. From the main menu, click Job Order.
  2. The Job Order page opens and shows the list of Job Orders.
  3. Use one or more filters to narrow the list.
Job Order list page with search, filters, statuses and row actions
Job Order list page with search, filters, statuses and row actions
Click the screenshot to open it full size
ControlHow to use it
Search boxType a Job Order number or Job Order name to locate a specific record.
AllShows every Job Order when no specific filter is applied.
Asset filterSelect a specific asset, or leave the asset choice at the all-types option to see Job Orders for every asset.
Priority filterFilter by Low, Medium, High or Critical priority.
TipFilters can be combined. For example, select a vehicle and Critical priority to focus on urgent work for that asset.
Job Order › Create a Job Order
Module 5 · Job Order · Create

Creating a New Job Order

Create the work record, assign responsibility, set the schedule and add To-Do tasks.

New Job Order form — details, assignment, schedule, progress and To-Do task
New Job Order form — details, assignment, schedule, progress and To-Do task
Click the screenshot to open it full size

1. Basic Details and Priority

FieldWhat it means / how to use it
Job DetailsEnter the basic description and details of the work to be done.
AssetSelect the vehicle/equipment this Job Order applies to. Assets created in the system are available from the dropdown.
PriorityChoose Low, Medium, High or Critical based on urgency.

2. Assignment and Scheduling

FieldWhat it means / how to use it
Assign ToSelect the employee responsible for the work. Employee accounts such as drivers, mechanics and admins appear in the dropdown. Confirm the selection so the assignee appears under Assigned To.
Scheduled DateSet the date on which the work is planned to be carried out.
ProgressStarts at 0% when the Job Order is created and is updated as work progresses.

3. Add a To-Do Task

  1. Type the task as a sentence in the Add Task box.
  2. Click the + icon to add it to the To-Do list.
  3. Repeat for additional tasks.

4. Save

  1. Check the details, priority, assignee, scheduled date and tasks.
  2. Click Create Job Order.
  3. If the Job Order is assigned, it appears in the Assigned list.
Job Order › View, Edit & Cancel
Module 5 · Job Order · Manage

Viewing, Editing and Cancelling

Open an existing Job Order and manage its setup.

Job Order row actions, Job Order details and edit screen
Job Order row actions, Job Order details and edit screen
Click the screenshot to open it full size

Row actions

Editing a Job Order

Click Edit to update a Job Order after it is created. The edit screen also provides sections that are not part of the initial creation form.

FieldHow to use it
Service ChecklistSelect an applicable checklist from the defaults already configured in Settings.
PartsSelect required parts, tick the checkbox and use Add Part to add them to the Job Order.

After saving, instructions are visible under Instructions, services under Work List, and parts under Materials.

Cancelling

Select Cancel Job Order from the three-dot menu when the work is no longer required. The Job Order moves to the Cancelled status.

Job Order › Job Order Tabs
Module 5 · Job Order · Details

Job Order Detail Tabs

Each tab separates a different type of work information and activity.

Job Order Details tab showing the core Job Order information
Job Order Details tab showing the core Job Order information
Click the screenshot to open it full size
TabWhat is stored / shown here
DetailsCore information entered when the Job Order was created, including asset, priority, assignment and schedule.
InstructionsInstructions added for the Job Order.
Work ListServices added to the job, including work derived from the Service Checklist.
MaterialsParts added to the Job Order.
Work TimeRecorded start/end work time and total hours worked.
DocumentsAttached files, including documents uploaded from Work List or Materials.
Work LogWork updates posted for the Job Order.
Audit LogAutomatic history of actions taken on the Job Order.
The detail screen also provides Edit and Change Status controls alongside the tabs.
Job Order › Track Work
Module 5 · Job Order · Work tracking

Tracking Work on a Job Order

Record instructions, work performed, materials, time, documents and history while the job is active.

Instructions

Use Add Task under To Do Task and the + icon to add questions or instructions. The added items are saved under Instructions when the Job Order is reviewed.

Instructions tab — tasks/questions recorded for the Job Order
Instructions tab — tasks/questions recorded for the Job Order
Click the screenshot to open it full size

Work List

Work List contains the services that have been added to the Job Order. Use this area to work through the required service/checklist items.

Work List tab — service checklist items and Pass/Fail controls
Work List tab — service checklist items and Pass/Fail controls
Click the screenshot to open it full size

Materials

To add materials, open Job Order → Edit → Parts, select the required parts, enter the details and save the changes. The parts are then shown under Materials.

Materials tab — parts stored against the Job Order
Materials tab — parts stored against the Job Order
Click the screenshot to open it full size

Work Time

Use Work Time to record how long work took on the Job Order. Enter the Start Work Time; the system records the work period based on the captured entries.

Work Time tab — recorded work periods for the Job Order
Work Time tab — recorded work periods for the Job Order
Click the screenshot to open it full size

Documents

Use Documents to attach relevant files. Documents added while working in Work List or Materials are also stored here.

Documents tab — files stored against the Job Order
Documents tab — files stored against the Job Order
Click the screenshot to open it full size

Work Log

Use Work Log to post updates about the work being carried out.

Work Log tab — progress updates posted to the Job Order
Work Log tab — progress updates posted to the Job Order
Click the screenshot to open it full size

Audit Log

Creation, edits, status changes and other actions are automatically recorded in Audit Log, providing the activity history of the Job Order.

Audit Log tab — automatic history of Job Order actions
Audit Log tab — automatic history of Job Order actions
Click the screenshot to open it full size
Job Order › Status Lifecycle
Module 5 · Job Order · Status

Changing the Status of a Job Order

Use Change Status to move the Job Order through its lifecycle.

StatusWhen to use it
In ProgressSelect while work on the Job Order is underway.
CompleteSelect once all work on the Job Order is finished.
CancelSelect when the Job Order is no longer proceeding.
↓
↓
Work finished
Work not proceeding

After a status is selected, the Job Order automatically appears in the corresponding list such as In Progress, Completed or Cancelled.

Job Order › Maintenance Policy & Forecast
Module 5 · Job Order · Linked modules

Maintenance Policy and Forecast Link

How service pricing flows into the Job Order and then into Forecast.

Why this mattersPricing the service correctly in Maintenance Policy allows the service to flow through the linked Job Order and, once completed, into Forecast without manual re-entry.
↓
↓
↓
Job Order › Complete & Sign Off
Module 5 · Job Order · Completion

Signing Off a Completed Job Order

Finalise a Job Order after all work has been completed.

Before sign-offThe Job Order must first be marked Complete.
  1. Go to Settings > Company Profile.
  2. Scroll to the final section, Job Order Sign Off.
  3. Click the comment area and tick the checkbox used for the sign-off configuration.
  4. Return to the completed Job Order and click Sign Off.
  5. Confirm the sign-off and provide the signature where prompted.
  6. After successful sign-off, the Job Order record is finalised.
Completed Job Order sign-off sequence — Sign Off confirmation, signature and final success state
Completed Job Order sign-off sequence — Sign Off confirmation, signature and final success state
Click the screenshot to open it full size
Job Order › Quick Reference
Module 5 · Job Order · Reference

Quick Reference Summary

The Job Order process from opening the module to final sign-off.

StepActionNavigation / key control
1NavigateMain Menu > Job Order.
2Filter / SearchUse the search box, Asset filter and Priority filter.
3CreateEnter Details, Priority, Assign To, Scheduled Date and To-Do Task; then Create Job Order.
4ManageUse the eye icon or three-dot menu to View Details, Edit or Cancel.
5EditAdd Service Checklist and Parts as required.
6TrackUse Work List, Materials, Work Time, Documents, Work Log and Audit Log.
7Update statusChange Status > In Progress, Complete or Cancel.
8Sign offAfter completion, use the configured Job Order Sign Off process.

Job Order at a glance

Create & AssignDefine the work, asset, priority, assignee and scheduled date.
PrepareAdd instructions, Service Checklist and required parts.
WorkTrack services, materials, time, documents and progress.
CloseChange status to Complete and finish the sign-off.
Expected result: The Job Order provides one traceable record from creation and assignment through work tracking, status change and final sign-off.
Module 6 · Job Request · Introduction

Job Request — Overview

Raise a request for work on an asset, and track the decision.

The Job Request module is used to raise a request for work to be carried out on an asset (equipment or machine). Once a request is submitted it is reviewed and either approved — which automatically creates a Job Order — or declined.

The Four Tabs

AllEvery Job Request ever raised, regardless of status.
OpenSubmitted but not yet Approved or Declined.
ApprovedApproved — a Job Order has been created.
DeclinedRequests that have been rejected.

A '+' Request Job Order button sits in the bottom-right corner of every tab and opens the new request form.

Columns in Every Tab

ColumnDescription
RequestThe title / name of the Job Request.
StatusOpen, Approved or Declined.
DateDate the request was created or last updated.
ActionsA View option that opens the full details of that request.
Job Request main list screen showing the four tabs
Figure JR-1 — Job Request list, All tab, with status badges and the ‘+’ button
Click the screenshot to open it full size
The count beside each tab name (All 23, Open 14, Approved 5, Declined 4) is a live total — a quick way to see the outstanding workload.
Module 6 · Job Request · Introduction

Accessing the Job Request Module

How to get to the module and what you see when you arrive.

  1. Open the application and go to the Main Menu.
  2. Tap or click Job Request from the menu list.
  3. The Job Request screen opens, showing four tabs at the top: All, Open, Approved, Declined.
  4. A '+' (plus) icon is available in the bottom-right corner, labelled Request Job Order — this is used to raise a new request.
Where a request lives over its life
RaisedAll + OpenDecisionApprovedDeclined
Job Requests raised against an asset also appear under Asset Details → Job Request, so the asset's history stays complete.
Module 6 · Job Request · Raising a request

Creating a New Job Request

From the plus button to a submitted request.

  1. From the Job Request screen, click the '+' icon (Request Job Order) in the bottom-right corner.
  2. The New Job Request form opens.
  3. Select the Request Type — for example, Asset.
  4. Choose the specific Asset from the dropdown list.
  5. Enter a Title for the request.
  6. Enter a Description explaining the issue or work needed.
  7. Select the Priority: Low, Medium or High.
  8. Optionally use Attach Document to upload existing photos or files, or Take Photo to capture a new photo directly.
  9. Click Submit Request at the bottom of the form.
  10. The screen returns to the main Job Request page. The new request is now visible in the All tab and the Open tab.
New Job Request form
Figure JR-2 — New Job Request form, with Attachment options and Submit Request
Click the screenshot to open it full size

Workflow — Creating & Submitting

Module 6 · Job Request · Raising a request

Fields & Validation

What each field expects, and what stops a submission.

FieldTypeNotes
Request TypeDropdownFor example, Asset.
AssetDropdownSelect the exact asset the request is for.
TitleTextShort name for the request.
DescriptionText (multi-line)Explain the issue or work required.
PriorityDropdownLow / Medium / High.
Attach Document / PhotoOptional uploadAttach existing files or take a new photo.
Validation — if a mandatory field such as Asset or Title is left empty, the form shows an error message under that field and blocks submission until it is corrected. Always double-check the Asset and the Priority before submitting.
Priority drives how the request is triaged, so a wrong value is harder to correct later than a wrong description — set it deliberately rather than leaving the default.
Module 6 · Job Request · Decision & follow-through

Reviewing, Approving & Declining

The decision point — and the moment a Job Order is born.

  1. Go to the Open tab — this lists every request awaiting a decision.
  2. On the request row, click the three-dot icon (⋮) labelled More Action.
  3. Select View to open the full request details.
  4. Review the Asset, Priority and Description shown.
  5. Choose Approve if the work should go ahead, or Reject if it should not.
  6. If approved, the status changes to Approved, the request moves to the Approved tab, and a Job Order is created automatically.
  7. If declined, the status changes to Declined and the request moves to the Declined tab.
Job Request detail screen with approve and reject buttons
Figure JR-3 — Request detail screen with Asset, Priority, Description and the Reject / Approve actions
Click the screenshot to open it full size

Workflow — Approval Decision

Important — approving a request is the trigger that creates the Job Order. Once approved, the request cannot be edited from the Job Request screen; further changes must be made on the Job Order page.
Module 6 · Job Request · Decision & follow-through

From Approved Request to Job Order

Where the request stops and the actual work begins.

  1. Open the Approved tab. Each row shows the Request name, Status (Approved) and Date.
  2. Click Actions on the request row, then click View.
  3. The detail screen shows the Asset, Priority, Description and other details of the request.
  4. Click View Job Order at the bottom of the screen.
  5. The Job Order page opens, showing Details, Instructions, Worklist, Material, Work Time, Document and Work Log.
  6. From here you can edit details, add a Work Log entry, and make changes as the job progresses.
  7. When the work is finished, mark the Job Order Complete and Sign Off — or mark it Cancel if the job is not going ahead.
Approve dialog, approved request and job order page
Figure JR-4 — Approve dialog (assign to, schedule date, comments), the approved request, and the Job Order page
Click the screenshot to open it full size

Job Order Page — What Each Section Means

SectionPurpose
DetailsCore information carried over from the approved request — asset, priority, description.
InstructionsStep-by-step instructions for the technician performing the work.
WorklistChecklist of individual tasks to be completed as part of the job.
MaterialParts and materials used or required for the job.
Work TimeTime logged or spent performing the work.
DocumentSupporting files or photos attached to the job order.
Work LogA running log of updates — use Add Log to record progress notes.

Workflow — Approved Request to Completion

Module 6 · Job Request · Reference

Complete End-to-End Navigation Flow

Every step from raising the request to final sign-off, on one screen.

This combines the raising, decision and job-order stages into a single big-picture map. Click any step to open its page.

The decision at step 6 is the hinge of the whole module: Approve creates a Job Order and moves the work into the Job Order module; Decline ends the request in the Declined tab.
Module 6 · Job Request · Reference

Quick Reference — Tabs & Statuses

Which actions are available from where.

TabStatus shownCan move toAction available
AllAny—View
OpenOpenApproved or DeclinedMore Action → View → Approve / Decline
ApprovedApprovedJob Order createdActions → View → View Job Order
DeclinedDeclined—View

Key Points to Remember

Tip — if you cannot find a request, check the All tab first; it always contains every request regardless of its current status.

Job Request Module – Training Guide | Internal User Guide

Module · Settings · Introduction

Settings — Purpose & Overview

The central configuration area for company details, operational rules, compliance requirements, checklists, vehicle configuration, fatigue-management schemes, user roles and system preferences.

ModuleSettings
Main ScreenSettings (left menu → Setting)
Primary PurposeConfigure company, operational and compliance data used throughout the application.
CoversCompany Profile, Customer, Product Types, Departments, Contractors, Locations, Checklist Templates, Vehicle Configuration, Road Train Combinations, Fitness for Work Questions, Fatigue Rules, Roles, Sync Status, Appearance, Terms & Conditions, Storage, About.

Main Settings Screen

Settings main screen — configuration groups, Storage and About.
Settings main screen — configuration groups, Storage and About.
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

Settings Groups & Subgroups

Company & Reference DataCompany Profile · Customer · Product Types · Departments · Contractors · Locations
Fleet, Safety & ComplianceChecklist Templates · Vehicle Configuration · Road Train Combinations · Fitness for Work Questions · Fatigue Rules
Access & SystemRoles · Sync Status · Appearance · Terms & Conditions
Storage & AboutTimesheets · Logbook · Pending Sync Items · App Name · Version
Module · Settings · Section 1

Company Profile

Stores and manages the transport company's core business, contact, compliance and operational information, used throughout the application.

Company Profile — identity, contact and registered address fields.
Company Profile — identity, contact and registered address fields.
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

Purpose

Company Profile is used to store and manage the transport company’s core business, contact, compliance and operational information. This information is used throughout the Fidentra application.

Navigation

Login → Settings → Company Profile → Identity → Enter Details → Save

Step-by-Step

1

Open Settings from the main navigation menu.

2

Select Company Profile.

3

Open the Identity section.

4

Select Upload Logo and upload the company logo.

5

Enter the Legal Entity Name.

6

Enter the Trading Name.

7

Enter the ABN.

8

Select the appropriate Industry.

9

Review the entered information.

10

Select Save.

Structure

SETTINGS
│
└── Company Profile
   │
   ├── Identity — Upload Logo, Legal Entity Name, Trading Name, ABN, Industry
   ├── Contact — Primary Phone, Primary Email, Primary Website
   ├── Registration Address — Street Address, Address Line 2, Suburb, State, Postcode
   ├── Compliance — Fatigue Management, NHVAS Accreditation No., NHVAS Modules, Record Retention Years, Insurance Policy No., Insurance Expiry, Accreditation Expiry
   ├── Operations — Time Zone, Distance Management, Week Started
   ├── Logbook — Driver Certification Declaration
   ├── Logbook Flags — Email Recipients
   ├── Fault Report — Email Recipients
   ├── Load Bridge — Email Recipients
   ├── Job Types — Job Order, Completion Declaration, Labour Sign-off
   └── Account — Storage, Allowance, Company ID
Expected Result: The company identity information is saved successfully and is available for use throughout the Fidentra application. Note: field-level steps for Contact, Registration Address, Compliance, Operations, Logbook, Logbook Flags, Fault Report, Load Bridge, Job Types and Account are pending confirmation and will be added in a future revision.
Module · Settings · Section 2

Customer

Create, manage and track the clients of the transport company; linked to Job Orders, Invoicing and Load assignments.

Purpose

The Customer section is used to create, manage and track the clients of the transport company. Customer records are used to link details in Job Orders, Invoicing and Load assignments.

Navigation

Settings → Customer → Add Customer → Enter Customer Details → Save

Step-by-Step

1

Open Settings from the main navigation menu.

2

Select Customer.

3

Select Add Customer from the top-right corner.

4

Enter the Customer Name (business / legal name).

5

Enter the Contact Person name.

6

Enter the Phone Number.

7

Enter the Email Address.

8

Enter the Billing Address: Street Address, Address Line 2, Suburb, State, Postcode.

9

Enter the ABN (if applicable).

10

Select the Customer Type, if configured (e.g. Regular, Contract, One-Off).

11

Ensure the Active option is switched ON if the customer should be available for use.

12

Review the entered information.

13

Select Save.

Structure

Editing: Open Customer → select record → Edit → change details → Save.

Deleting: Open the customer’s three-dot menu → Delete → confirm. Confirm the customer is not linked to any active Job Orders, Invoices or ongoing business processes first.

Searching: Use the Search field at the top of the page.

Pagination: Large customer lists are divided into pages.

Expected Result: The customer record is saved successfully and displayed in the Customer list. It becomes available for selection in Job Orders and other relevant workflows.
Module · Settings · Section 3

3. Product Types

Maintain the product-type reference list used throughout operational workflows.

Product Types — searchable list with edit and delete actions.
Product Types — searchable list with edit and delete actions.
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

Purpose. Product Types maintain the reusable list of commodities/materials that are hauled or handled — this is what a Log Book, Load Record or dispatch transaction records as the cargo, not a spare-part or consumable. The supplied Product Types screen provides a searchable list with row-level edit and delete actions.

Navigation

Settings → Product Types

Main screen

ItemHow it is used
SearchSearch product types by name.
Product Type NameThe list displays the configured commodity/material name.
EditUse the row edit action to change an existing product type.
DeleteUse the row delete action to remove a product type that is no longer required.
Pagination / countThe supplied screen shows a paged list and indicates how many product types are displayed.

Typical bulk-haulage product types

Iron OreConfigured product type.
SilicaConfigured product type.
LimestoneConfigured product type.
FertilizerConfigured product type.
GypsumConfigured product type.
GrainsConfigured product type.
Blue MetalConfigured product type.
GoldConfigured product type.
CopperConfigured product type.
These are examples of the commodity names a site typically maintains here — the actual list is configured per site and can include any material that is hauled (e.g. coal, bauxite, sand, aggregate, manganese) rather than parts or workshop consumables.
Expected Result: Product Types are available as maintained commodity/material reference values wherever the application records what is being carried — Log Book, Load Record and related operational screens.
Module · Settings · Section 4

4. Departments

Create organisational departments used when assigning users and assets.

New Department — confirmed Name field with Cancel and Create actions.
New Department — confirmed Name field with Cancel and Create actions.
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

Purpose. Departments provide the organisational grouping used when assigning users/employees and assets to business areas.

Navigation and workflow

↓
↓
↓

Confirmed Create fields

Field / actionTraining use
NameEnter the department name.
CancelClose the New Department dialog without creating a record.
CreateCreate the department using the entered name.

Department examples supplied in the demo data

#Department
1Linehaul Operations
2Metro & Regional Operations
3Bulk Haulage Operations
4Heavy Haulage
5Fleet & Maintenance
6Workshop
7Yard Operations
8Safety & Compliance
9Driver Operations
10Scheduling & Dispatch
11Administration
12Finance & Accounts
13Human Resources
14Management
Expected Result: The new department becomes available as a Department selection in records such as users/employees and assets.
Module · Settings · Section 5

5. Contractors

Maintain external contractor and service-provider names.

New Contractor — confirmed Name field with Cancel and Create actions.
New Contractor — confirmed Name field with Cancel and Create actions.
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

Purpose. Contractors maintain the contractor names used by the application when a record needs to identify an external contractor or service provider.

Navigation and workflow

↓
↓
↓

Confirmed Create fields

Field / actionTraining use
NameEnter the contractor name.
CancelClose the New Contractor dialog without creating a record.
CreateCreate the contractor using the entered name.

Example contractor names supplied

Pilbara Heavy Haulage Pty LtdContractor example.
Goldfields Freight Services Pty LtdContractor example.
Kewdale Diesel & Fleet Services Pty LtdContractor example.
Welshpool Heavy Vehicle Repairs Pty LtdContractor example.
Pilbara Mobile Mechanical Pty LtdContractor example.
WA Heavy Vehicle Recovery Pty LtdContractor example.
WestRoad Tyre Services Pty LtdContractor example.
WA Mobile Welding Services Pty LtdContractor example.
Important: The supplied New Contractor screen confirms only a Name field. Contact, ABN, email and address fields are not shown in the supplied contractor screen, so they are not documented here as editable contractor fields.
Expected Result: The contractor is created and is available for selection in records that use the Contractor reference.
Module · Settings · Section 6

6. Locations

Maintain depots, loading/unloading points, terminals and operational sites.

Locations — Name, Type and Address list with search, filtering and row actions.
Locations — Name, Type and Address list with search, filtering and row actions.
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

Purpose. Locations maintain operational sites used for loading, unloading, depots and customer/site destinations. The supplied list screen shows Name, Type and Address, with search, type filtering, edit and delete actions.

Navigation

Settings → Locations

Main screen and fields

Field / controlTraining use
Search locations by nameFilter the list by location name.
TypeFilter the list by location type. The supplied data uses Loading Point, Unloading Point, and Loading & Unloading.
NameIdentifies the depot, terminal, customer site, yard or operational location.
AddressStores/displays the location address.
EditOpen the row edit action to update the location.
DeleteRemove a location that is no longer required.
Pagination / countThe list indicates how many locations are being shown.

Location types and examples from the supplied data

NameTypeAddress
Fidentra Welshpool Main DepotLoading & Unloading18 Meridian Drive, Welshpool WA 6106
Kewdale Freight TerminalLoading & Unloading34 Logistics Drive, Kewdale WA 6105
Fremantle Port Freight FacilityLoading & Unloading12 Harbour Link Road, Fremantle WA 6160
Pilbara Mining Supplies - KarrathaUnloading Point28 Industrial Avenue, Karratha WA 6714
Wheatbelt Grain Depot - NorthamLoading Point16 Grain Terminal Road, Northam WA 6401
Southern Cross Logistics DepotLoading & Unloading41 Freight Way, Forrestfield WA 6058
Geraldton Regional Freight DepotLoading & Unloading26 Industrial Road, Geraldton WA 6530
Albany Freight FacilityLoading & Unloading14 Transport Avenue, Albany WA 6330

Operational use

Expected Result: Locations are available as consistent operational reference values in workflows that require depot, loading, unloading or site selection.
Module · Settings · Section 7

Checklist Templates

Create reusable checklists for vehicle and operational inspections such as Pre-Start, Post-Trip and Service checks.

Checklist Templates — search, type filter, template list and actions.
Checklist Templates — search, type filter, template list and actions.
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.
New Checklist Template — template details, checklist items and item type choices.
New Checklist Template — template details, checklist items and item type choices.
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

Purpose

Checklist Templates are used to create reusable checklists for vehicle and operational inspections such as Pre-Start, Post-Trip and Service checks.

Navigation

Settings → Checklist Templates → New Template → Enter Template Details → Add Checklist Items → Select Item Type → Activate Template → Save

Step-by-Step

1

Open Settings.

2

Select Checklist Templates.

3

Select New Template from the top-right corner.

4

Enter the Template Name.

5

Select the required Category: Pre-Start, Post-Trip, Service.

6

Enter the first Checklist Item / Question.

7

Select the appropriate Item Type: Pass / Fail, Text, Number, Photo.

8

To add additional questions, select Add Items.

9

Ensure the Active option is switched ON if the template should be available for use.

10

Select Save.

Structure

Editing: Open the template → Edit → modify name, category or items → remove unwanted items with the Remove icon → Save.

Deleting an item: Select the Remove/Delete icon beside the item.

Deleting a template: Three-dot menu → Delete Template → confirm.

Searching: Use the Search field. Filtering: Use All Types / Pre-Start / Post-Trip / Service. Pagination: large lists are divided into pages.

Expected Result: The checklist template is saved and displayed in the Checklist Templates list.
Module · Settings · Section 8

Vehicle Configuration

Define vehicle/asset types and their associated axle groups and vehicle images.

Navigation Workflow

1. SettingsOpen configuration
→
2. Vehicle ConfigurationSelect vehicle / asset type
→
3. Add Vehicle TypeEnter the group name
→
4. Add Axle GroupName + image
→
5. SaveConfiguration becomes available

Purpose

Vehicle Configuration is used to define vehicle/asset types and their associated axle groups and vehicle images. Examples: Prime Mover, Rigid Truck, Semi-Trailer, Car Dolly, Dog Trailer, UTE, Excavator, Forklift, Loader.

Navigation

Settings → Vehicle Configuration → Add Vehicle Type → Vehicle / Asset Group → Add Axle Group → Axle Group Name + Image → Save

Step-by-Step

1

Open Settings → Vehicle Configuration.

2

Select Add Vehicle Type.

3

Enter the vehicle/asset group name (e.g. Prime Mover).

4

Select Save — the vehicle type now appears on the Vehicle Configuration page.

5

Adding an Axle Group: select the vehicle configuration (e.g. Prime Mover).

6

Select Add Axle Group.

7

Enter the Axle Group Name.

8

Upload the corresponding vehicle/axle-group image.

9

Select Save.

Structure

Prime Mover
│
├── Axle Group 1
│  └── Vehicle Image
├── Axle Group 2
│  └── Vehicle Image
└── Axle Group 3
   └── Vehicle Image

Editing an Axle Group: open the configuration → select the image/configuration → three-dot menu → Edit → change name/image → Save.

Renaming: three-dot menu → Rename → enter new name → Save.

Deleting: delete a configuration or image only when no longer required by the business.

Module · Settings · Section 9

Road Train Combinations

Define approved vehicle combinations using trucks, dollies and trailers configured in the system.

Road Train Combinations — configured combinations and Add Combination action.
Road Train Combinations — configured combinations and Add Combination action.
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

Purpose

Road Train Combinations are used to define approved vehicle combinations using trucks, dollies and trailers configured in the system.

Navigation

Settings → Road Train Combinations → Add Combination → Combination Name → Add Trailer → Select Assets → Select Combination Image → Save

Step-by-Step

1

Open Settings → Road Train Combinations.

2

Select Add Combination.

3

Enter the Combination Name.

4

Select Add Trailer.

5

Available configured assets are displayed: Truck, Prime Mover, Dolly, Trailer, Dog Trailer, Semi-Trailer.

6

Select the assets required for the combination.

7

Select the appropriate Combination Image.

8

Select Save.

Expected Result:

Editing: open the combination → Edit → change assets/details → Save.

Deleting: combination’s three-dot menu → Delete.

Module · Settings · Section 10

Fitness for Work Questions

Capture driver fitness information before work activities.

Fitness for Work Questions — configurable questions and risky-answer selections.
Fitness for Work Questions — configurable questions and risky-answer selections.
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

Purpose

Fitness for Work Questions are used to capture driver fitness information before work activities.

Navigation

Settings → Fitness for Work Questions → Add Question → Enter Question → Define Answer → Save

Step-by-Step

1

Open Fitness for Work Questions.

2

Select Add Question.

3

Enter the required question.

4

Configure the available response, such as Yes / No.

5

Select Save — the question becomes available in the relevant driver workflow.

Expected Result:

Removing a question: select the Remove icon beside the question.

Module · Settings · Section 11

Fatigue Rules

Configured fatigue-management requirements used to monitor work, rest and break requirements and support fatigue breach notifications.

Fatigue Rules — Work & Rest Cycle settings.
Fatigue Rules — Work & Rest Cycle settings.
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.
Fatigue Rules — Corrective Action defaults and breach overrides.
Fatigue Rules — Corrective Action defaults and breach overrides.
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

Purpose

Fatigue Rules define the company’s configured fatigue-management requirements.

Navigation

Settings → Fatigue Rules → New Scheme (+) → Enter Fatigue Rules → Configure Work / Rest Requirements → Configure Cycle Rules → Save

Step-by-Step

1

Open Settings → Fatigue Rules.

2

Select New Scheme (+).

3

Enter the required fatigue-rule details.

4

Configure the relevant work, break and rest requirements.

5

Review the configured values.

6

Select Save.

11.1 Breaks from Driving

Defines the required break arrangement during driving/work periods.

Driving / Work Period → Required Break → Break Duration → Continue Work

Example: a company may require a 20-minute break after a defined work period, subject to its applicable fatigue-management rules. If the requirement is not met, the system can identify a fatigue-related breach and trigger the configured notification/email workflow.

11.2 Work and Rest Cycle

Defines the relationship between minimum continuous rest, maximum time between qualifying rest periods, work periods and required rest periods.

Work → Required Rest → Work → Required Rest → Continue Cycle

11.3 72-Hour Rest Requirement

Non-Work Hours Required127 (example)
Required Long Rest3 (example)
Assessment Period72 hours
Minimum Qualifying Non-Work Event30 (example)
Qualifying Long Rest Duration4.14 (example)

Training note: these values should be entered per the company’s approved fatigue scheme and not changed without authorisation.

11.4 14-Day Cycle

Period14 days
Work Time Limit168 hours
Required 24-Hour Rest2
Qualifying 24-Hour Rest1,440 minutes
Advisory Threshold150 / 156 / 162

14-Day Period → Monitor Work Time → Check Required Rest → Check Advisory Threshold → Identify Potential Breach

11.5 28-Day Cycle

Assessment Period28 days
Work Time Limit per 14-Day Sub-Window144 hours
Qualifying 24-Hour Rest1,440 minutes

28-Day Assessment → 14-Day Sub-Window → Check Work Time → Check Qualifying Rest → Continue Monitoring

11.6 Shift Change Rest

Consecutive Shift Days Threshold5
Required Rest Between Shift Changes24 hours
Assessment LogicAny Pattern Change / Different Shift Type Only

Any Pattern Change — assessed whenever the worker’s shift pattern changes. Different Shift Type Only — assessed only when the worker changes to a different shift type.

Current Shift → Shift Pattern Changes → Check Consecutive Days → Check Required Rest → Apply Fatigue Rule → Continue / Breach

Important: Fatigue-rule values are configuration data. Production values should be confirmed against the company’s approved fatigue-management scheme and applicable Western Australian requirements before activation.
Module · Settings · Section 12

Roles

Control user access and permissions within the Fidentra application.

Roles Workflow

SettingsOpen module
→
RolesView existing roles
→
Add / Edit / DeleteManage role configuration
→
Save / ConfirmApply the change

Purpose

Roles are used to control user access and permissions within the Fidentra application.

Navigation

Settings → Roles → View Existing Roles → Add New Role / Edit Role / Delete Role

Step-by-Step

1

Open Settings.

2

Select Roles.

3

Select Add New Role.

4

Enter the required role details and permissions.

5

Review the selected permissions.

6

Select Save.

Expected Result: The new role is created and displayed in the Roles list. Editing: open Roles → select role → Edit → modify → Save. Deleting: role’s action menu → Delete → confirm (only if not required by active users/processes).
Module · Settings · Section 13

Sync Status

Monitor whether application data has successfully synchronised: pending, failed, conflicts, or not yet synchronised.

Sync Status — sync health, conflicts, failed operations and pending items.
Sync Status — sync health, conflicts, failed operations and pending items.
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

Purpose

Sync Status allows users to monitor whether application data has successfully synchronised.

Navigation

Settings → Sync Status → Review Synchronisation (Pending / Failed / Conflict / Completed) → Sync Now or Sync Everything

Step-by-Step

1

Open Settings.

2

Select Sync Status.

3

Review the displayed synchronisation records.

4

Check whether any records have a status such as Pending, Failed, Conflict.

5

Select the relevant record to review its status/details.

6

For a specific pending item, select it then Sync Now and wait for completion.

7

Use Sync Everything when multiple records need to be synchronised.

Structure

PendingSynchronisation is waiting to be processed
FailedSynchronisation was not completed successfully
ConflictThe system has identified conflicting data
CompletedSynchronisation was completed successfully
Expected Result: The system processes the available synchronisation items and updates their status.
Module · Settings · Section 14

Appearance

Select the visual theme used by the application.

Appearance — System default, Light and Dark options.
Appearance — System default, Light and Dark options.
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

Purpose

The Appearance section allows users to select the visual theme used by the application.

Navigation

Settings → Appearance → Select Theme (System Default / Light Mode / Dark Mode)

Step-by-Step

1

Open Settings.

2

Select Appearance.

3

Select one of: System Default (follows the device setting), Light Mode, or Dark Mode.

Expected Result: The application interface changes according to the selected appearance setting.
Module · Settings · Section 15

Terms & Conditions

Access the terms applicable to the Fidentra application.

Terms & Conditions — application licence terms screen.
Terms & Conditions — application licence terms screen.
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

Purpose

The Terms and Conditions section provides access to the terms applicable to the Fidentra application.

Navigation

Settings → Terms & Conditions → View Terms → Read Application Terms

Step-by-Step

1

Open Settings.

2

Select Terms & Conditions.

3

Review the displayed terms.

4

Scroll through the document to read the complete content.

Expected Result: The application’s current Terms and Conditions are displayed for review.
Module · Settings · Section 16

Storage

Contains Timesheets, Logbook and Pending Sync Items data areas.

Settings main screen — configuration groups, Storage and About.
Settings main screen — configuration groups, Storage and About.
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

Purpose

The Storage area groups Timesheets, Logbook and Pending Sync Items.

Structure

Status: Pending. Field-level details for Storage (Timesheets, Logbook, Pending Sync Items) have not yet been provided. This section will be completed once configuration details are confirmed.

Module · Settings · Section 17

About

Displays App Name and Version.

Settings main screen — configuration groups, Storage and About.
Settings main screen — configuration groups, Storage and About.
Click the screenshot to enlarge it. Enhanced for clearer, brighter text.

Purpose

The About area displays the application name and version.

Structure

Status: Pending. Field-level details for About (App Name, Version) have not yet been provided. This section will be completed once configuration details are confirmed.

Module · Settings · Reference

Setting — Groups & Subgroups Reference

Every Setting section (Main Group), its subsections (Subgroup), and the specific fields or data captured in each.

Main GroupSubgroupFields / Data
1. Company ProfileIdentityUpload Logo, Legal Entity Name, Trading Name, ABN, Industry
ContactPrimary Phone, Primary Email, Primary Website
Registration AddressStreet Address, Address Line 2, Suburb, State, Postcode
ComplianceFatigue Management, NHVAS Accreditation No., NHVAS Modules, Record Retention Years, Insurance Policy No., Insurance Expiry, Accreditation Expiry
OperationsTime Zone, Distance Management, Week Started
LogbookDriver Certification Declaration
Logbook FlagsEmail Recipients
Fault ReportEmail Recipients
Load BridgeEmail Recipients
Job TypesJob Order, Completion Declaration, Labour Sign-off
AccountStorage, Allowance, Company ID
2. CustomerCustomer DetailsCustomer Name, Contact Person, Phone Number, Email Address, ABN, Customer Type, Active Status
Billing AddressStreet Address, Address Line 2, Suburb, State, Postcode
3–6. Product Types / Departments / Contractors / LocationsStatusDetailed training content added from supplied screens and datasets
7. Checklist TemplatesTemplate DetailsTemplate Name, Category (Pre-Start, Post-Trip, Service), Active Status
Checklist ItemsItem 1, Item 2, Item 3, Item 4, Add Items (Item 5, Item 6, …)
Item TypesPass / Fail, Text, Number, Photo
8. Vehicle ConfigurationVehicle / Asset TypesPrime Mover, Rigid Truck, Semi-Trailer, Car Dolly, Dog Trailer, UTE, Excavator, Forklift, Loader
Axle Groups (per Vehicle Type)Axle Group 1, Axle Group 2, Axle Group 3 — each with an Axle Group Name and Vehicle Image
9. Road Train CombinationsCombination DetailsCombination Name, Combination Image
AssetsTruck, Prime Mover, Dolly, Trailer, Dog Trailer, Semi-Trailer
10. Fitness for Work QuestionsQuestion SetupQuestion Text, Response Type (e.g. Yes / No)
11. Fatigue Rules11.1 Breaks from DrivingDriving/Work Period, Required Break, Break Duration
11.2 Work and Rest CycleMinimum Continuous Rest, Maximum Time Between Qualifying Rest, Work Periods, Required Rest Periods
11.3 72-Hour Rest RequirementNon-Work Hours Required, Required Long Rest, Assessment Period, Minimum Qualifying Non-Work Event, Qualifying Long Rest Duration
11.4 14-Day CyclePeriod, Work Time Limit, Required 24-Hour Rest, Qualifying 24-Hour Rest, Advisory Threshold
11.5 28-Day CycleAssessment Period, Work Time Limit per 14-Day Sub-Window, Qualifying 24-Hour Rest
11.6 Shift Change RestConsecutive Shift Days Threshold, Required Rest Between Shift Changes, Assessment Logic
12. RolesRole ManagementAdd New Role, Edit Role, Delete Role, Permissions
13. Sync StatusStatus GuidePending, Failed, Conflict, Completed
14. AppearanceThemeSystem Default, Light Mode, Dark Mode
15. Terms & ConditionsTermsView / Read Application Terms
16. StorageData AreasTimesheets, Logbook, Pending Sync Items
17. AboutApp InfoApp Name, Version
User Module

User Management & Roles / Permissions

Step-by-step training for creating and maintaining user accounts, learning assignments, documents, notifications, signing requests, and role-based access.

The User module is the workforce-account management area. It contains two core working areas: User Management for account records and Roles & Permissions for access control.

User ManagementCreate, search, filter, export and maintain user accounts.
Learning & RecordsAssign learning forms/courses, store documents, and configure notifications.
SignerCreate and review signing requests for documents that require acknowledgement/signature.
Roles & PermissionsUnderstand the access available to Company Admin, Driver and Mechanic roles.
User Management main screen — user list, status, role and list actions
User Management main screen — user list, status, role and list actions
Click the image to enlarge. The enhanced copy uses higher contrast and brightness for training readability.
User · Navigation

Navigation & Module Map

Clear subgroups for the User module.

User
Left Navigation
→
User Page
User Management
Roles & Permissions
User Management subgroup
  • Search & Filter
  • Export
  • All / Active / Inactive user lists
  • Add User
  • Manage Existing User
  • Learning Forms
  • Courses
  • Documents
  • Notifications
  • Signer
Roles & Permissions subgroup
  • Company Admin access
  • Driver access
  • Mechanic access
  • Full / View Only / No Access definitions
Navigation: Left menu → User → choose the required subgroup from the expanded menu.
User · User Management

User Management Workspace

The main working screen for handling user accounts.

The workspace combines the search bar, filters, export, Add User action and categorised user list. Use it as the starting point for day-to-day account administration.

SearchFind users by name, email ID or role.
FilterNarrow by status and role.
ExportExport the currently displayed list, including active search/filter conditions.
User ListsSwitch between All Users, Active and Inactive.
User Management workspace — complete list view
User Management workspace — complete list view
Click the image to enlarge. The enhanced copy uses higher contrast and brightness for training readability.
User · User Management

Search, Filter, Export & User Lists

Search Bar

Search users by Name, Email ID or Role.

Filter

Filter GroupOptions
All StatusActive / Inactive
All RolesMaster Admin / Company Admin / Driver / Mechanic

Choose the required combination and select Done. Only matching users are displayed.

Export

The Export action exports the currently displayed user list and respects the active search and filter selections.

List Views

All UsersEvery user created through Add User.
ActiveOnly users currently marked Active.
InactiveOnly users currently marked Inactive.
PaginationMultiple users are divided across Page 1, Page 2, Page 3 and so on.
User · User Management

Add New User

Complete the account, personal, compliance, shift/pay and fatigue-scheme details.

Add User form — account and user details
Add User form — account and user details
Click the image to enlarge. The enhanced copy uses higher contrast and brightness for training readability.

Clear Add User workflow

1. Click
“Add User”
→
2. Basic Details
Name, Email, Password, Role
→
3. Personal Details
Phone, Dept, Position, Trade, Address, Emergency Contact
→
4. Licence & Medical
Number, Expiry, Certificate
5. Shift & Pay
Start/End Time, Pay Rate
→
6. Fatigue Scheme
Default or selected scheme + date
→
Create
Record is added

Fields required to create a user

FieldDetails / Options
Full NameUser's full name.
Email IDUsed as login ID.
Temporary PasswordSet by admin; user changes it on first login.
RoleMaster Admin / Company Admin / Driver / Mechanic.
Phone NumberContact number.
DepartmentDepartment the user belongs to.
PositionJob position / title.
TradeTrade or specialisation.
AddressResidential address.
Emergency Contact NameName of emergency contact.
Emergency Contact NumberPhone number of emergency contact.
Date of JoiningDate the user joined.
Date of BirthUser's date of birth.
Licence NumberDriving / trade licence number.
Licence Expiry DateExpiry date of the licence.
Medical Certificate StatusValid / Expired / Pending Renewal.
Medical Certificate Expiry DateExpiry date of the medical certificate.
Shift Start TimeStart of the user's shift.
Shift End TimeEnd of the user's shift.
Pay RateUser's pay rate.
Fatigue SchemeAuto-applies the default scheme from Fatigue Rules, or select a specific scheme together with a Scheme Date.

Save options

Save OfflineSaves locally and syncs automatically when the device is online again.
CreateSubmits the form and creates the user record immediately.
CancelDiscards the form without saving.
User · User Management

Manage an Existing User

Clear management workflow

User record in
“All Users”
→
Pencil icon
Edit fields
→
Save
User record
→
Three-dot menu
→
View Details
Deactivate / Activate
Existing user details — profile tabs and management actions
Existing user details — profile tabs and management actions
Click the image to enlarge. The enhanced copy uses higher contrast and brightness for training readability.
User · Training & Records

Learning Forms

Assign forms already created in the Learning module.

Learning Forms — assigned learning forms and assignment controls
Learning Forms — assigned learning forms and assignment controls
Click the image to enlarge. The enhanced copy uses higher contrast and brightness for training readability.
ActionBehaviour
Assign FormDisplays the list of existing learning forms for selection.
UploadAttaches the selected form to the user.
Send MailEmails the assigned form to the user. If not selected, the form remains listed under Assigned without email delivery.
CourseUsed to upload learning documents/courses for the user.
User · Training & Records

Courses

View and manage learning course assignments linked to the user.

Courses / assigned learning content for the selected user
Courses / assigned learning content for the selected user
Click the image to enlarge. The enhanced copy uses higher contrast and brightness for training readability.
The source guide identifies the Course area as the place used to upload or manage learning documents/courses for the user.
User · Training & Records

Documents

Files and images stored against a user record.

Documents — uploaded user files with list actions
Documents — uploaded user files with list actions
Click the image to enlarge. The enhanced copy uses higher contrast and brightness for training readability.

Uploaded documents can be viewed or edited from this section. Use the list controls to work with the user-specific records shown in the document area.

User · Training & Records

Notifications

Control system and email alerts for the selected user.

Notifications — system notification and email selections
Notifications — system notification and email selections
Click the image to enlarge. The enhanced copy uses higher contrast and brightness for training readability.
Notification EventBehaviour
Maintenance PolicySystem event enabled by default; mail checkbox sends an email for this event only.
Job Order FormSystem event enabled by default; mail checkbox sends an email for this event only.
LogbookSystem event enabled by default; mail checkbox sends an email for this event only.
Fatigue BreachSystem event enabled by default; mail checkbox sends an email for this event only.
Load BreachSystem event enabled by default; mail checkbox sends an email for this event only.
Course CompletionSystem event enabled by default; mail checkbox sends an email for this event only.

A Refresh action reloads the page and shows the latest data.

User · Training & Records

Signer / Signing Requests

Send documents for signature and review signing request details.

Signer tab — documents for signature and current request status
Signer tab — documents for signature and current request status
Click the image to enlarge. The enhanced copy uses higher contrast and brightness for training readability.

Create a signing request

Create Signing Request — request title, signer, email, expiration and reminder
Create Signing Request — request title, signer, email, expiration and reminder
Click the image to enlarge. The enhanced copy uses higher contrast and brightness for training readability.
  1. Open the Signer tab for the user.
  2. Select Send document.
  3. Confirm the request title.
  4. Select the signer name and verify the email address.
  5. Choose an expiration period and reminder frequency.
  6. Select Review.

Review before sending

Review Signing Request — document, recipient, signing order and expiration
Review Signing Request — document, recipient, signing order and expiration
Click the image to enlarge. The enhanced copy uses higher contrast and brightness for training readability.

The review screen shows the document, recipient, signing order and expiration before the request is sent.

Signing request review — final confirmation before Send for Signature
Signing request review — final confirmation before Send for Signature
Click the image to enlarge. The enhanced copy uses higher contrast and brightness for training readability.
User · Access & Reference

Roles & Permissions

Access by role across the FidentraOS modules.

Roles & Permissions — role access matrix in the application
Roles & Permissions — role access matrix in the application
Click the image to enlarge. The enhanced copy uses higher contrast and brightness for training readability.
Access meanings: Full = fully accessible; View Only = visible but not editable; — = not available to that role.
ModuleCompany AdminDriverMechanic
My PlaceFullFullFull
AssetFullView OnlyView Only
LogbookFullFull—
Job OrderFull—Full
Job RequestFull—Full
Load RecordFullFull—
Maintenance PolicyFull——
FilesFull——
LearningFull——
UsersFull——
SettingsFullView OnlyView Only
FatigueFullFullFull
User · Access & Reference

Quick Reference Summary

User
→
Search / Filter
→
Add or Select User
→
Maintain Details & Records
→
Save / Send / Assign
Help

Getting Support

Where to go when you need a hand.

For assistance with FidentraOS, contact your system administrator or the FidentraOS team.

Placeholder — insert official support email, phone number, or help portal URL.
Learning Module

Learning Module — Overview

Create, distribute and track learning activities for users.

The Learning Module contains two independent content areas: Learning Forms and Learning Document. Both can be sent to users by email, responses can be tracked, and the content can be edited, deleted or refreshed.

Learning FormsQuestion-and-answer forms where each question has its own title and URL/link.
Learning DocumentUploaded learning material with multiple-choice questions and optional refresher interval.
SignerCreate signing templates, assign requests, monitor status and review auto-log history.
Learning module — Learning Forms list
Learning module — Learning Forms list
Click the image to enlarge. Enhanced brightness, contrast and sharpness improve training readability.
Learning · Introduction

Navigation Map

How users reach the two main learning areas.

Navigation path: Main Menu → Learning Module → Learning Forms / Learning Document
Navigation path: Main Menu → Learning Module → Learning Forms / Learning Document
Click the image to enlarge. Enhanced brightness, contrast and sharpness improve training readability.
Main Menu
→
Learning Module
→
Learning FormsTab 1
Learning DocumentTab 2
Learning · Learning Forms

Purpose & Create a Learning Form

Learning Forms are short questionnaires made up of one or more questions. Each question has a title and valid URL. Forms are sent by email and responses are tracked automatically.

Learning Forms list
Learning Forms list
Click the image to enlarge. Enhanced brightness, contrast and sharpness improve training readability.
New Learning Form screen
New Learning Form screen
Click the image to enlarge. Enhanced brightness, contrast and sharpness improve training readability.
  1. Open Learning → Learning Forms.
  2. Click New Learning Form.
  3. Enter the Form Title and Description.
  4. Enter the Question Title and relevant URL.
  5. Use Add Questions to add more questions as required.
  6. Click Create Form. The new form becomes available under Learning Forms.
Learning · Learning Forms

Assign to User & Complete

Assign the form

  1. Go to the User module.
  2. Select the required user and open the user's View page.
  3. Open Learning Form and click Assign Learning Form.
  4. Select the required form.
  5. Click Send Mail to send it to the user's email.
Assign Learning Form — selection list
Assign Learning Form — selection list
Click the image to enlarge. Enhanced brightness, contrast and sharpness improve training readability.
Assigned Learning Forms for a selected user
Assigned Learning Forms for a selected user
Click the image to enlarge. Enhanced brightness, contrast and sharpness improve training readability.

Complete the form

  1. Open the learning form from the received email.
  2. View the learning content.
  3. Answer the questions.
  4. If required, upload the relevant file.
  5. Complete and submit the form.
Invitation sent confirmation
Invitation sent confirmation
Click the image to enlarge. Enhanced brightness, contrast and sharpness improve training readability.
Learning · Learning Forms

Workflow & Tracking

The form workflow moves from creation to user assignment, email delivery, completion and response tracking.

Learning Form workflow — create, assign, complete and track status
Learning Form workflow — create, assign, complete and track status
Click the image to enlarge. Enhanced brightness, contrast and sharpness improve training readability.
Create Form
→
Assign to User
→
Send by Email
→
User Completes
→
Track Responses

After submission, open the Learning Form page to see the number of questions, sent count, sent date/time and user response information.

Learning · Learning Forms

Manage an Existing Form

OptionUse
Edit / Edit FormReopen the form to change the title, description or questions.
DeletePermanently remove the form when it is no longer needed.
RefreshReload the Learning Forms list after changes.
Learning · Learning Documents

Purpose & Create a Learning Document

Learning Document is used when training material is an actual file—such as an image, PDF or Word file—combined with multiple-choice questions. It also supports a Refresher Interval in days.

Learning Documents list
Learning Documents list
Click the image to enlarge. Enhanced brightness, contrast and sharpness improve training readability.
New Learning Document screen
New Learning Document screen
Click the image to enlarge. Enhanced brightness, contrast and sharpness improve training readability.
  1. Open Learning → Learning Documents.
  2. Click New Learning Document.
  3. Enter Document Title, Description and Refresher Interval.
  4. Under Instruction Document, choose the required file.
  5. Add Question 1 and the required choices.
  6. Use Add Choice for additional choices, up to 7 per question.
  7. Use Add Question for more questions.
  8. Click Create Document.
Learning · Learning Documents

Assign to User & User Response

Assign the document

  1. Open the User module and select the required user.
  2. Open the user's details and select Course.
  3. Click Assigned Document.
  4. Select the required Learning Document. It is assigned/sent to the user's registered email address.

User response

  1. Open the email and view the assigned document.
  2. Review the document and select the appropriate choice for each question.
  3. Click Submit.
  4. Open the relevant Learning Form/Document page to view total questions, sent count and submitted responses.
Learning · Learning Documents

Workflow & Tracking

Learning Document workflow — create, assign, respond and view response
Learning Document workflow — create, assign, respond and view response
Click the image to enlarge. Enhanced brightness, contrast and sharpness improve training readability.
Create Document
→
Assign to User
→
Email Sent
→
User Responds
→
View Response
Learning · Learning Documents

Manage an Existing Document

OptionUse
EditChange title, description, refresher interval, file or questions.
DeletePermanently remove the document.
RefreshReload the Learning Document list.
Learning · Signer

Signer Workflow

The Signer area contains Dashboard, Templates, Requested Document and Auto Log.

Signer Dashboard — total, pending, completed, declined and expired requests
Signer Dashboard — total, pending, completed, declined and expired requests
Click the image to enlarge. Enhanced brightness, contrast and sharpness improve training readability.
Create Signer Template
Create Signer Template
Click the image to enlarge. Enhanced brightness, contrast and sharpness improve training readability.
Signer Requested Documents
Signer Requested Documents
Click the image to enlarge. Enhanced brightness, contrast and sharpness improve training readability.
Signer Auto Log
Signer Auto Log
Click the image to enlarge. Enhanced brightness, contrast and sharpness improve training readability.
  1. Open Learning → Signer.
  2. Use Dashboard to review request totals and status.
  3. Open Templates and select Create Template.
  4. Enter Template Name, Description and Category such as HR, Legal, Safety or Operations.
  5. Upload the required PDF and click Next.
  6. Go to the User module and assign the template to the required user.
  7. The user receives the request by email, prepares the PDF, adds a signature and submits.
  8. Use Requested Document to track status and Auto Log to review activity such as Created, Pending, Completed and Cancelled.
Create Template
→
Assign User
→
Email Sent
→
User Signs
→
Status Updated
→
Auto Log
Learning · Reference

Quick Reference Summary

FeatureLearning FormsLearning Document
Content typeQuestion title + URL linkUploaded file + multiple-choice questions
Answer formatRecipient follows the link and answersRecipient selects a choice per question
Repeats automatically?NoYes, based on Refresher Interval (days)
Tracking tabsResponses, InvitationsResponses, Invitations
Management optionsEdit, Delete, RefreshEdit, Delete, Refresh
Training note: Double-check the recipient's email ID before sending, and confirm delivery using the Invitations tab.