Aerial Evidence for a Grant or Funding Application

Published 2026-11-02 · UAV Imaging Inc.

Key takeaways

The before capture is the one that gets forgotten. An after image on its own shows a finished thing; the pair shows the change the funding paid for.
A reviewer can verify extent, location, surface condition and the date. They cannot verify quality of workmanship, what is below grade, or anything inside a structure.
Dates are the whole point. Imagery with a defensible capture date is evidence; imagery with an uncertain date is an illustration.
Grant audits arrive years later, so retention is part of the deliverable. Unedited originals, flight logs and a written method matter more at audit than the polished figure in the application.
An aerial capture quantifies as well as illustrates. Area treated, length constructed, volume moved and count installed are all measurable from the same flight.
Reporting obligations are set by your funder, not by us. The capture produces evidence that fits a reporting requirement you define; it does not interpret the requirement.
A capture taken for a grant file is reusable. The same dataset usually serves asset records, insurance and the next application, so it is worth specifying once properly.
If the before window has already passed, say so in the application rather than working around it. A stated baseline gap is far better than a reconstructed one.

Grant and funding files have a documentation problem that nobody notices until the reporting deadline. The work gets done, the invoices get filed, and then somebody has to demonstrate to a funder that the thing described in the application is the thing that was built, on the ground, at a given scale.

Photographs from a phone do some of that. What they do badly is scale, extent and date, which are exactly the three things a reviewer is trying to establish.

What a reviewer can actually verify from imagery

Being precise about this is useful, because it tells you what to capture and what not to bother claiming.

From a dated aerial capture, a reviewer can see and check:

Extent. How much was done, over what area, with boundaries that can be measured rather than described.
Location. That the work happened where the application said it would, in a coordinate system somebody else can independently check.
Surface condition. What the ground, the structure or the site looked like at a point in time, at a level of detail nobody gets from eye level.
Quantities. Area treated or seeded, length of trail or road constructed, volume of material moved, number of units installed.
Change. The difference between two captures, which is the closest thing to direct evidence that funding produced an outcome.

What a reviewer cannot verify from imagery is everything below the surface, anything inside a structure, the quality of workmanship, the specification of materials used, and whether the work meets an engineering standard. Those stay with your invoices, your inspection records and your professional sign-offs. Aerial capture is evidence of extent and condition, not of compliance or quality.

The before capture is the one that gets missed

This is the recurring regret, and it is not a minor one. An after capture on its own shows a reviewer a finished thing. It does not show them the thing that was there before, which means the change the funding paid for is asserted rather than demonstrated.

A pair of captures, same boundary, same method, a known interval apart, is a different class of evidence. It supports a sentence like "this area was in this condition on this date and in this condition on this date", and that is a sentence a reviewer can check.

The practical problem is timing. The before capture has to happen before the work starts, which is usually before the funding is confirmed, which is why it gets skipped. Two ways round that. If a capture is cheap relative to the project and the application has any real chance, flying the baseline at application time is the straightforward answer. If that window is already gone, say so plainly in the file and rely on whatever genuinely dated material exists, such as public imagery with a known date or your own records. A stated gap in the baseline is a far better position than a reconstructed one that falls apart under questioning.

Dates are what make it evidence

Imagery with an uncertain date is an illustration. Imagery with a defensible date is evidence, and the difference is entirely in the record that travels with it.

What makes a date defensible is not a watermark. It is the chain: the original unedited files with their embedded capture metadata intact, the flight logs from the aircraft, the processing record showing what was done to the data and when, and the derived products traceable back to those originals. If a reviewer or an auditor asks how you know the capture happened on the stated date, that chain is the answer.

This is the same discipline that makes aerial imagery useful in a dispute or an insurance claim, and it costs nothing extra at capture time. It costs a great deal to reconstruct later, which is to say it usually cannot be.

Audits arrive long after the project closes

Grant programs commonly reserve the right to review a funded project well after the money is spent. By then the project manager has moved on, the contractor's records are archived, and whoever has to answer the question is working from whatever is left in a shared drive.

So retention is part of the deliverable rather than an afterthought. What is worth holding:

The unedited original imagery, not just the exported figures.
Flight logs and, where ground control was used, the control point coordinates with the datum and epoch written down.
A short written method: the aircraft, the sensor, the capture parameters, the processing software and the accuracy achieved along with how it was established.
The boundary used, as a file.
Any derived quantity with the surfaces or measurements it was computed from.

That is a small package and it answers nearly every question a later audit raises. Without it, an audit question about a quantity in the final report has no better answer than somebody's recollection.

Quantities, not just pictures

The figure in the application tends to be the photogenic part. The part that holds up is the number.

From the same flight you can report area, length, volume and count, each measured rather than estimated, each tied to a boundary file and a date. If the funding was for a specified quantity of work, that is direct evidence of delivery. If the reporting requires an outcome measure, a measured quantity is a far stronger input to that calculation than an estimate from a drawing.

Two cautions. First, a measured quantity needs its reference stated: an area is an area within a stated boundary, and a volume is a volume above a stated base surface. Without those, the number is not reproducible and an auditor is right to question it. Second, we measure; we do not decide whether the measured quantity satisfies your funding agreement. That reading is yours and your funder's.

The capture is reusable, so specify it once properly

A capture flown for a grant file is rarely only useful for the grant file. The same dataset typically serves an asset record, an insurance or valuation conversation, a planning or engineering input, and the baseline for the next application.

Which argues for specifying it slightly better than the grant strictly requires. A written coordinate system rather than whatever was convenient. A boundary that matches your other records. Open deliverable formats rather than something only one software package opens. Originals retained rather than discarded after the figure was exported. None of that costs much at capture time, and all of it is what determines whether the data is still usable in three years.

What this does not do

It does not make a weak application strong. It does not interpret your funder's reporting requirements, which vary by program and are set out in your own agreement rather than by us. It does not verify that work met a standard, which remains the job of whoever inspected it. And it does not substitute for the financial records, which are what most audits actually turn on.

What it does is close the specific gap where a file is strong on invoices and weak on physical evidence, which is a common and entirely avoidable position to be in.

How to scope it

Three questions. What does your funding agreement actually require you to demonstrate, since that determines whether a single capture or a pair is needed. What is the boundary, as a file. And what quantities does the reporting ask for, because area, length, volume and count are not all served equally well by the same flight plan and the time to find that out is before the aircraft is in the air.

Frequently Asked Questions

What can a funder's reviewer actually verify from drone imagery?

Extent, location, surface condition, measured quantities and change between two dated captures. Those are the things a reviewer can independently check rather than take on trust. What imagery cannot establish is anything below the surface, anything inside a structure, the quality of workmanship or whether the work met a specification. Those stay with your invoices, inspection records and professional sign-offs. Aerial capture closes the physical evidence gap in a file; it does not replace the rest of the file.

We are already partway through the project. Is it too late for a before capture?

For a true baseline, yes, and the better response is to state that plainly in the file rather than work around it. A reconstructed baseline tends to fall apart under questioning in a way a stated gap does not. What you can still do is capture now, so that the remaining work has a before image, and rely on whatever genuinely dated material already exists for the original condition, such as public imagery with a known date or your own records. Capturing the current state immediately is worth doing in any case, because the window keeps closing.

How do you prove the imagery was captured on the date you say?

Through the record that travels with it rather than through a watermark. That means the unedited original files with their embedded capture metadata intact, the aircraft flight logs, a processing record showing what was done to the data and when, and derived products that trace back to those originals. If an auditor asks how the date is known, that chain is the answer. It costs nothing at capture time and it generally cannot be reconstructed later, which is why the retention decision has to be made up front.

What should we keep after the reporting is submitted?

The unedited original imagery rather than just the exported figures, the flight logs, any ground control coordinates with the datum and epoch written down, a short written method covering aircraft, sensor, capture parameters, processing software and the accuracy achieved with how it was established, the boundary file, and any reported quantity together with the surfaces or measurements it was computed from. Grant audits commonly arrive years after a project closes, by which time that package is the only thing that can answer a question about a number in the final report.

Can you tell us whether this satisfies our grant reporting requirements?

No, and you should be wary of a vendor who says yes. Reporting requirements vary by program and are set out in your own funding agreement, which is where that reading belongs, with you and your funder. What we can do is produce evidence that fits a requirement you define: a dated capture, a measured quantity against a stated boundary and base, a written method and a stated accuracy. If you can tell us what has to be demonstrated, we can scope a capture that demonstrates it.

Is the capture useful for anything other than the grant file?

Usually, and that is a reason to specify it slightly better than the grant strictly requires. The same dataset commonly serves an asset record, an insurance or valuation conversation, an engineering or planning input and the baseline for the next application. Getting the coordinate system written down, the boundary aligned with your other records, the deliverables in open formats and the originals retained costs very little at capture time, and it is what decides whether the data is still usable in three years.

Book a commercial drone flightMapping, inspection, multispectral and thermal across Alberta.Request a quote →or call 587-532-9000