Title document versions

A title document version is an observation belonging to a specific property packet. Its sequence, description, observation date and document date help a reviewer understand which version came first and which source was used. The source reference and source record identifier point back to the item being interpreted. A version can carry a parcel identifier, document type, content hash, encumbrance reference and sharing expiry, so a change in title material stays visible beside the packet it may affect.

A reviewer can mark an observation Pending, Accepted or Rejected. That outcome is about the version; it is separate from the decision on the whole packet. One rejected version need not erase earlier accepted material. The packet owner should resolve the source conflict and retain the record of what the reviewer saw.

• Sequence. Review versions in their recorded order and use dates to explain when each document was observed.
• Source. Compare the source reference and parcel identifier with the packet before accepting an observation.
• Outcome. Keep Pending observations visible until the reviewer has enough evidence to accept or reject them.

Choose a naming convention for document types and a rule for version sequence. Decide how a changed deed or agreement becomes a new version and who may set its outcome. The source record identifier should refer to an item that the team can retrieve; agree who maintains that connection. If amount or quantity applies to a document observation, agree its unit and meaning before using it in a report.

The team should also decide whether a newer observation supersedes an earlier accepted one or sits alongside it. The version record keeps both available, while the packet revision identifies which set of source material was reviewed. This is especially useful when a parcel number or encumbrance reference differs between copies.

A Packet Owner receives a corrected title document after the original was indexed. They add a new version with the corrected document date and source reference, leaving the earlier sequence intact. The Document Reviewer compares both versions with the packet’s parcel identifier and the underlying evidence. If the correction is sound, the reviewer records Accepted on the new observation and the packet follows a new review path. If the source still conflicts, the reviewer records Rejected and explains the issue through a follow-up action. The reader can see the sequence and outcome without treating a later upload as an automatic approval.

• Title Versions Awaiting Outcome — Pending observations that need a source comparison.
• Indexed Packets for Review — Packets whose current revision is ready for a decision.

See title version review and review and sharing.