Quality-system documentation

About quality-system documentation

Quality-system documentation support helps a laboratory organise procedures and records around the way its work is actually performed. It links document preparation with implementation evidence, clear owners and controlled versions rather than relying on unused templates.

NABL Labs support is for businesses setting up a testing or calibration laboratory, preparing for accreditation or organising improvements to an existing laboratory. The starting point is the work the laboratory intends to perform: its methods, equipment, people, facilities and proposed scope. This service is separate from arranging a product test report from an external laboratory.

For quality-system documentation, agree the product, activity, application or record involved and the working output. Focus the preparation on the information needed at this stage, with clear evidence references and an understandable handover for the person continuing the work.

When this support is useful

New and existing testing or calibration laboratories can discuss setup planning and accreditation preparation. Identify the intended activities, methods, locations and present readiness before deciding on the work. The appropriate accreditation route should match the laboratory type and scope; requirements for medical laboratories or other conformity-assessment bodies need a separate scope discussion.

This subservice can be discussed when the business has reached the relevant stage, received a request for information or identified a gap it cannot resolve from its existing records. Start with the actual request and explain what work has already been completed. That avoids both duplicating earlier preparation and overlooking an unresolved dependency.

TenderCert provides consultancy and coordination support. Accreditation is awarded by NABL for a stated scope through its assessment process. A laboratory’s accredited activities, a product test report and an ISO management-system certificate are different forms of evidence.

The starting information for this work

The task-specific inputs are: The laboratory scope, existing procedures and forms, responsibility information, examples of completed records, document-control arrangements and findings from earlier reviews.

Identify the current version of each input and the person who can confirm it. Keep the original requirement alongside any summary. Where an input has not yet been verified, mark that point clearly so the preparation does not convert an assumption into an application statement.

• Laboratory profile and proposed testing or calibration scope
• Facility information and setup plans
• Equipment inventory and available calibration records
• Method information and personnel competence records
• Existing procedures, technical records and quality-system documents
• Internal review findings and accreditation correspondence

How the work is organised

1. Review the documents already used by the laboratory.

   Begin with the relevant source record and the scope agreed with the applicant. Record the fact being checked and identify what would establish it, rather than relying only on a title or a previous file name.

2. Connect procedures and records to the relevant activities.

   Compare the related information as a connected set. A change to one attachment can affect a product description, application field or evidence reference elsewhere, so keep those relationships visible.

3. Identify owners, versions and implementation gaps.

   Retain the reviewed result and any question that remains open. Identify the next owner and the evidence needed before the applicant treats the work as ready for the next stage.

4. Prepare a reviewed document index and action list.

   undefined

The steps should be agreed with the business and adapted to the actual record or product. Where a question requires a technical, regulatory or other professional conclusion, the preparation should identify the appropriate reviewer. Administrative organisation and professional assessment remain different responsibilities.

Evidence and consistency checks

Use this wider service context to check whether the task-specific records remain coherent. For example, names, models, locations and reporting periods should be understandable across related files. If they differ for a valid reason, explain the relationship with the applicant and keep the source evidence accessible.

The working output and its handover

An organised quality-system document set and an implementation-evidence checklist for the agreed scope.

A useful handover identifies what was reviewed, the version or date, the evidence references and the outstanding questions. It should also identify the next responsible person. That allows another team member or an external reviewer to continue the work without reconstructing the preparation history from scattered messages.

An organised output is not a substitute for the relevant external decision. Where the next step is a submission, test, assessment or professional review, agree who authorises it and which reviewed information will be used. Keep the acknowledgement or response with the same record.

Why careful preparation matters

• A clearer plan for the laboratory activities being proposed.
• Better links between equipment, methods and evidence.
• More useful documents and defined information owners.
• An organised starting point for accreditation and assessment discussions.

For this subservice, judge the preparation by how clearly it resolves the task and supports the next decision. An output that still contains unexplained identity or scope differences can create avoidable questions later, even if the folder appears complete. The practical aim is a record that the business can understand and stand behind.

An illustrative working example

A manufacturer wants to establish an internal testing laboratory. Its team lists the intended tests and methods before buying equipment or describing the laboratory as accredited. It reviews facility needs, assigns technical responsibilities and gathers the records already available. The preparation plan identifies questions for competent technical reviewers and distinguishes setup work from the later accreditation process. This is an illustrative planning example, not a claim that every laboratory follows an identical route.

At the quality-system documentation stage, the team would focus on this question: Do the laboratory’s documents reflect its actual working arrangements? The evidence for the answer should be recorded in the working output, with any unresolved point assigned to a person rather than silently treated as settled.

Common issues and the final review

• Buying equipment before defining the proposed laboratory activities and methods.
• Preparing blank procedures without evidence of how the laboratory works.
• Presenting an intended scope as already accredited or using another laboratory’s certificate as coverage.

The task-specific review question is: Do the laboratory’s documents reflect its actual working arrangements?

Separate a missing document from an unsupported claim and from a technical question. These need different actions. Obtaining a file may resolve the first; correcting the statement or obtaining competent review may be necessary for the others. Keep those actions visible until the responsible person has reviewed the result.

After this stage is completed

Maintain the laboratory’s technical and management records in normal use. Review changes to methods, equipment, personnel, locations and scope with the responsible team. Keep assessment correspondence and improvement actions together, and confirm the follow-up arrangements applicable to the actual accreditation status.

Retain the task output with the source information, reviewed version and relevant correspondence. If the underlying business facts change before the next submission or assessment, check the effect on the prepared material rather than assuming the earlier result still applies.

Discuss your requirement with TenderCert

Start with the outcome you need and the evidence you already hold. Bring the exact buyer clause, authority request or assessment enquiry where available, together with a short description of the product, activity or site. This makes the conversation more useful than asking for an unspecified certificate.

TenderCert’s consultancy scope can then identify the preparation and coordination tasks to discuss, the person responsible for each input and the questions for the relevant decision-maker. The applicant should review information and declarations before any external submission. Keep the final reviewed version and the acknowledgement together so later follow-up begins from the same record.

Common questions