Facility condition assessments: who owns them and what they're worth

What does a facility condition assessment record set contain?#

A facility condition assessment record set contains far more than the bound report the owner receives. Behind each report sit field observations, photos, asset inventories, condition ratings, deficiency records, cost estimates and renewal forecasts, plus the internal review comments that shaped the final numbers.

Most FCA practices capture this material in an inspection app or tablet forms, roll it into a spreadsheet or a capital planning export, and then publish a narrative report. Each layer has a different author and a different contract position, which is why ownership questions rarely have a single answer.

• 1Field observation records: system, component, location, condition notes and the assessor's name.
• 2Photo sets tagged to assets or deficiencies.
• 3Asset inventories with install dates, quantities and remaining useful life estimates.
• 4Deficiency records with category, priority, recommended action and estimated cost.
• 5Renewal forecasts and facility condition index calculations delivered to the owner.
• 6Internal QA comments where a senior reviewer changed a rating, cost or priority.

Who owns the FCA report, and who owns the method behind it?#

The facility condition assessment report belongs to whichever party the contract names, and many owner-drafted FCA agreements give the owner ownership of, or unrestricted rights in, the report and the delivered data. The firm's tools for producing the report are a separate question, and they usually stay with the firm when the contract reserves them or says nothing.

Read the deliverables clause and the data clause together. Some agreements define work product broadly enough to sweep in every spreadsheet and photo created on the project, while others separate deliverables from pre-existing materials and the firm's general know-how.

Why delivered FCA data is harder to reuse than the report#

Delivered FCA data is harder to reuse because owners load it into capital planning and maintenance systems, where it becomes part of the owner's operating records. Once a deficiency list sits inside an owner's CMMS, the owner reasonably expects that the same list will not reappear elsewhere, even with the building name stripped out.

Repeat engagements add a complication. When a firm reassesses the same portfolio on a cycle, each new assessment starts from the owner's prior data, so a single record can mix firm observations with owner-maintained fields. Treat any record that started in the owner's system as client-furnished until a rights review says otherwise.

Inspection apps raise their own question. If assessors collect data in a vendor-hosted app, the vendor's terms govern export, access after cancellation and any vendor use of customer content. Export scope, photo and audit-field export, and access after cancellation differ by vendor and plan, so check the subscription terms and run a test export before relying on an archive.

What are FCA records worth to AI developers?#

FCA records are worth most to AI developers when they show expert judgment in sequence: an assessor observes a condition, rates it, recommends an action, prices it and sets a priority, and a reviewer sometimes changes the result. That chain is human-generated, domain-specific and hard to reproduce from public sources, which are drivers in the SourceX Enterprise Data Value Framework.

The same records carry real costs. Photos show interiors, signage and sometimes people; addresses and asset tags identify the property; and owner-specific cost adjustments can reveal budgets. Preparation cost and privacy burden reduce net value, so a smaller, cleaner set of linked observations often beats a large archive of PDFs.

Illustrative: an MEP firm separates its method from its clients' findings#

Illustrative: a fictional MEP and building envelope engineering firm runs an FCA practice for private office landlords and industrial owners. Its assessors collect observations in a tablet inspection app, estimators maintain a cost library in spreadsheets, and every report passes a principal review logged as comments in the draft.

When the firm considered licensing, counsel sorted its contracts into two groups. Agreements on owners' paper assigned all project data to the owner, so those projects were excluded. Agreements on the firm's own terms reserved its methods and permitted de-identified internal use, so those projects became the candidate set.

The firm proposed a package of its deficiency taxonomy, rating rubric and principal review comments, with building names, addresses, photos and owner budgets removed. Commercial cost data was excluded entirely. The package was smaller than the firm first imagined, but every record in it had a documented basis for licensing.

What to check before reusing FCA records#

Check each contract family before touching any archive, because FCA work often runs under a mix of owner master agreements, task orders and the firm's own proposal terms. A short, shared checklist keeps the review consistent across practice leaders and offices.

• 1Find the ownership, work product and data clauses in each master agreement and task order.
• 2Look for a pre-existing materials or background IP clause that reserves your methods.
• 3Flag confidentiality terms covering building condition, security systems or budgets.
• 4Identify any commercial cost data inside your cost library and read its license.
• 5Confirm whether your inspection app allows a full export with history, photos and audit fields.
• 6Mark public owners and portfolios with security-sensitive facilities for default exclusion.

How SourceX approaches facility condition assessment records#

SourceX treats an FCA practice as two record families: client findings, which are usually excluded, and the firm's own method and review records, which are assessed for licensing. Within the SourceX five-step transaction, the Rights step sorts contracts, the Preparation step removes locations, photos and owner identifiers, and the firm approves the package before Delivery.

Each approved package carries a SourceX Evidence Packet recording provenance, licensing rights, permitted use, the privacy record and release authorization. Nothing is shared during the initial fit check, which collects only metadata such as system names, record families and contract types.