# Defect closeout: a worked reappearing-defect case | SourceX

Canonical: https://refer.sourcex.si/guides/defect-closeout-verification-exception-examples
Last updated: 2026-11-04

The defect closeout records that explain an exception are the linked ones: the punch item with every status change, the before and after repair photos attached to each step, the rejection when a fix was not accepted, the test that proved the real cause was fixed, and the acceptance record that names the root cause. The hard exception is a repaired defect that reappears in a linked area, because only the linked history shows what actually went wrong. Below is one such case, Illustrative and built for this page, worked step by step, followed by how to recognize similar histories at a contractor.

This worked case belongs to the [defect closeout verification guide](/guides/workflow-defect-closeout-verification), which covers what to inventory before asset handover. Here the focus is one case and the decisions inside it.

## The case file (Illustrative)

A fictional 410-person general contractor is finishing a seven-story residential building. Nobody below is real, and nothing describes a completed deal; the item numbers are placeholders.

| Item | Illustrative value |
|---|---|
| Project | Seven-story residential building, final fit-out and closeout |
| Items involved | PL-118 (unit 402 ceiling), PL-131 (level 4 corridor ceiling), PL-134 (unit 502 shower pan) |
| People deciding | Quality inspector, drywall and plumbing foremen, quality manager, owner's representative |
| Duration | Week 1 to week 12 |
| Outcome | Three items verified and accepted together, root cause named |

## Six steps: what happened, who decided, what was recorded

### Step 1, week 1: the defect is logged

A quality inspector finds a water stain on the ceiling of unit 402 and logs item PL-118 with a photo, assigned to the drywall trade. **Decision:** treat it as a finish defect. **Record:** the punch item, its location, the before photo and the assignee.

### Step 2, week 2: the repair is accepted

The drywall crew replaces and paints the board, uploads an after photo and marks the item ready for review. The quality manager accepts it and it closes. **Decision:** the repair is sufficient. **Record:** the status history and the after photo. In Procore's punch list workflow, for example, assignees mark work ready for review and only the final approver or an admin can close an item, so each status change has an author.

### Step 3, week 7: a new stain, next door

A new stain appears on the level 4 corridor ceiling, beside unit 402. It is logged as PL-131 and assigned to drywall again. **Decision, so far:** another finish defect. **Record:** a new punch item with its own photo.

### Step 4, week 7: the cosmetic repair is rejected and the source traced

The quality manager rejects a second cosmetic repair, links PL-131 to PL-118 and asks for a plumbing inspection of the unit above. The plumber finds a failed shower pan seal in unit 502, logged as PL-134 and linked to both. **Decision:** stop repeating the fix and find the cause. **Record:** the rejection with its reason, the links between items and the new plumbing item.

### Step 5, week 9: the real fix is tested

The shower pan is rebuilt and flood tested. **Decision:** prove the repair before touching the ceilings again. **Record:** the flood test result and photos attached to PL-134.

### Step 6, week 12: verified together

After a dry period, the ceilings are repaired once more, and the three items are inspected together and accepted by the owner's representative. **Decision:** accept only once the source is proven fixed. **Record:** the acceptance record naming all three items and the root cause.

## The fork at week 7: repeat the fix or find the cause

Everything useful in this case happens at step 4. Until then, the records describe two unrelated defects that each looked fixed. At week 7 the quality manager had two options.

| Option | What the records would show | Result |
|---|---|---|
| Repeat the cosmetic repair on PL-131 | Two closed drywall items, no link, no cause | A third stain later, probably after handover |
| Reject, link and trace the source | A rejection, three linked items, a plumbing finding, a flood test, one acceptance | The cause fixed and proven before handover |

The second path leaves a dated chain: the initial problem, the authorized action and the checked result. That chain is also commercially meaningful. On U.S. federal work, a contractor must correct nonconforming work without charge, and inspections do not imply acceptance; the warranty on repaired work runs one year from the date of repair. Private contracts set their own terms, but the logic is similar: a contractor that can show how a defect was traced and proven fixed is in a stronger position. This is general information, not legal advice.

## Why a reappearing defect is better evidence than a clean closeout

A punch list where every item closed first time shows that tasks were done. A case like this one shows reasoning under uncertainty: noticing a pattern across locations, overruling the obvious fix, sequencing trades and refusing acceptance until a test passed. For an AI developer studying how inspection and repair decisions are made, that sequence is far harder to find than a list of closed items. The live page on [construction punch lists](/data-types/construction-punch-list-process) explains a single item's loop; this case shows what happens when loops connect.

Whether a contractor's history holds such chains depends on habits: whether rejections were recorded with reasons, whether items were linked or simply re-created, and whether test records were attached to items. The [records across systems map](/guides/defect-closeout-verification-records-across-systems) covers where each piece usually lives.

## Recognizing linked-defect histories at a contractor

Ask the quality manager these questions and note only the answers. None requires opening an item.

1. When a repaired defect comes back, is the new item linked to the old one, reopened, or logged fresh?
2. Are rejected repairs recorded with a reason, or only as a status?
3. Are flood tests, pressure tests and similar checks attached to the item they prove?
4. Does the acceptance record list item numbers, or only state that the punch list was completed?
5. Roughly how many projects over how many years used the same inspection platform?

Mostly yes suggests a decision-rich history. The [Procore export page](/systems/procore-export-project-data) lists questions for that platform's administrator. The same pattern of linked exceptions turns up in freight, as the [logistics exceptions guide](/guides/how-to-identify-logistics-exceptions-and-their-documented-resolutions) shows, and post-handover callbacks extend it into [warranty claims](/data-types/warranty-claims-data).

## Qualification and what stays unknown

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 never collect photos, exports or logins; discovery stays at metadata level. Unknown until SourceX reviews the opportunity with the contractor: whether owner contracts give the building owner rights in these records, how photos showing residents 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, and the [referral brief template](/resources/defect-closeout-verification-referral-brief-template) turns the answers above into a note. Partners sign the Channel Partner Agreement before submitting introductions, 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 confirms that rejected repairs, linked items and test records were kept across many projects, [register as a partner](/register), check the contractor on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce it.

## Sources

- https://support.procore.com/faq/what-is-the-punch-list-work-flow
- https://www.acquisition.gov/far/52.246-12
- https://www.acquisition.gov/far/52.246-21
- https://refer.sourcex.si/terms
