Landscape BOQ Format in India
A landscape BOQ format is where procurement converts design intent into buildable scope. For commercial and estate-scale work, a useful BOQ structure clarifies package boundaries, unit basis, interfaces, exclusions, commissioning/QA acceptance, and what is delivered for handover and AMC.
What package structure should a landscape BOQ use?
Organize the BOQ into packages that match execution reality: hardscape/civil, softscape/horticulture, irrigation, water features, lighting, and maintenance where in scope.
Each package should carry its own interface responsibility so procurement can validate sign-offs without guesswork.
How should unit basis and quantities be specified?
Set unit basis consistently and verify that quantities map to the same take-off assumptions used in drawings and schedules.
When a line item uses a provisional sum, define the discovery logic so the final value is not arbitrary.
How do you write exclusions and assumptions in BOQ language?
Exclusions should be explicit and tied to interfaces: drainage responsibilities, waterproofing boundaries, irrigation zone logic, and working-site constraints.
Assumptions should be documented so substitutions or scope changes trigger an approvals process.
What QA and acceptance checkpoints belong in the BOQ?
Include acceptance checkpoints for civil base readiness, drainage observation, irrigation commissioning coverage, planting establishment stages, and any commissioning records tied to FM readiness.
The BOQ should also indicate what is recorded and what becomes part of as-builts.
How should procurement plan handover artifacts from day one?
A BOQ that enables handover specifies what documents are delivered: as-builts, O&M notes, valve charts/controller records, and maintenance program structure.
This reduces post-opening disputes because FM teams receive the same artifacts the tender promised.
When should you request a site assessment to finalize the BOQ?
Request a site assessment once levels, access, drainage outfalls, and working-site realities are uncertain. Use the visit outcome to lock interfaces and exclusions.
This is how procurement protects bid comparability and prevents scope drift into construction.