The Revit faucet family on your model almost never matches what the manufacturer will actually ship, because the family was built to populate a schedule, not to carry submittal-grade data. If your 22 41 00 schedule was generated straight from family parameters without a cross-check against cut sheets, you have a mismatch waiting to surface at submittal review, and probably a substitution fight waiting behind it.
Where Manufacturer Content Diverges From Spec
Manufacturer-published Revit content is marketing collateral with geometry attached. It is built by a BIM content vendor working from a spec sheet and a few photos, often before the product ships, and it gets revised on its own schedule, not yours. The family you loaded in design development may represent a finish option that was discontinued, a handle configuration that was never offered in the flow rate your spec calls out, or a body style that differs from what’s actually stocked.
None of this shows up when you’re placing fixtures. It shows up when the contractor’s submittal lists a model number and the architect pulls up the Revit family to check it against the schedule, and the two don’t agree. At that point you’re not reviewing a submittal, you’re investigating a discrepancy, and the clock on your review period is running.
LOD 350 and What It Skips
LOD 350 means the model element is geometrically accurate enough to coordinate with other trades, including connection points, clearances, and interfaces with adjacent systems. For a faucet, that’s supply connections, deck penetration, and rough-in envelope. It does not mean the family carries accurate flow rate, aerator type, valve cartridge data, or finish code. Those are submittal-level attributes, not coordination-level geometry, and LOD 350 has no obligation to include them.
This is the gap that catches people. A faucet family can be fully LOD 350 compliant, perfectly coordinated against the counter and the wall, and still carry a placeholder flow rate of 2.2 gpm when the specified model is rated at 1.5 gpm, or list a generic “chrome” finish parameter when three finish options are actually available and only one meets the project’s dark-finish schedule. The model passes coordination review. The schedule it generates is still wrong.
Connector Data That Breaks the Schedule
Faucet families carry MEP connector data for supply size, typically 1/2 inch NPT, and sometimes for drain or waste in bar and prep sink assemblies. When a generic or early-release family uses a placeholder connector, your schedule’s “supply connection” column populates with whatever the family author typed in, not with what the product actually requires. This rarely gets caught in design review because connector size doesn’t change the fixture’s footprint or its position in a rendered view.
It gets caught in plumbing coordination, when the MEP engineer pulls connector data to size branch lines and the number doesn’t match the cut sheet the plumber is holding. If you’re specifying matte black kitchen taps for a residential or light-commercial job, for example, check that the connector and valve data in the family actually matches the specific finish and body style called out, not a generic version of the product line, since finish variants sometimes ship on different valve platforms with different rough-in requirements. Juno Showers stocks matte black kitchen taps if you are comparing options.
| Field | Typically in LOD 350 Geometry | Typically Missing Without Manual QC |
|---|---|---|
| Rough-in dimensions | Yes | — |
| Supply connector size | Sometimes, placeholder common | Verified NPT size per actual model |
| Flow rate (gpm) | Rarely accurate | Yes, needs cut sheet cross-check |
| Finish code | Generic parameter | Yes, against approved finish schedule |
| Valve/cartridge type | No | Yes |
Shared Parameters vs Submittal Fields
Most offices have a shared parameter file built up over years, with fields like “Spec Section,” “Basis of Design,” and “Flow Rate (GPM)” mapped to specific submittal and schedule templates. Manufacturer families almost never use your shared parameters. They come with their own parameter set, named and typed however the content vendor set them up, and when you load that family into a project using your office template, Revit doesn’t merge the two. You end up with duplicate fields, one empty and one populated, and a schedule that silently drops data because it’s pulling from the parameter nobody filled in.
This is a maintenance problem as much as a data problem. The fix is not glamorous: every faucet family that enters the project needs its parameters mapped to the office shared parameter file before it goes into the model, not after someone notices the schedule has blank cells. Some offices handle this with a family audit step built into their BIM execution plan; others catch it manually at each phase gate. Either way, it needs to happen before the family is placed, because remapping parameters after fixtures are scheduled and tagged across a hundred sheets is a bigger job than doing it once on load.
- Confirm the family’s flow rate parameter is typed as a number, not text, so it sorts and filters correctly.
- Map manufacturer “Model” or “SKU” fields to your office’s “Basis of Design” parameter, don’t let both exist unmapped.
- Check that finish parameters use your project’s approved finish list as values, not the manufacturer’s internal naming.
- Verify the family’s “Type Comments” or equivalent field is not being used by the schedule and by your own annotation system for two different purposes.
Flagging Substitution Risk Inside the Family
Every faucet selection written into a 22 41 00 schedule carries some substitution risk, the possibility the contractor proposes a different model at submittal, typically on cost or availability grounds. Lead times matter here more than they used to. A faucet that was in stock when the spec was written can be twelve weeks out by bid date, and the contractor’s first move is often to request a substitution rather than wait.
You can flag this risk inside the model instead of discovering it at submittal review. Add a shared parameter, something like “Substitution Risk” with values for low, medium, and high, and populate it at the point the fixture is selected, based on how many approved equals exist and how tight the lead time is. A single-source item with a twelve-week lead time gets flagged high. A commodity lavatory faucet with three approved manufacturers gets flagged low. This doesn’t prevent substitution requests, but it tells whoever is reviewing the submittal, often someone who wasn’t in the room when the fixture was selected, which items are likely to generate a fight and which aren’t.
The same flag is useful before the bid deadline. If a generic placeholder family is still sitting in the schedule where a specific manufacturer product should be, because the real family hadn’t been loaded yet when the model was issued for pricing, that placeholder needs its own flag. An unflagged generic family in a bid set reads to an estimator as “basis of design to be determined,” which invites low-balling the allowance or padding it, neither of which serves the owner.
Before you issue a fixture schedule for submittal or bid, pull every faucet family and check three things against the current cut sheet: the connector size and type, the flow rate, and the finish code. Confirm each family’s parameters map to your office’s shared parameter file, not a vendor’s independent set. Flag substitution risk and placeholder geometry explicitly rather than leaving them to be discovered during construction administration, when the discovery costs more than the fifteen minutes it takes to check now.
