Engineering and architecture

How long should architects and engineers keep project records?

By SourceX Editorial · Reviewed by Noah Loul · October 9, 2026

Short answer

Architects and engineers should keep project records at least through the statute of repose for each project's state, plus a buffer for claims served near the deadline, then extend for any longer contract, insurer or legal hold requirement. There is no single national period. Drawings that define what was built usually get the longest retention.

Key takeaways

The floor is the statute of repose for the state where the project was built, counted from that statute's trigger event.
Add a claims buffer on top of the repose period, because a late claim takes time to reach the firm.
Owner contracts, professional liability insurers and legal holds can each require longer retention.
Write the retention date per project at closeout, with the state, trigger date and source of each input.

How long should architects and engineers keep project records?#

Architects and engineers should keep project records for at least the statute of repose period that applies to each project, plus a buffer for late claims, and longer where a contract, insurer or legal hold requires it. A statute of repose sets an outer limit on when most construction-related claims can be brought, and repose periods vary by state and sometimes by type of claim.

That is why no honest answer gives one number for every firm. A firm practicing in several states may need different periods for different projects, set by where the project was built rather than where the firm is based. Counsel should confirm which periods apply and how they are counted.

Treat the result as a minimum, not a deletion date. Reaching the end of the period means the firm may decide what to do with a record; it does not mean the record must go.

The answer framework: repose, buffer, contract, insurer#

A retention period for design records is built from a few inputs applied in order. Each one can only lengthen the period set by the inputs before it, never shorten it.

Write the result for each project at closeout: the state, the trigger date, the repose period counsel confirmed, the buffer, any longer contract term and the resulting earliest review date. A schedule with those fields filled in can be defended. A shared drive with no dates cannot.

The answer framework: repose, buffer, contract, insurer
Input	Where to find it	Effect on the period
Statute of repose	State law for the project location, confirmed by counsel	Sets the floor, counted from the statute's trigger, such as substantial completion
Claims buffer	Firm policy, informed by counsel and the firm's claims history	Extends past repose to cover claims served late and questions about when the clock started
Contract terms	Owner agreements, consultant agreements and public client terms	May require records to be kept longer or made available to the client
Insurer guidance	Professional liability policy, broker and carrier risk guidance	May recommend longer retention for some project types
Legal holds	Counsel, claim notices and subpoenas	Suspends destruction of affected records until counsel releases the hold

Which records need the longest retention?#

Records that show what the firm designed, what it approved and what it was told need the longest retention, because a claim turns on them. Administrative records generally follow business and tax rules set with the firm's accountant rather than the repose framework.

Which records need the longest retention?
Record type	Why it matters later	Retention guide
Issued and sealed drawing sets, specifications	Define the design of record	Repose plus buffer at minimum, and often the longest of all
Native CAD and BIM files	Show model content behind the sheets	Same as issued sets where practical, with an openable format alongside
Calculations and design criteria	Support engineering judgment	Repose plus buffer
RFIs, submittal reviews, ASIs and change documents	Show what the firm approved or clarified during construction	Repose plus buffer
Field observation reports and punch lists	Show what the firm saw and reported	Repose plus buffer
Contracts, amendments and scope letters	Define duties and limits of liability	Repose plus buffer, or longer if the contract says so
Project correspondence and meeting minutes	Explain why decisions were made	Repose plus buffer for project-relevant material
Unsuccessful proposals and marketing drafts	Little relevance to claims	Business need, set with counsel under firm policy
Time, billing and payroll records	Financial and tax support	Set with the firm's accountant; IRS guidance, for example, says to keep employment tax records at least 4 years after the tax becomes due or is paid, whichever is later

Who should own the retention schedule?#

The retention schedule should be owned by one person at firm level, usually the COO or a records manager, with counsel setting the legal inputs and project managers supplying the dates. Splitting ownership across IT, accounting and individual studios is how a firm ends up with three schedules and no answer when a claim letter arrives.

The owner keeps a single table of states, repose periods, triggers and the buffer the principals approved, and reviews it when the firm starts work in a new state or counsel flags a change in law. Project managers enter the trigger date and any longer contract term at closeout. An annual review then lists every project past its earliest review date, so destruction, retention or reuse is always a decision someone signed.

Mistakes that shorten the real retention period#

The most common retention mistake is keeping files but losing the ability to use them. A firm that kept everything can still struggle to defend a claim if native files need software nobody licenses anymore, or if the RFI log points to attachments that were purged with a platform subscription.

Counting from the wrong date, such as contract signing instead of the statute's trigger.
Applying the home state's period to projects built in other states.
Keeping drawings but not the RFI and submittal logs that explain changes to them.
Letting a cloud platform's project archive lapse when the subscription or project access ends.
Deleting on schedule without checking for legal holds.
Keeping native files only, with no PDF or other long-lived copy of the issued sets.

Illustrative: an architecture firm sets periods by state#

Illustrative: a fictional architecture firm based in one state has completed projects in three neighboring states, with records on a file server, Procore logs from contractor-run projects and Revit models spanning several software versions. The COO asks outside counsel for the repose period and trigger in each state, and asks the professional liability broker for any carrier guidance.

The firm builds a retention table keyed to project location, adds a claims buffer set by the principals and flags two public-agency projects whose agreements require longer access. It exports Procore logs before contractors close their projects and saves issued sets as PDFs beside the native models. At each annual review, closed projects past their date go to the principals, who keep those with complete RFI and submittal histories in a read-only archive.

What happens when the retention period ends?#

When the retention period ends, the firm has three choices: destroy on schedule with a documented sign-off, keep the record for reference, or prepare a de-identified copy for another use. Record the decision per project, after confirming that no legal hold applies.

Some firms find that closed projects with complete RFI, submittal and review histories are worth keeping, as training material for staff or as records that could be licensed in de-identified form. SourceX reviews such archives through the SourceX five-step transaction, Supply, Rights, Preparation, Approval and Delivery, starting with metadata only and leaving the records in the firm's own storage. Retention decisions stay with the firm and its counsel.

Frequently asked questions

Do public clients require longer retention?

Sometimes. Public agency agreements can include record retention and audit access clauses, and public records rules may apply to what the agency holds. Read each agreement, and record any longer term on that project's retention entry so the general schedule does not override it.

Does our professional liability policy set the period?

The policy itself may not specify retention, but carriers and brokers often publish risk guidance on record keeping. Because many professional liability policies are claims-made, the firm's ability to defend a late claim depends on the records it still holds. Ask the broker what the carrier recommends.

When does the clock start on a phased project?

It depends on the statute's trigger and how it treats phases, which counsel should confirm. Many firms count from the latest relevant trigger for the whole project to stay conservative, and record the date they used. Phased projects are a common source of retention errors.

Should project email be kept as long as drawings?

Project-relevant email often explains why a design changed, so it belongs in the project record and follows the same period. General administrative email does not. Filing project email to the project when it is sent makes this distinction workable years later.

Is it enough to keep PDFs of drawings?

PDFs of issued and sealed sets are often the most durable record of the design of record. Native files add model content that PDFs do not show. Many firms keep both for the full period and accept that native files may need older software to open.

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. Source

Related resources

See if your company qualifies

A short company assessment. No data uploads are needed.

Check your archive with the readiness checklist Talk to SourceX