Management system maintenance

Maintaining a management system isn't filing the manual away the day after certification. Between one audit and the next there are objectives to review, indicators to update, non-conformities to close and internal audits to schedule and run. When no one keeps that calendar going, the system becomes what the industry calls a shelf-ware system: correct-looking documents that don't reflect what the company actually does, and behind that expression sits a risk with a name in the standard: suspension (subclause 9.6.5.2).

The cycle the certification imposes is specific. Under ISO/IEC 17021-1:2015, subclause 9.1.3.2, the first certification cycle runs for three years from the decision to certify: surveillance audits are planned in the first and second year, and a recertification audit in the third, before the certificate expires. Each surveillance audit reviews a sample of the system, not the full scope, so what hasn't been touched in a year can reach the next visit unscathed, but it can also build up debt no one notices until it's too late.

The real risk has a name and a documented consequence. The very standard that governs certification bodies (subclause 9.6.5.2) obliges them to suspend a certificate when the client fails to meet the certification requirements or doesn't allow surveillance or recertification audits at the agreed frequency. Under suspension, the certification is temporarily invalid (9.6.5.3); if the reason isn't resolved within the usual period of up to six months the standard notes (subclause 9.6.5.4), the suspension turns into withdrawal or a reduction of the certificate's scope. A carelessly maintained system rarely loses its certificate overnight: it arrives at the surveillance audit with accumulated non-conformities that, if not closed in time, become that scenario.

The outsourced or shared quality manager fills exactly the gap that cycle leaves: sustaining the annual calendar, updating the risk matrix and the legal matrix, preparing the management review, following up open corrective actions and coordinating, without necessarily replacing, the internal audit programme. They arrive at the surveillance audit with the evidence ready, instead of rebuilding it the week before.

This service isn't the same as internal audit: internal audit is a scheduled milestone required by clause 9.2 of each standard, with its own calendar and its own report. Maintenance covers everything that happens around that milestone, throughout the twelve months of the year, including coordinating those same internal audits when contracted separately. And if the system being maintained is an integrated system across several standards, the calendar and the dashboard are sustained the same way, with more pieces to coordinate in the same management review.

At Summum Calidad we've supported management systems in Castilla y León and the Canary Islands since 2007; in that time we've added close to 200 certifications accompanied. The outsourced quality manager doesn't replace the certification body, which still decides whether to maintain, suspend or withdraw the certificate; our role is to make sure that moment never catches you with a neglected system.

The twelve-month template calendar

No two companies share exactly the same certification calendar, but most maintenance tasks repeat each year in a similar order. This is the template calendar we apply, later adjusted to each client's real surveillance audit month:

The month of the surveillance audit changes depending on when the company was certified: what doesn't change is that all twelve tasks have to run through the calendar, whether the audit falls in October or any other month.

In-house, outsourced or shared: which model fits

There's no single best model in the abstract: it depends on the company's size, how many standards it maintains and whether the certification body has already issued a warning.

The shared model is the one that most often ends up in mid-sized companies: an in-house person sustains day-to-day work and Summum Calidad provides the calendar, regulatory expertise and preparation for the external audit.

What happens if the system is left unattended

"Shelf-ware system" isn't an empty figure of speech: it describes a risk documented in the very standard that governs certification bodies. ISO/IEC 17021-1:2015 obliges suspension of certification when the client fails to meet the requirements, or doesn't allow surveillance or recertification audits at the agreed frequency (subclause 9.6.5.2). Under suspension, the certification is temporarily invalid: the company can't use it with clients or in tenders while it lasts (subclause 9.6.5.3).

Suspension isn't indefinite: in most cases it shouldn't exceed six months (subclause 9.6.5.4, note). If the reason isn't resolved within that period, it results in withdrawal of the certificate or a reduction of its scope (subclause 9.6.5.5). It's almost never reached all at once: the usual path starts with repeated minor non-conformities for lack of follow-up, moves to a major one once the pattern is confirmed, and only reaches suspension if that major finding isn't closed in time.

The certification cycle: surveillance and recertification

The cycle's clock starts on the day of the decision to certify, not the day of the stage 2 audit (ISO/IEC 17021-1:2015, subclause 9.1.3.2). From there, the certification body plans surveillance audits at least once every calendar year, except in recertification years (subclause 9.1.3.3): on-site visits that don't necessarily cover the whole system (subclause 9.6.2.2).

The recertification audit, in the third year, carries an intensity comparable to the initial stage 2 audit: it confirms the system remains effective, reviews the history of previous surveillance visits and, if there's a major non-conformity, requires it to be corrected before the certificate expires to renew it without interruption (subclause 9.6.3). Keeping the system alive across all three years, not just before each visit, is what turns that audit into a formality rather than a surprise.