From the journal

Blog

Faucet Tags That Still Make Sense at Closeout

PRZ Coming Soon: image pending

Name the fixture tag so it carries flow rate, finish, and governing standard in one string, and keep that string identical across the CD set, the submittal log, substitution requests, and the O&M manual. A tag like FCT-01-BRZ-1.5GPM does that. Most tags fail not because nobody thought about naming, but because the four documents that reference the tag are produced by four different people on four different schedules, and nobody owns the string.

Why Fixture Tags Break After Bid

The architect sets the tag in the fixture schedule during CD production. The contractor’s buyer re-keys it into a submittal transmittal, often shortened to fit a spreadsheet column. The rep writes a substitution request using the manufacturer’s SKU, which may bear no relation to your tag at all. By closeout, the O&M binder references a model number that nobody can trace back to the room it’s installed in without opening three PDFs.

This isn’t a discipline problem. It’s a structural one: the tag has to survive translation across people who don’t share your drawing set and don’t care about your naming logic. A tag that only makes sense next to the fixture schedule it was written in will not survive a submittal cycle.

Where the Thread Actually Snaps

  • Bid set uses “Lav Faucet Type 2,” addendum changes it to “Lav Faucet Type 2A,” and the submittal log still shows Type 2.
  • Contractor’s RFI references “the bronze faucet in the schedule” because the alphanumeric tag got dropped from a cut sheet.
  • Substitution request lists a competitor’s model number with no cross-reference to your tag, so the reviewer has to reverse-engineer which schedule line it replaces.
  • O&M manual is organized by manufacturer catalog section, not by room or tag, so facilities can’t match a service call to a document.

Four Documents, Four Different Names

Every faucet on a project gets named at least four times before occupancy. If the tag isn’t fixed early and referenced verbatim each time, you get drift.

Document Who writes it Common failure
Fixture schedule (CDs) Architect/spec writer Tag changed in a later addendum without updating all sheet references
Submittal transmittal Contractor/supplier Tag truncated or replaced with manufacturer SKU
Substitution request Contractor on behalf of sub No cross-reference to original tag, only proposed product data
O&M manual Contractor/closeout coordinator Organized by catalog section instead of by tag or room

The fix isn’t a new document. It’s requiring the tag string to appear, unmodified, in all four. Spec Section 22 42 00 (Commercial Plumbing Fixtures, under CSI MasterFormat) is the right place to state this as a submittal requirement rather than leaving it to habit.

Encoding Flow Rate and Finish in the Tag

A tag that only identifies fixture type and location (FCT-01) forces anyone downstream to open a cut sheet to find flow rate or finish. Build those into the string instead. FCT-01-BRZ-1.5GPM tells a reviewer the fixture type, finish, and flow rate without opening a second document. If your firm issues metric sets or works with a client who expects LPM, carry both: FCT-01-BRZ-1.5GPM-5.7LPM.

Flow rate matters enough to earn a place in the tag because it’s the number most likely to get substituted quietly. A contractor swapping in a value-engineered faucet may keep the finish and body style close enough to pass a glance, but drop the flow rate half a gallon per minute. If the rate is in the tag, that discrepancy shows up in the submittal log instead of in a commissioning report six months later.

  • Finish code: use a short, consistent abbreviation (BRZ, CHR, BLK, PN) and define it once in the schedule legend.
  • Flow rate: state in GPM, and add LPM if the project has any international design, ownership, or certification reporting involved.
  • Governing standard: note ASME A112.18.1 in the schedule notes as the mark that governs faucet performance and construction, since that’s what a submittal reviewer checks against, not the tag itself.

Tags That Survive a Substitution Request

Substitution requests are where tags most often get orphaned. The sub proposes a different manufacturer, submits that manufacturer’s data sheet, and the transmittal references the new SKU instead of your tag. The reviewer then has to reconstruct which schedule line is under discussion.

Require, in the spec section, that every substitution request cite the original tag string verbatim in the subject line and body of the request, alongside the proposed replacement’s model number. This is a one-line addition to your submittal procedures paragraph, but it’s the difference between a reviewer approving a swap in five minutes and spending twenty minutes cross-referencing schedules.

If the substitution changes flow rate or finish, the tag should flag that explicitly rather than let it get buried in a cut sheet. For finish-driven substitutions specifically, the comparison is usually straightforward: a reviewer checking a proposed swap against, say, black basin faucets from an alternate manufacturer can confirm finish match fast if the original tag already states BLK rather than a vague “dark bronze” descriptor that leaves room for interpretation.

What Facilities Teams Need in O&M Files

Facilities staff don’t open an O&M manual to read about the project. They open it because a faucet is leaking in Room 214 and they need a part number, fast. If the O&M manual is organized by manufacturer catalog section, they’re searching blind. If it’s organized by tag, and the tag matches a wall-mounted equipment list or room-by-room index, they find it in one lookup.

At closeout, require that the O&M table of contents cross-reference each tag to its room number and to the original fixture schedule line. This is a half-page addition to the closeout submittal but it’s the single most-used page in the binder for the life of the building.

A Reusable Tag Format for Schedules

A tag format that works across projects needs four fields, in a fixed order, with a legend defined once per schedule:

  • Fixture type code (FCT for faucet, LAV for lavatory, etc.) plus a sequential number.
  • Finish abbreviation, consistent across the project and ideally across your firm’s template.
  • Flow rate in GPM, with LPM appended where the project requires it.
  • Optional suffix for ADA-compliant units or special mounting, if your project has enough variants to need it.

Example: FCT-01-BRZ-1.5GPM-5.7LPM-ADA. It’s longer than a bare schedule number, but every field answers a question a submittal reviewer, contractor, or facilities tech will actually ask. Put the legend once, at the top of the fixture schedule sheet and again in the Section 22 42 00 submittal requirements, so it travels with the spec rather than living only in your head.

Before the fixture schedule goes out with the CD set, check three things: the tag format is defined once and used consistently across every sheet, the submittal requirements paragraph in 22 42 00 explicitly requires the tag string in every transmittal and substitution request, and the closeout requirements specify that the O&M table of contents is organized by tag, not by manufacturer catalog section. Those three checks cost an hour and prevent the kind of closeout scramble where nobody can confirm which faucet is actually installed where.

About Khan Parwez

View all articles ↗