Service

ISO 9001 Quality Management System

The outcome of an ISO 9001 project is not a certificate but a way of managing that sits on the organization's own processes. The work starts with an analysis of the current state, clarifies processes and responsibilities, structures documentation only as far as it will actually be used, and does not leave the team alone during implementation. The certification audit comes after the system genuinely works.

Who is it for?

Organizations establishing an ISO 9001 system, preparing for certification or improving an existing system.

Scope of work

  • Current-state and gap analysis
  • Defining processes and responsibilities
  • Structuring the system documentation
  • Implementation and team support
  • Internal audit and management review preparation

Expected outputs

  • A management system structure that fits the organization
  • Process maps and a responsibility matrix
  • The required procedures, forms and tracking tools

Implementation and development plan

On-site, live online or hybrid delivery.

Frequently asked

Questions we hear about this service

If your question is not answered here, we can go through it directly in a short conversation.

It begins with a current state analysis; processes and responsibilities are clarified, risks and opportunities are identified, and documentation is built only as far as it will be used. Implementation, internal audit and management review follow. The certification audit comes once those steps are complete.

No. The certificate is issued by an accredited certification body. As consultant, ELQA builds the system, runs the internal audit and the preparation, and is present alongside the organization during the audit.

The standard does not ask for a set number of procedures; it asks for the documented information that is needed. The document set is therefore sized to the complexity of your processes, avoiding forms produced for their own sake.

That is the most common situation. The first task is to find where the system broke: usually the problem is not the requirement but the distance between the written process and what actually happens. Documentation is simplified to match the floor and the record-keeping load is brought back to a workable level.