Qualification belongs to the work someone will perform
A training percentage cannot answer whether an analyst may run a particular method today. The decision can depend on the procedure version, demonstrated competence, assessor evidence, role, validity period and any restriction. Seal keeps those requirements with the records that demonstrate them and the work that uses them.
The native query above shows six fictional person-method records. J. Patel has recorded authorisation for AM-014, but not AM-022. M. Chen has the reverse pattern. A. Lewis has acknowledged AM-014 but has no recorded practical assessment. The useful view is the scope of qualification, not a row of indistinguishable completion ticks.
Define the curriculum around a role
Connect job responsibilities to procedures, methods, equipment and required skills. Each requirement can specify acknowledgement, knowledge assessment, observed practice or another defined verification method. Keep prerequisites, assessors, validity and evidence requirements explicit; one form of training does not silently substitute for another.
When a person changes role, retain both their history and the requirements of the new scope. Qualifications that remain relevant can stay visible alongside new gaps. Contractor and temporary scopes need the same clarity about what is permitted, by whom and for how long.
Make a procedure revision an assessable change
The example records AM-014 v04 as the current method. M. Chen's acknowledgement remains on v03; the illustrative revision-impact assessment calls for reassessment. Historical work still retains the version and authorisation applicable when it happened.
Not every document change requires the same response. Record the impact assessment and resulting training work. Keep the procedure, learning material, practical assessment and release of the revised workflow connected rather than treating them as unrelated updates.
Capture how competence was demonstrated
Record the assessment criteria, actual execution, observations, result, assessor and time. Where supervised practice is needed, retain the individual sessions and the eventual scope decision. Supporting learning material can include procedures, video, presentations and job aids with their versions preserved.
The reviewer should be able to inspect the evidence behind an authorisation, not just the date of a signature. Corrections, reassessment and restrictions remain part of the history.
Check qualification at the intended point of work
Training, laboratory execution and manufacturing can use linked records in Seal. Configure the relevant prerequisite for the task and verify the permitted and blocked paths. Test a missing assessment, a superseded procedure, an expired scope and an attempted use of an unrelated method qualification.
The example selector is a read-only explanation of recorded scope. It does not assign work or grant permission. Operational enforcement depends on the configured and verified workflow.
Give neil the procedure and the role
neil can compare supplied procedures and existing requirements, propose a curriculum, create linked assessment records and author capture fields or review states. Ask for an affected-person view and a verification package alongside the configuration—not just a list of training recommendations.
People assess competence, review the proposed requirements, verify the workflow and authorise use. The output should make their work inspectable rather than replace their judgement.
Review gaps and outcomes together
Use the qualification records to inspect overdue or missing work by person, method and role. Then investigate outcomes separately: recurring deviations, reassessment results or difficulties in observed practice may challenge the adequacy of the training or the procedure itself. Retain the source population before drawing a conclusion.
Explore document control, laboratory execution and manufacturing.