Engineering and architecture
Third-party database reports inside Phase I files: what the licenses allow
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
An environmental database report license generally covers use for the named project and its authorized users, so radius reports, historical maps and city directory abstracts inside Phase I files should be excluded from any dataset. Treat every third-party appendix as out by default, then consider only consultant-authored internal records, and only where client contracts allow.
Key takeaways
- Database reports in a Phase I file are a provider's licensed product, not records the consultant owns.
- The provider agreement and the terms delivered with each report, not the folder it sits in, decide reuse.
- Historical maps, aerial photos and city directory abstracts usually carry their own provider terms.
- Database content also hides in report body tables, redrawn figures and GIS layers, not only in appendices.
- Removing third-party content does not clear the rest of the report, which is usually a client deliverable.
What do environmental database report licenses allow?#
An environmental database report license generally allows the consultant and its client to use the report to support the assessment it was ordered for. Providers compile federal, state and local agency listings, geocode them and package them as a radius report for one property, and the terms that come with that product commonly tie use to that property, that project and the named users.
Reuse outside that purpose is where the limits bite. Terms commonly restrict resale, redistribution, inclusion in other products and access by anyone other than authorized users. A dataset licensed to an AI developer is a new use by a new party, which is exactly the kind of reuse those terms tend to address.
The working rule for a data license is simple: third-party database reports are licensed per project, so exclude them from any dataset. Read the actual agreement before relying on any narrower reading.
Third-party content commonly found in a Phase I file#
A Phase I file prepared under the ASTM E1527 standard practice draws on several outside sources, and each arrives with its own terms. The table lists the usual items and a default treatment for a licensing review.
| Item | Typical source | Default in a dataset |
|---|---|---|
| Environmental database radius report | Commercial database provider | Exclude |
| Historical fire insurance maps | Map archive provider under license | Exclude |
| Historical aerial photographs | Commercial vendors or government archives | Exclude unless source and terms are confirmed |
| City directory abstracts | Commercial directory provider | Exclude |
| Topographic maps | Often government sources, sometimes resold | Exclude; low value even when public |
| Agency file review copies | Records responses from regulators | Exclude; may hold personal data and others' work |
| User questionnaire and interview notes | Client, site contacts and past owners | Exclude; client-confidential |
| Site reconnaissance photos and narrative | Consultant staff | Firm-authored but a client deliverable; needs client release |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
Which provider terms to read before any reuse#
The provider agreement and the terms printed in or delivered with each report decide what reuse is permitted. Firms often order reports under a master subscription, so the controlling language may sit in an account agreement signed long ago rather than on the report itself.
Answers to these questions shape the archive, not just the license. A firm may be allowed to keep reports in its professional file while still being barred from passing them to anyone else.
| Clause | What it usually addresses | Question for your review |
|---|---|---|
| Permitted use | The purpose the report may serve | Is use limited to the named project and assessment? |
| Authorized users | Who may access and rely on the report | Does access extend beyond the firm and its client? |
| Redistribution and resale | Sharing with third parties | Is any transfer to an unrelated party allowed? |
| Derivative products | Use of report content in other work | Are summaries or extracted tables covered? |
| Retention | Keeping copies after the project | May archived copies be kept, and for what purpose? |
| Survival | Terms that outlast the subscription | Do restrictions continue after the account ends? |
Where database content hides beyond the appendix#
Database content hides in more places than the appendix tab, which is why a folder-level exclusion is not enough. Consultants paste listing summaries into the report body, redraw radius maps for figures and load provider data into their own templates and GIS projects.
Older projects add a wrinkle. Reports ordered years ago may have been delivered on disc, printed and scanned, or saved under a provider's earlier product name, so a search for current provider names will miss them. Search by report type and appendix label as well, and ask senior staff which sources the group used in earlier eras.
- Report body tables summarizing listed sites, distances and database names.
- Figures that reproduce or trace the provider's radius map.
- Report-writing templates that import provider data fields.
- GIS layers built from provider downloads for site figures.
- Email threads that quote or attach report excerpts for internal review.
- Lender reliance packages that bundle the full report with its appendices.
A carve-out checklist for Phase I archives#
A Phase I carve-out works best as a repeatable checklist run on every project folder before anything is staged for review. The goal is a record of what was removed and why, not just a cleaner folder.
Run the checklist on a few sample projects from different years before applying it across the archive. Folder conventions, report templates and provider relationships change over time, and a sample pass shows where the checklist needs another step before staff apply it at scale.
- Tag each project folder with the client, the property and the providers used for database and historical sources.
- Remove appendices containing database reports, historical maps, aerial photos and directory abstracts.
- Search report text and figures for provider names and listing tables, then remove or flag those passages.
- Exclude GIS layers and spreadsheets derived from provider data.
- Hold the remaining consultant-authored material until the client contract has been reviewed.
- Log each exclusion with the folder, item type and reason, so the record can be audited later.
Illustrative: a due diligence group decides what to keep#
Illustrative: a fictional engineering firm runs a due diligence group that completes Phase I assessments for lenders and commercial buyers. Its archive holds final reports with full appendices, draft reports with reviewer markups, a proposal and scoping database, and a shared mailbox where reviewers discuss findings.
The diligence manager excludes every final report outright, because each one mixes provider content, client information and lender reliance terms. Draft reports go too, since the appendices travel with them. What remains is internal: reviewer checklists, scoping notes on how the group judges whether a historical source is reasonably ascertainable, and anonymized review comments on how findings were classified.
Those internal records carry the firm's judgment without carrying anyone else's licensed product. The group files its exclusion log and moves only that internal layer forward to a rights review.
How SourceX treats third-party content#
SourceX treats third-party licensed content as out of scope by default. During the Rights step of the SourceX five-step transaction, provider reports, purchased maps and similar materials are identified and excluded before any Preparation work begins, and each exclusion is recorded rather than assumed.
For records that do proceed, the SourceX Evidence Packet documents provenance, licensing rights, permitted use, the privacy record and release authorization. A buyer reviewing it can see that the package contains the firm's own work and that third-party products were removed.
Frequently asked questions
Can we keep database reports in our archive after the project closes?
Keeping a report in the professional file is a different question from licensing it. Many firms retain complete reports to support their work if it is later questioned, and provider terms may address archival copies. Check the retention language, but do not read permission to keep a copy as permission to share it.
Are the underlying government records free to use?
The agency listings behind a database report are often public records, but the provider's compilation, geocoding and formatting are its product, delivered under its terms. Pulling the same public listings fresh would be a separate exercise, and public listings are reproducible, so they add little value to a licensed dataset anyway.
Does rewriting database findings in our own words solve the problem?
Not reliably. Provider terms may address derivative use of report content, and a paraphrased list of nearby listed sites still reveals the client's property and its surroundings. The safer approach is to exclude findings tied to a specific property and keep only the firm's methods and review reasoning.
Can the client license the database report instead?
Usually not. The client is typically an authorized user of the report for its transaction, not its owner. Rights to redistribute rest with the provider, so any broader use would need the provider's agreement, not just the client's.
Do lender reliance letters change anything?
Reliance letters extend who may rely on a report's conclusions; they do not expand rights to reuse third-party content. They can add confidentiality expectations of their own, which is one more reason final reports and their appendices stay out of any data license.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.