IMScollect
ISO 9001ISO 14001ISO 27001

Clause 6.2: Objectives

Title in the standard: “Objectives and planning to achieve them”

What do you want to achieve by when, how do you measure it, and what are you doing to get there? Clause 6.2 in ISO 9001, 14001 and 27001 from the audit’s point of view.

Philipp Kappe

Philipp Kappe

Founder of IMScollect

Updated 15 November 2026

What it is about

Objectives turn the policy into something measurable. The policy says where the organisation wants to go; the objectives say what it concretely wants to achieve by when, in quality, environmental protection or information security. They are consistent with the policy, measurable where possible, monitored, communicated and updated as needed.

An objective on its own is not enough. Clause 6.2 requires a plan for it: what will be done, what resources are needed, who is responsible, when it will be completed and how the result will be evaluated. Only this plan turns an intention into a task whose progress can be tracked.

Where objectives come from is not arbitrary. They take up what planning has already produced: risks and opportunities, requirements of customers and other interested parties, the significant environmental aspects and compliance obligations under ISO 14001, and the results of the risk assessment under ISO 27001. Their status is tracked through indicators and evaluated in the management review.

What the auditor checks

  • “Where does this objective stand, and how do you know?”

    Whether the status is known and backed up: an indicator, a measured value with a date, a short report. Anyone who first has to look up where an objective currently stands is not tracking it.

  • “What do you do if the objective is missed?”

    Whether there is a response before the year is over: a countermeasure, an adjusted plan, a decision by top management. A missed objective is not a finding in itself. An objective that has been off track for months without anyone discussing it, however, shows that monitoring is not working.

  • “How does this objective fit your policy?”

    The common thread. If the policy promises, for example, to protect customer data, at least one information security objective should relate to it. Objectives that have nothing to do with any statement in the policy stand out just as much as policy statements without any objective.

  • “Who is responsible for this objective, and what resources do they have for it?”

    Name, budget, time. An objective that belongs to everyone belongs to no one, and an objective without resources remains a wish.

  • “Why is this your objective and not another one?”

    Whether the objective comes from your own organisation. Good objectives are highly individual; there is no model objective that fits every organisation. A complaint rate can be the right objective for a series manufacturer and say nothing at all for an engineering consultancy with three major clients. “Increase customer satisfaction” with no figure, no occasion and no reason usually gives away the template.

  • “Which objectives apply to your area?”

    Asked of the head of production or the person responsible for IT. Objectives have to be communicated, and anyone who contributes to achieving them should be able to name them without opening the overview.

Which evidence convinces

  • An overview of objectives with indicator, target value, deadline and responsible person

    All three standards require objectives as documented information. An overview shows at a glance what applies and who stands behind it.

  • The plan for each objective

    Actions, resources, dates and the way of evaluating. It shows that the objective is more than a figure set at the start of the year.

  • Measured values over time

    Several measurement points over the year show that the objective really is monitored. A single measurement shortly before the audit shows the opposite.

  • The link to the policy and to planning

    A reference to the risk, the environmental aspect or the customer requirement the objective comes from. That way it can be explained in the audit why this particular objective was chosen.

  • Results in the management review

    Achieved, missed, with conclusions and new objectives. This shows that top management knows the status and has made decisions based on it.

Typical nonconformities

  1. Objectives without a yardstick

    “Improve quality”, “strengthen environmental protection”, “increase security”: without an indicator or a clear criterion, there is no way of saying whether an objective has been achieved. If there are no objectives at all for one standard, the requirement is not met, and that is a major nonconformity. If individual objectives are not measurable although they could be, it is a minor nonconformity.

  2. No link to the policy

    The objectives stand on their own, while the policy promises something else. The connection the standards require is then missing on both sides.

  3. Objectives without a plan

    Target value and deadline are there, but no action, no resources and no responsible person. How the objective is to be achieved remains open.

  4. Status is not tracked

    Objectives set in January, the first measurement in November, shortly before the audit. An objective is only monitored in the sense of the standards once its status is known during the year.

  5. Objectives for one standard only

    The integrated system has quality objectives but not a single environmental or security objective. Every certified standard needs objectives of its own, even if they sit in a shared overview.

Differences by standard

ISO 9001ISO 9001

ISO 9001 requires quality objectives for the relevant functions, levels and processes. They take applicable requirements into account, relate to the conformity of products and services and to customer satisfaction, and are measurable without qualification. The article on the 2026 edition lists, as a question for the transition, whether quality objectives are linked to responsible persons, resources and an evaluation of effectiveness. More on this in the article linked below.

ISO 14001ISO 14001

ISO 14001 requires environmental objectives to take into account the significant environmental aspects and compliance obligations and to consider risks and opportunities. They are measurable where practicable. The plan explicitly includes indicators for monitoring progress and consideration of how the actions will be integrated into the organisation’s business processes.

ISO 27001ISO/IEC 27001

ISO/IEC 27001 requires information security objectives to take into account applicable information security requirements and the results of risk assessment and risk treatment. Since the 2022 edition, they explicitly have to be monitored and be available as documented information. They are measurable where practicable; planning sits in the same clause 6.2 without subclauses.

How IMScollect covers it

In IMScollect, objectives and indicators sit side by side, as a list or as cards. Every objective needs, when it is created, a statement of how it will be measured, a deadline and a responsible person; larger objectives can be broken down into sub-objectives. Indicators have a target value, a direction and a measurement frequency. Their status follows from the measured values and not from an estimate: on track, at risk or off track.

You report the status of an objective with progress, an assessment and a sentence of explanation, and the history records every report. An objective or an indicator gives rise to an action with an owner and a deadline, which continues as a task. Completed objectives are shown as achieved, not achieved or cancelled, and objectives and indicators feed into the management review as inputs.

Try it yourself, no call needed.Prefer a walkthrough? Book a guided demo →

Frequently asked questions

How many objectives does a management system need?▾

The standards do not set a number. Each certified standard needs objectives for the functions and levels that matter. A few objectives that are really tracked are more convincing in the audit than a long list whose status nobody knows.

Do objectives always have to be measurable?▾

ISO 9001 requires measurable quality objectives. ISO 14001 and ISO 27001 require measurability where practicable. Where no figure fits, the objective needs a clear criterion against which it can be decided at the end whether it has been achieved.

Is a missed objective a nonconformity?▾

No. The standards require objectives to be set, tracked and acted upon, not always achieved. It becomes a nonconformity when nobody has noticed that an objective is being missed, or when nothing follows from it.

What is the difference between an objective and an indicator?▾

The objective describes what is to be achieved by when, for example to reduce the complaint rate to below 0.5 per cent by the end of the year. The indicator is the measured value from which progress can be read. One indicator can support several objectives, and some indicators are only monitored without carrying an objective.

Is a shared set of objectives enough for ISO 9001, 14001 and 27001?▾

Yes. An overview with a column for the standard concerned is sufficient, as long as each standard has objectives of its own with a plan and the specific requirements are met, such as the progress indicators under ISO 14001.

Further reading and viewing

Philipp Kappe

Philipp Kappe

Founder of IMScollect

Philipp builds IMScollect. TÜV-certified auditor with a background in governance, risk and compliance, more than 200 audits conducted and supported.

This page explains in our own words and does not replace the text of the standard. You can obtain the standards from ISO(opens in a new window) or from your national standards body. Clause numbers and titles follow ISO 9001:2026, ISO 14001:2026 and ISO/IEC 27001:2022.