Punchlist Management

Punch as an activity type on the live completions workflow — not a separate punch register.

Snagging belongs on the tag, with evidence, an owner, and a status the gateway can see. Punch List is a seeded activity type. Severity is labels or attributes you configure — Cat-A, Cat-B — and readiness rules can block certification sign-off while Category A items remain open in scope.

There is no second punch table. Raise from the field or from a blocked gate’s readiness panel. Assign into My Work. Export the same list from Data Hub. Discipline filters stop an electrical snag blocking an unrelated mechanical gate when you configure scope that way.

Snag on the tag, hold the gate

A punch that cannot stop MC-1 is just a note. Readiness treats open punches as blockers when the matcher and severity say so. Clear the item, attach the evidence, and the gate can move. That is punchlist management inside completions, not beside it.

Punchlists Work Space table listing punch activities PL-1, PL-2, and PL-3 — Punchlists — the same activity list as ITRs, not a sidecar register.

Punchlists — the same activity list as ITRs, not a sidecar register.

The punch is an activity

Open a punch and you get the same panel as any other Work Space item: status, target, evidence, and sign-off. Raise from field or desktop; assign into My Work; export from Data Hub. Category and blocking rules are labels and readiness, not a second table.

Punch activity panel for PL-3 showing Ready to sign on the same activity engine as ITRs — PL-3 — Ready to sign on the same activity engine. Punch blockers show here when they exist.

PL-3 — Ready to sign on the same activity engine. Punch blockers show here when they exist.

What it does

✓Raise punch items as Punch List activities against tags, systems, or documents
✓Classify severity with labels or attributes — Cat-A and Cat-B are the usual pattern
✓Block certification sign-off when Category A punches remain open in scope
✓Capture photo and video evidence at raise or on steps
✓Assign punches into the same My Work queue as ITR and cert work
✓Raise a related issue from a gate that is blocked on open punches
✓Filter and export punch activities by type, label, status, and target
✓Tie punches to subsystems and disciplines so scope stays honest
✓Use the same hierarchical activity model as preservation, queries, and NCRs
✓Offline field capture with desktop oversight on the same record

Highlights

• Punch blocking is readiness logic, not a spreadsheet sidecar
• One activity list, one audit trail — no duplicate punch register
• Field and desktop share the record
• Label conventions are project-configured

Demo

Demo video coming soon

See the rest of the platform, or talk to us about a demo.

All solutions Request a demo