Engineering and architecture
Revit families and content libraries: firm-owned or vendor content?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Revit family library ownership depends on each family's source. Families your employees built for the firm are generally firm-owned, while manufacturer families, Autodesk default content and purchased libraries arrive under someone else's license. Sort the library by source before any reuse, because a modified manufacturer family still carries the manufacturer's terms.
Key takeaways
- Families created by employees as part of their regular duties are generally the firm's work under the work made for hire rule.
- Manufacturer, Autodesk default and purchased families are licensed content, and their terms travel with any reuse.
- A firm-modified copy of a manufacturer family is mixed content and should be treated as vendor content unless rebuilt.
- Autodesk's General Terms say customers retain ownership of material they create and upload, but ownership does not settle permitted uses.
- Templates, shared parameters and standards often hold more firm-specific value than individual families.
Who owns the families in a Revit library?#
The families in a Revit library are owned by whoever created them, and most firm libraries mix several sources. Families that employees built as part of their regular duties are generally the firm's work: under the work made for hire rule, the employer is treated as the author and copyright owner. Everything else arrived under a license.
Contractor-built families are the most common gap. Firms often hire a BIM consultant to build a family set or clean up a template, and the engagement letter may say nothing about ownership. Without a written assignment, the consultant may still hold the copyright while the firm has only an implied license, which works for projects but is thin support for licensing.
The table shows the usual position for each source. It describes typical arrangements; the actual download terms, purchase agreement or subscription terms control.
| Family source | Usual owner | Licensing note | Include in a data license? |
|---|---|---|---|
| Built by employees | Firm | Generally firm work product | Candidate |
| Built by freelancers or contractors | Depends on the agreement | Needs a written assignment or a clear license | Only with documented rights |
| Manufacturer families | Manufacturer | Download or website terms apply | Exclude |
| Autodesk default content | Autodesk | Provided with the software license | Exclude |
| Purchased or subscription libraries | Library vendor | Purchase or subscription license | Exclude |
| Firm-modified manufacturer families | Mixed | Manufacturer terms still cover the original | Exclude unless rebuilt from scratch |
| Families received from consultants or clients | Consultant or client | Project use only | Exclude |
How do you tell which families came from where?#
You tell where families came from by reading their parameters, file history and download records, because file names rarely tell the truth after years of renaming. Manufacturer content often carries Manufacturer, Model and URL parameters, embedded product codes and type catalogs that mirror a product line.
A BIM manager can run the audit as a library cleanup project, using a parameter export or a content management add-in to list values across the library. The goal is a source tag on every family, kept in the library itself so it survives the next reorganization.
- Export family parameters and flag Manufacturer, Model, URL and product code values.
- Compare names and categories against the Autodesk default library folders installed with Revit.
- Check content platform download histories and purchase records for vendor libraries.
- Ask long-tenured staff which families they built from scratch and which they adapted.
- Tag each family with a source value and store the tag as a shared parameter.
- Quarantine families of unknown origin until someone can document them.
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
What do Autodesk's terms say about your work?#
Autodesk's General Terms include a section titled You Own Your Work, which says the customer retains ownership of files, designs, models, data sets, images, documents and similar material that the customer or its authorized users create and submit or upload to an Autodesk offering. That supports the view that firm-built families and models belong to the firm.
Ownership is not the whole question. AEC Magazine has reported that a broad clause in Autodesk's terms and Acceptable Use Policy, read literally, would stop users from training their own AI models on output from an Autodesk application. Read the current terms, the acceptable use policy and any enterprise agreement with counsel before planning any AI-related use of Revit output.
Manufacturer portals and content platforms carry terms of their own, separate from Autodesk's. Keep a record of where and when each family was downloaded, and by whom, so counsel can later identify which terms applied to that copy and whether they allow anything beyond design use.
Templates, shared parameters and standards: the firm's real library#
Templates, shared parameters and standards are often the most firm-specific content a practice holds. A project template encodes view templates, object styles, annotation, schedules and phasing conventions that took many internal decisions to settle, and a shared parameter file and keynote file describe how the firm classifies and specifies building elements.
These files are usually built in-house and rarely contain client information, which makes them cleaner candidates than project models. Check that no template was adapted from a client's BIM standard or a contractor's requirements, since client-issued standards stay with the client.
Project models are a different matter. Families placed in a delivered model travel with the instruments of service under the project contract, so the model as a whole follows that contract even when the families inside it are firm-built.
Is a family library worth anything for AI?#
A family library on its own is usually worth less than firms assume, because geometry and parameters for common objects are reproducible and widely available. Under the SourceX Enterprise Data Value Framework, reproducibility reduces value, while uniqueness, domain expertise and human-generated signal increase it.
Value rises when content links to decisions. BIM coordination logs, standards committee notes on why a template changed, QA checks that flagged modeling errors, and RFI responses that led to a family revision show how the firm thinks. The library then becomes the reference that makes those records readable.
| Content | Reproducibility | Firm-specific signal |
|---|---|---|
| Generic doors, windows and furniture families | High | Low |
| Firm-built specialty families with formulas | Medium | Medium |
| Project templates and view standards | Low | High |
| Standards committee notes and change history | Low | High |
| Model QA logs and coordination issue records | Low | High |
Illustrative: an architecture firm sorts its content library#
Illustrative: a fictional architecture firm keeps its Revit library on a network share alongside project templates, a shared parameter file and keynotes. Over many years, staff added manufacturer families, families from a purchased library and a large set of firm-built content.
The BIM manager exported parameters across the library, tagged each family by source and quarantined the unknowns. Manufacturer, purchased and default families were excluded. The candidate set became the firm-built families, the templates and standards, and the BIM committee's notes and QA logs explaining standards changes, with project and client names removed. The firm also confirmed with counsel how its Autodesk terms applied before going further.
How SourceX approaches BIM content#
SourceX approaches BIM content by separating owned content from licensed content during the Rights step of the SourceX five-step transaction. Vendor, manufacturer and purchased content is excluded, and firm-built content is assessed alongside the decision records that give it context.
The firm approves the final scope. The SourceX Evidence Packet records provenance for each content source, the licensing rights relied on, permitted use, the privacy record and release authorization.
Frequently asked questions
If we edit a manufacturer family heavily, does it become ours?
Not automatically. Your edits may be your own work, but the original remains the manufacturer's, and the download terms still apply to it. If a family matters for reuse, a firm may choose to rebuild it independently from published product data and document how it was rebuilt, then have counsel confirm the result.
Can we share firm-built families with clients and consultants?
Usually yes for project purposes, since families travel inside models. Sharing them on a project is different from licensing them to a third party. Check whether project contracts gave owners rights in content embedded in models, and keep your library's source tags current.
Do families built by a freelancer belong to us?
Only if the agreement says so. A commissioned work by an independent contractor is a work made for hire only in narrow statutory categories with a signed written agreement. Without an assignment, the firm may hold only a license, so have counsel review freelancer agreements.
Should we keep manufacturer families in the library at all?
Yes for design work, which is what they are provided for. The issue is reuse outside that purpose. Tagging them by source keeps daily work unchanged while making it simple to exclude them from any data package.
Does a free download from a content platform make a family free to reuse?
No. Free to download usually means free to use in design projects under the platform's and manufacturer's terms, and those terms commonly limit redistribution of the content itself. Read the terms attached to each download, and treat anything without clear terms as excluded.
What about Dynamo scripts and add-in tools?
Scripts written by employees are generally firm work, but check each package's license, since many scripts depend on open-source or third-party packages with their own terms. Scripts can be useful evidence of firm process when paired with notes on why they were built.
Sources
- Autodesk's General Terms include a section titled 'You Own Your Work' saying the customer retains ownership of files, designs, models, data sets, images, documents or similar material that the customer or its Authorized Users create and submit or upload to an Offering. Source
- AEC Magazine reported that a broad clause in Autodesk's terms and Acceptable Use Policy, if read literally, would stop users from training their own AI models on output from an Autodesk application. Source
- Copyright Office Circular 30 explains a work made for hire arises either when an employee creates the work as part of regular duties, or when a work in certain statutory categories is created under an express written agreement, and in either case the employer or commissioning party is considered the author and copyright owner. Source
Related resources
- QuestionDo AI labs buy images?
- QuestionWhat if my data contains errors?
- InsightCan I license Epicor Kinetic data to AI companies?
- InsightCan roofing contractors sell their data to AI companies?
- InsightCan fire protection contractors license inspection and deficiency data?
- SolutionData partnerships between businesses and AI developers
See if your company qualifies
A short company assessment. No data uploads are needed.