punch list with photos template

Project Deficiency and Remediation Documentation Protocol

Document Control

• Document ID: SOP-QA-00[__]
• Version: [].[]
• Effective Date: [YYYY-MM-DD]
• Review Cycle: [__] Months

1. Purpose & Scope

This procedure establishes a standardized method for identifying, documenting, and tracking construction or project deficiencies. It applies to all [Project Name] stakeholders responsible for site inspections, quality control, and final closeout. The objective is to ensure clear visual evidence and actionable data for rapid resolution of outstanding items.

2. Prerequisites

• Access to [Project Management Software/Platform Name]
• Mobile device with minimum [__] Megapixel camera resolution
• High-visibility safety vest and required PPE for [Project Site Name]
• Access credentials for [Cloud Storage Folder/Server]
• Digital measuring device (laser measure or tape)

3. Roles & Responsibilities

4. Step-by-Step Procedure

Phase 1: Site Inspection and Data Collection

• Verify location using [Floor Plan/Grid Reference].
• Capture a wide-angle orientation photo to provide context of the room/area.
• Capture a close-up photo of the deficiency with a reference object (e.g., coin or ruler) for scale.
• Annotate the photo with a digital marker indicating the exact point of failure.
• Record the specific location coordinate: [__________].

Phase 2: Documentation and Logging

• Open the digital ledger at [Project URL/Link].
• Assign a unique identifier: [DEF-####].
• Select the trade responsible: [__________].
• Set priority level: [Low/Medium/High/Critical].
• Upload photos to the designated cloud directory: [__________].
• Input the required corrective action: [__________].

Phase 3: Verification and Closure

• Notify the responsible party via [Communication Channel].
• Upon notice of completion, perform a site revisit.
• Capture "After" photos from the exact angle/distance as the "Before" photos.
• Verify the work meets [Standard/Code Reference].
• Update status to "Closed" and archive the record.

5. Quality Assurance, Pro-Tips, and Common Pitfalls

• Pro-Tip: Always use a consistent naming convention for files: [Date]_[Location]_[DeficiencyType].jpg.
• Pro-Tip: Use a stylus on your tablet to draw directly on photos while standing in front of the issue.
• Common Pitfall: Failing to include a scale reference in close-up photos, making it impossible to judge the severity of gaps or cracks.
• Common Pitfall: Vague descriptions like "Fix wall" instead of "Repair drywall corner bead at Grid Line A-4."

6. FAQs

Q: How many photos are required per item? A: A minimum of two: one wide shot for spatial context and one close-up shot for technical detail.

Q: What should I do if the responsible subcontractor is unclear? A: Flag the item as "Pending Assignment" and escalate it to the [Project Manager/Superintendent] for immediate classification.

Q: Can I use a personal phone for documentation? A: Only if the device is synced to the [Company Name] secure cloud environment and complies with the BYOD policy.