What this review is for

A proposed ongoing support arrangement for the work between audits: planning, document reviews, action follow-up and preparation for management decisions. Build a repeatable operating rhythm with clear ownership.

Who this is for. For organisations with an established or developing system that need structured coordination, especially where a small team manages several standards alongside its day-to-day work.

Scope and evidence

What the review covers

  • Agree a recurring programme based on the organisation’s risks, standards, sites and available internal capacity.
  • Coordinate planned internal audits, review dates and follow-up of open findings.
  • Support document control by tracking ownership, approval, review and obsolete versions.
  • Prepare management-review inputs and record decisions, actions and accountable owners.
  • Maintain a dated watchlist of relevant standards changes and flag items that need a management decision.

Evidence to prepare

  • The current scopes, certificates and certification-body assessment schedules.
  • Audit programmes, document registers and existing action logs.
  • Objectives, performance measures and management-review arrangements.
  • Named process owners and the internal authority to approve changes.
  • Known deadlines, planned business changes and recurring areas of difficulty.

What the review is intended to produce

  1. A proposed annual management-system calendar with responsibilities.
  2. A maintained action view showing overdue items, dependencies and completion evidence.
  3. Document-review and approval tracking appropriate to the agreed arrangement.
  4. Management-review preparation notes and a record of agreed decisions.
  5. Periodic status summaries that separate completed work, outstanding evidence and decisions needed.

How the work is structured

01

Establish the baseline

Identify what already works, where coordination fails and which activities need specialist input. Agree a realistic division of responsibilities.

02

Plan the recurring cycle

Connect audits, objectives, reviews and external assessment dates. Allow time for actions to operate before their effectiveness is evaluated.

03

Review progress and evidence

Use scheduled checkpoints to remove obstacles and update priorities. An action is not complete merely because its due date has arrived.

04

Adjust to change

Revisit the programme when the business, risks or standards change. Record the reason for altered coverage and priorities.

Service boundaries

  • Certification audits are carried out by independent certification bodies, ideally accredited by UKAS. ISOaudit does not issue certificates and is independent of ISO, UKAS and certification bodies.
  • ISO Desk is a proposed support model. Service frequency, capacity, response commitments and commercial terms require an agreed engagement. Management retains approval and accountability.
  • This page describes a proposed service method. An audit brief records your needs; it does not place an order or confirm scope, availability or delivery terms.
Proposed service specification

The specification does not constitute an offer or an agreed engagement. Trading identity, price, availability, scope, liability and service terms must be confirmed before a paid engagement can be accepted.

Common questions

Does ISO Desk replace our management representative or process owners?

No. Support can coordinate work and prepare information, but the organisation must retain the authority and capacity to operate its controls and make management decisions.

Does it include unlimited audits or legal advice?

No such inclusion is implied. The brief should identify required activities and specialist needs so the scope can be agreed explicitly.

Can the same person advise and audit the system?

Potential conflicts need to be assessed. An arrangement that involves designing or running a control may require separate audit responsibility to preserve objectivity.

Fictional example: making an overdue action reviewable

A fictional small team uses a recurring review to coordinate open management-system actions. This educational scenario does not establish an ISO Desk service commitment or client result.

From agreed criteria to a proportionate next step
Criteria to establishAgree the engagement responsibilities, the organisation's approval rules and the evidence needed to close each action. Management retains accountability for priorities and decisions.
Evidence and sampleSelect an overdue action and trace the original finding, intended result, owner, dependency and available evidence. Include the reason for changed priorities in the record.
What the evidence showsThe fictional tracker says 'complete', while the linked note records only that a revised procedure was requested. The evidence does not yet support either implementation or effectiveness.
Next stepReturn the action to its accurate state, identify the missing work and decision owner, and agree a meaningful follow-up. Preserve the history so that a later reviewer can understand the change.

Coordination is not independent assurance over every action. Frequency, capacity, response times and commercial inclusions require an agreed engagement.

YOUR NEXT STEP

Make the scope concrete.

Describe your organisation, objective and constraints. Download the brief and review it before commissioning work.

Prepare an audit brief ↗

SOURCES & REVIEW

Check the underlying information.

These are independent summaries and implementation suggestions, not the copyrighted standard text. Use an authorised copy of the applicable standard for its full requirements.

  1. ISO: guidance on auditing management systems
  2. ISO: certification and accreditation explained

Reviewed 1 November 2026 · Next editorial review 1 December 2026 · Editorial policy

The displayed review date records an editorial source check. Named specialist review is still to be assigned for this private edition. The 2 November 2026 content update added an original fictional worked example and related guidance; source corrections are recorded in the project change log.