Choosing a Remote Collaboration Tool for an Architecture Firm: Four Categories and How to Test Them

Why is this a category decision, not a product ranking?

Because the tools architecture firms use for remote collaboration do different jobs, and most firms need more than one. The question is rarely which product wins; it’s which job your current stack leaves undone.

Distributed practice is now normal. An AIA Architect report profiled firms ranging from a 12-person fully virtual practice to SmithGroup, with 1,400 people across 19 locations, and HOK, with 1,700 across 26. Design leaders said many clients and consultants are content with fewer in-person meetings, which tend to be kept for major milestones, and that higher-education clients value virtual sessions because they can bring in more stakeholders.¹

The words don’t help. “Collaboration room” means three different things in AEC, and each comes from a different part of the market:

• A physical project room, with pinned sheets and a standing table for the life of a job. Supplied by audiovisual integrators and workplace fit-out firms.
• A common data environment, the governed system where coordinated project information is shared among the parties. Supplied by design-software and construction-platform vendors.
• A persistent virtual review room, an online space that keeps its media, layout and participants between sessions, so a recurring review resumes instead of restarting. Supplied by collaboration-workspace and visualization vendors.

Write down which one you mean before contacting anyone. It removes most of the market, and it stops you sitting through demos for a category you didn’t need.

What are the four kinds of tool?

A persistent workspace differs from a meeting tool in three ways. It keeps its participants, media and settings between sessions, so on a project running through schematic design, documents and construction administration, nobody hunts for the link or re-uploads the current set. It favors detail over call stability, and many can show several sources at once, such as a plan, an elevation and a site feed. And guests usually join from a browser, which removes the access problems that eat the start of client meetings. For how that plays out across different kinds of design review, see our guide to side-by-side viewing in design review.

These categories complement each other. The common data environment holds the record; a review room hosts the conversation about it. Be wary of any review tool that presents itself as the project record.

Where do firms find these suppliers?

• What you already license. Design-software, project-platform and enterprise agreements often include collaboration features nobody has configured. Check before starting a procurement.
• Peer firms. A practice of similar size and project type can tell you how a tool behaved in year three of a job, which no demo covers. Ask what happened when the project team changed.
• Professional events and technology programs, where vendors show tools in an AEC context.
• Design technology leads and independent advisors, who see many firms’ stacks. For a practice without its own design technology role, often the fastest route to a credible shortlist.

How do you test image fidelity?

Fidelity is the criterion most often judged casually and most often regretted. The failure is quiet: a review seems to go fine, and only later does someone realize a detail was approved that nobody could actually read on screen.

Build a test set from a real project: a dense construction detail, a full sheet at working scale, a photorealistic interior rendering and a model view with fine geometry. Use the same set with every vendor. Have reviewers in different offices, on different connections and displays, describe specific small elements, such as a dimension string or a hatch, without zooming. Where locations disagree about what they can see, you’ve found the real constraint.

Account for the whole chain. Many firms now give staff a laptop or tablet that connects remotely to a desktop machine or the cloud for Revit and rendering;¹ in that setup, the picture has already been compressed once before a collaboration tool touches it.

Treat resolution claims without stated conditions as best-case ceilings. What a reviewer actually sees depends on the source, the encoding, the connection, the display and the viewing distance.

What do remote reviews need from the network and hardware?

Check upload speed, not just download, at every office that will present. The presenting office sends video for the length of the session, and connections bought for downloading files can fall short. Plan for several reviews running at once, alongside cloud rendering and model syncing, not one review in an empty office.

The display often matters more than the workstation. Be explicit about what equipment a meaningful review needs, and don’t assume a laptop screen will do for checking a detail.

How should client access and security be handled?

Projects carry sensitive material: unreleased designs, client business information, security-relevant building details and, on government or healthcare work, information with specific handling rules. Any platform that holds it belongs in the firm’s security review, not a departmental purchase. For sensitive projects, ISO 19650-5 sets out principles and requirements for security-minded information management across the life of a built asset.²

Ask practical questions:

• How is guest access granted, and how is it revoked?
• Can guests view material without being able to download it?
• How are recordings stored, and for how long?
• Who at the vendor can reach project content?
• What persists between sessions: the files, the layout, the participant list and permissions, or only the address?
• What can you export at closeout, in what formats, and is it usable without the vendor’s software?

Then check the contract. Where an AIA E203 exhibit is attached to the agreement, it sets the parties’ expectations for digital data and BIM on the project, and the detailed protocols that follow are recorded in G201 and G202.³ A new review tool has to fit those protocols. Decide internally, before it comes up, whether a decision made in a live review counts as an approval; usually it shouldn’t until it’s recorded through the agreed process. No platform relieves the firm of its own obligations, so verify compliance claims with counsel and against the client’s contract, not a marketing page.

What does it cost?

The categories are priced differently, so compare like with like. Seat count is a poor guide in a firm, because the people who need full accounts are usually a minority. Many firms find a few licensed hosts plus easy guest access for clients and consultants matches how reviews actually run.

Don’t compare the subscription against zero. Compare it against travel for reviews, rework from decisions made on unreadable drawings, and senior time spent re-explaining what a client couldn’t see. Scope setup separately: large media storage, integrations and client-facing configuration take effort a per-seat price won’t show.

When isn’t a dedicated tool worth it?

When the work is co-located. A single-studio practice with most clients a short drive away will pay for capability it rarely uses.

When the problem is process. If reviews run long because decisions aren’t recorded or the wrong people attend, a better platform will host the same problem at higher resolution. You should be able to name the failure you expect the software to fix.

When the timing is wrong. Introducing a new review environment during construction administration on a critical project usually costs more in disruption than it returns.

When the gap is narrow. A configuration change or an added module from a current vendor is usually cheaper than another platform and another login.

How to choose

1. Name the failing review. Internal design review, client presentation or consultant coordination, and what goes wrong today.
2. Decide which kind of room you mean. Physical, common data environment or virtual review room.
3. Check what you already license.
4. Assemble a real test set and use it with every candidate.
5. Test across offices, networks and displays, including a client’s network and an unmanaged device.
6. Run the security review and check the contract before the tool spreads across projects.
7. Pilot on one project with a decision date and success criteria agreed in advance.

Coresee makes a persistent, browser-based video collaboration workspace, one of the four kinds of tool this guide describes.

Published November 9, 2026