Aggregation can make multiple savings actions practical to process, but it does not turn heterogeneous actions into one item of evidence. The applicable threshold and rules must be checked in current legislation and procedures. Every action retains its own eligibility, calculation, ownership and evidence, while the aggregated dossier also needs common controls.
Confirm threshold and boundary
Aggregation begins with the current minimum threshold and procedural perimeter, checked in the legislation and filing guidance applicable on the intended submission date. Do not rely on a threshold remembered from an earlier version or assume that any energy total may be combined. Record the required unit, eligible types of action, relevant period and filing route. The threshold is an entry condition for the dossier; reaching it does not make each underlying action eligible or complete.
Create an action-level inventory before forming a batch. Each row should identify site, holder, technical sheet or methodology, completion date, calculated savings, evidence status, verification readiness and transfer status. Keep raw values and units visible, with controlled conversions. A total at the top of a sales pipeline cannot replace this register because it hides missing documents, duplicated sites and incompatible methodologies. Only rows meeting declared maturity criteria should count toward the submission candidate.
Classify actions before adding
Classify actions into ready, remediable, waiting and excluded groups. Ready means the evidence and rights package has passed defined checks, not merely that installation is complete. Remediable items need an owner and deadline; waiting items depend on an event such as invoice receipt; excluded items retain the reason for audit. This triage allows the coordinator to forecast a credible cut-off while preventing weak actions from borrowing apparent quality from stronger members of the lot.
Technical calculation remains individual even when administration is shared. Apply the correct sheet version or non-standard method to each action, preserve inputs and evidence, and then reconcile the approved aggregation rule. Similar equipment at different sites may have different dates, baselines or operating conditions. Sampling or common evidence should be used only where the governing method permits and the factual population supports it. Aggregation does not turn one representative invoice or photograph into proof for every installation.
Design a traceable batch
Rights and transfer controls also operate per action. Confirm the original holder, identify prior commitments and connect each CAE agreement to the site and savings included. An aggregator's master contract may organise cooperation, but it cannot cure a missing transfer or confer rights the counterparty did not hold. Maintain a quantity ledger to prevent duplication across batches, especially when projects move between cut-offs or a partial amount is retained for a later filing.
Design a buffer above the threshold based on identified attrition, not a promise that all volume will survive review. The buffer may reflect open evidence items, recalculation exposure or possible withdrawals, with each assumption documented. Too little resilience risks falling below the applicable requirement after a reduction; excessive overloading creates unnecessary coordination and delay. Scenario testing should show which mature actions can replace a withdrawn row without double filing or disturbing completed verification work.
Manage withdrawals and reductions
Batch contracts need clear entry, exit and cut-off rules. Specify evidence deadlines, authority to remove an action, cost allocation, treatment of verification findings, consideration after quantity adjustment and consequences of holder withdrawal. Participants should know that inclusion in a preliminary list is conditional. A common unit price or service fee is a contractual matter, not the FNEE equivalence or proof of a general market price, and it cannot guarantee that the lot will clear the threshold.
Operate a single reconciliation from inventory through verification and filing. Version the batch list, freeze identifiers at each hand-off and record every addition, removal or quantity change. The verifier's scope, technical annex, agreements and submission total should resolve to the same population. Automated checks can identify duplicate identifiers, unit errors and missing fields, but a named reviewer should investigate exceptions. Silent spreadsheet edits are particularly dangerous when several coordinators prepare parallel batches.
Close without promising volume
If review reduces savings, assess both the affected action and the aggregate condition. Correct clerical issues through the controlled process, recalculate totals and decide whether substitution is permitted and operationally sound. Do not rewrite historical evidence or move the same action into another live dossier to protect a forecast. Communicate revised contractual quantities and costs according to agreed rules. A failed row may teach a portfolio control lesson without invalidating unrelated, well-supported actions.
Final closure requires tenable headroom, complete action files, reconciled rights and a signed decision on residual exceptions. Archive the submitted batch and its calculation so later changes are distinguishable from the filed version. Even a carefully designed lot remains subject to verification and administrative treatment; neither aggregation nor excess estimated volume guarantees recognition. The method improves efficiency and traceability while preserving the principle that every included saving must stand on its own applicable rules and evidence.