# Who can license defect closeout records? | SourceX

Canonical: https://refer.sourcex.si/questions/who-can-license-defect-closeout-verification-records
Last updated: 2026-11-04

Introduce the contractor's CEO, with the contracts manager or general counsel, and bring in the quality manager as sponsor. The quality manager knows which projects have clean, linked defect histories and which were closed in a rush, so they are the right first contact. Being able to log in to the inspection platform, or even to close punch items as final approver, is access, not authority. Owner contracts and photos taken inside occupied units go to counsel, and what can be licensed stays unknown until SourceX's rights review.

This tree is part of the [defect closeout verification guide](/guides/workflow-defect-closeout-verification), which covers what to inventory before asset handover. It does one job: helping a construction QA consultant find the person inside a contractor who can say yes to a conversation about its closeout records.

## Approving a punch item is not approving a license

The confusion starts inside the inspection platform. Platforms give roles real power over each item. In Procore's punch list workflow, for example, only the final approver or an admin can close a punch item, and a final approver can reject an item as not accepted. People who hold those roles are used to deciding things about defect records.

That authority stops at the item. Whether the company licenses years of closeout history is a different decision about company assets, contracts and risk, and it belongs to the CEO. A consultant who has worked closely with a project's final approver should treat that person as a source of facts and, ideally, a route to the quality manager.

## The tree: five gates from platform role to signer

Pass each gate in order. A gate either moves you one step closer to the signer or opens a branch for counsel.

1. **Gate 1: Who can describe the records?** The quality manager. Ask which record classes exist (punch items with status history, rejections, linked items, photos, test records, sign-offs), across how many projects and years. *Result:* a sponsor and the facts for a brief.
2. **Gate 2: Who runs the systems?** The inspection platform admin and the project controls lead. They know export options, linking habits and archive settings. *Result:* coverage facts; no authority.
3. **Gate 3: Do owner contracts reserve project records?** Many owner contracts require the contractor to deliver quality records at project close or keep them confidential. What the owner received tells you little; the contract wording decides who may reuse what. *Result:* branch to the contracts manager or general counsel.
4. **Gate 4: Do photos or records identify people?** Photos taken inside occupied homes can show residents, belongings and addresses, and inspection notes can name tenants. Under the GDPR, personal data means any information relating to an identified or identifiable natural person, and similar concepts exist elsewhere. *Result:* branch to counsel or the privacy lead.
5. **Gate 5: Who approves new uses of company data?** The CEO; in a portfolio company, sometimes with the investor's operating partner informed. *Result:* the signer you introduce, with counsel alongside.

## Roles on a construction project, and what each can decide

| Role | What they know | Can they authorize a licensing discussion? |
|---|---|---|
| Quality manager | Which projects have linked, complete histories | Sponsors and convenes; rarely approves alone |
| Superintendent or final approver | Item-level decisions on their projects | No; project authority only |
| Inspection platform admin | Exports, roles, archive settings | No; technical access only |
| Project controls lead | Back-charges, subcontracts, cost records | No; technical access only |
| Contracts manager or general counsel | Owner contracts, subcontracts, privacy duties | No; advises on rights questions |
| CEO | The value and risk of a new revenue line | Yes, as the decision-maker and signer |

## The amber gates: owner contracts and resident photos

Two questions decide scope more than anything else, and neither belongs to the quality manager or the partner.

**Owner contracts.** Contractors usually create and hold their own quality records, but owner contracts vary. Some require delivery of the full closeout record; some restrict reuse of project information; public owners may add their own rules. Counsel reads the contracts project by project, and the answer may differ between a private residential job and a public building.

**Photos and names.** Repair photos are often the most persuasive evidence in a defect history, and the most sensitive. They can be de-identified, cropped or excluded, but deciding how is part of SourceX's rights review with the contractor's counsel, not something to settle before an introduction. The [data rights explainer](/proof/why-data-rights-matter) explains why that review comes first.

What stays unknown until SourceX reviews the opportunity: which projects and record classes are in scope, what must be removed or de-identified, whether there is dataset demand, and whether any offer is made. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout.

## Making the introduction

Draft a brief with the [referral brief template](/resources/defect-closeout-verification-referral-brief-template), ask the quality manager to correct it, and suggest they forward it to the CEO with the contracts manager copied. The [exception examples page](/guides/defect-closeout-verification-exception-examples) shows the kind of linked case worth mentioning, and the [Procore export page](/systems/procore-export-project-data) lists questions for the platform admin at gate 2. To find more candidates, the [partner field guide to quality inspection records](/guides/a-partner-field-guide-to-finding-companies-with-quality-inspection-records) covers other sectors, the [construction technology consultant page](/for/construction-technology-consultant-referral) explains how this fits a consulting practice, and [engineering services outsourcing](/industries/engineering-services-outsourcing-private-equity) shows a related investor-owned profile.

The introduced contractor needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Partners sign the Channel Partner Agreement before submitting introductions; the first valid introduction within the 90-day window is credited when the company submits a verified application, and one partner is credited per company.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

Once the quality manager has agreed to sponsor and you know the CEO will take the introduction, [register as a partner](/register), check the contractor on [who qualifies](/who-qualifies) and read the [program terms](/terms) before the introduction goes out.

## Sources

- https://support.procore.com/faq/what-is-the-punch-list-work-flow
- https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng
- https://refer.sourcex.si/terms
