Old project archives: asset or liability for a design firm?

Is an old project archive an asset or a liability?#

An old project archive is both an asset and a liability, and governance decides which side wins. The same drawings, models, RFIs and correspondence that could be requested in a claim against the firm also help defend it, feed proposals and reuse, and may be licensable.

What tips the balance is whether anyone can find things, whether the firm knows what it must keep, and whether it knows which records it controls. An indexed, scheduled and rights-mapped archive leans toward asset. Unlabeled servers, boxes in offsite storage and lapsed cloud accounts lean toward liability.

The balance: liability side versus asset side#

An old project archive weighs on the liability side through claims exposure, cost, security, personal data and confidentiality, and on the asset side through defense, knowledge and possible licensing. Use the table to discuss the archive with partners factor by factor instead of in terms of general unease.

What must the firm keep, and for how long?#

What a design firm must keep depends on its contracts, the claims periods in the states where it worked, its insurer's guidance and any legal holds, and these differ enough that no single period fits every firm. Statutes of limitation run from when a claim arises or is discovered, while statutes of repose generally cut off claims a set time after completion, whenever a defect appears. Both vary by state, and some contracts set retention terms of their own.

Legal holds override everything else. When a claim is threatened or pending, or a dispute is reasonably expected, records relating to that project must be preserved, whatever the general schedule says. Destroying them can carry serious consequences, so the hold process should be written down and known to IT.

Agree the retention schedule with counsel and your professional liability insurer, apply it by project and record type, and log every disposal: what was disposed of, when, under which rule and approved by whom.

What does the archive actually cost?#

The archive's real cost sits mostly in time and legacy systems rather than in storage. Disk and cloud storage are visible line items; the larger costs are old servers kept running for one application, legacy software kept licensed to open old files, and staff hours spent searching for a drawing someone needs today.

Old file formats add cost of their own. Models and drawings saved in releases the firm no longer runs may need conversion, and some proprietary formats become harder to open over time. Exporting key sheets to PDF and recording the software versions used reduces that cost without converting everything.

Security is the cost most often missed. An old file server running an unsupported operating system, a cloud account still tied to a former employee's login, or external drives with no encryption can expose client drawings and personal data long after anyone last opened them. Consolidating onto supported, access-controlled storage usually reduces both risk and running cost.

A decision rule for each project archive#

Each project archive should get one of five actions, set by the condition that applies to it. The rule turns a vague debate into a list someone can work through.

Apply the rule per project and record family, not per server. A single project can hold drawings that must be kept, personal data that should be minimized and review histories worth assessing.

Personal data needs its own pass inside each kept project. Employee files, client contact lists and occupant information rarely need to sit alongside drawings and review histories, so moving them into a restricted tier lets the rest of the project stay usable without widening exposure.

Illustrative: two partners disagree about the old server#

Illustrative: a fictional design firm, Fennimore Lowe Architects, kept files from its whole history on an aging server, plus boxes of paper sets in offsite storage. One partner wanted to delete everything older than the firm's assumed claims period; another wanted to keep everything indefinitely.

The managing principal asked counsel and the firm's insurer to set a retention schedule, then had staff build an index of projects, contract forms and record families. Projects with open claims or ongoing client relationships were preserved. Paper sets duplicated by digital records were scheduled for disposal, with each disposal logged.

The index also surfaced a group of projects on standard-form contracts with complete RFI and submittal histories. Those were moved to restricted storage and marked for a licensing assessment once counsel had confirmed the contract terms. The old server was retired after the archive had moved and the copy was verified.

Turning a pile into a governed archive#

A pile of old files becomes a governed archive through a short sequence of steps, run once and then maintained on a regular cycle.

• 1Inventory locations: servers, cloud accounts, external drives, offsite boxes and former employees' folders.
• 2Build an index by project with dates, client, contract form and record families.
• 3Adopt a retention schedule with counsel and the insurer, plus a written legal hold process.
• 4Map rights: which projects the firm controls and which carry ownership or confidentiality limits.
• 5Move personal data and client confidences into a protected tier.
• 6Consolidate onto supported storage and retire old hardware and accounts.
• 7Review the archive periodically and log every disposal.

How SourceX assesses design firm archives#

SourceX assesses an archive only after a firm chooses to explore licensing, and the first step uses metadata from the index: record families, years, contract forms and known restrictions. Under the SourceX Enterprise Data Value Framework, review histories the firm controls can rate well on rights, domain expertise and human-generated signal, while personal data raises privacy burden. If a package proceeds, the SourceX Evidence Packet documents provenance, licensing rights, permitted use, the privacy record and release authorization, and the firm approves each step of the SourceX five-step transaction.