Review should not split the record
If browser feedback stays isolated in the portal, the project record becomes harder to trust. Pulling those events back into desktop keeps the narrative in one place.
Portal comments, approvals, and rejections are most useful when they do not remain browser-only. ChangeSpan treats them as review events that can be pulled back into the desktop workflow.
If browser feedback stays isolated in the portal, the project record becomes harder to trust. Pulling those events back into desktop keeps the narrative in one place.
Once comments and decisions return to desktop, the team can respond, revise, or document the next action directly in the same controls workflow.
The overall loop becomes desktop publish, portal review, desktop sync, then action. That shape is easier to explain later during internal review or external scrutiny.