Engineering and architecture
Estimating cost books and unit-price databases: can they be licensed?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
An estimating cost database can be licensed only to the extent your firm created the data. Unit prices built from your own estimates, bids and project history may qualify after a client review. Lines copied from a subscribed cost book or supplier price list usually cannot be passed on, and any subscriber could reproduce them anyway.
Key takeaways
- Run a source check on every cost line family before discussing value: origin decides who controls the number.
- Subscribed cost book lines and supplier quotes are usually excluded, even after your estimators adjusted them.
- Estimate revisions, reviewer comments and estimate-versus-outcome comparisons carry more value than unit-price tables.
- Owner budgets and closeout costs are often confidential client information, not the firm's data.
- A smaller package with clean provenance is easier to license than a whole blended database.
Can an estimating cost database be licensed?#
An estimating cost database can be licensed where the unit prices, assemblies and history in it originated with your firm and your contracts allow disclosure. Most firm databases are blends: a core of subscribed cost book lines adjusted with the firm's own factors, plus years of estimates, bid tabulations and closeout figures from real projects.
The licensing question is therefore not whether the database as a whole can be licensed but which columns and records can. A source check, done one line family at a time, gives the answer and also shows where the value sits.
Source check: where did each cost line come from?#
Cost data should be sorted by origin before anyone discusses value. The origin decides who controls the number, what you must check and whether the line belongs in a license at all.
| Source of the cost data | Who typically controls it | Licensing position |
|---|---|---|
| Unit prices your estimators derived from your own projects | Your firm, subject to client confidentiality | Candidate after client and confidentiality review |
| Your estimates, revisions and reviewer comments | Your firm, as part of its work product | Candidate, and often the most useful part |
| Closeout costs from contractor pay applications or owner reports | Shared with the owner, often confidential | Check the owner agreement; aggregate or exclude |
| Bid tabulations | Public bids may be public records; private bids are often confidential | Check how you obtained them and any terms attached |
| Lines copied from a subscribed cost book or online cost service | The publisher, under your subscription license | Usually excluded; redistribution is commonly restricted |
| Supplier quotes and distributor price lists | The supplier, often under confidentiality | Usually excluded |
| Location factors and escalation indices from a subscription | The publisher | Excluded; keep only your own adjustment decisions |
How do you tell your own numbers from subscribed ones?#
Estimating software and spreadsheets usually hold the clues that separate firm-created numbers from subscribed ones. The goal is a source field on each line or assembly that says where the number came from.
Expect a gray zone. A cost book line your chief estimator adjusted for a regional labor market is still built on licensed content. In most cases the safer path is to license the adjustment rationale and the estimate history, not the adjusted number on its own.
- Check source or reference fields in the estimating software, which often carry the cost book line number.
- Compare assemblies against the cost book release they were built from; unchanged lines are the publisher's.
- Look for estimator notes explaining adjustments, which record your firm's judgment even when the base is not yours.
- Review workbook version histories to see which values estimators typed and which were pasted in.
- Tag lines with no traceable source as unknown and keep them out until resolved.
What makes cost history useful to AI teams?#
Cost history is useful to AI teams when it shows how estimators reasoned, not just what a number was. A unit price on its own is a lookup. A sequence of estimate revisions, quantity takeoffs, assumption notes and the final result shows how professionals estimate under uncertainty.
These notes line up with the SourceX Enterprise Data Value Framework, where domain expertise, human-generated signal, uniqueness and recency increase value and reproducibility reduces it. Subscribed cost book values are reproducible by anyone with the same subscription, which is one more reason to leave them out.
| Record | What it shows | Value note |
|---|---|---|
| Estimate revisions by design phase | How scope and assumptions changed as the design matured | High: linked, human-generated and domain-specific |
| Reviewer and principal comments | Where experienced reviewers challenged quantities or prices | High: expert judgment in plain language |
| Estimate compared with bids and final cost | How accurate estimates were and why they missed | High when outcomes are recorded |
| Quantity takeoffs linked to drawings | How quantities were measured from documents | Medium to high, depending on linkage |
| Standalone unit-price tables | A snapshot of rates | Low: reproducible and quickly dated |
Bid tabulations, closeout costs and other borrowed numbers#
Bid tabulations and closeout costs are the gray middle of most cost databases, because they record real market outcomes that the firm observed but did not create. Their status depends on how the firm obtained them. A tabulation read aloud at a public bid opening is different from a private bid list an owner shared with the firm in confidence.
Closeout costs raise a similar issue. When an owner shares final contractor costs so the firm can calibrate its estimates, that information usually arrives under the owner agreement's confidentiality terms. The firm can learn from it internally, but passing it to a third party is a separate question that the agreement, not the firm's convenience, answers.
A practical approach is to keep these borrowed numbers as outcome markers rather than as data products. Recording that an estimate came in above or below the low bid, and why, often preserves most of the learning value while leaving the underlying figures out.
Illustrative: a cost estimating group sorting its database#
Illustrative: Northgate Civil, a fictional engineering firm, runs a cost estimating group that prices site work for private developers and industrial owners. Its estimates live in Excel workbooks linked to a master unit-price sheet, and project budgets sit in Deltek Vantagepoint.
A source check finds that most of the master sheet began as cost book lines, adjusted every year. The firm keeps that sheet out. It proposes instead the estimate workbooks for closed projects, principal review comments and a table comparing each estimate with the low bid, with client names, sites and supplier quotes removed.
The result is smaller than the database the managing principal first pictured, but it is clean on rights and rich in the reasoning that buyers look for.
Mistakes that sink a cost data license#
Most problems in cost data licensing come from scope, not from the data itself. Each of the mistakes below can be caught during the source check if someone is looking for it.
- Offering the whole database without separating subscribed content.
- Including supplier quotes received under confidentiality or nondisclosure terms.
- Leaving client names, project addresses or owner budgets in estimate headers.
- Treating closeout costs from an owner's books as the firm's own data.
- Describing the package as a price database when its value lies in the estimating history.
How SourceX handles estimating records#
SourceX reviews estimating records in the Rights step of the SourceX five-step transaction, after a metadata-only fit check. Subscribed and supplier content is identified and carved out before Preparation, where client identifiers, addresses and owner budgets are removed.
Each package that proceeds carries a SourceX Evidence Packet recording provenance, the rights relied on, permitted use, the privacy record and release authorization. There is no SourceX price list for estimating data; value is known only once a buyer engages with a specific package.
Frequently asked questions
Does our estimating software vendor have any claim to our cost data?
Usually not to data your estimators entered, but read the software terms. Some products bundle cost content under a separate license, and some cloud platforms have terms covering aggregated or usage data. Your own entries and estimates are generally treated as customer data under those agreements.
Do we need client permission to license estimate histories?
It depends on the owner agreement and its confidentiality clause. Many agreements treat project budgets and cost information as confidential. Removing client names may be enough under some terms and not under others, so review each client's terms with counsel before including their projects.
Is old cost data still worth anything?
Dated unit prices lose relevance quickly, but the reasoning around them ages better. Estimate revisions, assumptions and the reasons estimates missed remain useful because they show how estimators work. Recency still matters, so recent years usually carry more weight than older ones.
Can we license averages aggregated across many projects?
Aggregation can ease client confidentiality concerns because no single client's numbers are visible. It does not cure subscribed content mixed into the averages, and averages carry far less reasoning than project-level records. Most AI teams prefer documented project histories over summary tables.
Who inside the firm should approve a cost data package?
The managing principal or another authorized officer signs, but the chief estimator should confirm the source check, because only the estimating team knows which lines came from subscriptions and supplier quotes. Counsel should review client confidentiality terms, and finance should confirm that no owner budgets or fee data remain.
Related resources
- IndustryConstruction data
- InsightCan I license my Autodesk Construction Cloud data to AI companies?
- InsightAI value creation in portfolio companies: start with operating records
- InsightOld project archives: asset or liability for a design firm?
- SolutionEnterprise data: the records of how organizations actually work
- SolutionProprietary data: information only your company has
See if your company qualifies
A short company assessment. No data uploads are needed.