Most drainage problems on a project are decided long before anything is installed \u2014 they are decided in the bill of quantities. A BOQ line that reads “floor drain \u2014 24 no.” looks complete, but it hides everything that determines whether the right product arrives: which model, which variant, which material, which outlet, which grate, whether a trap is included, and which documents the consultant will ask for. Each missing detail becomes a clarification round during procurement, a substitution argument during submittals, or a mismatch discovered when the screed is already going down.<\/p>\n
The fix is not a longer BOQ; it is a more precise one. The checklist below sets out what a plumbing and drainage BOQ needs, group by group, so suppliers quote the same products, consultants can approve without detective work, and site receives what the drawings intended. It is written for contractors, consultants and procurement teams on Saudi projects and follows the way project supply actually runs \u2014 Fanoos’s project-based approach is described on the \u0627\u0644\u062d\u0644\u0648\u0644<\/a> page.<\/p>\n Write the count location by location, and name the location on the line or in the line reference. A location count forces the drain type to be chosen deliberately \u2014 a roof point, a finished-floor point and an external area point are different products with different duties. If the line just says “drains, 60 no.”, procurement has to reverse-engineer the design intent, and whatever they assume becomes the project’s problem at installation.<\/p>\n Write the full model code on every line, including variant suffixes. Drainage ranges are built as families \u2014 one base code with suffixed variants that change the configuration \u2014 so a family name on a BOQ line authorises the supplier to price any variant in it. One line per variant keeps the specified configuration locked from BOQ to delivery.<\/p>\n Write the material and finish from the specification onto the BOQ line itself, rather than referring the reader to a spec clause. BOQs get priced by people who price what is on the line; a clause reference invites each bidder to interpret it differently. Where the location carries special conditions \u2014 a commercial kitchen, a chemical store, a trafficked yard \u2014 note the condition on the line so material suitability is argued now, while it is still an argument about paper.<\/p>\n Write the nominal size and the outlet size on every drain line, plus the outlet configuration where the pipework design depends on it. The drain body is only half the product: two drains from one family can carry different outlets, and the wrong one is discovered when the pipework is already set out below the slab. Checking BOQ sizes against the pipework drawings before issue removes the entire category of error.<\/p>\n Write traps, cleanouts and accessories as lines in their own right. These are the items most often missing at installation because they are invisible in the finished building and absent from finishes schedules \u2014 nobody counts them, so nobody orders them. If a component is not a BOQ line, it is not in any supplier’s price, and it will be procured late while a floor waits.<\/p>\n Write the required documents against the lines that need them. Submittal approval gates ordering on most projects, and the products with the longest approval path are usually the ones nobody flagged. Attaching the document requirement to the BOQ line means the supplier assembles datasheets and dimensional information with the quotation, and the consultant reviews the actual product first time.<\/p>\n Write the delivery city on the BOQ package itself. Drainage is bulky and phased \u2014 below-ground items are needed months before finished-floor items \u2014 and a supplier planning around the wrong city builds the error into the quotation. Splitting quantities by phase on the BOQ turns delivery from a negotiation into a schedule both sides already share.<\/p>\n Variants merged into one line.<\/strong> A drain family priced as a single averaged line means the installed variant gets decided by availability, not by the specification. Split the line by full model code and the decision stays where it belongs \u2014 in the design.<\/p>\n “Floor drain” with no outlet information.<\/strong> Without outlet size and configuration, procurement is guessing at the connection the pipework was designed around. The guess is discovered below a finished slab, where corrections are demolition.<\/p>\n Materials left open.<\/strong> Lines that name neither the specified material nor an approval route for alternatives invite substitutions that surface at submittal stage, the most expensive moment to re-open the decision.<\/p>\n Accessories assumed included.<\/strong> Traps, cleanouts, frames and extension pieces are routinely absent from unit rates because they were absent from the BOQ. If it is not a line, it is not in the price.<\/p>\n Extension pieces forgotten on deep floor build-ups.<\/strong> Where finished floor level sits well above the slab, standard drain bodies need extension pieces to reach it. BOQs written from the slab drawing alone miss them, and the shortfall appears when the screed is being laid.<\/p>\n Quantities from a superseded revision.<\/strong> Drainage counts move between drawing issues as bathrooms and kitchens are replanned. A BOQ dated against an old revision orders the wrong building \u2014 confidently, and in full.<\/p>\n Approval-gated lines ordered before approval.<\/strong> Ordering long-lead drainage before the consultant approves the submittal converts a paperwork step into a financial risk: if the submittal is rejected, the project owns stock it cannot install and a programme it cannot recover.<\/p>\n A BOQ built on this checklist converts directly into a clean RFQ, because every field a supplier needs is already on the lines. Fanoos AlHadeeth Trading Co., based in Jeddah, supplies plumbing and drainage products for projects across Saudi Arabia on a quotation basis. Send the RFQ through the contact and quote form<\/a> using the Product Inquiry\/RFQ<\/strong> enquiry type: add a short project summary, set the delivery city (the form provides a dropdown of 15 cities) and attach or paste the BOQ product lines. If the product list is still being built, the live ranges show what can be specified: \u0645\u0635\u0627\u0631\u0641 \u0627\u0644\u0623\u0633\u0637\u062d \u0648\u0627\u0644\u0623\u0631\u0636\u064a\u0627\u062a \u0648\u0627\u0644\u0645\u0646\u0627\u0637\u0642<\/a>, \u0645\u0635\u0627\u0631\u0641 \u0627\u0644\u0641\u0648\u0644\u0627\u0630 \u0627\u0644\u0645\u0642\u0627\u0648\u0645 \u0644\u0644\u0635\u062f\u0623<\/a>, \u0645\u0635\u0627\u0631\u0641 \u0627\u0644\u062e\u0646\u0627\u062f\u0642 \u0648\u0627\u0644\u0645\u0635\u0627\u0631\u0641 \u0627\u0644\u0645\u0639\u064a\u0627\u0631\u064a\u0629<\/a> and \u0627\u0644\u0623\u0646\u0627\u0628\u064a\u0628 \u0648\u0627\u0644\u0648\u0635\u0644\u0627\u062a \u0627\u0644\u0628\u0644\u0627\u0633\u062a\u064a\u0643\u064a\u0629<\/a>.<\/p>\n The BOQ is the project’s own document: the items, quantities and specifications the works require. The RFQ is the request sent to suppliers asking them to quote against that list. They are only as good as each other \u2014 a vague BOQ produces incomparable quotations, while a precise one produces quotes that can be evaluated line by line.<\/p>\n Yes. A specification section, a drainage schedule or marked-up drawings give a supplier enough to propose models against. Full model codes are still worth adding wherever the design has settled: they remove a round of interpretation and prevent variant substitutions between quotation and delivery.<\/p>\n The live range covers roof, floor and area drains; stainless steel drains; trench and modular drainage; and plastic pipes and fittings, alongside a valves range that includes a brass ball valve. The category pages list the models available to specify against BOQ lines.<\/p>\n Select the nearest listed city and state the actual project city clearly in the message, with any site delivery notes. The delivery city drives how supply is planned and how delivery terms are quoted, so it should always be stated explicitly.<\/p>\nThe BOQ checklist<\/h2>\n
Drainage points by location<\/h3>\n
\n
Models and variants<\/h3>\n
\n
Materials and finishes as specified<\/h3>\n
\n
Sizes and outlets<\/h3>\n
\n
Traps and accessories<\/h3>\n
\n
Documents and submittals<\/h3>\n
\n
Delivery city and programme<\/h3>\n
\n
Common BOQ mistakes<\/h2>\n
From BOQ to RFQ: sending it to Fanoos<\/h2>\n
Frequently asked questions<\/h2>\n
What is the difference between a BOQ and an RFQ?<\/h3>\n
Can we send an RFQ without model codes?<\/h3>\n
Which product categories does Fanoos cover for project BOQs?<\/h3>\n
What if the project city is not in the form’s dropdown?<\/h3>\n
Run the checklist before the BOQ leaves the office<\/h2>\n