What to capture during a technical visit
- client information
- on-site observations
- site photos
- visit notes
- shading / horizon profile data
- first technical assumptions
- inputs for pre-study
Structure the visit without scattered tools
- centralize key information
- group notes, observations and photos
- link findings to pre-study outputs
- avoid tool fragmentation
- retrieve the file quickly after the visit
Information to keep in the site file
- client context
- photos
- constraints and remarks
- shading-related elements
- selected assumptions
- pre-study base
- post-visit deliverables
What this avoids after the visit
- manual re-entry overload
- lost information
- slow retrieval of field observations
- poorly justified assumptions
- friction in next project steps
The value comes from what remains usable after the visit.
For installers and engineering firms
Installers get faster qualification and cleaner commercial preparation. Engineering teams get better structured field inputs for downstream analysis.
Post-visit deliverables
- pre-study base
- PDF report
- field-data exports
- visit file with notes and photos
- working support for project continuation
Go further
FAQ
What should be captured during a PV technical visit?
Field observations, photos, notes, shading elements and first assumptions for next project steps.
Why keep everything in one file?
It reduces information loss between site and office and makes project restart faster.
Does a technical visit replace detailed study?
No. It prepares a clean first-level analysis before detailed engineering.
What can be reused after the visit?
The visit file, pre-study base, PDF report and exports.
Structure photovoltaic technical visits from the field
Azimutis consolidates useful site information and prepares cleaner downstream project work.