Skip to content

Engineering and architecture

How long should engineering and architecture firms keep project records?

By SourceX Editorial · Reviewed by Noah Loul ·

Short answer

Engineering and architecture firms should keep project records at least as long as the longest statute of repose or limitations period in the states where they practice, plus any longer contract, insurer or licensing-board requirement, and for as long as a legal hold applies. There is no single national number, so counsel sets periods by record category.

Key takeaways

  • No single national retention period applies to A/E project records; periods depend on state law, contracts and insurer guidance.
  • Statutes of repose and limitations set the floor for most project records, and counsel confirms when each clock starts.
  • A legal hold suspends destruction of the records it covers, whatever the schedule says.
  • Records kept for a long period are only useful if they can still be opened, so file formats belong in the policy.
  • A prepared copy can be licensed while the original stays under the retention policy.

Is there a standard retention period for A/E project records?#

There is no standard retention period for A/E project records that applies nationwide. Each firm sets its own schedule from several inputs: the statutes of repose and limitations in the states where it works, its client contracts, its professional liability insurer's guidance, state licensing board rules, and tax and employment rules for its business records.

That is why retention guidance for design firms is usually a method rather than a number. Counsel identifies the longest applicable period for each record category, the firm adds a margin it is comfortable with, and the schedule is reviewed when the firm starts working in a new state or signs contracts with unusual records terms.

What sets the retention clock#

The retention clock for a record is set by whichever requirement runs longest for it. Many firms find that repose periods in their busiest states drive project records, while tax and payroll rules drive business records.

List every driver that applies before setting any period, because the shortest-looking rule is rarely the one that governs.

  • Statutes of repose: state laws that cut off certain claims a set time after a defined event, such as substantial completion, regardless of when a problem is found.
  • Statutes of limitations: deadlines measured from when a claim arises or is discovered, which interact with repose periods differently from state to state.
  • Client contracts: clauses requiring records to be kept for a stated period or made available for audit.
  • Insurer guidance: professional liability carriers often recommend practices for keeping records that support a defense.
  • Licensing board rules: some state boards address records of sealed work.
  • Business record rules: tax, payroll and benefits records follow their own requirements. The IRS, for example, says to keep employment tax records for at least 4 years after the tax becomes due or is paid, whichever is later, and records about property until the limitations period expires for the year the property is disposed of.
  • Legal holds: any claim, demand or reasonably anticipated dispute.

Retention considerations by record category#

Retention considerations differ by record category because each category answers a different question later, whether in a claim, an audit or a renovation of the same building. The table shows what each category usually proves and what drives its period; counsel sets the actual periods.

Retention considerations by record category
Record categoryWhat it shows laterMain retention driverNotes
Contracts and amendmentsScope, standard of care, ownership and confidentiality termsRepose and limitations periods, plus audit clausesKeep the signed version with every amendment
RFIs and responsesWhat was asked during construction and how the firm answeredRepose period for the projectKeep linked to the sheets and revisions they changed
Submittals and review actionsWhat the firm reviewed, accepted or rejected, and whyRepose period for the projectReview stamps and comments matter as much as the submittal
Calculations and design criteriaThe basis for sealed design decisionsRepose period and any board rules on sealed workKeep native files and printed packages together
Correspondence and emailClient instructions, decisions and disputesRepose period for project threads; policy for the restFile project threads to the project, not only in mailboxes
Field reports and meeting minutesSite conditions observed and decisions recordedRepose period for the projectKeep photo dates and locations with the images
Time, billing and HR recordsEffort, fees and employment historyTax, payroll and employment rulesContain personal data; restrict access
Unsuccessful proposalsPursuit history and approach to feesFirm policyReview for confidential client material before keeping

When does the retention clock start?#

The retention clock for project records usually starts at a project event, such as substantial completion or the end of the firm's services, rather than the date a document was created. Which event applies depends on the state statute and sometimes on the contract, so the schedule should name the trigger for each category.

Firms that track only document dates tend to destroy records too early on long projects. Record the trigger date in Deltek or BQE when a project closes, so the destruction date for its records can be calculated rather than guessed.

Projects that run in phases, or that return for additional services later, may need the clock tracked by phase. Note those exceptions in the closeout record so the next person to review the archive sees them.

A legal hold overrides the retention schedule for every record it covers, from the moment a claim, demand letter or likely dispute is known. Destruction under the normal schedule stops for those records until counsel releases the hold.

Holds fail in practice when nobody tells IT or the people who manage shared platforms. Write the process down: who issues a hold, which systems it reaches, including Procore projects and Bluebeam sessions the firm can access, and how its release is recorded.

Records under hold also stay out of any data licensing scope until the hold is released. A license is a new use of records, and counsel will want them untouched while a dispute is live.

Kept is not the same as readable#

Records kept for a long retention period are only useful if they can still be opened at the end of it. Native Revit models, older CAD formats and calculation files tied to retired software versions can become hard to read well before the period runs out.

Many firms keep two forms of key records: the native file for reuse and a stable format such as PDF for the record. Export Procore logs and Bluebeam markup summaries at closeout too, because access to a shared platform can end when a contractor's or owner's account closes. Check what the export actually produces: Procore's documentation says most items exported through Procore Extracts download as PDFs, while documents and photos keep their original file type, so a PDF log keeps the record but not the structured fields.

Destroy, keep or license at the end of the period#

At the end of a retention period a firm has a real choice, and destruction is not the only option. Records past every applicable period, with no hold, can be destroyed on schedule, kept for the firm's own reference or, where the firm controls them, prepared and licensed.

Licensing does not change the firm's retention duties. The firm keeps its originals under the policy, and the license agreement sets how long the licensee may hold its prepared copy and what the licensee must do with it when the agreement ends.

SourceX starts any such review with a metadata-only fit check, so no records are shared at the outset. Where a firm continues, the SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and release authorization, which sits alongside the firm's own retention and destruction logs.

Destroy, keep or license at the end of the period
ChoiceFits whenWatch for
Destroy on scheduleRecords have no legal, reference or licensing use leftContracts requiring return or certified destruction of client material
Keep for referenceRecords support renovation work, repeat clients or staff trainingStorage cost, access control and personal data
License a prepared copyFirm-controlled decision records with outcomes, such as RFIs and review commentsClient ownership, confidentiality, de-identification and approvals

Illustrative: an MEP firm writes its first retention schedule#

Illustrative: a fictional mechanical, electrical and plumbing engineering firm has never had a written retention policy. Its file server holds every project since founding, its Deltek history starts after a migration, and departed engineers' mailboxes were kept with no rule at all.

Counsel builds a category schedule keyed to substantial completion, using the longest repose period among the states where the firm works. Closeout now records the trigger date in Deltek and exports Procore RFI logs and Bluebeam review summaries to the project folder. Old records past every period are reviewed: most are destroyed under a logged process, while internal design review records from firm-controlled projects are set aside for a licensing fit check.

Frequently asked questions

Should we keep paper originals after scanning?

Many firms scan and then destroy paper, but sealed originals, signed contracts and records under a legal hold deserve a separate decision. Confirm with counsel whether a scanned copy will serve your purposes, and keep a log of what was scanned, checked and destroyed.

Do we have to keep every project email?

Not every email, but correspondence that records instructions, decisions or disputes usually follows the project's retention period. The practical fix is to file project threads into project folders and apply a shorter rule to general mailbox content.

Can a client ask us to destroy their project records?

Some contracts require return or destruction of client confidential information at the end of a project, which can conflict with the firm's need to keep records for its own defense. Counsel reconciles the two, often by keeping what the firm needs under continuing confidentiality.

Do records from an acquired firm follow our schedule?

Usually they should once integrated, but the acquired firm's contracts and any open claims come with them. Inventory the acquired archive, map its project numbers and apply holds before folding its records into your own schedule.

Who should approve the retention policy?

The managing principal or executive team typically approves it, with counsel drafting the periods and the IT lead confirming each system can follow it. Many firms also share the policy with their professional liability insurer and revisit it when they enter new states.

Sources

  • The IRS says to keep employment tax records for at least 4 years after the date that the tax becomes due or is paid, whichever is later, and to keep records relating to property until the period of limitations expires for the year in which you dispose of the property. Source
  • Procore's Extracts documentation says most Procore items download as PDFs, while documents and photos keep their original file type. Source

Related resources

See if your company qualifies

A short company assessment. No data uploads are needed.

See if you qualify