7.2 Multi-Review Programs & PQA Best Practices

Overview

Large suppliers and general contractors often run structured, recurring Quality Review programs across multiple regions, crews, and subcontractors. Pathwave supports these workflows through scheduled reviews, standardized rejection reasons, consistent reviewer protocols, and real-time communication with field teams.

This article outlines best practices for running Picture Quality Audits (PQAs), coordinating multiple review teams, and ensuring scalability across high-volume photo programs.

---

1. Understanding PQAs in Pathwave

Many suppliers use Pathwave to perform PQAs (Picture Quality Audits)—formal quality checks that run in parallel with field activity.

Typical PQA Characteristics

• A review is created while crews are actively in the field
• Reviewers monitor live photo capture
• Corrections are requested in real time
• Subcontractor performance is tracked across multiple jobs
• Photos feed directly into customer deliverables (e.g., AT&T COPs)

Pathwave’s real-time review tools enable rapid audit cycles, uniform review practices, and program-level visibility across all participating teams.

---

2. Use Scheduled Reviews for Multi-Team Programs

For high-volume programs or multi-region operations:

Scheduling a review is strongly recommended.

Scheduled reviews help:

• Assign specific reviewers to specific jobs
• Provide visibility to program managers
• Ensure subcontractors understand review expectations 
• Create predictable, repeatable auditing cycles

Scheduling does not lock the review; it simply structures expectations across a large stakeholder group.

---

3. Standardize Rejection Reasons Across All Reviewers

Consistent rejection categories enable:

• Uniform feedback across teams
• Cleaner reporting in Pathwave
• Better training data for subcontractors
• Faster corrective cycles

Configuration Path for Admins:

Configuration → Quality Review Rejection Reasons

Partners should review and update these categories periodically to support program-level requirements.

---

4. Assign Defined Reviewers for Each Region or Project

In multi-review environments, designate clear reviewer ownership:

• By region
• By customer (AT&T, Crown Castle, internal programs, etc.)
• By project type (Small Cell, Macro, Rooftops, DAS, P&I)
• By supplier/subcontractor group
• By photo list or SOW type

This ensures consistency in quality expectations and reduces conflicting instructions to the field.

---

5. Monitor Reviewer Activity Through the Quality Review Dashboard

For PQA or multi-review programs, use the dashboard to:

• Track reviews by status (New, In Progress, Completed, Canceled)
• Identify reviews lagging behind field activity
• Monitor subcontractor responsiveness
• Track reviewer workloads
• Export reports for customer or internal oversight

High-performing programs use this dashboard daily.

---

6. Use “View N/A” to Validate Subcontractor Accuracy

In large programs, subcontractors may incorrectly mark items N/A.

Reviewers should:

• Regularly check the View N/A section
• Validate whether each N/A is legitimate
• Remove incorrect N/As to trigger the correct photo capture
• Log subcontractor accuracy trends for performance scoring

This ensures complete documentation and supports supplier accountability.

---

7. Enforce the Correct Re-Take Workflow

In large programs, avoid bad data by ensuring field personnel always use Re-Take when responding to rejections.

Why it matters:

• Guarantees linkages remain intact
• Ensures reviewers see replacements in Resubmitted Photos
• Supports subcontractor scoring
• Prevents missing or orphaned photos in reports
• Keeps review timelines consistent

---

8. Consider Smaller Targeted Reviews for Issue-Specific PQAs

Instead of reviewing the entire photo list:

Use Targeted Reviews when:

• Auditing specific steps of construction
• Reviewing a subcontractor’s weak areas
• Monitoring remediation of a specific issue type
• Performing follow-up checks after repeated rejections

This keeps reviews focused, faster, and easier to manage for large teams.

---

9. Maintain Clear Communication Protocols Across Reviewers

In multi-review programs:

• All comments must be professional and actionable
• Markup should clearly highlight required corrections
• Messages should remain tied to the photo (never external threads)
• Reviewers should align on acceptance standards and interpretation of SOWs

Consistency is essential to maintaining high-quality deliverables.

---

10. Export Review Reports for Supplier and Subcontractor Accountability

Exports can be used to:

• Provide subcontractor performance feedback
• Document customer-facing audit activity
• Support internal QA programs
• Track repeated rejection categories
• Surface trends for operational improvement

Exports may be produced at:

• The review level
• The dashboard level (all reviews)

This supports both job-specific and program-wide analytics.

---

Why These Practices Matter

Effective multi-review and PQA operations lead to:

• Faster job closeouts
• Higher-quality deliverables
• Stronger subcontractor performance
• Better customer audit outcomes
• Predictable workflows across all teams
• Accountability and traceability at scale

Pathwave is built to support these large, complex photo programs—and these practices ensure your teams get maximum value with minimal rework.