Can several management systems share one application?

Yes. Several management systems can share one IAF Consultancy application. Shared processes, such as internal audit, competence, and corrective action, can be sampled once. The parts that fail in different ways stay separate, and the offer shows where the days are combined and where they are not.

Where can the systems share one process?

Most management systems ask the company to know its obligations, set priorities, control the important risks, prepare for emergencies, and check whether the controls work. Internal audit, management review, competence, and corrective action can be one process with more than one column, rather than separate departments that never speak.

One application can ask for all of them. IAF Consultancy audits most ISO management system standards, so the scope is whatever the application names. The offer then shows combined days where the evidence is shared, and separate time where it is not. That is usually calmer than running two projects a month apart.

Where must the systems stay distinct?

A shared heading is not a shared risk. One activity can matter for two reasons, and the controls may differ. A register that uses one score for both tends to understate one of them.

Legal requirements differ too. Obligations do not collapse into a single list just because the spreadsheet has one tab. The audit will sample each list against the work.

Some duties are specific to one system. Consultation with the people who do the work is not the same meeting as a briefing. The audit looks for the participation the system actually requires, not only whether a slide was shown.

What does a combined audit walk?

On site, a combined audit still walks the work. Two controls might be twenty metres apart. The sample follows each one back to the register, the control, and the check that the control is still in place. What an audit samples describes that trail for a single system. The method is the same when several systems share the visit.

Surveillance keeps each system alive. A certificate covering more than one system is not maintained by auditing one of them thoroughly and waving at the others. Each surveillance visit should touch each system in the scope, across the cycle, until re-certification starts that cycle again at Surveillance 1. The sequence is in how certification works. Submit one application and name every system you want in the scope.