How to organise user training and accreditation in a shared-instrument facility
In a shared-instrument facility the everyday question is who can use what, and when. If the answer lives in a technician's memory, it does not scale and it cannot be proven. These are the basics of a level system that does.
1. Why you need a system
Instruments are expensive, samples often cannot be repeated, and misuse can cause a breakdown or a safety risk. Even so, in many facilities training is passed on informally: someone "knows how to use it" because they watched someone else. That leaves no record, depends on one person, and does not help when a reviewer or an accreditation body asks how access is authorised.
2. Levels per instrument, not per person
Competence is specific to each instrument: someone can work alone on the confocal microscope and still be a beginner on the sorter. So the level should be assigned per person and per instrument. A simple three-level scheme is usually enough:
- Novice: may use the instrument only accompanied or supervised by a technician.
- Independent: books and works independently within the facility's general hours.
- Advanced: also gets whatever extended slots or permissions your policy reserves for the most experienced users.
3. Clear criteria for moving up
Decide in advance what it takes to move from one level to the next. The most practical option is a number of approved supervised sessions per instrument, with the technician's assessment and notes that justify the decision. More complex instruments can require more sessions than others; the threshold does not have to be the same across the whole facility.
4. What each level can do
The level must have concrete consequences for bookings. For example: novices book only during hours when a technician is present, independent users during the facility's working hours, and advanced users in extended slots, if your policy allows it. If the rules are applied by hand, sooner or later they get skipped; if the system applies them when booking, nobody has to remember.
5. Keeping a record of every decision
Store who approved each level change, when and with what notes. That history is what lets you answer an audit, a project reviewer or an internal question, and it also protects the technician when they refuse access.
6. Keeping training from becoming a bottleneck
- Access requests with an approval inbox, so you do not depend on scattered emails.
- A pre-session form, which saves the technician basic questions.
- Bulk permissions when a whole group or course joins, instead of person by person.
7. How JoulesCloud handles it
In JoulesCloud each user has a level per instrument (Novice, Independent, Advanced) earned through approved supervised sessions. Thresholds are configurable per instrument, the technician approves or rejects with notes and time slots, and a full history of each change is kept. Booking hours depend on the level, access requests have their own inbox, and bulk permissions grant access to many people and instruments at once. You can see the rest of the booking system, or how it fits into running the whole facility. The detail is on the access control and user training page.