WORKFLOWS / KNOWLEDGE & DESIGN

Drone Facade Inspection | From Request to Repair Decision

What to find, how to verify it, and who will use it. Work backward from the deliverable so the flight becomes real work.

Read this page in order
01

Start by separating the purposes of an inspection

A client who wants a rough picture of a facade's condition and an inspection that feeds Japan's periodic reporting system (Building Standards Act Article 12) carry different responsibilities and call for different methods. MLIT (Japan's Ministry of Land, Infrastructure, Transport and Tourism) publishes guidelines for facade inspections and infrared inspections under the periodic reporting system. Check the target materials and the conditions of applicability, and never tell a client that photography alone completes a statutory inspection.

Source: MLIT | Periodic reporting system and facade inspection
Example requestAgree on this firstHow the deliverable is used
Condition survey before repairsScope, phenomena to detect, areas that cannot be inspectedPlanning a detailed inspection or repairs
Inspection tied to periodic reportingApplicable standards, responsible person, verification method, reporting requirementsA report that follows the statutory system
Comparison over timeComparability at the same positions and under the same conditionsTracking change and deciding on re-inspection
02

Six stages and what each hands on

StageTypical ownerInformation handed on
RequirementsClient, inspection leadPurpose, scope, delivery conditions
Site planningFlight operations, inspection staffCapture zones, sunlight, access control, permits
AcquisitionPilot, camera operatorImages, positions, timestamps, conditions, gaps in coverage
Sorting and interpretationAnalystAnomaly candidates, supporting images, uninterpretable areas
Cross-checking and verificationA person with the appropriate qualifications and expertiseVerification results, follow-up inspections, limits of the assessment
ReportingInspection leadLocation map, findings, unverified areas, next steps

Don't leave any stage with the "who" blank. Rather than a design where the analyst's own candidates become the final verdict, build one where roles and verification records can be traced.

03

Don't build the quote on flight time alone

Effort isn't set by floor area alone. It changes with access control, takeoff and landing conditions, the hours when capture is possible, drawing preparation, interpretation, re-inspection and the depth of the report. Making the hours per stage and the outsourced scope visible up front helps you avoid underbidding.

Example cost structure for a job
  = site preparation + flight and capture + data sorting
  + interpretation and cross-checking + report writing + travel and equipment
  + allowance for re-inspection depending on conditions

Decide before accepting the job
  scope / deadline / exclusions / acceptance criteria / extra work

The formula above is a design example so no stage gets forgotten. It does not represent actual costs or market rates. Refine it from the records of your own jobs.

04

Bringing it into Airffic Vision

Under each project, link the building, facade faces, capture zones, images, findings and report versions. Piling up photos alone won't tell you which parts of the building are still uninspected. Overlay "captured", "interpreted" and "needs follow-up" on the overall map, and the bottlenecks become visible.

DEFINITION OF DONE

When you build it, check these.

  • The report distinguishes out-of-scope, could-not-capture and could-not-interpret.
  • Every stage has an owner and defined hand-off information.
  • The quote includes hours for interpretation and reporting.

Design checklist items for spec reviews and functional testing.

Check the sources

Explanations of regulations and definitions refer to the material below. Screens, data and the definition of done are our own design proposals.

Sources checked on September 30, 2026. For your specific case, please confirm against the latest official information.