Version Control

Version control matters more in commercial real estate than in most industries because lease documents, amendments, and estoppel certificates are frequently renegotiated, and the difference between the current fully-executed version and an earlier draft can carry real legal and financial consequences. A property manager who attaches an outdated rent schedule to a tenant notice, or a compliance team that audits against a superseded insurance certificate, is working from bad data — even though the correct version exists somewhere in the system.

SharePoint Online provides version control natively: every document library can retain major and minor versions, track who made each change and when, and allow authorized users to restore a prior version. That native versioning is real and reliable, but it is scoped to a single library. The moment a document moves between libraries — for example, when a lease graduates from an active deal-room library to a permanent property-record library — SharePoint's out-of-the-box tools do not automatically preserve that version history across the move.

ARC-Files closes that specific gap. The Document Mover module relocates files between libraries while carrying forward metadata and version lineage, so a document's history stays intact even as it moves through its lifecycle. Document Templates further reduce version confusion at the source by standardizing the starting point for leases, insurance certificates, and financial documents across every market, so fewer conflicting drafts are created in the first place.

Common mistakes teams make: relying on file names ("Lease_v2_FINAL_updated.docx") instead of SharePoint's built-in version history, turning off minor versioning to save storage and losing the ability to see incremental edits, and failing to restrict who can permanently delete version history during a library cleanup. Any of these can leave a compliance or legal team unable to answer a straightforward question: which version was in effect on a given date?