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

# Review Task

> Add quality checks to your workflow using human reviewers or AI validation.

Review tasks let you check the quality of your workflow's output before moving on. You can have a real person review it (Human Review) or let AI check it automatically (Agentic Review).

<Note>
  Only Opus Agent, Custom Agent, Human Task, and Text Extraction tasks can connect to a Review Task.
</Note>

<CardGroup cols={2}>
  <Card title="Human Review" icon="user-check" href="#human-review">
    Pause your workflow for a person to accept or reject the output.
  </Card>

  <Card title="Agentic Review" icon="robot" href="#agentic-review">
    Let AI check the output and fix problems automatically.
  </Card>
</CardGroup>

## Human Review

Human Review pauses your workflow so a real person can look at the output and decide whether to accept it or reject it. Use it when you need human judgment before moving forward.

### Key Capabilities

<CardGroup cols={2}>
  <Card title="Accept or Reject" icon="check-to-slot">
    Reviewers decide whether the output is good enough to continue.
  </Card>

  <Card title="Edit on Reject" icon="pen-to-square">
    Reviewers can fix problems before the workflow continues.
  </Card>

  <Card title="Deadline Setting" icon="clock">
    Give people a specific timeframe to complete their review.
  </Card>

  <Card title="Accept/Reject Paths" icon="code-branch">
    Route your workflow differently based on the reviewer's decision.
  </Card>
</CardGroup>

### When to Use It

Use Human Review when you need a person to check the output before moving on:

* Verify AI-generated content before publishing
* Check that extracted data is accurate
* Confirm output meets compliance requirements
* Review flagged or uncertain results

<Note>
  Need someone to fill in information instead of just approve/reject? Use [Opus Human Task](/tasks/agent/opus-human-task) instead.
</Note>

### How to Add Human Review

<Steps>
  <Step title="Drop it into your workflow">
    Drag a Human Review task into your workflow after the task you want reviewed. The review automatically inherits all inputs and outputs from the previous task.
  </Step>

  <Step title="Write review guidance">
    Explain what the reviewer should check and when to accept or reject.
  </Step>

  <Step title="Set a deadline">
    Choose how many hours the reviewer has to complete the review.
  </Step>

  <Step title="Connect both paths">
    Wire the Accept output to one path and the Reject output to another. Make sure both are connected.
  </Step>

  <Step title="Test it">
    Run a preview to make sure both paths work as expected.
  </Step>
</Steps>

<Note>
  Make sure you connect both the Accept and Reject paths to something. If you leave one unconnected, your workflow might not work correctly.
</Note>

### Tips for Better Results

<AccordionGroup>
  <Accordion title="Write clear instructions">
    Reviewers need to know exactly what to look for:

    * Explain what makes output acceptable
    * Give examples of what to accept vs. reject
    * List specific things to check
  </Accordion>

  <Accordion title="Give people enough time">
    Be realistic about deadlines:

    * Remember people work in different time zones
    * Allow time for thorough evaluation
    * Factor in editing time if you enabled it
  </Accordion>
</AccordionGroup>

## Agentic Review

Agentic Review uses AI to check your workflow's output automatically. It can approve outputs that meet your criteria, flag problems, or even fix issues on its own—all without waiting for a person. Use it when you need to review lots of outputs quickly and consistently.

Agentic Review is powered by **Opus Swarm**, a set of review agents created by AppliedAI. More agentic providers may be supported in the future.

### Key Capabilities

<CardGroup cols={2}>
  <Card title="AI Validation" icon="magnifying-glass">
    AI checks outputs against your criteria automatically.
  </Card>

  <Card title="Auto-Correction" icon="wand-magic-sparkles">
    Optionally fix problems without human involvement.
  </Card>

  <Card title="High Volume" icon="chart-line">
    Review thousands of outputs quickly and consistently.
  </Card>

  <Card title="Pass/Fail Paths" icon="code-branch">
    Route your workflow based on whether the output passes or fails.
  </Card>
</CardGroup>

### When to Use It

Use Agentic Review when you need to check lots of outputs automatically:

* Validate that data matches an expected format
* Check that required fields are present
* Fix common formatting issues automatically
* Filter out outputs that need human attention

<Note>
  Need human judgment or accountability? Use Human Review instead. Agentic Review works best when you can clearly define what "correct" looks like.
</Note>

### How to Add Agentic Review

<Steps>
  <Step title="Drop it into your workflow">
    Drag an Agentic Review task into your workflow after the task you want reviewed. The review automatically inherits all inputs and outputs from the previous task.
  </Step>

  <Step title="Choose an agentic provider">
    Select the AI provider that will perform the review. Currently, **Opus Swarm** is available.
  </Step>

  <Step title="Write validation criteria">
    Explain what makes output acceptable—what to check, required fields, expected formats.
  </Step>

  <Step title="Connect both paths">
    Wire the Pass output to one path and the Fail output to another. Make sure both are connected.
  </Step>

  <Step title="Test it">
    Run a preview with both valid and invalid data to make sure both paths work.
  </Step>
</Steps>

<Note>
  Make sure you connect both the Pass and Fail paths to something. If you leave one unconnected, your workflow might not work correctly.
</Note>

### Tips for Better Results

<AccordionGroup>
  <Accordion title="Be specific about what to check">
    Vague criteria produce inconsistent results:

    * Good: "Date must be in YYYY-MM-DD format"
    * Bad: "Data should be correct"
  </Accordion>

  <Accordion title="Test with edge cases">
    Before activating:

    * Try data that should pass
    * Try data that should fail
    * Make sure both paths work correctly
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Opus Human Task" icon="user-pen" href="/tasks/agent/opus-human-task">
    Collect information from a person instead of just approve/reject.
  </Card>

  <Card title="Human Decision Agent" icon="user-check" href="/tasks/agent/human-decision-agent">
    Let a person choose which path your workflow takes.
  </Card>

  <Card title="Decision Agent" icon="code-branch" href="/tasks/agent/decision-agent">
    Route your workflow automatically based on conditions.
  </Card>

  <Card title="Workflows" icon="diagram-project" href="/guides/workflows">
    Learn how all the pieces fit together.
  </Card>
</CardGroup>