Engineering and architecture
Can structural engineering firms license their project data?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Yes, structural engineering firms can often license project data, mainly their review and decision records rather than sealed deliverables. RFI responses, shop drawing reviews, peer review comments and calculation revision histories show how engineers check and decide. Sealed documents, client-owned reports and security-sensitive projects usually stay out, and the firm approves every scope decision.
Key takeaways
- Review and response records, not sealed drawings, are usually a structural firm's strongest licensing candidates.
- Shop drawings belong to fabricators and detailers, but the structural engineer's review comments on them are generally the firm's own records.
- Subconsultant agreements often flow down prime contract terms, so the architect's agreement with the owner matters too.
- MEP and commissioning firms hold similar issue-to-resolution records, such as commissioning issues logs and design review comments.
What project data does a structural engineering firm hold?#
A structural engineering firm holds two kinds of project data: deliverables issued under seal and the working records behind them. Deliverables include drawings, specifications and calculation packages. Working records include RFI responses, shop drawing and submittal reviews, peer review comments, site observation reports and time charged by phase.
These records are spread across analysis software such as RISA, ETABS, SAP2000 and RAM Structural System, Revit structural models, Bluebeam review sessions, construction platforms such as Procore, email and an ERP such as Deltek Vantagepoint. Much of the review history lives in Bluebeam and email rather than in any single system, which is the first thing an inventory should map.
Which structural records carry the most value and the most risk?#
The structural records with the most value combine a technical question, the engineer's check and a decision; the riskiest are sealed deliverables and anything owned by someone else. The table ranks common record types by what they show, their rights position and their usual licensing outlook.
| Record | What it shows | Rights position | Licensing outlook |
|---|---|---|---|
| RFI responses | Field question, engineer's reasoning, resolution | Firm's response; the contractor's question is third-party content | Strong after preparation |
| Shop drawing and submittal reviews | What the engineer checked, accepted or rejected | Comments are generally the firm's own; drawings belong to the fabricator or detailer | Strong if comments are separated from drawings |
| Peer review comments | Independent check of another engineer's design | Depends on who engaged the review and on its terms | Case by case |
| Delegated design reviews | Review of connections, precast or framing designed by others | Firm's comments; the design belongs to the delegated engineer | Strong for comments only |
| Calculation revision histories | How a design changed as loads and geometry changed | Firm work product, often subject to the client's license and confidentiality | Rights review required |
| Site observation reports | Field conditions, deficiencies and corrective actions | Firm records that may describe client facilities | Strong after site details are removed |
| Sealed drawings and specifications | The final design of record | Instruments of service licensed to the client | Usually excluded |
| Time by phase and staffing | Effort, overruns and staffing decisions | Firm records | Strong after client and rate removal |
Why do review and response records outrank the drawings?#
Review and response records outrank drawings because they capture reasoning, which AI developers building engineering tools cannot get from finished documents. A sealed drawing shows the answer; an RFI response shows the question from the field, the engineer's check against design intent and the decision that followed.
Shop drawing reviews are especially useful because they record errors caught. A comment rejecting a connection detail, with the reason and the resubmittal that fixed it, is a labeled example of engineering judgment. Peer review comments do the same at the level of the overall design.
Linkage multiplies the value. When an RFI number connects to a bulletin, a revised calculation and a later site observation, the chain shows how one decision moved through the project.
What should stay out of a structural engineering license?#
Sealed deliverables, other parties' work product, security-sensitive projects and anything tied to disputes should stay out of a structural engineering license. These exclusions protect the firm's clients, its liability position and the people whose work sits inside its files.
Forensic work deserves particular care. Failure investigations are among a structural firm's most instructive records, but they often sit under attorney engagement, privilege or protective orders, and they should not be scoped without counsel.
- Sealed drawings, specifications and calculation packages issued as documents of record.
- Shop drawings, delegated design calculations and reports prepared by others.
- Client-owned studies, such as condition assessments the client commissioned and paid for.
- Secure facilities, critical infrastructure and projects under nondisclosure agreements.
- Forensic and expert witness work, privileged material and projects with open claims.
- Defense and export-controlled work of any kind.
Who approves, and which contracts need checking?#
The firm's authorized signer approves any license, but the contracts that limit it often belong to someone else. Structural firms frequently work as subconsultants to an architect, and subconsultant agreements commonly flow down the prime agreement's terms on ownership, confidentiality and use of project documents.
Rights are assessed project by project with counsel. A record family that clears on direct owner work may still be excluded on subconsultant projects where the prime agreement is restrictive.
| Document | What to check |
|---|---|
| Subconsultant agreement with the architect | Flow-down clauses, confidentiality, ownership of documents |
| Prime agreement between architect and owner | Terms that bind subconsultants through flow-down |
| Direct owner agreements | Instruments of service, confidentiality, AI or data use language |
| Peer review engagement letters | Who owns the comments and whether they are confidential |
| Professional liability policy | Whether the insurer wants notice of new data uses |
| Analysis software licenses | Any limits on exporting or sharing model files |
Does the same apply to MEP and commissioning firms?#
The same logic applies to MEP and commissioning firms: issue-to-resolution records usually outrank design deliverables. HVAC design review comments, coordination RFIs, equipment submittal reviews and energy model revision notes show how engineers balance loads, space and cost.
Commissioning issues logs are a strong example. Each entry records a deficiency found during functional testing, the responsible party, the fix and the retest, which is the problem, action and outcome structure AI developers look for. Building automation trend data is usually controlled by the owner and needs the owner's permission.
Illustrative: a structural firm scopes its review archive#
Illustrative: a fictional structural engineering firm works mostly as a subconsultant to architects on schools, offices and parking structures. Its RFI responses live in Procore and email, shop drawing reviews in Bluebeam Studio and calculations in RAM Structural System and spreadsheets, with project time in Deltek Vantagepoint.
The CEO scopes a first package around RFI responses and shop drawing review comments, with drawings, fabricator documents, client names and addresses removed. Calculation packages are deferred pending rights review, and forensic projects are excluded outright.
The rights review finds that several prime agreements flow down strict confidentiality on all project documents, so those projects are excluded. The package that remains is smaller, but every project in it has a documented rights basis.
How SourceX works with structural and MEP firms#
SourceX starts with a metadata-only fit check: which systems hold RFIs, shop drawing reviews and calculations, how far back they reach, which project types dominate and how much of the work was done as a subconsultant. No drawings or calculations are shared at that stage.
If the firm proceeds, flow-down terms are checked project by project in the Rights step, Preparation separates the engineer's comments from fabricator drawings and client details, and the firm signs off on the final scope before Delivery, following the SourceX five-step transaction of Supply, Rights, Preparation, Approval and Delivery. A SourceX Evidence Packet records, for every project in scope, its provenance, the licensing rights relied on, the permitted use, the privacy record and the release authorization.
Frequently asked questions
Can calculations be licensed if project names are removed?
Removing names helps with privacy and confidentiality, but it does not settle rights. A calculation package can still identify a building through its geometry and loads, and the client agreement may restrict its use. Calculations usually go through a project-level rights review and are often deferred to a later phase.
Does licensing records change our responsibility as engineer of record?
Licensed records are provided for AI development, not for design reliance, and the license should say so. Your obligations on the original projects do not change. Ask your professional liability carrier whether it wants notice, and have counsel review the reliance and warranty language.
Are older projects in legacy systems still usable?
Often, if they can still be exported. Older RFIs and reviews may sit in retired document management systems, archived email or file servers. Check date coverage and export routes early, because history lost in a migration cannot be recovered later.
Is there demand for structural records specifically?
Demand varies by buyer and changes over time. Review and response records are relevant to developers building tools for design checking, submittal review and construction coordination, but whether a given buyer wants a particular package is known only when that buyer engages. A fit check shows whether the records are worth putting forward.
Is a small structural firm too small to qualify?
Typical fit is a firm with 50 or more full-time employees at peak and several years of operating history. Smaller specialized firms may still be reviewed when a buyer requests a specific record type, such as shop drawing reviews for a particular structural system.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.