---
title: Annotation Points
slug: annotation-points
docTags: 
createdAt: 2024-01-31T08:27:51.264Z
---

## Annotation Points (AP) Overview

:::hint{type="info"}
**What are Annotation Points?**
Annotation Points (AP) are a project-level scoring system that quantifies every annotation action—tasks, objects, shapes, and properties—into a single, normalized unit. 

For setting AP see our [Annotation Points & Targets](https://docs.kognic.com/annotation-points-and-target) guide for details.
:::

## 1. Why use AP?

- **Normalize effort.** Different projects and taxonomies vary in complexity; AP lets you compare “apples to apples.”
- **Set clear targets.** Define an AP/hour goal per project and track productivity as a percentage of that target.
- **Align on value.** Reward high-effort work (3D boxes, property setting etc..) and discourage low value work such as micro adjustments.

## 2. How is AP calculated?

**AP Calculation Formula**

:::BlockQuote
AP = (Points Per Task × #Tasks)
   \+ ∑\[Points Per Object × #Objects]
   \+ ∑\[Points Per Shape  × #Total Shapes]
   \+ ∑\[Points Per Property × #Properties]
   \+ ∑\[Points Per Dynamic Shape × (#Total Shapes - #Static Shapes)]
   \+ ∑\[Points Per Static Object × #Static Objects]
:::

- **Points Per Task:** flat bonus for submitting a task
- **Points Per Object:** base points for creating each object
- **Points Per Shape:** additional points per frame/shape instance
- **Points Per Property:** points for setting or updating object/scene properties
- **Points Per Static Objects: **Points for setting or updating a static object
- **Points Per Dynamic Object**: Points for setting or updating a dynamic object.

AP are only generated during annotation and correction tasks (not pure reviews).
Actual AP appear in parentheses next to your productivity percentage.

### AP Targets & Productivity %

Once your project’s AP specification is configured, set an **hourly AP target** (e.g. 300 AP/h). Productivity is then:

:::BlockQuote
Productivity (%) = (Total AP earned ÷ (Target AP/h × Hours worked)) × 100
:::

- 🟢 **≥ 100%:** meeting or exceeding target
- 🔴 **\< 100%:** below target

Stopwatch-reported hours are used for “Hours worked.” If no stopwatch data exists, Productivity shows as **N/A**.

In addition to the overall AP/hour target, projects can configure an **expected learning curve** — a per-week speed ramp-up expressed as a percentage of the annotation speed target. This is used on the Learning Curve metrics tab to visualize whether new annotators are onboarding at the expected pace. See Annotation Points and Target for configuration details.

## 3. FAQs

### Q: Why did my AP drop, or even go negative when I added shapes?

**A:&#x20;**&#x4F;ur system takes a “snapshot” of your total AP every 10 minutes and recalculates the **entire** annotation chain using the **current** point weights. If the Project Manager have recently **lowered** the points per object/shape, the snapshot will:&#x20;

1. Apply the **new** lower weights retroactively to all previously annotated shapes.
2. Compare that new total against your last snapshot.

If the new weights are lower than before, your **historic** AP total shrinks—so adding shapes can produce a **negative delta** in AP.