A few weeks of hunting before every visit
A surveillance visit is booked. The quality manager opens a checklist of what the assessor will want: the internal audit programme and findings, management review minutes, validation files for new methods, measurement uncertainty, proficiency test results, staff competence records, complaints and corrective actions. Each lives somewhere different. Some are in the quality system software, some in folders, some in email.
The weeks before a visit become a scramble, and gaps are found at the worst possible time.
Why evidence is spread so thin
- Different records are kept by different people in different tools.
- Links between methods, validations and competence are not recorded.
- Scope changes create new evidence needs that are easy to miss.
- Due dates for audits and reviews are tracked separately from the records.
- Nobody sees gaps until preparing for a visit.
Extensions to scope show the gap most clearly. Adding a method means validation, uncertainty, competence sign-off for the analysts, PT enrolment and document control, each owned by different people. Unless those pieces are tied to the method in one place, it is easy for one to be missing when the extension is assessed.
What it costs
Senior staff time is pulled into preparation. Gaps found late are closed in a hurry. Findings raised during an assessment add corrective work. The quality manager carries the anxiety of knowing where everything is.
| Evidence | Scattered | In an evidence hub |
|---|---|---|
| Internal audits | Folder per year | Linked to clauses and areas, with due dates |
| Method validation | Files per method | Linked to the method in your scope |
| Competence | Training spreadsheet | Linked to methods each person is authorised for |
| Proficiency testing | Separate folder | Results linked to methods |
| Complaints and actions | Separate log | Linked to affected areas and closed out |
Findings that come from record-keeping rather than technical failings are especially frustrating. The work was done properly, but the evidence could not be produced quickly or completely, and the lab now has a corrective action to close for something that was really a filing problem.
How we build it
- We map your scope, methods and quality system areas with your quality manager.
- Existing records stay where they are where possible; the hub links to them, or holds them if they have no better home.
- Each method shows its validation, uncertainty, proficiency testing and the staff authorised to run it.
- Audit programmes, management reviews and other periodic activities show due dates and completion.
- Gaps and overdue items appear on a dashboard all year round.
- An export assembles an organised evidence pack for an assessment.
We do not write procedures or decide whether evidence satisfies a standard. The hub organises what your quality team produces.
What changes
Preparing for an assessment becomes a review rather than a search. Gaps show up months in advance. Method owners see the state of their own methods. The quality manager is no longer the only person who knows where everything is.
Management review becomes easier as well. The inputs your procedures require, such as audit results, PT performance, complaints and corrective actions, are already summarised, so the review can focus on decisions rather than on assembling the pack.
Is this your quality manager's year?
- Assessment preparation takes weeks.
- Evidence lives in several tools and folders.
- Links between methods, validation and competence are not recorded.
- Gaps are found during preparation.
- Only the quality manager knows where everything is.