User Competencies

The User Competencies page is the personnel competence matrix: one row per user and Competency Requirement, with its status and the dates that govern it (ISO/IEC 17025 §6.2.5(c)-(f), §6.2.6). It is the evidence that whoever performs a task is authorised to, and the system reads it when someone tries to approve an analysis or release an opinion.

Found under: ISO 17025 → Personnel & Competency → User Competencies.

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
User	Who it concerns — required
Competency Requirement	Which competence; only active requirements are listed — required
Status	Where the user stands in the cycle — see the table below
Last Monitoring	When the competence was last confirmed
Next Monitoring	When the next one falls due; filled in automatically from monitoring entries
Authorized Until	How long the authorisation holds; filled in automatically on authorisation
Evidence URL	Pointer to the evidence (certificate, assessment report)
Notes	Additional remarks

Opening an existing record that has been authorised shows, at the foot of the dialog, when authorisation was granted and by whom.

Statuses

Status	Meaning
Draft	The record exists; assessment has not started
Training	Training in progress (§6.2.5(c))
Supervised	Supervised practice in progress (§6.2.5(d))
Authorized	The user performs the activity unsupervised (§6.2.6), until Authorized Until
Suspended	Competence withdrawn after a monitoring failure or other quality event
Expired	Authorized Until lapsed without renewal

What the system does on its own

On authorisation, Authorized Until is computed from the requirement's Authorisation Validity. Anything typed there by hand is overwritten. If the requirement has no validity window, the field is left blank.
On leaving authorisation, the "authorised by / when" stamps are cleared, so a suspended or expired row never shows a stale signature.
Every night, authorised rows whose Authorized Until has passed become Expired. Suspended rows are left alone.
A monitoring entry with the result Suspension Recommended moves the row to Suspended automatically.

Dates that have passed render in bold red in the grid.

One live row per competence

Exactly one live row is allowed for each user and requirement pair. Attempting a second one is refused, with a message pointing you at the existing row. The reason is auditability: two coexisting rows for the same competence make it ambiguous which authorisation was in force.

Connects to

Points at — this page does not stand without these:

Users

Used by — a change here shows up in these:

If this is missing

🔴 Sampling is checked per person: the named collector must hold Authorized competence for

the SAMPLING activity. Supervised is not enough.

If the sample names no collector, the check does not run at all. An empty field is not neutral;

it bypasses the guard.

Competence depends on the requirements list: with no active

requirement, no authorization is enforced anywhere.

A competency at Supervised with no supervised practice

entries is an evidence gap; one at Authorized with no recent

monitoring is stale.

Notes

Renewing an authorisation is not a date change on an old row; it is a new cycle.
Changes are made by the Lab Director or the Quality Manager.
See also: Supervised Practice, Competency Monitoring, Training Records.