Engineering and architecture
Can you license specifications built on a third-party master spec?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
You usually cannot license the base text of a third-party master specification, because your subscription licenses that text to you for project use rather than transferring ownership. What may be licensable is your firm's own layer: edits, coordination notes, custom sections and the decisions behind spec revisions, once separated from the base text and reviewed.
Key takeaways
- Base master-spec text is licensed to your firm for project use, not owned, so it stays out of any third-party license.
- An edited project specification is mixed material: licensed base text with the firm's decisions layered on top.
- A change record that captures edits and their reasons can describe firm decisions without reproducing the publisher's text.
- Custom sections written without a master base, coordination notes and substitution reviews are the strongest candidates.
- Read your actual subscription agreement, including any terms on automated processing, before any outside use.
Which parts of a master-spec-based specification can be licensed?#
Specifications built on a third-party master spec can be licensed only in part. The base text, whether from MasterSpec or another commercial master guide specification service, reaches your firm under a subscription agreement that typically lets you edit and issue specifications for your projects, not pass the master content on to others.
Your firm's contribution is a different matter. Edits that reflect project decisions, sections written from scratch, coordination notes and the history of why sections changed are the firm's work, subject to client confidentiality. The practical job is separating the two layers so that only the firm's layer is considered.
Three layers inside every edited specification#
Every edited project specification contains up to three layers of authorship, plus material from outside parties. Naming the layers makes the included and excluded lists almost automatic.
| Layer | Who authored it | Included or excluded | Why |
|---|---|---|---|
| Master base text and publisher's editor notes | The publisher | Excluded | Licensed to you under the subscription, not owned |
| Office master edits | Your firm, on licensed text | Mostly excluded as text | Still largely the publisher's words, with firm changes inside |
| Project edits, inserts and deletions | Your firm | Included as a change record, after review | Reflects project decisions, but sits inside licensed text |
| Custom sections written without a master base | Your firm | Included, after review | Firm-authored work |
| Coordination notes, review comments and substitution reviews | Your firm | Included, after review | Firm work product that records reasoning |
| Manufacturer guide specs and product data | Manufacturers | Excluded | Owned by the manufacturers |
| Owner-furnished specification standards | The client | Excluded | Client material under the owner agreement |
Questions to ask about your subscription terms#
Your subscription terms decide how far the firm's layer can travel, so read the agreement your firm actually accepted rather than relying on memory or a colleague's summary. Terms vary by publisher and subscription tier and change over time.
If the answers are unclear, ask the publisher in writing before any outside use. A short written confirmation is far cheaper than unwinding a license later.
- What does the license allow the firm to do with master text beyond issuing project specifications?
- Are there restrictions on databases, extracts or works derived from the master content?
- Do the terms address automated processing, text mining or AI use of the content?
- Is the subscription tied to a named firm, office or user count, and what happens on a merger or closure?
- What happens to the office master if the subscription ends?
- Who at the firm accepted the terms, and where is the signed or clicked agreement stored?
Building a change record instead of copying sections#
A change record captures what the firm decided without reproducing the publisher's text. It compares each project section against the unedited master release it came from and keeps only the differences and the reasons for them.
Even a careful change record can carry short quoted fragments of base text, especially where an edit modified a sentence rather than replacing it. Review the record against the subscription terms before it leaves the firm, and paraphrase or drop fragments where needed.
- Identify the master release used for each project from section footers or the spec software's records.
- Compare each project section with the unedited master section from that release.
- Keep the differences: inserted language, deleted paragraphs and selected options.
- Attach the reason for each change from coordination notes, RFIs or review comments.
- Drop manufacturer-provided text and owner standards from the record.
- Mark sections whose source release cannot be identified as unknown and leave them out.
Office masters: the hardest case#
An office master is the hardest case because it feels like the firm's own document. Specifiers have tuned it for years, deleted options the firm never uses and inserted preferred products and standard language. Yet most of its sentences still come from the publisher's base text.
Treat the office master like any project section: compare it with the master release it was built from and keep only the differences. Those differences, such as the firm's preferred assemblies, its standard quality requirements and the notes explaining them, are often a concise record of the firm's technical standards.
Firms that wrote their own sections for building types they specialize in, without a master base, hold a cleaner asset. Keep the drafting history that proves it, because a later reviewer will ask.
Which specification decisions carry the most value?#
The specification decisions that carry the most value are the ones that show judgment under constraints. A base master spec is available to every subscriber and is therefore reproducible, which lowers its value in the SourceX Enterprise Data Value Framework; firm decisions are unique and carry domain expertise and human-generated signal, which raise it.
| Decision record | What it shows |
|---|---|
| Product and system selections with reasons | How a specifier balanced performance, cost, availability and owner preference |
| Substitution request reviews | How proposed alternates were judged against the specified basis of design |
| Spec-related RFIs and responses | Where specifications were unclear in the field and how intent was clarified |
| Coordination comments between drawings and specs | How conflicts between documents were found and resolved |
| Addenda that revised sections during bidding | Why requirements changed under bidder questions |
Illustrative: a COO scoping the spec archive#
Illustrative: Lanternfield Architects, a fictional firm, produces specifications from a commercial master guide specification and keeps an office master in its spec software. The COO is asked whether years of project manuals could form part of a data license.
The answer is mostly no for the manuals themselves. The firm instead assembles change records for closed projects: the edits made to each section, the specifier's coordination notes, substitution request reviews and spec-related RFIs. Client names, project addresses and manufacturer text are removed.
The COO also writes to the publisher to confirm how its terms treat derived records. Until that answer arrives, the firm limits the candidate set to custom sections and decision records that reproduce no master text.
How SourceX handles master spec content#
SourceX flags third-party content during the Rights step of the SourceX five-step transaction, before any Preparation work begins. Master spec text, manufacturer data and owner standards are excluded from scope, and the SourceX Evidence Packet records the licensing rights relied on for each included record, including how firm edits were separated from licensed base text.
The first conversation needs no specifications at all. The fit check asks which systems hold specifications and related records, how many years are accessible and which master spec services the firm subscribes to, so third-party content is visible before anything is prepared.
Frequently asked questions
Does editing master spec text make it our firm's property?
Generally not. Editing licensed text produces a document that combines the publisher's content with your changes. Your changes may be your work, but the underlying text remains licensed to you. Treat edited sections as mixed material and consider only the separable firm layer.
Can we share our office master with a merger partner?
That depends on the subscription terms and how the merger is structured. Many subscriptions are tied to a named firm or office, so a transfer may need the publisher's consent. Check the agreement before sharing or combining office masters.
Are performance specifications we wrote from scratch fully ours?
Sections written without a master base are usually the firm's work, subject to client confidentiality and the owner agreement. Keep evidence that they were authored from scratch, such as drafting history, because mixed provenance is common in spec archives.
What about specifications issued publicly for bidding?
Issued specifications may become publicly available as bid documents, but public availability does not change copyright or license terms. The master text is still the publisher's, and public access does not give anyone the right to license it.
Can we license our specification review comments on contractor submittals?
Often yes, because review comments are firm work product, subject to client confidentiality. Remove quoted master text and manufacturer data, keep the reviewer's reasoning, and check the owner agreement for restrictions on project information before any outside use.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.