Completion Fields

Completion Fields are used to capture what happened when work was finished. They appear when a Work Order is marked as Complete and provide important detail about outcomes, causes, and observations.

Completion Fields support analysis, learning, and continuous improvement by recording more than just the fact that work was done.

What Completion Fields are

Completion Fields record final outcome information for a Work Order.

They answer key questions such as:

  • Was there a failure?
  • What caused the issue?
  • What symptoms were observed?
  • What was done to complete the work?

These fields are recorded at the end of the maintenance process and become part of the permanent Work Order history.

How Completion Fields work

Completion Fields are status-driven.

When a Work Order status is changed to Complete:

  • Scheduling and progress fields are no longer editable
  • Completion Fields become visible
  • Required completion information must be entered before saving

Completion Fields

The following fields are shown when completing a Work Order.

Field name Required Description
Complete Date Yes Date and time the Work Order was completed. Automatically set when status changes to Complete, but can be adjusted if required.
Failure No Indicates whether the work was the result of a failure. Used for reliability analysis.
Cause No Classification of the underlying cause of the issue. Supports root cause analysis.
Symptom No Observed symptom that led to the Work Order being raised.
Completion Notes No Free-text notes describing the work performed, findings, or outcomes.

Some fields may be configured as mandatory depending on system rules.

Completing a Work Order

Completion Fields are entered when the Work Order is finished.

To complete a Work Order:

  1. Open the Work Order.
  2. Confirm all work has been carried out.
  3. Change the Status to Complete.
  4. Review the Complete Date.
  5. Enter Failure, Cause, and Symptom if applicable.
  6. Add Completion Notes with relevant detail.
  7. Save the Work Order.

The Work Order is now closed and moved to the Complete category.

Where Completion Fields apply

Completion Fields apply only to:

  • Work Orders
  • Completed maintenance records
  • Reporting, dashboards, and analysis

They do not apply to Tasks or Events.

How Completion Fields are used

Completion Fields are commonly used to:

  • Identify failure-driven maintenance
  • Support root cause and reliability analysis
  • Improve preventative maintenance programs
  • Track recurring issues and symptoms
  • Provide detailed work history for audits and reviews

Accurate completion data improves decision-making.

Pre-requisites

Before completing a Work Order:

  • The Work Order should be In Progress
  • All required work and records should be finalised
  • Users must have permission to complete Work Orders
  • Reference tables for Failure, Cause, and Symptom must be configured if used

Example of Completion Fields in use

A breakdown Work Order is completed.

The technician records:

  • Failure: Yes
  • Symptom: Loss of power
  • Cause: Turbocharger bearing failure
  • Completion Notes: Replaced turbocharger and tested under load

This information supports future failure trend analysis and maintenance planning.

Important considerations and best practices

  • Complete Work Orders promptly after work finishes
  • Use Failure, Cause, and Symptom consistently
  • Provide clear and factual Completion Notes
  • Avoid leaving Completion Fields blank for failure-related work
  • Do not reopen completed Work Orders unless correcting genuine errors
  • Completion data is critical for reliability and continuous improvement initiatives

Completion Fields turn completed Work Orders into valuable operational data, not just closed tasks.