Documentation
Tutorials
Workflows
Kebab actions
Daily Work
Dashboard & Reports
Quality Control
ISO 17025
Reagents & Storage
Logs
Contacts
Billing
Analysis Setup
Settings
Initial Setup
Help & Reference
Architecture decisions
ISO 17025

Competency Monitoring

The Competency Monitoring page records the periodic events by which the laboratory confirms that a competence still holds (ISO/IEC 17025 §6.2.5(f)). It is the page that keeps the cycle alive: each entry moves the next monitoring date on the matching User Competency.

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

Toolbar

ButtonAction
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

FieldDescription
User CompetencyWhich competence is being monitored — required
Monitored AtWhen it took place — required, pre-filled with today
Monitored ByWho carried out the monitoring — required
Monitoring MethodHow it was confirmed — required, see below
ResultThe finding — required, see below
Score (%)The measured score where the method produces one; leave blank if none applies
NotesAdditional remarks

Methods

MethodWhat it means
ObservationDirect supervisor observation of a routine task
Blind RetestRe-analysis of an already analysed sample without knowledge of the prior result
Result ReviewReview of recent results and trends
Witnessed PTSupervised participation in a proficiency test
Internal AuditAn observation noted during an internal audit (§8.8)
OtherAnything not covered above

Results, and what each triggers

ResultWhat happens
SatisfactoryCompetence confirmed; no action
Retrain RequiredCompetence held but flagged for follow-up
Suspension RecommendedThe user's competency is set to Suspended automatically

On every new entry, the matching competency takes the date you gave as Last Monitoring, and Next Monitoring becomes that date plus the requirement's Monitoring Frequency. If the requirement sets no frequency, the next date is left blank.

Notes

  • Back-dated entries do not move the schedule. If the date you give is earlier than the last one recorded, the entry is saved but the competency's dates stay pinned to the most recent event.
  • The automation runs on creation only. Editing an existing entry's result to Suspension Recommended does not suspend the competency — record a new event instead.
  • A suspension is not lifted automatically by a later satisfactory monitoring; reinstatement is a new authorisation cycle.
  • A score of 0% is a real value and is stored; blank means no score applies.