Engineering and architecture
EJCDC E-500 ownership of documents: what the engineer keeps
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Under the EJCDC E-500 owner-engineer agreement, the engineer generally keeps an ownership interest in its documents, including copyright, and grants the owner a limited license to use them for the project. Reuse without the engineer's written verification is generally at the owner's risk, and electronic files are convenience copies. Check the signed edition and its modifications.
Key takeaways
- E-500 generally treats the engineer's documents as instruments of service in which the engineer keeps an ownership interest.
- The owner's license is tied to the project, and reuse without the engineer's written verification is at the owner's risk.
- Electronic files are generally convenience copies, and the printed or sealed documents govern if they differ.
- Public owners often modify these clauses, so the signed agreement matters more than the published form.
- Owning the documents does not by itself clear them for licensing; confidentiality and owner-provided data still apply.
What does EJCDC E-500 say about ownership of documents?#
EJCDC E-500, the Engineers Joint Contract Documents Committee's standard agreement between owner and engineer for professional services, generally treats the engineer's documents as instruments of service in which the engineer keeps an ownership and property interest, including copyright. The owner receives a limited license to use the documents for the project, subject to conditions in the agreement.
That is the standard form's starting point. The agreement a firm actually signed may differ, because owners and engineers often edit the documents provisions, and EJCDC revises its forms over time. Everything below assumes you are reading your executed agreement, its exhibits and any supplementary conditions, not a published sample.
What the engineer keeps#
What the engineer keeps under the standard language is its ownership interest in the drawings, specifications and other documents it prepared, together with copyright and the right to reuse them at its own discretion, whether or not the project is completed. The engineer also keeps its general expertise and methods, which no project agreement transfers.
In practice, a civil firm working under an unmodified E-500 generally holds the copyright in its sealed drawings and calculations even though the owner paid for the services. That interest is narrower than it sounds for licensing purposes, for reasons covered further down.
The retained interest mainly protects the engineer. It limits the firm's exposure when documents are reused without it, and it preserves the firm's ability to draw on its own prior work on later projects.
What the owner may and may not do with the documents#
The owner may generally use the documents to complete, operate and maintain the project, and the standard license is commonly conditioned on the engineer being paid for the services that produced them. Use on extensions of the project or on other projects without the engineer's written verification, completion or adaptation is generally at the owner's sole risk, and owners are commonly asked to indemnify the engineer for such use.
Modifications made by the owner without the engineer follow the same logic: responsibility for unverified changes sits with the owner. The allocation protects the engineer's liability position more than it creates a commercial asset.
| Use by the owner | Generally permitted? | Typical condition |
|---|---|---|
| Construct and complete the project | Yes | Commonly tied to payment for the engineer's services |
| Operate, maintain and repair the project | Yes | Within the licensed project use |
| Extensions of the project | Limited | At the owner's risk without the engineer's written verification or adaptation |
| Reuse on a different project | Limited | At the owner's sole risk without written verification, typically with an indemnity |
| Modify the documents | Limited | Owner bears responsibility for changes the engineer did not make or verify |
How electronic files are treated#
Electronic files are generally treated as convenience copies under E-500: the printed or sealed documents govern if the two differ, and the receiving party relies on electronic files at its own risk. Standard language also tends to give the recipient a set period to report errors in transferred files and to disclaim responsibility for long-term software compatibility.
For a firm thinking about its archive, this clause cuts both ways. The firm's CAD and model files are its working copies, which supports the view that the firm controls them. But files received from the owner, surveyors and other consultants under similar terms are someone else's convenience copies, and they do not become the firm's to license.
What to check in your signed agreements#
Checking signed agreements matters more than knowing the form, because projects signed years apart may use different editions, and many owners attach their own changes. Use the table as a review sheet for each contract family rather than for each project.
| Point to check | Question to ask | Why it matters for licensing |
|---|---|---|
| Edition | Which EJCDC edition was used, and was the documents article modified? | Wording and defined terms differ across editions |
| Ownership | Does ownership stay with the engineer or vest in the owner? | Owner-vested documents are generally excluded |
| Copyright | Is copyright retained, assigned or licensed? | An assignment removes the firm's basis to license |
| Confidentiality | Does a confidentiality clause cover project information? | Ownership does not override confidentiality |
| Owner-provided data | Which surveys, reports and records came from the owner? | Owner-provided material remains the owner's |
| Electronic files | What reliance and transfer terms apply? | Separates files the firm received from files it authored |
| Supplementary conditions | Did a public owner add statutory or policy terms? | Public terms can restrict internal records too |
Why ownership is not the same as permission to license#
Ownership of documents is not the same as permission to license them, because other duties sit alongside ownership. For that reason, many firms treat sealed deliverables cautiously even under an unmodified E-500 and focus licensing reviews on internal process records: QA/QC logs, calculation check histories, staffing patterns and review comments. Those records were never deliverables, and their status under the agreement is usually simpler to assess.
The duties below can limit both deliverables and internal records, so each one is checked contract family by contract family, whether or not the firm holds the copyright in the drawings.
- Confidentiality clauses covering project information or working files.
- Owner-provided surveys, reports and records embedded in the documents.
- Personal information, such as property owner names in easement and right-of-way records.
- Security-sensitive details of water, wastewater, power and transportation infrastructure.
- Third-party content, such as manufacturer details and excerpts from published standards.
Illustrative: sorting contracts at a municipal civil firm#
Illustrative: a fictional civil engineering firm that designs water and wastewater facilities for municipal utilities pulls its executed agreements. Some use the E-500 documents article unchanged. Others replace it with language vesting all documents and data in the utility, and several add confidentiality clauses that reach working files.
Counsel sorts the agreements into contract families. The firm excludes every owner-vested project and all facility security details, then scopes internal calculation check logs and review comments from the remaining projects, with utility names and locations removed. The CEO approves the narrower scope, and the sorting itself becomes a reusable map for future rights questions.
How SourceX approaches E-500 projects#
SourceX reviews E-500 projects in the Rights step of the SourceX five-step transaction, contract family by contract family. The executed documents article, any supplementary conditions and the confidentiality terms decide whether a project's internal records may proceed, and owner-vested projects are left out.
The SourceX Evidence Packet records the agreement relied on, the licensing rights and permitted use, and the firm's release authorization. A license grants defined uses while the engineer keeps title to its records, and the initial assessment collects descriptions of systems and contracts rather than any documents.
Frequently asked questions
Do public owners usually accept the E-500 ownership terms?
Not always. Many public owners modify the documents provisions or use their own agreement forms that vest ownership in the agency. Check each executed agreement rather than assuming the standard language applies to a public project. Many agencies publish their standard consultant agreements, so the ownership position can often be known before a pursuit, which helps the firm decide how to file that project's records from the start.
Does the engineer's copyright let us license drawings for AI training?
Not by itself. Copyright is one right among several. Confidentiality clauses, owner-provided content, personal data and security restrictions can still limit use. Counsel should review each contract family before any project documents are considered for licensing.
What if we signed the owner's agreement instead of E-500?
Then the owner's form governs, and its ownership, reuse and confidentiality clauses replace the EJCDC language. Owner forms often vest ownership in the owner, so projects under them are frequently excluded from licensing reviews. The rights review itself works the same way; only the clauses being read change.
Are calculations covered by the documents provisions?
Calculations prepared for the project are generally among the documents the engineer prepares, though some contracts list them as deliverables and others do not. Whether they were delivered, and what the agreement says about them, affects how they are treated.
Does E-500 address AI training or data licensing directly?
Generally not directly. The documents provisions deal with ownership, reuse and electronic files, so questions about AI training or data licensing are answered by applying those clauses together with any confidentiality terms and exhibits the parties added. Check your edition and attachments for data or technology terms, and have counsel review the result.
Can the owner give our files to another engineer to finish or adapt?
Under the standard language, generally yes for the project, but at the owner's risk. Use or modification without the engineer's written verification, completion or adaptation is allocated to the owner, typically with an indemnity for the engineer. Owner forms and negotiated changes often expand the owner's rights, so check the executed agreement.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.