Defect closeout verification records across systems: a map of the location, item and subcontract keys that join one defect

Short answer

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.

Visual briefFull-size diagram
Five system nodes in two rows, room schedule, inspection platform, photo store, project system and acceptance record, with the room code, item ID, subcontract number and item list keys traveling along the links to join one defect case, and the meeting minutes link marked as the weak join.
Illustrative system map for a stair door defect; the item numbers and keys are invented examples.

This map is part of the defect closeout verification guide. 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.

SystemRecords it holdsLinking keyUsual owner
Room schedule or modelBuilding, level, unit and room codes from the design team's room dataRoom codeDesign or BIM coordinator
Inspection platformPunch items, status history, rejections, item links, assigneesItem ID plus room codeQuality manager
Photo storeBefore and after repair photosItem ID, if attached in the platform or named in the fileQuality manager or document control
Project systemSubcontracts, back-charges, change events, cost codesSubcontract number; item ID in the back-charge noteProject controls lead
Acceptance recordOwner sign-off, substantial completion certificate, closeout lettersList of item IDs, or noneProject 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 works through a different case decision by decision.

StepSystemRecordKey that joins it
First defectInspection platformPL-207, stair door fails to self-close, closed after closer adjustedRoom L3-STR-2, door D3-14
ReopenInspection platformPL-207 reopened, door drifts open again two weeks laterSame item ID, status history kept
Cause foundInspection platformPL-226, door frame out of plumb, linked to PL-207Room L3-STR-2
ProofPhoto storeLevel readings and closing test video after the frame resetAttached to PL-226
Who paidProject systemBack-charge BC-041 against the door and frame subcontract SC-118Note quotes PL-207 and PL-226
AcceptanceAcceptance recordArchitect's field report and owner sign-off for level 3Lists 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

BreakTypical causeWhat to note in an inventory
Corridor and unit names differ between systemsInspection platform set up before the room schedule was finalProjects where codes match, and projects where they do not
Reappearing defect logged as a new itemLinking not used, or reopen not allowed for that roleThe year linking became standard practice
Photos lose their itemExported to folders without item IDs in file namesWhether photos were kept inside the platform
Root cause only in email or meeting minutesNo root-cause field or habit of using itWhether minutes are filed by project and date
Acceptance covers the whole listBatch sign-off without item numbersWhether 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 covers that stage, and change order data 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 lists questions for that platform's administrator, the construction punch list page explains a single item's loop, and the 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 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, check the contractor on who qualifies and read the program terms before you describe the coverage.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Our inspection platform and project system use different room names. Is the history still usable?

Often yes, but the join is weaker. Note whether a room schedule or model maps one naming scheme to the other, and from which projects. A partial mapping is worth stating honestly rather than hiding.

Do repair photos need item IDs in their file names?

Only if photos are stored outside the inspection platform. Photos attached to an item inside the platform are already joined. The risk is in exports and closeout folders, where photos can lose their link to the item.

Is a back-charge record really evidence of root cause?

It is a strong cross-check, because a company rarely charges a subcontractor without a documented reason. It is not proof on its own; the linked items and test record carry the technical evidence.

Sources

  1. support.procore.com/faq/what-is-the-punch-list-work-flow
  2. support.procore.com/products/online/user-guide/project-level/pun…
  3. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment