The Review Queue

The Investor Communications → Company Updates admin page is the review queue. It is the only place admins need to look to keep the Company Updates pipeline healthy.

The page is a two-pane layout:

• Left pane -- a list of every update, with the ones needing admin attention floated to the top
• Right pane -- the selected update's TLDR, KPI table, asks, wins, team changes, press mentions, body, and raw source

A top metrics row shows total updates, how many KPIs need review, how many asks are still open, and how many updates the AI extracted with low confidence.

The Sort Order: Review-First

The left pane is sorted to put work in front of you:

1. Updates with KPIs that the AI's reviewer flagged as suspicious (Needs review)
2. Updates with legacy KPIs that never got reviewed (treated the same way)
3. Everything else, newest first

Inside an update, the KPI table is also sorted review-first: Needs review at the top, then Not yet reviewed, then Auto-verified, then settled rows. The original ordering is preserved within each band.

KPI Statuses

Every KPI sits in one of these states:

The whole design exists so that the typical update has zero clicks of work: the AI's first pass extracts, the citation guard proves the number is verbatim, the second pass double-checks the meaning, and only the rows the second pass disagreed with surface for review.

Approving, Editing, Rejecting

For any KPI that needs review (or any auto-verified row you want to override):

• Approve -- accept the value as-is. The row moves to Verified by admin.
• Edit -- open the inline form to change the raw value, numeric value, unit, change text, or change percent. Saving moves the row to Edited by admin and audit-logs the before/after. Editing also implicitly approves the row -- there is no separate save-without-verify step.
• Reject -- mark the row as wrong. You'll be prompted for a reason (optional). The row is hidden from investor charts and the reason is recorded in the audit trail.

Every action is audit-logged with the admin's identity, the timestamp, and a description that includes the deal and the KPI name.

Resolving Asks

The Asks tab lists every request the founder made of investors. An ask stays Open until an admin resolves it. The default resolution reason when you click Mark filled is "founder reported filled," but you can also resolve an ask as "admin hidden" if it shouldn't surface to investors at all.

Resolved asks stay on the record (so the history is complete) but no longer appear on investor surfaces as open requests.

Re-extracting

The Re-extract button at the top of the right pane re-runs the AI extraction against the update's current body. Use it when:

• The first extraction produced garbage and you want a fresh attempt
• You edited the body upstream (e.g. the source email was re-cleaned) and want the extracted fields to catch up

Two safety rails are built in:

1. If the update's body is still on the placeholder text the platform writes when the cleaner fails ("empty body -- inbound message #N"), or if you explicitly ask for it, the platform will first re-clean the body from the original source email before re-extracting.
2. If an extraction is already in flight for this update, the button is blocked. Double-clicking, or clicking during a slow run, will not enqueue a duplicate -- doing so would race two AI jobs against each other and overwrite the loser's work, including any admin verifications that happened between the two runs.

Re-extracting replaces all KPIs, asks, wins, team changes, and press mentions with the new extraction. Anything an admin had already approved or edited will be wiped and re-derived. The audit trail keeps the previous values, so the action is reversible in principle, but in practice you should only re-extract when the existing extracted state is not worth keeping.

Hiding vs Retracting

Two destructive actions live at the top of the right pane. They look similar but mean very different things to investors.

Both actions are audit-logged and reversible by re-extracting from the source. The hide and retract decision is intentionally not a delete -- the row stays for portfolio history.

When the AI is Slow or Confused

The Extracting status means the AI is still working on the update. Investors do not see anything yet. This usually completes in a minute or two. If an update is stuck in Extracting for more than a few minutes:

• Check whether the source email was forwarded and the body is unusually long
• Use Re-extract to retry (the in-flight guard will tell you if the original is still running)
• If the update repeatedly fails extraction, Hide it and re-promote the source email manually from the Founder Emails page

The audit trail captures every extraction attempt and every admin action, so if anything looks off, start there.