1. Real Estate Document Vault
  2. Features
  3. Review decisions
Feature · Review decisions

Review decisions

Record an independent decision against the exact packet revision reviewed.

OverviewReview Decision Inbox
Real Estate Document Vault · Review decisions

Review Decision Inbox

Approval conditions

New
SourceSource revisionDecisionReviewerEvidence reference
PP-43265890PendingER-716
PP-72802320PendingER-714
PP-72698130PendingER-632
PP-66758140PendingER-605
PP-97721820PendingER-953
6 of 6 records
ER-716Review decisions · RD-31684
Pending
SourcePP-43265
Source revision890
Example screen with sample data

What you can do

Decide on a known revision

A review decision belongs to a property packet and identifies the source revision that the reviewer considered. Its decision can be Pending, Approved, Returned or Rejected. The reviewer, decision time, reason and evidence reference help the team understand why that outcome was recorded. This is the point where a person determines whether the assembled material can proceed, needs correction or must stop.

The reviewer should inspect the packet, title versions and evidence documents together. An attachment marked verified establishes a checked source item; it does not settle every title question. A version marked Accepted describes that observation; the packet decision still belongs to the independent reviewer. This separation lets the Sharing Manager find an approved decision for the revision being considered.

How the work is organized

  • Inbox. Pending decisions remain with a named reviewer until that person records an outcome.
  • Reason. Returned and Rejected decisions carry an explanation the owner can act on.
  • Revision. A later packet change calls for review of the new source revision rather than reusing an old approval.

What to agree during setup

Decide how reviewers are assigned and who may change a decision after it is recorded. Agree what evidence reference is sufficient for a property document decision. The team needs a clear rule for a return versus a rejection: a return asks the owner for a repair; a rejection records a stop on the submitted material. Also agree who checks that the reviewer is independent of the packet owner when that separation is required by the organization’s policy.

A review may discover a changed parcel number or a missing page in an attachment. The reviewer should make the issue concrete in the reason and leave the packet’s earlier revision understandable. A follow-up action can then put a due date and person on the correction, while the decision remains a historical record of what was reviewed.

Check the handoff on an actual case

The Document Reviewer opens an indexed packet and finds a title version with a different encumbrance reference from the source attachment. They record Returned on the decision for the current revision, write the discrepancy and point to the evidence. The Packet Owner obtains the correct source, adds a new version and resolves the follow-up. The reviewer then considers the revised packet and records a new decision. The Sharing Manager checks that the Approved decision refers to the revision about to be shared. An earlier approval cannot be treated as approval of the corrected material.

What your team sees

  • Review Decision Inbox — Pending revision decisions assigned for review.
  • Returned Reviews — Decisions with reasons that need owner attention.

Follow the work through

What it keeps track of

Data model
Review decisions
Independent reviewer decisions recorded against an exact packet revision.
Property packets
Document packets assembled for a property, with status and sharing scope.
Title document versions
Versioned title document observations belonging to a property packet.
Evidence documents
Source evidence documents supporting a property packet.
Follow up actions
Assigned follow-up work arising from review or execution.

Who uses it

Permissions
Document Reviewer
, Packet Owner, Sharing Manager, Records Auditor.

Set up Real Estate Document Vault your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started