Desktop stays the authoring layer
The desktop app is where schedules, scenarios, RFIs, submittals, and controls records are created and maintained. That keeps the working record closer to the team actually doing the controls work.
Guide 1
How ChangeSpan fits a desktop-first controls workflow
ChangeSpan is built around local-first authoring. Desktop users do the heavy project controls work locally, then publish reviewable snapshots when collaboration is needed.
The portal stays focused on review
The portal is the review layer, not the primary authoring system. Reviewers can respond to a stable snapshot without creating confusion around a constantly changing live desktop state.
The workflow closes back in desktop
When comments, approvals, or rejections sync back into desktop, the result is a clearer project record and a more explainable workflow from issue to response.