Engineering and architecture
Confidentiality clauses in A/E agreements: what they actually restrict
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
A confidentiality clause in an architect or engineering agreement usually restricts disclosing or using the client's confidential information outside the project, not every record the firm creates. Its reach depends on the definition: designation-based clauses cover marked information, while broad client clauses can cover all project information. Read the definition, carve-outs and survival term first.
Key takeaways
- The definition of confidential information sets the scope of the whole clause, so read it first.
- Standard exclusions for public, already known and independently developed information narrow what is protected.
- Many agreements, especially older ones, have no de-identified data carve-out, so its absence is common rather than a red flag.
- Survival periods and return-or-destroy duties can outlast the project, sometimes indefinitely.
- When a clause is ambiguous, asking the client for written consent is often simpler than arguing about scope.
What does a confidentiality clause in an A/E agreement restrict?#
A confidentiality clause in an A/E agreement restricts the firm from disclosing the client's confidential information to others and from using it for purposes other than the project. It does not, by default, make every drawing, email and timesheet secret; its reach depends on how confidential information is defined and what the clause excludes.
Most clauses are mutual, protecting the firm's proprietary methods as well as the client's business information. The firm's practical concern is usually the client side: security details, business plans, tenant information, financial data and anything the client marks as confidential.
The restriction matters whenever project information leaves the project team: in marketing, conference talks, insurer disclosures, internal knowledge tools and data licensing.
Clause elements and what to look for#
Each element of a confidentiality clause widens or narrows what is protected. Review them in this order, because the definition and the exclusions set the scope that every other element works within.
| Clause element | What to look for | Effect on internal records |
|---|---|---|
| Definition of confidential information | Designated or marked information, versus all information received or generated on the project | A designation-based definition leaves most internal records outside the clause |
| Exclusions | Public, already known, independently developed or received from a third party without restriction | Firm know-how and general methods often fall within the exclusions |
| Permitted disclosures | Consultants, insurers, advisors, legal requirements and a need-to-know standard | Shows whether outside processors are allowed at all |
| Use restriction | Use only for the project, or also for the firm's internal business purposes | An internal-use permission helps with knowledge tools, less with licensing |
| De-identified or aggregated carve-out | Express permission to use information that no longer identifies the client or project | The clearest path for licensing de-identified internal records |
| Survival | A fixed period after completion, or indefinite | Sets how long the restriction applies to closed projects |
| Return or destroy | Duties on request or at termination, with exceptions for archival copies | Copies kept under an archival exception may be limited to that purpose |
| Publicity | Separate consent for photos, names and project descriptions | Marketing consent does not usually extend to other uses |
Standard forms versus client paper#
Standard forms and client-drafted agreements usually differ most in the definition. Industry standard forms generally protect information that one party identifies as confidential or proprietary and make the obligation mutual. Client-drafted agreements, especially from developers, corporate occupiers and industrial owners, more often define confidential information as everything related to the project.
Within the AIA family, B101 includes a confidentiality provision that generally protects information a party specifically designates as confidential or business proprietary, and permits disclosure to consultants, contractors and others who need it for the project when they are bound by similar restrictions, or where the law requires. Check the edition your firm signed and whether an exhibit or amendment replaced that provision.
Client paper also tends to add nondisclosure agreements signed at the pursuit stage, facility security policies and data handling exhibits. Each may carry its own definition and survival period, and an order-of-precedence clause decides which one governs when they conflict.
Where confidentiality terms hide#
Confidentiality terms in A/E work rarely live in one document. A complete review collects everything that could restrict the same information, then reads them against the order-of-precedence clause.
- The prime agreement and every amendment.
- Nondisclosure agreements signed during pursuit, interviews or site visits.
- Master services agreements and the task orders issued under them.
- Client security, IT or data handling exhibits.
- Subconsultant agreements, which may pass obligations down or add new ones.
- Correspondence with the client that grants or limits consent for particular uses.
A decision path for de-identified internal records#
A decision path for de-identified internal records helps a firm sort projects consistently before counsel reviews the hard cases. Work through the questions in order and stop at the first answer that decides the project.
| Question | If yes | If no |
|---|---|---|
| Is the record a client deliverable rather than an internal process record? | Handle under the ownership terms; usually exclude | Go to the next question |
| Does the definition reach internal records, for example all project information? | Go to the next question | Likely outside the clause; check the other documents |
| Is there a de-identified, aggregated or internal-use carve-out that fits the use? | Include once de-identification removes client and site identifiers, with the basis documented | Go to the next question |
| Could the client or site still be identified after de-identification? | Exclude, or ask the client | Go to the next question |
| Has the survival period ended with no return-or-destroy demand outstanding? | Candidate, subject to counsel's view | Ask the client for written consent, or exclude |
Survival and return-or-destroy clauses#
Survival and return-or-destroy clauses decide how confidentiality applies to closed projects. A clause that survives for a fixed period eventually ends; an indefinite one does not, which matters for archives that span many years of work.
Return-or-destroy duties can collide with the firm's need to keep records for professional liability defense and any record-keeping rules set by state licensing boards. Most clauses resolve that with an exception for archival copies. Where a firm relies on that exception, the retained copies may be limited to archival and legal purposes, which is narrower than the firm's general use of its records.
Some agreements say nothing about survival at all. Counsel then reads the clause with the rest of the contract and state law, and the answer is less certain, so treat a silent clause as continuing until counsel has given a view.
Illustrative: a pursuit-stage NDA outranks the prime agreement#
Illustrative: a fictional structural engineering firm is considering licensing its internal QA/QC comment logs and calculation check records. Its risk manager collects every document that could restrict those records for each closed project, not just the prime agreements, and works through the decision path.
Projects under standard forms with designation-based clauses, where nothing in the QA logs was ever marked confidential, become candidates after de-identification. For one industrial client, the prime agreement also uses a designation-based clause, but a nondisclosure agreement signed during pursuit defines confidential information as all information about the facility and survives indefinitely. The prime agreement's order-of-precedence clause does not mention the NDA, so counsel advises treating the broader definition as still in force, and those projects are excluded.
For a long-standing developer client with a broad clause, the firm asks for written consent covering de-identified internal records and receives it. The risk manager records each outcome, the documents reviewed and the basis for the decision in the firm's rights index, so the reasoning travels with the records.
How SourceX treats confidentiality in the Rights step#
SourceX reviews confidentiality terms in the Rights step of the SourceX five-step transaction, alongside ownership, consultant rights and privacy. Each project is included, included after de-identification, held for client consent or excluded, and the firm approves the final list.
The SourceX Evidence Packet records licensing rights and permitted use for the package, with provenance, the privacy record and release authorization, so the firm and the buyer can both see which contract terms were reviewed and why each project is in or out.
Frequently asked questions
Does confidentiality end when the project ends?
Not necessarily. Many clauses survive completion or termination, either for a fixed period or indefinitely. Check the survival language in the agreement and in any separate nondisclosure agreement, since each can set its own period.
Is de-identified information still the client's confidential information?
It depends on the definition and on whether the information still points to the client or the site. Without an express carve-out, counsel will usually ask whether a reasonable reader could identify the client from what remains.
Are our internal emails about a project the client's confidential information?
They can be if they repeat the client's confidential information or if the definition covers everything generated on the project. Emails about the firm's own staffing or methods are less likely to be covered, but the definition decides.
Does consent to use project photos in marketing cover other uses?
Usually not. Publicity consent is typically limited to names, photos and descriptions used for promotion. Data licensing is a different use and generally needs its own basis under the agreement, or separate consent.
Do subconsultant agreements pass confidentiality obligations down?
Often. Prime agreements commonly require the firm to bind its consultants to the same obligations. The reverse matters too: consultants' own information in your files may be covered by your agreements with them.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.