Floor Plan Versioning

LogicSite tracks every floor plan as a version tree owned by the structure — not the project. That means as a site owner moves from one contractor engagement to another, the version history persists; every project that touches the structure contributes to the same tree.

The Version Tree

Structure: Building A – Floor 2
└── v5  As-Built (current)             ← isLatest = true
    ├── v4  CO #2 – Panel relocation   ← named milestone
    ├── v3  CO #1 – Added 4 cameras    ← named milestone
    ├── v2  Contractor working draft
    └── v1  Original Design            ← frozen at project start

• Named versions (change orders, milestones, as-builts) surface prominently in the version panel.
• Minor working-draft edits between milestones collapse under a "Show full history" toggle.
• The editor exposes two tabs: Project (versions created during this engagement) and Structure (the full cross-project history).

Change Orders

Once a project leaves Design, the floor plan is locked by default. Creating a change order explicitly captures the intent to modify the scope:

The snapshot is a full deep copy of pages, device icons, annotations, coverage shapes, junction boxes, and conduit paths — so prior change orders remain fully reconstructable for audit.

As-Built Freeze

When a project transitions to Substantial Completion, the current document is deep-copied and frozen as the As-Built. The warranty period begins at this moment. As-Builts are read-only; to edit later, fork them.

Forking

Site owners can fork any named version to create an editable copy — used when planning renovations, expansions, or handing a scoped working copy to a new contractor. The fork retains a parent pointer back to the source version.

Viewing Diffs

The version tree lets you open any two versions side-by-side to compare device placements and annotations. Use this during closeout walks to verify every scope change is reflected in the as-built.

What's Next?