How the code is organized and how to find a requirement

On Maya's second day, Luis handed her a question instead of a task. "The engineer shows a 75 millimeter stack serving six suites of kitchen sinks on the east side. The inspector asked whether that is big enough. Find me the rule." Maya opened the code book and stared at the table of contents. She knew the answer was in there somewhere, but the book had hundreds of pages, and she did not know where to start. By the end of the day she had found it, but it took her three hours. Luis said that with practice it would take three minutes.

This lesson is about those three minutes. Finding a requirement quickly and correctly is a skill, and like any skill it depends on knowing the layout of the tool. A plumber who knows how the code is organized can go straight to the right section, find the right table and check whether there are exceptions or notes that change the answer.

The big picture: what is in a plumbing code

Every plumbing code, whatever its origin, covers roughly the same ground. It starts with administration and definitions, then sets general rules that apply everywhere, then works through the systems one at a time: fixtures, water heaters, water supply, drainage, venting, traps and interceptors, storm water and special systems. At the back are lists of referenced standards and appendices with explanatory material. Once you know that order, you can guess where a rule lives before you open the book.

The International Plumbing Code is divided into chapters. Chapter 1 covers scope and administration, Chapter 2 definitions and Chapter 3 general regulations. The technical chapters follow in a logical order: fixtures, faucets and fixture fittings; water heaters; water supply and distribution; sanitary drainage; indirect and special waste; vents; traps, interceptors and separators; storm drainage; special piping and storage systems; and nonpotable water systems. A chapter of referenced standards and several appendices come at the end. The Ohio Plumbing Code keeps the IPC's chapter structure, with Ohio changes.

The UPC covers the same subjects in a similar order but numbers its chapters differently and includes chapters the IPC leaves to other codes, such as fuel gas piping. A plumber who moves from an IPC state to a UPC state finds most of the technical ideas the same, but has to learn where each rule lives and watch for the places where the two codes give different answers.

Reading a code reference

Every requirement in the IPC has a section number that works like an address. A number such as 704.1 means Chapter 7, Section 704, subsection 1. Deeper levels add more digits, such as 704.1.1, and lists inside a section use numbered items. When an inspector cites a rule, the number tells you exactly where to look. When you write a note or an email about a code question, always give the section number and the code edition so the reader can check it.

The structure also tells you something about how the rule relates to its neighbors. A requirement deep inside a subsection usually depends on the general statement above it. If the general statement says it applies only to certain buildings or certain piping, so does everything under it. Reading only the detailed line and skipping its parent is one of the most common ways to get a code question wrong.

The article and section numbers in this course are given to show how references work and where kinds of rules live. Numbers can move between editions, so always check the edition that applies to your job before quoting one.

Three ways into the code

There are three main ways to find a rule, and experienced plumbers use all three.

• The table of contents. Use it when you know which system the question is about. A question about stack sizing belongs in drainage; a question about vent pipe size belongs in venting. Go to the right section and scan its headings.
• The index. Use it when you know the topic but not where the code puts it. Look up a specific word, such as cleanout, interceptor or hose bibb, and follow the references. If the first word does not work, try a synonym.
• Search in an electronic copy. Many plumbers now use digital codes. Search is fast, but it finds words, not meaning. A search for "stack" returns hundreds of hits; a search for the exact phrase used in a heading is better. Search results also pull lines out of context, so always read the surrounding requirement.

Luis's advice was to start with the table of contents, because it forces you to think about which system the question belongs to. Many wrong answers come from finding a rule that sounds right but sits in the wrong section, such as a water supply sizing table used for a drain.

Tables, notes and footnotes

Much of the technical content of a plumbing code is in tables: fixture unit values, pipe sizes, slopes, vent lengths, minimum fixture counts and so on. Tables pack a lot of information into a small space, and they are easy to misread. Before using a table, read its title and any notes under it. The notes often limit when the table applies or change values for particular cases.

• Check the units. A table may give sizes in millimeters, inches or both, and lengths in meters or feet.
• Check what the numbers mean. A fixture unit value for drainage is not the same as a fixture unit value for water supply.
• Check the columns and rows carefully. Run a ruler or finger along the row, especially in wide tables.
• Read every note. Notes can say that a value applies only to horizontal pipes, only to certain fixtures or only above a certain height.
• Look for the requirement that sends you to the table. The table is part of a rule, and the rule may add conditions.

The IPC also contains appendices and commentary is published separately. Appendices are not enforceable unless the adopting government specifically adopts them, and the commentary explains the intent but is not part of the code. They are very useful for understanding a rule, but an inspector enforces the adopted requirement itself.

Finding Maya's stack rule

Luis made Maya walk through her stack question again so she could see the path an experienced plumber would take.

First, decide the system: a stack carrying kitchen sink waste is part of the sanitary drainage system, so the answer is in Chapter 7. Second, find the section on sizing: the table of contents lists a section on the size of drainage piping and fixture unit loads. Third, read the general requirement, which says how to add up drainage fixture units and refers to a table of maximum loads for stacks and branches. Fourth, read the table and its notes. Fifth, check for special rules, such as limits on the load from a single branch interval and rules for offsets, and check the Ohio amendments for changes.

Doing it in that order took Maya about ten minutes the second time. The answer was that the stack was big enough for the load the engineer had shown, but only because the kitchen sinks entered through branches that met the code's rules. If a branch had been undersized, the stack size alone would not have saved it.

The program below shows the logic of looking up a size in a table: find the smallest size whose capacity is at least the load. It uses a simplified practice table, not the code's values, so that the method is clear.

# Look up the smallest stack size that carries a given load (practice table only)
practice_table = [   # (size in inches, maximum drainage fixture units on the stack)
    (2, 10), (3, 30), (4, 240), (5, 540), (6, 960)]

def smallest_size(load, table):
    for size, capacity in table:
        if load <= capacity:
            return size
    return None

for load in (8, 18, 30, 31, 200, 1000):
    size = smallest_size(load, practice_table)
    print(f"load {load:5d} fixture units -> {str(size) + ' in' if size else 'beyond table'}")

load     8 fixture units -> 2 in
load    18 fixture units -> 3 in
load    30 fixture units -> 3 in
load    31 fixture units -> 4 in
load   200 fixture units -> 4 in
load  1000 fixture units -> beyond table

The numbers in the practice table are made up for teaching. Always take values from the adopted code for the job.

Exceptions and the word "except"

Many requirements contain exceptions, often written as a separate paragraph headed "Exception" or introduced by the words "except as provided in" followed by another section number. An exception can say that a rule does not apply in a certain case, or that a different rule applies instead. When a requirement sends you elsewhere, follow the reference and read it before deciding. A plumber who reads only the first part can install something the code allows only in a narrow case, or miss a relaxation that would have saved money.

Maya started keeping a small notebook of rules she had looked up, with the reference and a one-line summary in her own words. Luis approved. Writing the summary forced her to understand the rule, and the notebook became a quick index to the parts of the code she used most.

Other documents that act like code

The plumbing code is not the only document that controls plumbing work on a building. A plumber also has to know when to look elsewhere.

Other codes: the International Building Code contains accessibility references and fire-resistance rules for pipes passing through rated assemblies, and the Ohio Building Code adopts it with amendments. The fuel gas code, the mechanical code, the energy code and the electrical code also affect plumbing work, such as fire stopping, insulation and bonding of water piping.

• Referenced standards: when the code says a backflow preventer must be tested, or a water heater installed, to a particular standard, that standard's requirements apply.
• Manufacturers' installation instructions: codes usually require products to be installed according to the manufacturer's instructions, which makes those instructions enforceable.
• Local rules: sewer-use and water utility rules, and the engineer's specification for the project.

Luis summed it up: the plumbing code is the center, but not the whole picture. When a question touches fire separations, accessibility, electrical bonding or the city's sewer, check whether another document governs.