Your BCA Report Might Be Non-Compliant. Here’s How to Tell

A BCA submission can look “professional” at first glance. The formatting is neat, the photos are there, the tables are filled in, and the conclusions sound confident. Then the project gets delayed anyway, because a few compliance gaps showed up when someone tried to verify the work.

If you are the one submitting the report, that delay is frustrating. If you are the one approving it, it’s a risk. Either way, the outcome will be rework, extra site time, and decisions made later than they should be.

This article offers a practical way to spot non-compliance early, using a simple 4-point check that you can use in your PFI Report; it is a verifiable chain of evidence that follows the TR-78 format suggested by the BCA. If any link in that chain is weak, the whole submission becomes fragile.

What “non-compliant” means

A report is non-compliant when it cannot be independently validated.

When BCA (or an appointed reviewer) looks at your report, they are essentially asking:

Was the inspection done to the required scope?

Were the methods appropriate?

Were the measurements traceable?

Can I reproduce the reasoning from raw evidence to conclusions?

If your report answers those questions without forcing the reviewer to “trust you,” you are already in the right path.

To enhance your chances of compliance and validation, consider leveraging advanced technologies and services like those offered by Aerial Property Solutions. Their expertise can provide invaluable support in ensuring that your BCA submissions meet all necessary requirements and standards.

The fastest self-check: the 4-link evidence chain

Here is the framework I use when I want to audit a report quickly. Every finding in a BCA-facing report should connect four links:

• Scope: What exactly was inspected, and to what requirement?
• Method: How was it inspected, and why is that method acceptable?
• Evidence: What raw data proves it (not just annotated screenshots)?
• Decision: What conclusion follows, and what action is recommended?

If any finding skips a link, you can expect pushback or rework.

Link 1: Scope is where most reports get vague

Non-compliance often starts with language like “general inspection of façade” or “checked roof condition.” That is readable, but not auditable.

A compliant scope usually ties three things together: asset identity, inspection boundary, and acceptance reference. In plain English, it should be clear what object was inspected, which parts were included or excluded, and what standard or requirement the inspection is measured against.

For example:

“Periodic Façade Inspection covering: concrete surfaces, render and plaster finishes, tile and stone cladding, curtain wall systems, precast elements, canopies, ledges, and fins. Internal courtyards and elements under separate A&A approval are excluded.”

• Findings classified as Safe, Require Repair, or Unsafe per BCA’s PFI framework.

If your report does not clearly state exclusions, the reviewer may assume you included everything, and you can get flagged later.

Don’t assume the scope is obvious from the photos, because photos show what you captured, not what you intentionally covered.

In addition to these aspects of reporting, it’s also essential to consider cybersecurity risk management measures. This includes understanding the potential risks associated with the assets being inspected and ensuring that appropriate measures are in place to mitigate these risks during the inspection process.

Link 2: Method needs to be defensible, not fancy

A method section becomes non-compliant when it reads like a tool list. Reviewers do not approve tools. They approve whether the method can reasonably produce the stated outcome.

A defensible method explains cause and effect:

If you are claiming dimensional accuracy, the report should explain how accuracy was achieved and verified.

For example:

• Centimetre-level accuracy achieved through drone mapping workflows.
• Measurement methods and verification processes documented within the report.
• High-resolution imagery captured using enterprise drones to support accurate assessment.

If you are claiming a condition assessment, the report should explain how visibility, angles, and coverage were ensured.

An example of what APS may put in their report:

• 100% façade coverage using systematic flight paths.
• 10% close-up imagery of all identified defects for detailed assessment.
• Multiple viewing angles to inspect recessed or obstructed areas.
• Thermal imaging used where required to identify potential hidden anomalies.
• Sequential image capture to ensure no façade sections are missed.

If you are claiming change over time, the report should explain how comparisons were aligned.

Example: APS uses consistent flight paths (zig-zag or snake-like patterns) , camera angles, and reference points to accurately compare façade conditions over time.

This is especially true for drone reports. It should be structured in a way that a non-drone reviewer can follow.

Transparent bias note: Our team exists because we believe lean inspection teams can outperform traditional, bloated approaches when technology is used correctly. That belief only holds when the method is explained clearly enough to stand on its own.

Link 3: Evidence must be traceable back to raw data

The most common compliance gap I see is “pretty evidence.” The report shows selected photos with arrows and labels, but the raw set is not referenced, not indexed, or not retrievable.

Traceability usually requires a few basics:

Each image or dataset should have an identifier.

The location or element reference should be consistent.

The capture date should be unambiguous.

If there is any processing, the pipeline should be stated at a high level, including what was adjusted and what was not.

A good internal test is: Could someone else open your evidence package and find the original source of a claimed defect in under two minutes? If not, the report is easy to dispute.

Next question: “Do I need to attach all raw data to the submission?”

Not always. But you typically need a clear evidence register and a retrieval path, plus enough metadata to prove the evidence is real and relevant.

Link 4: Decisions must follow from evidence, not confidence

Many reports become non-compliant at the final step, where the writing turns into conclusions that feel stronger than the evidence.

A compliant conclusion should state:

What was observed.

How severe it appears, based on stated criteria.

What is recommended next, and that the recommendation is proportionate.

Simple financial logic helps here. If the evidence only supports a low-confidence finding, the “cost of being wrong” is high if you recommend major rectification immediately. A more defensible approach is often staged: confirm first, then act.

That is not being cautious for the sake of it. It is aligning decision strength with evidence strength.

Practical red flags that often trigger rework

Most teams do not fail on one big thing. They fail on several small things that add up. If you skim your report and see any of the patterns below, it is worth tightening before submission.

• Undefined terms like “minor,” “significant,” “acceptable,” without a reference scale or criteria.
• No inspection limitations stated, even though every inspection has limitations (access, lighting, weather, occlusion).
• No version control on drawings, models, or marked-up plans.
• Inconsistent naming of the same element across pages (Grid A1 vs Column A1 vs Area A1).
• Findings without locations, where a defect is shown but not tied to an identifiable asset position.
• Recommendations that skip steps, such as “replace” without proposing confirmation tests when evidence is visual-only.

A simple “compliance rehearsal” you can do in 15 minutes

Before you submit, run this checklist

Pick your three most important findings and check each one against this list:

Location – Can you point to the exact spot (grid reference, drawing coordinate) in under two minutes?

Scope – Is this element actually inside your stated inspection boundary, or does it fall just outside it?

Method – Does the report explain how the result was achieved and verified, not just which tool was used?

Limitations – Are access, lighting, weather, and occlusion limitations stated, and is there a note on how each was handled (e.g., a close-range follow-up check, a reference object for scale, a repeat flight in better conditions)?

Evidence – Can you open the raw image or dataset behind this finding, not just the cropped or annotated version?

Consistency – Is the same element named the same way everywhere in the report (not “Grid A1” on one page and “Column A1” on another)?

Terminology – Are words like “minor,” “significant,” or “acceptable” tied to a defined scale, not left to judgment?

Decision strength – Does the recommendation match the confidence level, or does it go further than the evidence supports (e.g., recommending rectification when the evidence only supports a confirmation test)?

Where drone inspections help, and where they don’t

Drones are most useful when access is the biggest challenge. A 40-storey curtain wall façade, a canopy soffit without safe rigger access, or a precast joint 30 metres above ground are situations where a drone can get you closer, faster, and more consistently than traditional access methods.

They are also valuable when the same areas need to be reviewed over time, as repeatable flight paths make year-on-year comparisons much easier.

Drones are less useful when the inspection ends with just a collection of photos. A close-up image of a hairline crack only tells part of the story if there is no scale reference, location reference, or context showing where and how it was captured.

This is not a limitation of drones themselves, but a reminder that good inspection data needs to be properly organised and traceable, regardless of how you collected it.

A good conclusion

A BCA report is meant to reduce uncertainty and help all the involved parties make better decisions. For instance, a well-prepared report gives you a reliable record of your building’s condition that your team can use to track changes over time, plan maintenance works, and fix small issues before they become larger problems.

If you’d like to see what a BCA-compliant TR 78 report looks like you can download a sample here.