For a roofer, surveyor or property professional using drone photographs, a clear report is only one part of the job. Before take-off, the pilot needs to understand the location, current restrictions, weather and permissions relevant to the operation. AyeInspect’s AyeSky integration brings those planning records closer to the survey they belong to, without mixing them into the customer’s roof-condition report.
This guide explains the workflow for trade customers carrying out drone roof inspections in Glasgow, Lanarkshire, Edinburgh and across Central Scotland. It is a guide to the integration, not a claim that every roof can be flown or that a planning tool can authorise a flight.
What is the AyeSky integration?
AyeInspect handles your survey photographs, reviewed roof findings and branded client report. AyeSky provides a separate place to review flight-planning information for the property location. You can open AyeSky from an authorised AyeInspect survey, then return a briefing and explicitly attach it to a survey you can access.
The practical benefit is continuity: the location you checked, the briefing you reviewed and your own planning notes can sit alongside the inspection record. The planning information stays distinct from the evidence about tiles, slates, gutters, chimneys and other roof features.
Start with the right roof, not just the right postcode
A postcode can be a useful starting point, but it is not proof that a pin marks the roof you intend to inspect. That matters on terraced streets, shared developments and larger commercial sites, where several buildings may sit close together. Open Flight planning and permissions in your survey and check the location before choosing Plan flight in AyeSky.
- If the location is approximate, use Adjust pin and inspect the visible map.
- Tap the correct property or drag the pin deliberately before confirming.
- If the map fails to load, use Retry; do not confirm a roof you cannot see.
- Check that the planned launch area and operating area are appropriate on site. A confirmed map pin does not establish landowner consent or a safe take-off point.
Review airspace, weather and permissions before a drone roof survey
The planning link opens the selected coordinates in AyeSky. Review the available airspace, weather and permission information for your proposed operation, including the planned time and height. A familiar street or a previous successful flight is not a substitute for checking the current situation.
Why planned height is shown in m AGL
AGL means above ground level. Airspace limits may instead be expressed as altitude above mean sea level, labelled AMSL or ALT, or as flight levels, labelled FL. Those references are not interchangeable: you must establish terrain elevation and the appropriate altitude reference before deciding whether a vertical limit applies.
AyeInspect keeps relevant and uncertain briefing findings in the main list. Some elevated airspace appears under Other airspace context, where vertical applicability remains unverified. Expand that section and Source detail when needed. Neither a collapsed entry, an empty findings list nor a low planned height should be read as clearance to fly.
Bring the briefing back to the correct trade survey
Use the return-to-AyeInspect link supplied by AyeSky. Sign in if prompted, select a survey you have access to and check the destination, property coordinates, planned time and height before explicitly attaching the briefing. Opening the link alone does not attach anything automatically.
- Return links expire after 15 minutes; obtain a fresh link if yours expires.
- Continue in the same tab if you need to sign in during the import.
- Treat the return link as private, not as a customer report link.
- Retrying the same briefing on the same survey does not create a duplicate history entry.
Keep a planning history without rewriting the evidence
Attached briefings are preserved as read-only snapshots with their import details. You can review the history, download a JSON copy or print a briefing. If the plan changes, obtain a new briefing rather than trying to edit an earlier snapshot. Saved weather and restriction information does not update automatically: check current information again before the flight.
Your own planning records remain separate. You can save notes, permission references and supporting documents alongside the survey, without turning them into imported AyeSky evidence. A note or uploaded document is not automatically verified permission to operate.
What happens to customer privacy and white-label reporting?
The outbound AyeSky planning link carries only latitude, longitude and the neutral label Inspection location. It does not include customer names, email addresses, telephone numbers, survey IDs, roof photographs or your AyeInspect planning notes. Coordinates still identify a location, so only open the property you intend to plan for.
Saved briefing access follows the survey’s authorised access rules. A public client report link does not give someone permission to import a briefing. Your client-facing roof report keeps its normal trade branding: the planning snapshot is a separate record, not a replacement for your logo, colours or photographic findings.
What if a source is incomplete or an import fails?
A connected source is not necessarily complete. A need review message, missing data or connected-but-incomplete weather needs attention before you rely on the briefing. Review the source status and original information, and do not interpret unavailable data as evidence that no restriction exists.
If an import fails, check your connection, signed-in access and whether the return link has expired. Retry while it remains valid or obtain a fresh link from AyeSky. Your existing survey and manual planning records remain available; an interrupted transfer must not be treated as a completed briefing check.
Does AyeSky planning use AyeInspect report credits?
Flight planning and briefing imports are optional and do not spend AyeInspect report credits. Your normal photograph upload, defect review and report-publishing process remains unchanged. Any account requirements, charges or usage terms within AyeSky are separate, so check AyeSky for its current terms.
A clearer workflow from flight preparation to client handover
For trade teams, the goal is a more organised survey record: confirm the roof, review the flight plan, preserve the briefing, capture useful photographs and review the findings before publishing your branded report. AyeInspect remains impartial to repairs and does not sell repair work or recommend specific roofing contractors.
Explore AyeInspect Trade for white-label roof reporting, or read the trade FAQs for the detailed AyeSky planning and import answers. If you want to discuss how the workflow fits your business, call AyeInspect on 01236338104.