Reviews are where wireframes earn their keep — catching structural problems while they're cheap to fix. This workflow shows how to run collaborative reviews in StretchWire and capture a clean sign-off using live rooms and version snapshots.
Why review at the wireframe stage
Structural mistakes are far cheaper to fix in a wireframe than in a design or a build. Reviewing early — while everything is low-fidelity — keeps feedback focused on what goes where and in what priority, not on colors and copy that aren't decided yet.
Step 1 — Prepare the boards
- Make sure each screen you want reviewed is its own board with a clear title.
- Replace placeholder content with real intent so reviewers evaluate the actual structure, not lorem ipsum.
- Capture a named snapshot before the review —
Review round 1 - start— so you have a clean baseline.
Step 2 — Run the review live
Invite reviewers to open the same board; everyone joins that board's live room and sees one shared document. Because sessions are board-scoped, different reviewers on different boards don't collide. Walk the group through the structure frame by frame — Desktop, then Tablet, then Mobile — and make edits in real time as consensus forms. Autosaves capture the evolving document as versions automatically.
Tip: Assign one person as the driver who makes edits during the call, so two people aren't reshaping the same block at once.
Step 3 — Capture each round
At the end of each review round, take a named snapshot — Review round 1 - final. This turns your version history into a decision log: each round has a clear before/after, and you can always return to how the board looked at any milestone.
Step 4 — Iterate between rounds
Between reviews, apply the agreed changes and snapshot again — Review round 2 - start. Because every save is preserved, you can experiment freely; if a direction doesn't land, roll back by re-saving an earlier version's document as the current one.
Step 5 — Sign-off
When stakeholders approve, capture a clearly named sign-off snapshot — Client-approved v1. This is the artifact you hand to design and development (see From wireframe to design and development handoff). Naming it unambiguously means there's never a question about which version was approved.
Example
An agency reviews a client's Home and Pricing boards. Before the call they snapshot Review 1 - start. On the call, the client and the design lead join the Home room; the agency's driver reorders the hero and testimonials live while everyone watches. They repeat for Pricing, then snapshot Review 1 - final. After one more round and a Client-approved v1 snapshot on each board, the structure is locked and ready to design against — with a full history of how each decision was reached.
Tips
- Snapshot at the start and end of every round so history reads like a clean decision log.
- Keep reviews focused on structure and hierarchy; park visual and copy debates for later stages.
- Use descriptive, dated snapshot titles (
Client-approved 2026-07-10) so the approved version is unmistakable.
Troubleshooting
Reviewers can't see each other's cursors/edits. Confirm everyone opened the same board and is in the same organization — each board is a separate room.
I need the pre-review version back. Open the snapshot you took before the round and re-save its document as current; the intervening versions are preserved.
A reviewer only has read access. On the workspace surface, editing requires a Pro entitlement. Reviewers without it can still view; have a licensed driver make the edits.
Was this helpful?
Help us improve this article
Use these controls to share whether this answer solved the issue. Feedback helps prioritize updates to StretchSuite Support.