> ## Documentation Index
> Fetch the complete documentation index at: https://help.iteam.works/llms.txt
> Use this file to discover all available pages before exploring further.

# Results

> The company's results meeting, always up to date: how each KPI evolves over time, current value × target, who measures it and a filter by area. Measurements run automatically (weekly by default), so the numbers never grow stale.

**Results** is where the evolution of the KPIs shows over time — the company's "results meeting", except live and always up to date. Instead of someone building a slide every week, Cortex **measures on its own** and keeps the history. You open it and see where each indicator is heading.

<Frame caption="📸 Screenshot to insert [/en/cortex/results]: Results page with the company KPIs at the top, each with current value, target and an evolution chart over the period; filter by area alongside.">
  <img src="https://mintcdn.com/iteam/E1mg8rFlXblsaNT0/images/placeholder.svg?fit=max&auto=format&n=E1mg8rFlXblsaNT0&q=85&s=36c435f4df28c31a7e114586a931bbd2" alt="Results — KPI evolution" width="800" height="420" data-path="images/placeholder.svg" />
</Frame>

## How it works, in one sentence

Cortex **measures** each KPI periodically (using the connected data) → stores each measurement with a date → here you see the **time series** (current × target × trend), the **company** first and then by **agent/area**.

## What you see

<AccordionGroup>
  <Accordion title="Company first, then the edge" icon="building">
    The **company** KPIs appear at the top (the result leadership cares about). Below, the **agents'** KPIs that feed each of them — the same cascade from [Objectives](/en/cortex/objectives), now in numbers over time.
  </Accordion>

  <Accordion title="Current × target × trend" icon="chart-line">
    Each KPI shows the **latest value**, the **target** and the **evolution chart** over the chosen period. At a glance you know whether it's rising, flat or falling — and whether the target is close.
  </Accordion>

  <Accordion title="Who measures" icon="user-check">
    Each KPI indicates **which agent** is responsible for measuring it. That makes it clear where the number comes from (and who to ask if something looks off).
  </Accordion>

  <Accordion title="Filter by area" icon="filter">
    Focus on a specific area to see only its KPIs — handy in team meetings.
  </Accordion>
</AccordionGroup>

## Automatic measurement (the numbers don't grow stale)

Cortex has a **global schedule** that measures the KPIs periodically — **weekly by default**. Each run is recorded in a **measurement log**, so you have the full history: when it was measured, what value came out.

<Info>
  You don't have to wait for the schedule: you can **run the measurement on the spot** from [Objectives](/en/cortex/objectives) (run the objective → measure KPIs). The new point shows up here in Results shortly after.
</Info>

## How to read it alongside Actions

The power of Cortex is in cross-referencing the two screens: in **Results** you see the **KPI rise or fall**; in [Actions](/en/cortex/actions) you see **what the humans did** in that period and the assessed **impact**. Together, they answer *"the number changed because of what?"* — which is exactly what becomes a [Learning](/en/cortex/learnings).

## Permissions

You see the results of the **areas you belong to** (owner/admin see everything). Running measurements follows the same configuration rule as [Objectives](/en/cortex/objectives).