How Do Scaftra's Punch Lists Work?

How do you make sure every snag from the walkthrough gets fixed before final payment?

Scaftra tracks each punch item as a record assigned to a responsible party with a due date and a status, and gates a sub's punch resolution to their own assigned items.

The problem it solves

Every finish-trade job ends with a punch list: the snags, scratches, miscuts, and missing trim the client wants fixed before they sign off. Each defect has to be assigned to a responsible party with a due date so nothing falls through the cracks before final payment. A punch list on a clipboard or in an email loses track of who owns what and what is still open.

Why it matters

The punch list stands between installed and accepted. If a defect is not assigned and tracked, it gets missed, and a missed punch item holds up final payment or, worse, gets discovered after sign-off. Assigning each item to the right party with a due date and a status is how the walkthrough turns into completed fixes instead of a list nobody owns.

Common mistakes

How it works

1. Create the punch item

   Each defect is recorded with its room, trade, description, location, priority, an assignee, and a due date.
2. Assign the responsible party

   The item is assigned to the party who owns the fix, so accountability is clear.
3. The assignee works it

   A subcontractor resolves items assigned to their own team from the sub portal, with each action logged.
4. Track to closed

   The item moves through its status so a project manager sees what is still open before sign-off.

How Scaftra does it

Scaftra tracks the Punch List Item as a record per defect: project, optional room and trade, description, location, category, priority, an assignee with a due date, and a status that moves from open through resolved, completed, verified, and closed. It carries up to ten attachments for before and after photos. A subcontractor assigned a punch item works it from the sub portal, and resolution is gated to the assigned sub's own users, so a sub cannot close another vendor's defects. The company is stamped server-side from the session, never trusted from the payload. One honest gap: punch resolution does not require a photo; proof upload is a separate, optional step. This is built and live.

Key capabilities

• Assigned defects with due dates: Each punch item carries an owner and a due date, so nothing is left unowned.
• Sub-scoped resolution: A sub can only resolve punch items assigned to their own team, not another vendor's.
• Status tracking to closed: Items move through open, resolved, verified, and closed, so the PM sees what is open.
• Before and after photos: Each item holds up to ten attachments for proof of the fix, though resolution does not force one.

Benefits

• Every snag from the walkthrough has a clear owner and a due date.
• A sub can only close their own items, so accountability stays clean.
• The PM sees what is still open before authorizing final payment.

Who it's for

• Project managers.PMs running the closeout walkthrough who need every defect assigned and tracked.
• Subcontractors.Subs who resolve their own assigned punch items from the sub portal.

Related on Scaftra

Go deeper