Short answer: A greenhouse contract technical annex should convert the accepted offer into one controlled description of design basis, scope, specifications, interfaces, documents, inspections, tests, acceptance, warranty and change management. Do not leave technical commitments scattered across quotations and chat messages.
The commercial contract states the legal and payment framework, while the technical annex defines what is being designed and supplied. It should be reviewed by qualified legal, engineering, tax and logistics advisers for the destination. This guide is a procurement checklist, not legal advice.
List the documents that form the agreement and their order of precedence: signed contract, technical annex, accepted deviations, drawings, bill of quantities and final offer. Record document numbers, dates and revision letters. State that later changes require written approval by named representatives. This reduces conflict between an old proposal and a newer clarification.
| Technical item | Annex requirement |
|---|---|
| Site criteria | Coordinates, wind, snow, rain, seismic, soil, corrosion and local codes with source and verifier. |
| Crop basis | Crop, layout, growing system, support loads, season and stated agronomy responsibility. |
| Climate basis | Weather data, crop-zone targets, calculation assumptions and system limits. |
| Interfaces | Foundations, utilities, drainage, roads, local works, permits and third-party systems. |
Name the designer for each discipline and the party responsible for local review. Avoid phrases such as suitable for all weather unless measurable limits and operating conditions are defined.
Describe structure, fasteners, covering, vents, nets, screens, cooling, heating, irrigation, fertigation, electrical, controls, sensors, alarms, tools and spares. Use model, specification, material and quantity where possible. State acceptable substitutions and approval process. Drawings and bills should agree; if quantity is estimated, explain how final adjustment is handled.
Create a responsibility matrix for permits, survey, soil report, foundations, civil works, water treatment, main power, backup power, fuel, communications, customs, unloading, storage, local labor, equipment hire, accommodation, crop materials and agronomy. Each boundary should identify connection point, required capacity, date and acceptance party.
Set dates and review periods for design basis, layouts, calculations, foundation information, fabrication drawings, hydraulic diagrams, electrical documents and control narratives. Define hold points before fabrication and shipping. Buyer approval should not automatically transfer the supplier's contractual design responsibility, subject to legal review.
Attach an inspection and test plan. Identify material checks, fabrication checks, coating or galvanizing evidence, covering datasheets, equipment nameplates, packing inspection and optional third-party witness points. Define package marks, photos, packing lists and container records. A passed pre-shipment inspection does not replace installation and functional testing.
State the supervision or installation scope, assumed local crew, tools, utilities and schedule conditions. Define mechanical completion, electrical checks, controller point tests, interlocks, irrigation tests, alarm tests, operator training and handover documents. Acceptance criteria should be measurable and achievable under stated site and utility conditions. Separate open minor items from safety or performance blockers.
Define start date, duration, covered parts, exclusions, claim evidence, response route, labor, travel, freight and replacement responsibility. List critical spares and software access. Structural, covering, equipment and workmanship warranties may have different terms; do not combine them into one vague statement.
Require a written change request describing technical effect, price, schedule, drawings and responsibility before work proceeds. Record delays caused by missing site information, approvals, utilities, buyer works, shipping or supplier work. A shared issue log helps both parties resolve facts before they become disputes.
Usually not. Consolidate scope, revisions, deviations, interfaces, deliverables and acceptance into controlled annexes.
Measurable inspections and tests for the agreed structure, equipment, installation, controls, irrigation, alarms and documents.
The contract should name qualified local verification and clearly divide supplier and buyer responsibility.
Require written technical comparison and approval before purchase, manufacture or shipment.
Use the drawing approval checklist, inspection guide and commissioning guide.
Send the project inputs and required scope through the contact page for a technical requirement checklist.