We would like to propose an enhancement to Wrike’s approval workflow that improves visibility into updates made between approval rounds.
Currently, when a file is reviewed by multiple approvers and at least one approver requests changes, the asset must be updated and re-routed through approvals. However, when the revised version is submitted, approvers must manually review the entire asset again or use the comparison tool to identify differences. This can be time-consuming and inefficient.
Current Workflow Challenge
- Asset is routed to multiple approvers (e.g., Approvers 1–3).
- Some approvers approve, while at least one requests changes and leaves comments.
- The creative/graphics team updates the asset.
- The asset is re-submitted for approval.
- Approvers must:
- Re-review the entire file, or
- Manually use comparison tools to identify what changed.
This creates inefficiencies and increases review time, especially for complex designs.
Proposed Solution
Introduce a feature that automatically highlights or summarizes changes made between approval versions when an asset is re-submitted.
Suggested capabilities:
- Auto-generated “change summary” between versions
- Visual highlights (e.g., callouts, overlays, or diff markers) showing what was updated
- Optional tagging of changes tied to specific reviewer comments
- A quick “review changes only” mode for approvers
Example Use Case
- Approver 1 requests updates to headline text and image placement.
- The design is revised accordingly.
- Upon re-routing:
- Approvers can immediately see exactly what changed
- They can quickly validate updates instead of re-reviewing the entire asset
Business Impact / Benefits
- Improves efficiency in approval cycles
- Reduces review time for stakeholders
- Increases clarity around implemented feedback
- Minimizes risk of missed changes
- Enhances overall user experience for cross-functional teams
Additional Notes:
This feature would be especially valuable for teams handling high volumes of creative assets or complex designs, where small changes can be difficult to track manually.
