← All articles

The Engineer Left. The Ten-Year Duty Didn’t.

By XNM Technologies · November 10, 2026 · 4 min read

Most engineering firms know where this year's project files are. Fewer can say with confidence where the files are for a culvert designed in 2017 by an engineer who has since left, on a server that has been migrated twice. In British Columbia, that question is not about tidiness. It is a professional obligation that runs for at least a decade after the project ends, and it follows the individual engineer as well as the firm.

Recent context

Under the Bylaws made under the Professional Governance Act, Engineers and Geoscientists BC requires registrants to establish, maintain and follow documented procedures for retaining complete project documentation, and to keep that documentation for at least 10 years after the later of the completion of the project or the date it is no longer used. The regulator's guide to the retention of project documentation (version 3.0, published June 15, 2023) sets out what that covers: designs, specifications, drawings, calculations, models, testing information, field review records, quality assurance documentation and copies of every authenticated document. The guide also notes that the Limitation Act or a contract may call for longer periods, and that a client's request does not remove the registrant's professional responsibility.

Two other points in the guide matter for anyone running a firm. Records may be paper or digital, as long as they can be readily retrieved and are stored in a way that prevents them from being altered. And when a registrant leaves a firm, the duty does not simply stay behind with the files: the registrant must keep the records or make sure they are kept.

Where the decade goes missing

Ten years is longer than most software, many partnerships and a fair number of careers at a single firm. The record tends to break at the same few points.

  • Departures. An engineer of record leaves, and their working folders, email and marked-up drawings disappear when the account is closed. The final issued set may survive. The calculations and field notes that explain it often do not.
  • System changes. A move to a new document platform or cloud drive brings over the folders someone remembered to map. Older projects are archived in a format nobody can open, or left on a drive that is eventually wiped.
  • Email as the file. Design decisions, client instructions and field review observations live in inboxes. The guide treats email and even voice mail as possible records. Few firms file them that way.
  • Mergers and closures. When firms combine, split or wind down, the question of who holds ten years of project records is often answered by whoever ends up with the server.

Why it matters after the invoice is paid

The projects that come back are rarely the ones anyone expects. A slope moves, a roof deflects, a client sells a building and the buyer's consultant asks how a load was calculated. A complaint reaches the regulator years after the work. In each case the firm is asked to show what was designed, what assumptions were made, what was reviewed in the field and what was sealed. A firm that can produce that record in an afternoon is in a very different position from one that has to reconstruct it from a former employee's memory.

A retention routine for a working firm

None of this needs a records department. It needs a few rules applied at the same points on every project.

  1. Write the procedure down. The bylaw asks for documented procedures, so put the firm's retention rule, the trigger date and who is responsible into the quality manual or practice management plan.
  2. Close every project the same way. At completion, move the issued and authenticated documents, calculations, models, field review reports and key correspondence into a single project record, and note the date retention starts.
  3. File decisions, not just drawings. Save the emails and meeting notes that changed the design or the scope into the project record, alongside the drawing revision they relate to.
  4. Run an exit check. When anyone leaves, confirm that their active and recent projects are complete in the firm's system before their accounts are closed, and record that the check was done.
  5. Test retrieval once a year. Pick a project that is six or eight years old and try to find its calculations and sealed drawings. If it takes more than a short search, fix the system, not just that project.
  6. Plan for migrations. Before any platform change, list the closed projects still inside their retention period and confirm they move, open and keep their dates.

The file is the firm's memory

Engineering firms sell judgment, and judgment is hard to defend years later without the evidence that supported it. Keeping complete project documentation in one auditable system, organized the same way on every project, is what turns a ten-year obligation into something a firm can actually meet. It also means the next engineer to open the file can understand the work without calling someone who left in 2019.

This article is general information, not legal advice. Retention obligations vary by jurisdiction, regulator and contract, so confirm the requirements that apply to your practice.