# Defect closeout system map: linking keys | SourceX

Canonical: https://refer.sourcex.si/guides/defect-closeout-verification-records-across-systems
Last updated: 2026-11-04

To reconstruct defect closeout verification across systems, you need four links: a location key that means the same room in every system, an item ID that survives reopening, a photo-to-item link that survives export, and an acceptance record that lists the item IDs it covers. A fifth, the subcontract or back-charge number, ties the defect to who paid for it. The inspection platform and the project system rarely share all of these, so this page maps which system holds each record, the key that joins it, who owns it, and what one fully joined Illustrative case looks like.

This map is part of the [defect closeout verification guide](/guides/workflow-defect-closeout-verification). It answers one question: can the contractor still follow a defect from the room where it was found to the record that accepted the repair?

## Five systems, their records and their keys

On a typical building project, a defect's evidence sits in several places. The table shows where, the identifier that lets each record find the next, and who usually administers it.

| System | Records it holds | Linking key | Usual owner |
|---|---|---|---|
| Room schedule or model | Building, level, unit and room codes from the design team's room data | Room code | Design or BIM coordinator |
| Inspection platform | Punch items, status history, rejections, item links, assignees | Item ID plus room code | Quality manager |
| Photo store | Before and after repair photos | Item ID, if attached in the platform or named in the file | Quality manager or document control |
| Project system | Subcontracts, back-charges, change events, cost codes | Subcontract number; item ID in the back-charge note | Project controls lead |
| Acceptance record | Owner sign-off, substantial completion certificate, closeout letters | List of item IDs, or none | Project manager |

The room code is the spine. Design teams usually publish a room list early, so a clean list of codes often exists somewhere. The question is whether the field crews logging items used it, or typed their own labels such as "corridor by 402". In Procore, for example, each punch item carries a location, the punch list log can be exported as CSV or PDF with that location field, and the log can be filtered by location before export. Whether those locations match the room schedule is the first thing to check.

## The joins and how to test them

Each join can be tested by asking a system owner a yes or no question. None requires opening an item or a photo.

1. **Location join.** Do the inspection platform and the room schedule use the same codes? If not, is there a mapping, and from which projects?
2. **Reopen join.** When a repaired defect returns, is the item reopened or linked, or is a fresh item created with no connection?
3. **Photo join.** Are photos attached to items in the platform? If photos were also copied to closeout folders, do file names keep the item ID?
4. **Cost join.** Do back-charges and change events quote the item ID or at least the room code?
5. **Acceptance join.** Does the owner's sign-off list item IDs, or only state that the punch list is complete?

A strong history answers yes to the first three. The status history itself is usually reliable where the platform enforces roles: in Procore's punch list workflow, assignees mark work ready for review and only the final approver or an admin can close an item, and a final approver can reject one as not accepted, so each status change carries an author.

## One fully joined case (Illustrative)

The identifiers below are invented for a fictional 520-person general contractor finishing a mid-rise office building. They show what fully joined means, using a stair door that would not stay shut; the [exception examples page](/guides/defect-closeout-verification-exception-examples) works through a different case decision by decision.

| Step | System | Record | Key that joins it |
|---|---|---|---|
| First defect | Inspection platform | PL-207, stair door fails to self-close, closed after closer adjusted | Room L3-STR-2, door D3-14 |
| Reopen | Inspection platform | PL-207 reopened, door drifts open again two weeks later | Same item ID, status history kept |
| Cause found | Inspection platform | PL-226, door frame out of plumb, linked to PL-207 | Room L3-STR-2 |
| Proof | Photo store | Level readings and closing test video after the frame reset | Attached to PL-226 |
| Who paid | Project system | Back-charge BC-041 against the door and frame subcontract SC-118 | Note quotes PL-207 and PL-226 |
| Acceptance | Acceptance record | Architect's field report and owner sign-off for level 3 | Lists PL-207 and PL-226 |

Every row can be reached from the room code, the door number or an item ID. The reopen in row two is what a weaker setup loses: had the crew logged a fresh item instead, the history would show two unrelated door complaints. The back-charge is the cost-side cross-check, confirming that the company held the frame installer responsible.

## Where the chain breaks

| Break | Typical cause | What to note in an inventory |
|---|---|---|
| Corridor and unit names differ between systems | Inspection platform set up before the room schedule was final | Projects where codes match, and projects where they do not |
| Reappearing defect logged as a new item | Linking not used, or reopen not allowed for that role | The year linking became standard practice |
| Photos lose their item | Exported to folders without item IDs in file names | Whether photos were kept inside the platform |
| Root cause only in email or meeting minutes | No root-cause field or habit of using it | Whether minutes are filed by project and date |
| Acceptance covers the whole list | Batch sign-off without item numbers | Whether sign-offs list item IDs, and from when |

Meeting minutes are the weakest join, because they are free text filed by date rather than linked to items. A history that relies on them can still be described, but should be described as partial. After handover, the same chain continues into callbacks; the live page on [warranty claims data](/data-types/warranty-claims-data) covers that stage, and [change order data](/data-types/change-order-data-construction) covers the cost side.

## Describing coverage in an introduction

The partner carries this map at metadata level only. A useful line reads: "About 35 projects over seven years; room codes match the schedule from year three; items linked on reopen from year four; photos kept in the platform throughout; back-charges quote item numbers on most projects; owner sign-offs list item IDs on recent projects only." The [Procore export page](/systems/procore-export-project-data) lists questions for that platform's administrator, the [construction punch list page](/data-types/construction-punch-list-process) explains a single item's loop, and the [manufacturing QA example pack](/resources/manufacturing-qa-example-pack) shows the factory equivalent.

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. What stays unknown until SourceX's review: which records owner contracts reserve to the building owner, how photos inside occupied units would be handled, whether there is dataset demand and any offer. The [who-can-license answer](/questions/who-can-license-defect-closeout-verification-records) covers who to introduce. Partners sign the Channel Partner Agreement before submitting, and the first valid introduction within the 90-day window is credited when the company submits a verified application.

## 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.

If the quality manager and project controls lead confirm that location, reopen and photo joins hold across several years of projects, [register as a partner](/register), check the contractor on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you describe the coverage.

## Sources

- https://support.procore.com/faq/what-is-the-punch-list-work-flow
- https://support.procore.com/products/online/user-guide/project-level/punch-list/tutorials/export-the-punch-list-log
- https://refer.sourcex.si/terms
