Destination and permitted product pathway
ARKEN · CADARN · VARDHUS · PROJECT AUTHORITY CENTRE
Move from product interest to a controlled project specification.
Select bespoke, kitset or modular outdoor architecture by span, geometry, wind, drainage, roof behaviour, enclosure, site interfaces and procurement model rather than by appearance alone.
01 · PROJECT INPUTS
Define the conditions before the exact system is released.
These inputs are deliberately upstream of model selection so the product does not dictate the brief.
Overall footprint, bays and required clear spans
Wall-mounted/freestanding/site interfaces
Local wind, snow where relevant and exposure category
Roof type, opening behaviour and rainwater strategy
Post height / site falls / slab levels
Screens, doors, lighting and accessory requirements
Foundation/fixing, power/controls, freight and installation responsibility
02 · EVIDENCE CONTROL
Keep project claims attached to what the evidence actually proves.
Generic declarations, outdated catalogues or unrelated certificates should not be carried into a project as exact-system evidence.
Exact aluminium/steel/material specification
Exact structural/span/wind evidence for selected configuration
Motor/control documentation where powered
Drainage/gutter/downpipe details
Screen/door/accessory compatibility
Coating/finish and coastal/environment evidence
Exact-system drawings, warranty and maintenance requirements
03 · CAD / DRAWING REGISTER
Planning references are not exact-system construction drawings.
Every drawing/model status stays visible so consultants know what can be used now and what only exists after configuration or project-specific design.
| Resource | Status | Purpose |
|---|---|---|
| Pergola / outdoor-architecture concept / planning layout | Public planning | Early scope, interface and consultant coordination only. |
| Generic technical reference / typical detail | Public planning | Explains system logic without representing an exact supplied configuration. |
| Exact-system GA / dimensional drawing | Exact-system | Issued only after the quoted system/configuration is known. |
| Native CAD / DWG / DXF | Verify availability | Availability and revision must be confirmed against the exact supplied system. |
| BIM / Revit / IFC object | Verify availability | Only described as BIM where a genuine verified native model exists. |
| Foundation / fixing / setting-out drawing | Project-specific | Depends on site/building conditions, local engineering and the selected system. |
| Services / electrical / controls interface | Project-specific | Coordinates the supplied system with local power, data, water, drainage or controls. |
04 · SPECIFICATION STARTER
Write the project around performance, interfaces and evidence.
These clauses are a project-planning structure, not a substitute for local professional specifications or exact-system documentation.
System pathway and procurement model
Plan geometry / bay arrangement / clear span
Posts, beams and roof configuration
Wind/site criteria and local structural design
Rainwater/drainage strategy
Motor/controls/electrical interfaces
Screens/doors/accessories
Finish/coastal/environment requirements
Foundations/fixings/installation boundary
05 · TENDER / RFP SCHEDULE
Ask bidders for the same controlled information.
A consistent schedule makes technical comparison easier and reduces hidden assumptions.
Site / building drawings
Dimensions / bay layout
Wind/site criteria
Roof/drainage requirements
Accessories / screens / doors
Finish/colour
Power/controls
Foundation/fixing responsibility
Freight/site access
Exact evidence and drawings
06 · OPERATIONS & HANDOVER
Specify how the system will be maintained after delivery.
Maintenance, spares, records and inspection should be defined before purchase, especially for remote or high-use projects.
Roof/moving-component inspection
Drainage/gutter/downpipe cleaning
Fastener/connection visual inspection
Motor/control maintenance
Screens/doors/accessory service
Coating/corrosion inspection
Seal/weather-interface check
Storm/high-wind operating procedure
DOWNLOADABLE PROJECT RESOURCE
Carry the authority pack into the project file.
Export the current project-control structure, then replace planning statements with exact project/system information as the design develops.
