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

# Tasks

> Tasks in Kodexa represent human-in-the-loop review steps inside Activities for verifying extracted data, resolving exceptions, and approvals.

A **Task** is a unit of human work inside an Activity. It is owned, reviewable, completable, and tied to the business process when the platform needs a person to make a decision, resolve an exception, or confirm extracted data.

Tasks are not the whole workflow and they are not the primary process model. They are how people participate in an Activity.

## What Tasks Are For

Tasks exist where automation should pause for judgment:

* Review extracted fields before a process continues
* Resolve validation errors or missing data
* Approve or reject a business decision
* Route an exception to the right queue
* Capture a user decision that determines the next Activity step

The Task gives the person the right document context, data form, exceptions, and actions. The Activity keeps the process state and continues after the Task is completed.

## Task Shape

| Area             | Purpose                                                            |
| ---------------- | ------------------------------------------------------------------ |
| Owner or queue   | Who should work on it?                                             |
| Status           | Is it open, in progress, blocked, complete, rejected, or canceled? |
| Document context | Which document, packet, or extracted data is being reviewed?       |
| Data form        | Which review UI should the user see?                               |
| Actions          | What decisions can the user make?                                  |
| Exceptions       | Which issues need attention before completion?                     |
| Audit            | Who completed the work, when, and with what result?                |

## Tasks in an Activity

An Activity creates a Task when a configured step needs a person. The Task completion result becomes workflow state that can drive the next Activity step.

```mermaid theme={null}
sequenceDiagram
  participant Activity
  participant Task
  participant Reviewer
  Activity->>Task: Create review task
  Task->>Reviewer: Assign work
  Reviewer->>Task: Review data and choose action
  Task->>Activity: Complete with result
  Activity->>Activity: Continue or branch
```

## What Belongs in a Task

A Task should be specific enough that a person can finish it without reconstructing the entire process.

Good Tasks:

* Review this invoice extraction
* Resolve these validation exceptions
* Approve this loan packet summary
* Confirm this vendor match
* Reject this claim intake with a reason

Weak Tasks:

* Process this business workflow
* Run invoice automation
* Handle the loan process
* Figure out what happened

If the work is the overall process, model it as an Activity. If the work is a human decision point inside the process, model it as a Task.

## Tasks and Data Forms

Most Tasks are paired with a Data Form. The form controls how extracted data, validation errors, document context, and user actions appear to the reviewer.

The Task owns the work item. The Data Form owns the review experience.

```mermaid theme={null}
flowchart LR
  Task["Task"] --> Form["Data Form"]
  Form --> Data["Extracted Data"]
  Form --> Doc["Document Context"]
  Form --> Exceptions["Exceptions"]
  Form --> Actions["Complete / Reject / Route"]
```

See [Data Forms](/guides/data-forms/introduction) for the schema-driven review UI model.

## Design Rule

Use a Task when you need a person to show up in the workflow.

Use an Activity when you need the platform to carry the business process forward.