Skip to content
English
Sign in
Go to pathwave.com
  • There are no suggestions because the search field is empty.

5.4 Managing N/A Photo Requirements (Mobile App)

How field teams mark photos as Not Applicable (N/A) from the field.

Overview

Not every photo requirement applies to every job. Differences in site structure, equipment types, customer requirements, and project scope may make certain items irrelevant. Pathwave provides a clear, consistent way to manage these scenarios through the Mark as N/A feature.

Both the field app and the portal allow users to mark photo list items as N/A. During a Quality Review, reviewers can validate all N/A selections to ensure accuracy before completing the review.

This keeps photo lists clean, prevents unnecessary corrective actions, and ensures documentation aligns with the actual job conditions.

Marking a Photo N/A from the Field App

Field crews can mark requirements as N/A directly from the mobile app while working through a photo list.

This is valuable when:

  • Certain equipment is not present
  • A requirement does not apply to the specific job variant
  • A customer-required item is irrelevant for this site
  • Conditions onsite differ from the expected configuration

  IMG_7102  IMG_7103  IMG_7104

Marking items N/A prevents field teams from being blocked on items that do not apply.

 

 

When N/A Should Be Used

N/A should be applied when:

  • The photo requirement does not apply to the job’s scope
  • The equipment referenced is not present
  • The job uses a different configuration than what the photo list anticipated
  • The customer or site owner does not require this item for this project
  • Optional items do not apply to this site
  • Regional variations make certain photos irrelevant

When N/A Should Not Be Used

N/A should not be used when:

  • A photo should exist but was not captured
  • The requirement applies but cannot be captured due to poor conditions
  • The field crew is unsure how to capture the photo
  • The photo was submitted incorrectly (should be rejected, not N/A)
  • Documentation is still required by the customer or site owner

In these cases, N/A hides required documentation and will cause issues downstream.

Benefits of Managing N/A Correctly

Correct N/A usage leads to:

  • Cleaner, more accurate photo lists
  • Faster reviews with fewer unnecessary items
  • Reduced field frustration
  • Higher-quality closeout packages
  • Accurate deliverables for customers and site owners
  • More predictable PQA outcomes
  • Stronger differentiation between “not applicable” and “not completed” work