Aviation & SAF
View this service
From Plan to Practice: Assessing the Implementation of an Approved Monitoring Plan
A Monitoring Plan can look perfect on paper.
The responsibilities are clearly assigned. The data sources are identified. The monitoring methodology is described. Control activities are documented, data gap procedures, and the process leading to the final emissions report appears complete.
But for a verifier, this is where the assessment begins – not where it ends.
The fundamental question is simple:
Does what happen in practice match what is described in the Monitoring Plan?
Answering that question takes the verifier beyond document review and into the operator’s actual monitoring environment: the people performing the activities, the systems processing the data, the control activities operating behind them and, ultimately, the evidence supporting the reported figures.
This is where a Monitoring Plan moves from being a regulatory document to becoming a basis for verification.
Consider a Monitoring Plan stating that fuel consumption is determined from a specified operational data source.
At the document level, the methodology may be clearly described. During verification, however, the verifier follows the process further. Where does the fuel information originate? How does it enter the monitoring system? Is it transferred automatically or manually? Is the same source described in the Monitoring Plan actually being used? Are any transformations performed before the data reach the emissions calculation?
The verification journey therefore follows a logical path:
What is documented → What is actually performed → What evidence exists → What is ultimately reported
This distinction is central to verification.
One of the principal aspects of implementation is establishing traceability through the operator’s fuel data flow. A typical fuel data chain may be represented as:
Fuel supplier/operational record → Fuel data capture → IT system → Data processing → Fuel quantity used for emissions calculation → Emissions Report
The verifier may select fuel records and trace the reported fuel quantity backwards through this chain to the original source record. This allows the verifier to assess whether the fuel data have been correctly captured, transferred and processed, and whether any manual adjustments, unit conversions or calculations have been appropriately applied before the value is included in the emissions calculation.
For example, where the Monitoring Plan identifies a fuel delivery record as the primary source, the verifier may compare the fuel quantity reported in the emissions dataset with the corresponding source record and examine the intermediate processing steps. This provides evidence that the fuel quantity ultimately used to calculate emissions is traceable to an appropriate source and has been processed in accordance with the documented monitoring methodology.
A verifier does not simply work through the Monitoring Plan line by line and apply the same level of testing everywhere.
Verification is risk-based.
Consider two monitoring environments. In the first, operational data move through controlled system interfaces into the emissions calculation with limited manual intervention. In the second, data pass through several systems, spreadsheets and manual adjustments before reaching the final report. Both may ultimately produce the correct result, but they do not necessarily present the same verification risk.
The verifier therefore identifies where a material misstatement or non-conformity could arise. Particular attention may be given to complex data flows, manual interventions, system changes, missing information, outsourced processes, changes in methodology and areas where controls are relied upon. This risk analysis shapes the nature and extent of verification activities.
The objective is not to examine every individual transaction. It is to obtain sufficient and appropriate evidence to support the verification conclusion.
The monitoring plan frequently describes control activities intended to protect the integrity of reported information. There may be checks for missing flights, duplicate records, unusual fuel values, missing data, aircraft identification, calculation errors or differences between independent data sources.
For the verifier, describing a control activity and operating a control activity are two different things.
If the Monitoring Plan states that flight completeness is reconciled periodically, evidence should demonstrate that the reconciliation took place. If abnormal fuel values are subject to review, the verifier may examine whether such reviews can be evidenced.
The verifier’s role is to assess whether the relevant controls have been implemented as represented and to evaluate the verification risk.
Aviation operations rarely remain static.
Aircraft enter and leave fleet. IT systems are replaced. Responsibilities change. New data sources become available. Wet-leased operations may be introduced. Monitoring methodologies or data-gap procedures may change. The actual monitoring environment can therefore evolve while the Monitoring Plan remains unchanged. During verification, differences between documented and actual practice must be understood and evaluated.
Importantly, a difference between the Monitoring Plan and its implementation does not automatically constitute a material problem. The verifier evaluates the nature and extent of the deviation, whether it is permitted under the applicable regulatory requirements, and whether it could result in an omission, misstatement, or incorrect application of the approved monitoring methodology that could materially affect the reported information. Where the deviation affects the reliability or completeness of the reported data, it may lead to a finding such as a misstatement, non-conformity, or non-compliance, based on objective evidence and the definitions established by the applicable verification framework.
The Monitoring Plan may be where the verifier starts, but the evidence is what ultimately supports the conclusion.
A robust verification process connects several elements:
Regulatory requirements → Approved Monitoring Plan → Risk Assessment → Actual implementation → Objective evidence → Verification conclusion
That sequence also defines the boundaries between the parties involved. The operator establishes and operates the monitoring and control system. The respective authority performs its regulatory approval or acceptance functions where required. The verifier independently assesses the reported information and the evidence demonstrating whether the relevant monitoring arrangements have been implemented in accordance with the applicable requirements.
Ultimately, verification is not about confirming that a well-written Monitoring Plan exists.
It is about determining whether the story told by that Monitoring Plan is the same story told by the systems, records, data and evidence behind the final report.
