Review Queue
Every discrepancy the document-extraction pipeline found between a source document and the current Master Record. Nothing here has been written yet — approve to apply, reject to discard.
What this page is for
When a source document (brochure, RERA certificate, price list, etc.) is processed, the extraction pipeline compares what it read against this project or partner's current Master Record. Anything it can't safely apply on its own lands here instead of silently overwriting anything.
- Pending — not yet applied anywhere. Each card shows the Current value already on file next to the Proposed value the pipeline extracted, along with its confidence and where it came from.
- Review the two values. Approve writes the Proposed value into the Master Record (an optional note explains why, for the audit trail). Reject discards the proposed value and leaves the Master Record untouched.
- A field the pipeline was unsure about, a value that conflicts with what's already saved, or a document describing a project/unit that doesn't exist yet in the CRM are the three reasons something ends up queued here rather than applied automatically — a genuinely blank field with a high-confidence read is applied immediately and never appears in this queue.
- Once resolved, an item moves to the Approved or Rejected tab — both stay visible as a permanent record of what was decided and why.