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

# Approving AI work

> Use human review to control customer promises, margin decisions, and system writebacks.

Approvals are how the team uses AI without losing operating control. Any action that changes a customer promise, margin position, supplier commitment, internal owner, or connected business system should be reviewed before it moves.

## What needs approval

<CardGroup cols={2}>
  <Card title="Customer commitments" icon="message-square-reply">
    Buyer replies with price, promise date, quantity, substitute product, or service recovery commitments.
  </Card>

  <Card title="Margin and finance" icon="chart-no-axes-combined">
    Margin exceptions, duty reserves, free-time exposure, credit notes, payment terms, and finance approvals.
  </Card>

  <Card title="System state" icon="database">
    PO extraction, SKU mapping, ERP writebacks, CRM changes, invoice checks, and document updates.
  </Card>

  <Card title="Sensitive context" icon="shield-alert">
    Actions that use customer, supplier, pricing, compliance, or internal operating notes.
  </Card>
</CardGroup>

## What each button means

| Action                                                  | Use when                                                              |
| ------------------------------------------------------- | --------------------------------------------------------------------- |
| <span className="ux-label is-success">Approve</span>    | The suggestion is correct and ready to move.                          |
| <span className="ux-label is-primary">Edit</span>       | The direction is right but the copy, data, or owner needs adjustment. |
| <span className="ux-label is-soft">Assign</span>        | Another operator, finance reviewer, or admin needs to decide.         |
| <span className="ux-label is-destructive">Reject</span> | The recommendation is wrong, stale, or unsafe.                        |

## Reviewer checklist

<div className="ubik-panel">
  <strong>Approval means accountability.</strong> Check source context, not just the drafted output. If the context is stale or missing, assign or reject the item instead of approving it.
</div>

* Source thread matches the customer, supplier, shipment, or account.
* SKU, quantity, unit, account, and owner mapping are correct.
* Pricing, margin, and promise-date logic fit the agreed guardrail.
* The action does not reveal internal notes, supplier pricing, or sensitive context.
* The activity trail will explain the decision later.

## Audit trail

Each reviewed action should leave enough context for a future operator to answer: what changed, who reviewed it, what was approved, and where it moved next.