Project, Contract and Liability Timelines: How AEC Principals Should Choose Long-Running Collaboration Tools

What are the three clocks?

The project. A hospital, campus or civic building can run four or five years from concept through construction administration, and longer if funding or approvals pause it.

The software agreement. Subscriptions run on commercial cycles, commonly one to three years, that have nothing to do with the building program. Over a long project the tool may be repriced, change its terms or ownership, or be replaced by the firm.

The firm’s exposure. Most states have statutes of repose, which bar claims against design professionals after a set period following completion of services or substantial completion of construction. The National Society of Professional Engineers proposes a uniform standard of seven years after completion, or eight where an injury occurs in the seventh year.¹ The actual periods and their scope are set state by state, so confirm the ones that apply to your work with counsel.

This is a principal’s question, not a design technology one, because the consequences fall on the firm. A firm may still have to answer for decisions years after the software in which they were discussed has been replaced or discontinued. Firms that plan for that export deliberately and keep their own records. Firms that don’t find the gap when a claim arrives and the material sits in a system nobody has licensed for three years.

What should the firm keep, and where?

Start from the obligation, not the software. Decide with counsel how long the firm may need to show what was designed, discussed and agreed, then work back to what any platform must support.

Keep the record separate from the conversation. Coordinated project information belongs in the governed common data environment; review sessions are where the team and client talk about it. Our guide to choosing a remote collaboration tool covers that distinction. Where an AIA E203 exhibit is attached to the agreement, it sets the parties’ expectations for digital data and BIM and the process for the protocols that govern how that data is used and exchanged,² so decide in advance whether anything agreed in a live review carries weight outside those protocols.

Then make retention concrete: what the firm exports, in what format, on what schedule, and where it’s stored under the firm’s control. A record you can only retrieve inside a platform you may not be licensing in five years isn’t a record the firm holds.

Most firms should do both: work in the platform, and export from it. A tool that only hosts the conversation, such as a live review room, needs a different test. If it doesn’t export, make sure nothing important exists only there: record each decision, and file anything shared, in the governed system the same day. Then the review tool can come and go without taking the record with it.

What does a multi-year project change about the choice?

Emphasis shifts from features to continuity. Over four years a platform will change its interface and probably its pricing, and the project team will turn over several times. Judge a tool on how it handles that, not on a demo in a stable moment.

Ask the vendor these questions:

• Context for new people. How does a project architect joining in year three find the history of decisions, and does it make sense without the people who made them?
• Accumulation. As media and recordings build up over years, does performance change, and how does storage cost grow?
• Archive pricing. Is material kept for the record priced differently from active project storage, or would the firm pay active rates for an archive?
• Dormancy. What happens to a project space after a year of inactivity: is it kept as is, moved to slower storage or deleted, and what notice does the firm get?
• Export. Can you produce a real export of a populated project, and is it readable without your software?
• Change and exit. How much notice is given before material changes to pricing or terms, and what happens to the firm’s data if the company is acquired or stops trading?

Put the answers that matter into the contract: export rights, retention terms, and notice periods for material change. With those in place, the risk from any vendor, large or small, is one the firm can manage.

Should the firm standardize, or let projects choose?

Standardizing usually wins on long-running work, and not mainly on cost. One environment builds habits people carry between projects, and it means one export process, one retention schedule and one place to look when a question arrives about a project that closed years ago. Several tools multiply that work and make it inconsistent.

The counterargument is real. Some clients require their own environment, and a rigid standard pushes project teams to work around it. The workable position for most firms is a firm standard with a written exception process: a project may use a client-mandated environment where the contract requires it, provided the firm still exports and keeps its own record on the standard schedule.

What does it cost across a portfolio?

Model the portfolio, not one project. Firms carry a changing mix of jobs at different stages, so the meaningful figure is a typical year at typical use, not one project at its peak.

Watch for commitments sized to a busy year. A rigid multi-year commitment gets expensive when the pipeline softens, and firms with cyclical workloads usually benefit from being able to scale down between projects, even at a higher unit rate.

Count what doesn’t appear on an invoice: duplicated administration across tools, inconsistent exports, and senior time spent sorting out who has access to what.

What should a principal own?

• The retention decision. What the firm keeps, for how long and where. It’s a risk decision, and it shouldn’t default to whatever a platform does automatically.
• Client flow-down. Where client agreements set rules for how project information is handled, stored or destroyed, those rules have to reach the tools actually in use. Only a principal is placed to confirm the commercial and technical arrangements match.
• Security on sensitive work. Government, healthcare and infrastructure projects carry building information that is itself sensitive, and need a recognized approach, not an ad hoc one.
• Succession. Administrative control of firm environments shouldn’t depend on one person, and access should survive their departure. Confirm it in writing.

When isn’t a long-running tool the right investment?

When projects are short. Practices doing mostly fit-out, residential or small commercial work, with engagements measured in months, won’t use the continuity this category is for.

When client environments dominate. A firm working mainly inside client-mandated systems may find its own platform duplicates what it already has to use. A disciplined export and retention practice is the better investment.

When the firm hasn’t decided what it keeps. Buying first makes the platform’s defaults the firm’s policy by accident.

When the real constraint is people. If reviews fail because the wrong people attend, decisions aren’t recorded or clients come in too late, a longer-lived platform won’t fix it. Fix the process first.

How to put it in place

1. Set the retention position with counsel, for each state you work in, before choosing tools.
2. Separate the record from the conversation, and decide what standing a live-review decision has.
3. Test a real export from each candidate that will hold part of the record, and open it without the vendor’s software. For review tools that don’t export, record their decisions elsewhere the same day.
4. Write the contract terms in: export rights, retention, archive pricing, and notice of material change.
5. Adopt a firm standard with a written exception process for client-mandated environments.
6. Export on a schedule, including at closeout and before any project pause.
7. Remove single-person dependencies from administration.

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

Published November 9, 2026