Copy page

Monitor & Review

Human review

Some decisions are best confirmed by a person. When the AI Agent needs human judgment on an item — a low-confidence extraction, a value that failed validation, an exception it can't resolve on its own — it asks a reviewer for help. The reviewer checks the source documents, gives the Agent the correction or confirmation it's asking for, and submits, so the Agent can continue processing the item.

This page is the complete guide to that experience: how the Agent asks for review, how reviewers find and open it, what they can inspect and correct, and how a submitted review gets back to the Agent.

Permissions. Reviewing items is the Reviewer role's primary job — reviewers can open items, inspect and download the source documents, correct field values, and submit reviews, but they don't build flows or see run history. Admins have full access as well. See Users and access.

How an item reaches review

The Agent asks for review through a Review node placed in the flow. When it reaches that node, the Agent puts the item into the Review status and tells the reviewer why it needs help, what specifically to review, and shares its insights and recommendations for what to do next. The reviewer gives the Agent the feedback it's asking for and submits, and the Agent continues processing the item. See Utility nodes.

The default Exception Details is a summary of the errors from the flow's Field Validation node. To show a different message, bind another field to the Exception Details card on the Insights tab, configured on the Review node. (A flow with no Review node never pauses for a person — it runs straight through to a Complete action.)

Find work in the Items list

Reviewers work from the Items list, which shows the items produced by your AI Agent across one or many flows. Each row shows the item's Name, an Agent Summary, its Status, the assigned Reviewer (or Unassigned), the Flow Name, and when it was Created.

To focus on what needs attention:

• Filter by status to show only items in Review.
• Filter by reviewer to see items assigned to you (or to anyone), and by flow to focus on one AI Agent.
• Search items — the search box accepts plain text and key:value tokens (for example, flow:fnol status:REVIEW).

You can sort the columns and page through the list. An item currently open by someone else shows an Editing disabled badge with a lock, so you know not to wait on it. If there are no items, the list shows No items yet with a note that items appear once they are created.

Click an item to open it.

The item screen

An open item has a header showing its name (or Item from [flow] flow) and its Status badge. Below the header are two tabs:

• Insights — an overview of the item: its key details (Item ID, Flow Name, number of Documents, Reviewer, Created date), what decisions the Agent made and why, any recommendations it has, and — if it's asking for help — the exception reason and what to do next. Use it to get oriented before you review.
• Review — where you give the Agent the feedback it's asking for: inspect and correct the item's fields. A badge on the tab shows how many fields still need review.

The actions for the review — Save, Cancel, and Submit Item — sit at the top right of the item screen.

Both tabs are fully configurable from the flow: the Field Groups setting on the Review and Complete nodes controls which fields appear here and how they're grouped.

Inspect the item

On the Review tab, the item's extracted fields are listed, organized into groups you can Expand All or Collapse All. Several tools help you find what matters:

• Field filters. Switch between All Fields, With Data, Needs Review, and Empty — each shows a count. Needs Review lists the fields flagged by the validation rules set up in the flow's Field Validation node.

• Source filter. When more than one document is attached, filter the fields down to a single source document.

• View Documents. Toggle the document viewer to see the source file alongside the fields, so you can confirm a value against the original.

• Field sources. Each field shows which document the Agent was reading when it extracted that field. Click the source to jump to it:

  • If Grounding was on and found a bounding box for the field, it jumps to the exact page and highlights the box.
  • Otherwise, it jumps to the first page of the document.

  See InsurGPT nodes for the Grounding setting.

• Confidence. Each field shows a confidence indicator with a tooltip (Confidence: X%). Whether a field is flagged for review depends on the flow's Field Validation rules — add a confidence rule for fields that are critical or high-risk.

Fields that need review are marked visually and carry a short validation message explaining what's wrong (for example, a value that didn't match the expected format).

Correct the information

When a review is open and you hold the item (see locking below), you can edit field values directly:

• Text fields are edited inline in a text box.
• Choice fields present a dropdown of the allowed options.
• Tables are edited as a grid, cell by cell, with a popout for larger tables.

As you change a value, the field is highlighted as edited and an indicator appears; hovering it shows the original extracted value, so you can always see what the Agent first produced versus your correction. Values the Agent derived — such as a record it matched — appear among the fields the same way, and you correct them in the same place.

One reviewer at a time

An item under review is locked to the person reviewing it, so two people don't overwrite each other:

• If someone else holds the item, you'll see "This item is currently being reviewed by [name]. Editing is disabled." and the fields are read-only.
• If you're inactive for about 15 minutes, your lock is released and a banner offers Reclaim editing to pick the item back up.
• If the lock status can't be confirmed, editing is disabled with "Could not verify lock status."

Correcting document splits

If a flow includes a Split Documents node, its segmented output shows on the Review tab as separate, labeled documents with their own page thumbnails. When a split isn't right, reviewers can correct it directly:

• Reassign a page to a different document — there's no requirement that documents be adjacent.
• Create a new document from a set of selected pages. This covers both consolidating several documents (or specific pages from across them) into one, and dividing a document in two by moving some of its pages into a new document.
• Reorder pages within a document or across documents.

Field values never move, merge, or clear automatically when you make one of these corrections — a field's value doesn't change just because its source pages get reassigned to a different document. If a correction changes the pages a field's value came from, that field gets a stale-data warning so you know to check it; dismiss the warning once you've confirmed or fixed the value, using the same field-editing tools as any other correction.

Save, submit, and return the item to the Agent

Three actions move your work forward:

• Save stores your edits without finishing the review, confirming with "Fields updated." Use it to step away and resume later — your corrections and progress are kept.
• Submit Item completes the review, confirming with "Review submitted." Submitting gives the Agent your feedback and it continues processing the item.
• Cancel discards any unsaved changes in this review session and marks the item Canceled, a terminal state. Any changes you already saved are kept, but the review can't be resumed.

How a completed review appears afterward

After you submit, the item carries your corrections forward:

• The item status advances past Review as the Agent continues processing, ending at Complete when it finishes.
• Corrected fields keep both your value and a record of the original extracted value (shown on the edit indicator), so it's clear what was changed during review.
• The assigned Reviewer is shown on the item.
• In Run history, the review appears as a step in the run, so an Admin or Partner can see where the Agent paused for review and resumed.

Where to go next

• Item status reporting — see review work and other items summarized by status.
• Utility nodes — add and configure the Review node.
• InsurGPT nodes — add and configure the Split Documents node.
• Run history — where the review step appears in a run (Admin or Partner).
• Monitor and Review — how review fits the production operating model.
• Users and access — the Reviewer role and what it can do.