DRONE CENTRAL / INSPECTION · PRACTICAL GUIDE
Build an inspection shot register before launching
A practical inspection workflow that connects every requested view to an asset, purpose, capture result and follow-up decision.
An inspection flight can produce hundreds of sharp images and still leave the reviewer asking whether the critical area was captured. The problem is often not camera quality. It is the missing connection between the inspection question, the planned view and the file delivered afterward.
A shot register makes that connection explicit. It is a compact list created before launch and completed during review. Each row says what must be seen, why it matters, whether it was captured and what limitation remains.
Turn the request into named evidence
Start with the decision the inspection supports. Replace broad instructions such as photograph the roof with named evidence requests: north parapet overview, drain outlet context, flashing transition and any area previously flagged for comparison. Give each request a stable shot ID so the pilot, reviewer and client can refer to the same item without relying on file names alone.
Add the asset or location, intended viewpoint, required context and purpose of each shot. Context matters because a tight image may show surface detail while hiding where it belongs. Plan an overview-to-detail sequence when both orientation and close observation are needed. Avoid promising that an image will establish a diagnosis that requires another specialist or method.
Record acceptance criteria before the site visit
For each row, describe what makes the capture usable: the relevant area is visible, orientation can be established, focus supports review and the frame is not blocked by glare, shadow, vegetation or a temporary object. Keep the criteria tied to the question. A visually attractive image can fail when the required edge or reference point is outside the frame.
Mark which shots are essential, useful if conditions allow or optional context. That priority helps the crew protect the core result when time, light or site access changes. It also makes an honest partial inspection possible. A missing optional image and a missing safety-critical view should not appear as equivalent gaps in the final handoff.
Use the register as a live field control
During the flight, mark each planned shot as captured, deferred or not obtainable. Add a short reason when the plan changes: people entered the area, the viewing angle was obstructed, conditions changed, the aircraft position would not be appropriate or the requested feature could not be identified. The register should never pressure the pilot to continue when the operation no longer fits the plan.
Capture an orientation view before a detail when the reviewer may not recognize the location. If a new concern appears, assign a new shot ID rather than quietly replacing a planned image. That preserves the difference between requested scope and an additional observation. Follow current official aviation requirements, site permissions and the aircraft manufacturer's instructions throughout the operation.
Reconcile the register before leaving
After landing, review the essential rows while a safe return to the site may still be practical. Open representative files rather than relying only on thumbnails. Confirm that the correct feature, not merely a similar nearby feature, appears in the frame. Check that file timestamps and camera sequence can be connected to the shot IDs.
If a row remains incomplete, decide whether a repeat capture is appropriate, the limitation can be accepted or another method is required. Record that decision in the register. Do not manufacture completeness by attaching the nearest available image. A clear gap is more useful than evidence that appears to answer a question but actually belongs somewhere else.
Deliver findings with traceable limits
The final package can include the completed register, selected images and a short findings note. Rename copies or provide a cross-reference table without destroying original file identity. Each observation should point to one or more shot IDs, and each shot should retain its capture date and asset location. Keep raw files under the project's retention and access rules.
State what the imagery could not establish. A shadow may hide a joint, an angle may prevent depth assessment, or aerial imagery may show a condition without revealing its cause. Assign the next action to a person or role: compare with the previous visit, request specialist review, plan a ground check or accept the documented condition. The handoff is complete when uncertainty has an owner.
A shot register turns an inspection flight from a collection exercise into a traceable evidence workflow. Name the required views, capture against explicit criteria and deliver every conclusion with its source and limitation.
Official operating resources checked September 30, 2026: Transport Canada drone safety and FAA UAS guidance.