TECHNICAL / CLOSE-OUT CONTROL
NCR Close-out & Punch Control
NCRs and punch items cause the most delays when close-out is unclear. MurphyEx links each finding to the tag, installed condition, evidence rules, and acceptance gate so items close once and stay closed.
What this system prevents
- “Closed” items that re-open during third-party inspection
- Late punch list growth caused by missing evidence
- Rework from poor categorisation (critical vs cosmetic)
- Interface gaps between Mechanical Completion and Ex acceptance
How it drives acceptance
- Defines clear evidence rules by finding type
- Aligns owners and due dates to acceptance gates
- Builds the close-out pack continuously with indexed evidence
- Forces traceability: tag → installed condition → register record
Purpose & Scope
Purpose
Create a repeatable close-out process for NCRs and punch items that survives inspection and supports predictable acceptance. Close-out is treated as a controlled process with defined evidence rules and verification steps.
Scope
Applies to Ex installation, hazardous area selection, certified equipment, documentation control, and close-out activities where acceptance depends on traceable evidence. Covers field findings, documentation gaps, certificate mismatches, installation non-conformances, and boundary issues.
Inputs & Outputs
Inputs
- HAER register (tags, zones, protection concepts)
- Inspection plan and hold/witness points
- NCR and punch list exports (open items, owners, due dates)
- Certificates, manufacturer data, and deviations
- Installation records (sealing, earthing, continuity)
- Installed evidence (photos, tag match, asset updates)
Outputs
- Close-out evidence rules by finding type
- Prioritised punch plan aligned to acceptance gates
- Verification log with recorded evidence
- Re-inspection schedule based on risk
- Inspection-ready close-out pack
- Acceptance readiness statement
Classification Rules
Define NCR vs Punch
Close-out fails when every issue is treated the same. Use NCRs for items that affect safety, compliance, certification, or acceptance. Use punch items for completion tasks that do not change the compliance condition.
Typical trigger errors
Misclassification creates wasted effort: punch items that later become NCRs, and NCRs that were simply missing documentation. Early classification and evidence rules prevent this.
| Class | Definition | Typical examples | Close-out requirement |
|---|---|---|---|
| Critical NCR | Affects safety, hazardous area compliance, certification validity, or creates an acceptance block. | Wrong equipment marking, incorrect protection concept, missing certificate conditions, installation mismatch, boundary violation. | Corrective action + verification evidence + re-inspection sign-off. Must link to register and dossier. |
| Major NCR | Likely to trigger rejection at inspection/close-out. | Gland/entry mismatch, sealing/threads not to condition, IP issue, documentation gaps that prevent traceability. | Evidence rules apply: corrective action + proof pack + targeted verification. |
| Punch Item | Controlled completion activity that does not change the compliance condition. | Label fixes, minor documentation tidy-up, non-critical photo capture, housekeeping. | Completion proof + spot verification. Escalate to NCR if compliance condition changes. |
Close-out Process
Capture & Classify
- Log finding with tag/location and photo reference
- Classify: critical, major, or punch
- Assign owner and due date aligned to gate
- Link to HAER / asset register
Define Close-out Evidence
- Define acceptable proof at issue, not after corrective work
- Set verification method (100%, sample, witness, hold point)
- Define re-inspection triggers
- Lock required documents
Execute & Verify
- Corrective action completed
- Evidence captured (photos, records)
- Verification performed and recorded
- Escalate if new mismatch found
Close & Package
- Close status only after evidence acceptance
- Update register and dossier references
- Prepare acceptance readiness statement
- Run final sampling and trend review
Hold Points & Acceptance Gates
Gate alignment
Each NCR or punch item must be tied to a defined gate: installation complete, inspection complete, dossier ready, mechanical completion boundary, or final sign-off. This prevents open items drifting into the last week of close-out.
When to stop the line
Stop-work or hold release decisions are based on classification and risk. Critical NCRs that affect the compliance condition cannot be deferred without formal disposition and acceptance by the responsible authority.
| Gate | What must be true | Typical blockers | Evidence expected |
|---|---|---|---|
| Inspection readiness | Registers aligned, prerequisites met, sampling logic set. | Missing tag data, unclear zones, incomplete certificates. | Register extracts, prerequisite checklist, inspection plan. |
| Close-out readiness | Open items classified and owned. Evidence rules defined. | Unclassified punch list, ambiguous close-out, missing evidence discipline. | Open items log, close-out rule set, verification plan. |
| Acceptance / handover | Critical and major NCRs closed with proof. Dossier pack reviewable. | “Closed” without evidence, certificate mismatches, missing cross references. | Dossier-ready pack, signed verification log, acceptance readiness statement. |
Evidence Rules
Evidence must be reviewable
Evidence is not a photo dump. It must be tagged, attributable, and linked to the correct asset and register entry. If it cannot be located quickly, it will not survive external review.
Evidence must match the compliance conditions
A close-out pack must demonstrate that compliance conditions are met: correct equipment selection, valid certification, correct installation, and complete documentation.
| Finding type | Minimum close-out evidence | Verification approach |
|---|---|---|
| Certificate / marking mismatch | Correct certificate set, selection justification, tag/register update, and photo of nameplate/marking. | 100% for critical assets; targeted sampling for repetitive minor issues. |
| Installation detail non-conformance | Corrective work record, photo before/after, method compliance, and verification sign-off. | Witness for critical; sample plus escalation for repetitive patterns. |
| Traceability / documentation gap | Document added/linked, register reference, pack index update, and reviewer check confirmation. | Spot checks against register extracts; trend review to prevent recurrence. |
| Boundary / interface discrepancy | Scope clarification, responsible party acceptance, updated drawings/register mapping, and agreed disposition. | Hold point until disposition is accepted; verify implementation evidence at close-out. |
Roles & Ownership
Owner’s representative (acceptance authority)
Defines acceptance thresholds and confirms which items block sign-off. Approves dispositions for critical NCRs and ensures close-out evidence is indexed and packaged.
Site execution (contractor / installation)
Executes corrective actions and captures required proof. Must follow close-out evidence rules and update records so verification is possible without rework.
Inspection / verification function
Verifies close-out against defined rules. Records what was checked, what evidence was accepted, and what sampling logic was applied.
MurphyEx (close-out system & evidence control)
Builds the close-out process, aligns it to HAER control, defines evidence rules, runs trend reviews, and produces inspection-ready close-out packs.
Common Failure Modes
Closed status without evidence
The number one reason items re-open: a closed status recorded before proof is reviewable, indexed, linked, and verified.
Late classification
Treating a mixed punch list as a single bucket until late-stage review guarantees surprises.
Interface drift
Boundaries between mechanical completion, QA packs, and hazardous area acceptance are not explicit.
Rework cycles from trend blindness
Repeating the same defect pattern without trend controls.
FAQs
What does “closed” mean in practice?
Closed means the corrective action is complete, the evidence is captured and reviewable, the verification is recorded, and the register and dossier links are updated. If any of those are missing, the item is worked but not closed out.
How do you stop punch lists exploding at the end?
Classify early, align each item to an acceptance gate, define close-out evidence rules immediately, and run weekly trend reviews. Items are indexed into the close-out pack continuously.
Do we need to re-inspect everything after corrective work?
Not always. Use risk-based verification: 100% for critical assets and high-consequence failure modes, targeted sampling for repetitive minor issues.
How does this link back to HAER?
Each finding is tied to the relevant tag and register entry. Close-out updates the register and references indexed evidence within the close-out pack.