presentsUNAIVERSE
The UN AI timeline

Learn AI /AI Agents and Automation /Feedback loop

Feedback loop

Also called: self-correction.

Detail

In five seconds

What it is

A process where the result of an action is fed back into the system and changes a later action, often through comparison with a goal or rule.

In plain words

It is a repeat-and-check pattern: do something, look at what happened, and use that result to improve the next step.

An everyday example

A technician at a water station sees that one pump is showing pressure that is higher than normal. She lowers the pump speed slightly and waits for the next sensor reading. The reading drops, but not enough, so she checks a valve position, adjusts it, and looks again. After two more checks, the pressure returns to the safe range and she records the final setting. She is not acting only once. Each new reading affects the next action.

Where the story stops working

In the water station, the technician uses human judgement, physical equipment and a clear measurement. In AI systems, the feedback may be noisier or indirect, such as a tool error message, a scoring function, or another model's output. Also, many AI loops happen very quickly in software and may optimise for a proxy measure rather than a directly observed real-world condition.

Remember thisIn a feedback loop, an outcome is not merely reported. It is routed back into the process and changes what the system does next, for better or, if the signal or rule is poor, repeatedly for worse.

Understand it

Understand it

Why it matters

For non-specialists, this term matters because many modern AI systems do more than produce one reply. They may take several steps, use tools, check results and try again. That can improve quality, but it can also repeat mistakes, chase the wrong target, or create hidden complexity. When you hear that a system can self-correct, the key questions are practical: What feedback is it using? Who set the goal? What tells it to stop? What happens if the feedback is wrong, delayed or easy to game? These questions affect reliability, safety, auditability, cost and oversight. In policy and operational settings, feedback loops shape accountability. A well-designed loop can catch errors before action is taken. A poorly designed loop can amplify them.

How a feedback loop changes the next step

Show that a feedback loop is a repeated cycle where the result of one action becomes an input for adjusting the next action.

  1. 01

    1. Goal

    The system starts with a target, rule or desired outcome.

    Draw a box labelled Goal with a small target icon and a short subtitle: 'What should happen?'.

  2. 02

    2. Action

    It takes a step, such as sending a query, using a tool or editing a draft.

    Draw a box labelled Action with a tool icon. Connect Goal to Action with a solid arrow.

  3. 03

    3. Observe result

    The system receives evidence about what happened, such as sensor data, a tool response or a validation score.

    Draw a box labelled Observe result with an eye or waveform icon. Connect Action to Observe result.

  4. 04

    4. Compare

    It checks whether the result matches the goal closely enough.

    Draw a box labelled Compare with a checklist icon. Connect Observe result to Compare.

  5. 05

    5. Stop or adjust

    If the result is acceptable, the process ends. If not, the system changes the next action and loops back.

    Draw a decision-style box labelled Stop or adjust. Add one arrow to an End label 'Goal met' and one loop arrow back to Action labelled 'Not yet'.

A left-to-right step diagram with five boxes connected by arrows. The reader follows one cycle: set a goal, take an action, observe the result, compare the result with the goal, then either stop or adjust and repeat. A loop arrow returns from the comparison box to the action box when the result is not yet good enough.

On hover or tap, highlight the loop arrow and reveal the note: 'Feedback changes the next action; without this loop, the system only acts once.'

Describe this without the diagram

The diagram presents five ordered steps. Step 1 is Goal: the system has a target. Step 2 is Action: it takes one step, such as using a tool. Step 3 is Observe result: it gets evidence about what happened. Step 4 is Compare: it checks the result against the target. Step 5 is Stop or adjust: if the result is good enough, the process ends; if not, the system changes its next action and returns to Step 2. The key idea is that the observed result of one step affects the next step.

With reduced motion: Show the same five boxes as a static sequence with a clearly labelled return arrow from Stop or adjust back to Action. Use contrasting colours or line styles to distinguish the forward path from the repeat path, with no animation.

A feedback loop occurs when the result of an action is returned to the system and affects a later step. The result may come from the world, a tool or another program. It may help the system correct its behaviour, but improvement is not guaranteed.

The system may compare the result with a goal, rule or score. If the result is acceptable, it may stop. If not, it may change something and try again. In AI systems, this can mean revising a draft, calling a different tool, asking a follow-up question or changing a threshold.

Inputs may include a goal, a current state and a way to observe an action's result. A common cycle is act, observe, compare and adjust. The process may produce revised attempts or stop because a goal, limit or escalation condition has been reached.

Observation and action name the signals received and steps taken in an acting system. A feedback loop emphasises how an action's result is returned and changes later behaviour. Reinforcement learning is a training method based on trial, feedback and accumulated reward across actions. A feedback loop can instead occur during one live task without retraining the model.

How “Checking a water pump after an unusual sensor reading” maps onto the real thing

In the storyIn the AI system
Target safe pressure rangeGoal or success condition
Sensor reading after each adjustmentFeedback from the environment or a tool
Changing pump speed or valve positionNext action chosen by the system
Repeating until pressure is safeIterative correction with a stopping rule

A worked example

During the annual workplan review at a shared services centre, an internal auditor asks an approved planning agent to sequence proposed engagements for a draft workplan due to the front office by close of business.

Starting from: Proposed engagements, risk ratings, estimated effort, staff availability, required coverage and scheduling constraints.

  1. The agent produces a first draft by matching the proposed engagements with available staff and planning periods.
  2. A validator checks the draft and reports that a required area is not covered and that one specialist is assigned to overlapping engagements.
  3. Those findings are routed back to the agent. It adds the missing coverage, changes the sequence and reallocates the overlapping assignment.
  4. The revised draft is checked again. If a constraint still fails, the finding triggers another revision. Once the checks pass, the draft is sent to the internal auditor for substantive review and clearance.

Result: The workflow returns a draft workplan that satisfies the encoded planning constraints, together with a record of the failed checks and revisions. The internal auditor can then assess whether the result is sensible, including whether the agent optimised what was easy to score while overlooking less readily quantified concerns.

In a United Nations workplace

At a shared services centre, an internal auditor uses an approved planning workflow to prepare the annual workplan before it goes to the front office for clearance. The workflow checks each draft against available capacity, required coverage and scheduling constraints, then uses the findings to revise and check the workplan again.

The validator's findings are fed into the next planning step rather than merely recorded. Each failed check changes the subsequent draft, creating an explicit revise-and-recheck loop. Passing the checks shows that the stated constraints were met, not that the workplan reflects sound audit judgement.

Before you try thisInternal audit planning may expose control weaknesses, allegations or personal information. Such material must not be entered into a tool that is not approved for it. Access controls and retention requirements still apply. The loop must not automatically remove, downgrade or clear an engagement. The internal auditor remains responsible for the workplan and its clearance.

Where you may hear it

  • An annual workplan review in an internal audit function
  • An ICT governance board discussion on controls for autonomous agents
  • A vendor demo during a procurement meeting
  • A design session for an automated workflow at a shared services centre
  • A post-implementation review after an automation pilot

Avoid confusion

Avoid confusion

Often confused with

Common misconceptions

  • Common misconception: A feedback loop means the system always gets better each time.

    Correction: Not necessarily. Improvement depends on the quality of the feedback and the comparison rule. If the feedback is noisy, delayed, biased or based on the wrong target, repeated adjustment can make performance worse rather than better.

  • Common misconception: Feedback loops are the same as reinforcement learning.

    Correction: They are related but different. Reinforcement learning usually refers to a training approach where a model is updated over many episodes using reward signals. A feedback loop can happen during one live task at run time, even if the model weights never change.

  • Common misconception: Any sequence of observe then act counts as a feedback loop.

    Correction: A single observe-act step is not enough. The defining feature is that the observed result affects a later action through repetition or correction. Without that return path, there is no loop.

Quick check

Which situation best shows a feedback loop in an AI system?

Go deeper

Go deeper

The simple version

It is a repeat-and-check pattern: do something, look at what happened, and use that result to improve the next step.

The technical version

In AI systems, a feedback loop is a structure in which an agent or workflow produces an action and routes an observation or evaluation of its outcome into a later step. The system may compare that signal with a goal, constraint or scoring rule and adjust the next action. Feedback may come from the external environment, a software tool, a validator, a user or another model. The loop may be explicit, such as retry-until-valid, or more complex, such as plan-execute-evaluate-replan. A feedback loop does not by itself imply model training. It can operate entirely at inference time, with no parameter update. Observation and action name the signals and steps in an acting system. A feedback loop emphasises the return path by which an outcome affects later behaviour. Design choices include the feedback source, delay, noise tolerance, stopping condition, human escalation and safeguards against oscillation, runaway retries or optimisation of a poor proxy.

Reviewed external resources

  • Primary sourceModel Context Protocol (opens in a new tab)Model Context Protocol

    This link explains the Model Context Protocol and how tools can provide structured information back to a model, which suits technical readers interested in how feedback is passed between systems.

    Deeperlink checked 2026-07-31

  • EncyclopaediaFeedback (opens in a new tab)Wikipedia

    This link gives a broad introductory explanation of feedback as a general idea across systems, which suits readers who want the core concept before applying it to AI.

    Intermediatelink checked 2026-07-31

  • ArticleBuilding effective agents (opens in a new tab)Anthropic

    This link explains how AI agents take actions and use results from those actions, which suits readers connecting feedback loops to agent behaviour.

    Intermediatelink checked 2026-07-31

  • VideoVideo explanations: Feedback loop (opens in a new tab)YouTube search

    This search results page offers multiple video explanations of feedback loops from different creators, which suits readers who prefer to compare visual teaching styles rather than rely on one source.

    search results, not one pagelink checked 2026-07-31

  • DiscussionCommunity discussion: Feedback loop (opens in a new tab)Reddit search

    This search results page shows community discussions and examples of how people talk about feedback loops in practice, which suits readers who want informal explanations and debate but should read critically.

    search results, not one pagelink checked 2026-07-31

Where this came from

Drafted with a language model through an offline pipeline, checked against this site's schema, and every external link above fetched to see whether it answers. Treat it as a starting point and check anything that matters against the primary sources. How this site is built and what that means.

The one thing to remember

In a feedback loop, an outcome is not merely reported. It is routed back into the process and changes what the system does next, for better or, if the signal or rule is poor, repeatedly for worse.