How does conditional hardware language split scope?
By Harsha Reddy · Founder, FastBid24 · Published August 18, 2026
Hardware schedules routinely contain conditional language — 'only at the IT room and lobby door,' 'restrooms only,' 'where required by code' — that makes a single set produce different quantities on different openings.
Pricing a conditional set identically across its openings is one of the quietest ways a takeoff goes wrong, because the schedule shows identical assignments and the condition lives one document away.
A worked example
In a real anonymized package, hardware group 05 served seven openings. Two lines inside it — a surface closer and 12" kickplates — applied 'only at the IT room and lobby door.' Priced as written-in-the-schedule, that's five closers and ten kickplates that may not exist; read the other way, it's a short bid. The delivered takeoff carried those lines as applies on two doors, omitted-by-rule on five, with the rule text preserved on every line.
The same package held the harder case: 'restrooms only' kickplates on a set serving a mothers' room. That one isn't decidable from the documents at all — it left as an RFI.
The rule for handling rules
Every conditional line deserves one of three states per opening: applies, omitted by rule, or in question. Anything that collapses those states into a single per-set quantity is guessing on someone's behalf.
Next
The workspace mapping view shows applies / omitted / in-question on a real set.
Watch the rules apply live →