Early access: join the waitlist.
OrgRelay
EN
English简体中文繁體中文Bahasa Indonesia
Join the waitlist
EXCEPTION REVIEWS

Make the review move a piece of work forward.

An exception review helps the team handle a condition that changes the plan. Bring the source, identify the affected result, and agree who provides the next answer or decision.

AI Chief compares supplier quotations using the source table
Product interface · sample data
01

Start with the work that needs intervention.

Choose a changed input, a held conclusion, or a decision blocking the next step. The exception workflow, dashboard, and goals-and-tasks workflow connect the issue to its result.

02

Bring one question the right person can answer.

State what was expected, what was observed, and where the evidence sits. Use the exception note, AI Chief, and company setup guide to identify the source and process owners.

Product illustration

A focused exception review

AI Chief retrieves the conclusion of an outgoing quality inspection report
Product interface · sample data
03

Choose the response that fits the gap.

A missing record needs a source owner; an unclear term needs interpretation; a commitment needs authority. The approval boundaries article and source-context article help distinguish them. Procurement and Finance contribute different supporting material.

Question typeWhat to askPerson responding
SourceWhich fact or condition needs confirmation?Source owner
RequirementWhich result now applies?Goal owner
AuthorityWho may decide this action?Authorized decision maker
HandoffWho accepts the next task?Recipient and process owner
04

Use the review to decide the next action.

An approval packet frames a choice. A Support Agent can draft wording and an Operations Agent can organize its handoff. The reviewer checks the relevant output and names the next responsibility.

05

Follow one issue from discovery to correction.

In a restaurant workflow, two branches use different units for a requirement. The preparer retains both rows. The source owner explains the units, the manager decides how to summarize them, and the recipient reviews the revised result.

  1. 01

    State the observed difference

    A branch requirement needs clarification about packs and weight.

  2. 02

    Name the source owner

    The manager routes the unit question to the person who can explain it.

  3. 03

    Update the summary

    The preparer preserves the confirmed basis in the revised result.

  4. 04

    Check the next handoff

    The recipient verifies the correction and identifies any separate purchasing decision.

Document library filtered to purchasing documents
Product interface · sample data
06

Close through the answer and the dependent work.

Check that the clarification is recorded and the affected output reflects it. The handoff template and weekly goal template keep the review connected to the result it serves.

07

Use recurring questions to improve the process.

The cause may be a source format, an unclear role, or a task condition. Review the team participation guide, manager scenarios, Agent brief, and first goal guide to choose a targeted change.

08

Give the next review a clear question.

Name the answer, owner, and affected result that should be checked next time. Use information guidance and integration requirements to select the source material and audience.

Questions, answered.

Who should join the review?

People who can explain the source, assess the effect, or authorize the needed action.

What should the preparer bring?

The observed difference, relevant source, affected result, and a specific question.

How should interim work be agreed?

Name the sections that can continue, their conditions, and the next review point.

When is the issue closed?

The answer is recorded, dependent work is reviewed, and the recipient understands the next step.

Join the waitlist
Product illustration