Second Brain / Industry term
Reviewed record
A reviewed record is a piece of information you have inspected, approved, and connected to the work it supports, so it can be reused with confidence instead of being treated as unchecked raw material.
A reviewed record is a piece of information you have inspected, approved, and connected to the work it supports, so it can be reused with confidence instead of being treated as unchecked raw material. It sits at the trusted end of a path that runs from raw capture, to a processed copy, to a record a person has signed off on. Picture an agent that turns a meeting recording into a summary with three action items. The summary starts as a processed draft; once you read it, fix a wrong owner on one task, and approve it, it becomes a reviewed record your other workflows can cite. Until that approval, the system keeps it labeled as unreviewed so nothing downstream treats it as fact.
Builder example
If your assistant reuses anything it generates as if it were confirmed, one early mistake spreads into every later answer. Tell the agent to mark each output as unreviewed until a person approves it, and to pull only reviewed records when it answers a question or starts a new task. A to-do app that auto-creates tasks from an email draft should hold them as proposals until you confirm, so a misread date never quietly lands on your calendar.
Common confusion: A processed record has been cleaned up, summarized, or filed by the assistant. A reviewed record has been checked and approved by a person on top of that. Processing is work the AI did; review is the human sign-off that makes the record safe to act on.