Tendering

Tender pack auto-assembled, vendor pre-qualification automated, bid comparison with historical-rate context.

What it is

Tendering compresses what is currently a 3-week manual process. Tender pack assembly (drawings + BOQ + GCC + SCC + tech spec) is generated from the project record. Vendor pre-qualification filters empanelled vendors by package, capacity, region — and Vendor 360 flags auto-exclude flagged vendors. Bid comparison enriches each line item with historical rates from prior projects, vendor history, and budget allocation. Award decisions are stamped with reasoning.

Inputs

Triggers

·BOQ finalised in M10
·Package scope confirmed by CPT and DCO
·Pre-qualified vendor list filtered against Vendor 360
·Tender release scheduled
·Bid responses received from invited vendors
·Award recommendation from CPT

Data reads

·BOQ from M10 (version-locked)
·Spec package from M09
·Drawing version from M07
·Vendor 360 from M13 with current flags, capacity, performance
·Rate library and historical award rates from Bandhoo
·Budget allocation from M11

Artefacts consumed

·GCC (General Conditions of Contract) template
·SCC (Special Conditions of Contract) per package
·Technical specification documents
·Vendor bid submissions

Tools & Techniques

Methods

·Auto-assembly of tender pack from project record
·Pre-qualification filter applied against Vendor 360
·Auto-exclusion of flagged vendors
·Bid comparison enriched with historical rates from prior projects
·Side-by-side techno-commercial analysis
·Award reasoning captured as structured data

Policies

·tendering policy by package type
·Pre-qualification criteria per discipline
·Award approval policy with thresholds for CPT Head, Director, MD
·GCC and SCC policy templates

Decision rules

·Tender pack assembled from current versions of drawings, BOQ, spec
·Pre-qualification filter auto-excludes Vendor 360 flagged vendors
·Award above threshold requires CPT Head plus Finance approval
·Award above major threshold requires MD approval
·WO issuance requires e-acceptance from vendor before activation

Outputs

Artefacts produced

·Tender pack (versioned, with all referenced artefacts)
·Pre-qualified vendor list per tender
·Bid submission record per vendor
·Comparison matrix with historical-rate context
·Award decision log with reasoning
·Work order with vendor e-acceptance

Data writes

·Tender status updated through lifecycle
·Award commitment recorded against budget
·Vendor engagement updated in Vendor 360
·WO created in SAP and Bandhoo

Downstream triggers

·WO release triggers material flow in M17 and schedule update in M16
·WO release triggers WIR workflow setup in M19
·Award decision feeds budget commitment in M11
·Engagement update feeds Vendor 360 capacity tracking in M13

Stakeholders

CPTOwns tendering process end to end
DCOBOQ source, rate validation
DesignDrawing and spec inputs to tender pack
CPT Head · FinanceAward decision

The flow

01Tender package preparation — drawings, BOQ, GCC, SCC, tech spec
02Vendor pre-qualification filter
03Tender release through Bandhoo
04Bid collection and structured comparison
05Technical and commercial analysis with historical-rate intelligence
06Work order release with reasoning logged
07E-acceptance by vendor

State change

Before

Tender assembly takes 2–3 weeks; bid comparison is spreadsheet-driven; context missing.

After

Tender pack assembled in hours; comparison shows historical context; decisions auditable.

Real-world example

Worli façade package tender — pack assembled from project record in 2 hours. 8 pre-qualified vendors invited; Sterling auto-excluded per Vendor 360 flag. Bids received within 14 days. Aluplex bid 4% below typical rate, flagged for technical review. WO awarded to Reliable Façade on 12 May at ₹38.4 Cr; e-acceptance received 14 May.

Artefacts

·Tender pack (versioned)
·Pre-qualified vendor list
·Bid submissions
·Comparison matrix with historical context
·Award decision log
·Work order
·E-acceptance record

Pain today

Tender pack assembly takes 2-3 weeks. Bid comparison is a spreadsheet exercise. Historical-rate context is not available at award time. WO release cycle is long.

Integrations

Bandhoo