As-Builts, O&M & Handover
Landscape documentation is a procurement asset because it protects the project after opening day. Procurement should request as-builts, O&M notes, and a handover pack that connects irrigation, lighting, and hardscape interfaces to maintenance responsibilities for facility teams.
What should a landscape handover pack include?
A handover pack should include as-builts, O&M notes for key systems, and a maintenance program structure that defines responsibilities and cadence.
For irrigation and lighting, include commissioning records and operating parameters so FM teams can maintain without guesswork.
How do as-builts reduce ambiguity during AMC?
As-builts clarify what was actually installed and where key assets are located, so AMC teams can troubleshoot quickly.
This reduces disputes caused by differences between drawings and the final field condition.
What documentation belongs to irrigation and controllers?
Procurement should require valve charts, controller/program notes, and documented commissioning outputs tied to zoning logic and coverage verification.
These artifacts help maintenance teams run schedules consistently through seasons.
How should documentation connect to acceptance and QA logs?
Acceptance proof should connect to documentation: QA logs, hold points, and recorded commissioning checks should appear in the handover pack.
When documentation isn’t linked to acceptance, FM teams lose traceability.
How can architects and procurement align documentation expectations?
Align documentation expectations during tender lock and confirm that interface responsibilities are written into BOQ language.
Use the for-architects channel as a documentation-first planning lane.
When should you request a documentation-ready site assessment?
Request a site assessment when interface realities aren’t clear so the final record includes what will be maintained.
This keeps handover discipline aligned from day one through AMC.