Fixture counts get rejected in procurement review for one reason more often than any other: the math exists somewhere in the design file but never made it into the submittal as a standalone, traceable document. Approval authorities do not want to dig through an engineer’s calc sheet. They want a line item that states the passenger load assumption, the code table used, the ratio applied, and the resulting fixture count, with a signature attached. Build that document first and the fixture schedule defends itself.

Why Throughput Needs a Paper Trail

A terminal restroom fixture count is a code compliance item and a budget item at the same time. Procurement teams get questioned on both fronts: auditors want to see that the count meets or exceeds code minimums, and finance wants to see why the count isn’t lower. Without a documented throughput calculation sitting in the submittal package, neither question has a defensible answer. The calculation itself is not complicated. What’s missing in most rejected packages is the chain of custody showing where the passenger number came from, which code table converted it to fixtures, and who approved any departure from the table minimum.

Treat the throughput justification as its own exhibit, not a footnote in the mechanical narrative. It should be a single page or two that a reviewer can read without opening the architectural drawings.

Peak-Hour Passenger Loads as Spec Inputs

The number that drives everything downstream is peak-hour passenger load, usually expressed as enplaned and deplaned passengers during the design hour, not daily or annual totals. Airport design teams typically pull this from the terminal’s master plan or FAA Advisory Circular guidance on terminal planning, and it gets refined by concourse, by gate cluster, or by security checkpoint zone depending on how granular the restroom siting is.

For procurement documentation, record this figure explicitly and cite its source document by name and date. A typical entry looks like: “Design peak-hour load, Concourse B, 1,450 passengers (Terminal Area Forecast Update, FY2024).” That single line is what lets a reviewer trace the fixture count back to something other than an assumption. If the passenger load gets revised during the project, that revision has to cascade into the fixture calc and the procurement line item has to be reissued. Treat the passenger number as a spec input with the same version control as a drawing revision.

IPC and UPC Fixture Count Tables

Once the passenger load is set, the applicable plumbing code table converts occupant load into required fixture counts. Most US airport projects fall under either the International Plumbing Code or the Uniform Plumbing Code depending on the jurisdiction, and the relevant reference is IPC Table 403.1 or the equivalent UPC fixture count table. These tables assign minimum water closets, lavatories, and urinals per occupant load, broken out by occupancy classification and sometimes by sex-specific or all-gender fixture ratios.

Airport terminals are typically classified under assembly or mercantile occupancy depending on the code edition and local amendment, and some jurisdictions have adopted airport-specific ratios that are stricter than the base table because of the public assembly nature of security queues and gate-hold areas. Confirm which occupancy classification the local authority has assigned to the terminal space before pulling numbers from the table, because using the wrong occupancy row is the single most common error in these calculations.

Turning Ratios Into Procurement Line Items

The code table gives a minimum count, not a purchase order. Procurement needs that minimum translated into a line item that states fixture type, quantity, and the calculation that produced the quantity, formatted the same way the rest of the submittal is formatted. A reviewer should be able to open the fixture schedule and see, for each restroom, the occupant load assigned to it, the table-derived minimum, and the specified count, with any difference between minimum and specified explained in one sentence.

This is also where fixture selection gets tied to the throughput number instead of floating as a separate design decision. If the calculation shows six lavatories required for a given restroom, the procurement package should carry six units of whatever commercial bathroom faucets have been specified for that location, not five with a note that a sixth is “pending.” Partial compliance on paper invites a rejection, even if the physical installation is scheduled to catch up. Keep the line item count and the calculated minimum identical unless a deviation has been formally logged.

Documenting Deviations From Code Minimums

Fixture counts below the code-calculated minimum are sometimes justified, usually because the design team has data showing actual usage patterns differ from the generic occupancy assumptions baked into the code table, or because an alternate compliance path has been negotiated with the authority having jurisdiction. Whatever the reason, a lower-than-minimum count cannot sit in the fixture schedule without a companion deviation record.

That record should include the code section being varied from, the engineering or operational justification, and the signature of the AHJ representative who accepted the variance. Procurement should never accept a fixture count below the table minimum on the basis of a verbal agreement or an email thread. If the variance isn’t in a signed document, the fixture schedule has to default to the code minimum until it is.

• Cite the specific code section or table row being varied from, not just “code minimum.”
• State the justification in operational terms (actual observed usage, alternate fixture type, phased occupancy) rather than budget terms.
• Attach the AHJ’s written acceptance, dated and signed, not a meeting summary referencing a verbal okay.
• Cross-reference the deviation memo number directly in the fixture schedule line item it affects.

Filing Throughput Proof With Submittals

The throughput exhibit, the code basis statement, and any deviation memos should be bound into the submittal package as a labeled section, not scattered across engineering appendices. Reviewers approving large terminal procurement packages are working through dozens of exhibits, and a throughput calculation that isn’t where they expect it gets flagged as missing even when it exists somewhere in the file structure.

Name the section consistently across projects (something like “Fixture Count Basis of Design”) so that repeat reviewers at the same airport authority know where to look. Include a one-line summary table at the front of that section listing each restroom, its occupant load, its code-required minimum, and its specified count, with deviations flagged. That summary table is usually the only page a reviewer reads in detail; the supporting documents behind it exist to answer follow-up questions, not to be read cover to cover on first pass.

Before submitting, confirm three things: the passenger load figure matches the current terminal forecast on file with the authority, the code table citation matches the edition currently adopted by the jurisdiction, and every fixture count in the schedule either meets the table minimum or carries a signed deviation memo. If any of those three don’t check out, fix the paperwork before the package goes in, because a rejected fixture count delays the entire procurement cycle, not just the restroom line item.