Competency Requirements

The Competency Requirements page is the catalogue of competences the laboratory requires: one row per competence, for one of the activities that are gated on authorisation (ISO/IEC 17025 §6.2.2, §6.2.5(a)). A requirement may optionally be scoped to a single method or instrument. The page does not say who is competent — that is User Competencies — it says what is required.

Found under: ISO 17025 → Personnel & Competency → Competency Requirements.

Button	Action
	Add — Create a new record
	Columns — Show/hide table columns
	Filters — Open/close the filter panel. A red dot indicates active filters
	Export CSV — Download table data as a CSV file
	Orientation — Toggle between portrait and landscape printing
	Print — Generate a PDF of the current view
	Help — Open the help dialog
	Search — Quick search through table data

Record Actions

Clicking the icon on each row shows:

Edit — Open the edit form
Delete — Delete the record (with confirmation)

Fields

Field	Description
Requirement Name	How the competence is referred to; required, up to 150 characters
Activity	Which work the competence unlocks — required, see the table below
Active	Only active requirements are offered when a new user competency is recorded
Method (optional)	Scopes the requirement to one laboratory method
Instrument (optional)	Scopes the requirement to one instrument
Monitoring Frequency (months)	The §6.2.5(f) window; sets when the next monitoring falls due
Minimum Monitoring Score (%)	The examiner-reliability floor for qualitative examinations
Authorisation Validity (months)	The §6.2.6 window; sets when an authorisation expires
Description · Qualifications · Training · Experience	Free text — what the operator must have
Linked Document (SOP)	The Document Control procedure that describes the competence
Notes	Additional remarks

Activities

The Activity is what makes a requirement enforceable: the system checks competence when a user attempts the matching action.

Activity	What it covers
Analysis	Releasing a measurement or analysis (§6.2.6)
Review	Peer review of an analysis record before approval
Approval	Final approval and signatory authority
Sampling	Sampling activities
Opinion Release	Release of opinions and interpretations (§7.8.7.1)
Method Validation	Method development and validation (§7.2.2)
Maintenance	Authorisation to maintain or repair equipment
Other	Anything not covered above

The two windows

The two month figures are not decorative: they are copied onto every user competency that points at this requirement and drive its dates.

Monitoring Frequency — how often the competence must be confirmed (§6.2.5(f)). After each entry in Competency Monitoring the next date is computed from here.
Authorisation Validity — how long an authorisation holds before renewal (§6.2.6). When a competency moves to Authorized, its Authorized Until date is filled in from here.

Leave a window blank and the matching date stays blank: the competence neither expires nor asks for monitoring.

Connects to

Points at — this page does not stand without these:

If this is missing

🔴 An empty requirements list turns the check off. The guard that stops an unauthorized

collector first looks for an active requirement for the activity; if there is none it returns

silently and nobody is checked. That is a deliberate soft start for new installations, but it

means the safety here only switches on once you define the first requirement.

A requirement that exists but is inactive counts exactly the same as one that does not exist.
A requirement with no method or instrument attached applies generally; it is weaker evidence than

one tied to a specific activity.

Notes

A value of 0 in either window is not stored — it means blank. By contrast 0% in the Minimum Monitoring Score is a real floor and is stored.
Deactivating a requirement leaves existing competencies alone but hides it when a new one is recorded.
Changes on this page are made by the Lab Director.