Who is this article for?

Administrators who need to understand the non-conformance raising functionality.

No special access or permissions are required.

There are two main controls that determine the availability of the option to raise a non-conformance.

This article explains them in more detail.

1. Status logic

The option to raise a non-conformance is only available when a record status is set to Performed, which is the expected behaviour.

It remains disabled in other statuses like Draft or Planned.

This restriction is by design and cannot be changed through standard configuration, ensuring non-conformances are raised only after the activity is performed.

Note
If you require non-conformances to be raised at different stages in your process, open a ticket with us to discuss potential customization options.

2. Permissions

Even when the status is correct, the user must have the appropriate permissions to raise a non-conformance from that module.

Users also need access to the CA/PA module if non-conformances are managed there. Without the right permissions, the option will remain disabled.