Plumbing Plan Review: Verifying Design on Paper
The Reviewer's Mindset
Plan review is a systematic comparison between submitted documents and code requirements before construction begins. A candidate must know what a complete submittal contains: floor plans showing fixture locations, riser diagrams, isometric or schematic drawings, fixture schedules, pipe sizing calculations, water supply and drainage calculations, venting layout, and manufacturer cut sheets for special devices. Reviewers check completeness first, then compliance, then coordination with structural and architectural drawings.
Concepts You Must Understand
Know how to verify drainage sizing by fixture units and slope, vent sizing and vent terminal locations relative to openings, water distribution sizing and available pressure, backflow protection at the service connection, and fixture clearance and accessibility. Understand that a plan review approval does not guarantee field compliance; it confirms the design intent meets code. Reviewers also check that the drawings show testable and maintainable installations, such as accessible cleanouts and valves.
Typical Traps
- Approving a plan that lacks sizing calculations because the layout "looks right."
- Missing that a fixture schedule conflicts with the floor plan.
- Overlooking a vent terminating too close to an operable window or air intake.
- Failing to check that the water service has required backflow protection.
- Confusing plan review approval with a certificate of occupancy or final inspection.
Rule of Thumb and Worked Example
Rule of thumb: review in a fixed order: completeness, then drainage, then venting, then water supply, then special devices, then coordination. Example: a submittal shows a bathroom group but no vent routing. Rather than approving the drainage layout, the reviewer notes the missing vent design, requests a revised riser diagram showing vent connections and the vent terminal location, and confirms the terminal meets distance requirements from openings. The correction notice should cite the specific code section and describe the required fix, not just say "revise."