An evidence matrix turns a CAE dossier into a controllable system: it links each eligibility condition and calculation input to a specific record, owner, version and status. No universal template replaces the applicable catalogue sheet or methodology. The matrix is valuable because it translates the current or transitionally applicable version and current procedure into verifiable tasks, without creating new requirements or concealing gaps.
Design the matrix from the applicable rule
Begin with a row inventory, not a folder inventory. Read the applicable catalogue sheet or non-standardised methodology and split every eligibility condition, formula input, date constraint and required attachment into a separately testable row. Give the row a durable identifier such as EL-04 or CAL-07, quote the controlling passage, and record the applicable version. This prevents one broad label such as technical report from hiding several facts that must be demonstrated by different records.
Design the columns around decisions a reviewer must make. Alongside the requirement, capture the fact asserted, source filename, page or cell, site and asset identifier, evidence date, document owner, reviewer, status and resolution note. Calculation rows should also name the variable, unit, transformation and destination cell. Mark whether a record is original, a controlled copy or still expected. The matrix then works as a navigation layer rather than becoming another unverified summary of the dossier.
Assign evidence, owners and versions
Populate the matrix from primary records while they are created. Contract staff can map rights and dates; site teams can map equipment and commissioning evidence; the calculation owner can map quantities, ratings and assumptions. The authorised CAE scheme participant should receive a view that distinguishes complete, conditional and blocked rows. A file should not be marked complete merely because it exists: its content, signatory, location and timing must support the precise assertion assigned to that row.
Use bidirectional references. Each matrix row points to an immutable file and exact location, while filenames or document covers carry the relevant row identifiers. For a photograph, include image code and caption; for an invoice, line number; for a spreadsheet, workbook, tab and cell. Preserve source files separately from redacted or converted copies. If a record is replaced, keep its earlier checksum or version reference and explain why the successor is authoritative instead of silently overwriting project history.
Test consistency and handle exceptions
Run horizontal and vertical tests before declaring coverage. A horizontal test follows one requirement across contract, invoice, photograph, commissioning record and calculation. A vertical test selects one asset and checks every relevant requirement from initial condition through final quantity. Compare addresses, serial numbers, models, dates, powers, units and parties. Duplicate files do not increase coverage, and several mutually inconsistent records are not stronger than one. Log contradictions as issues with an owner and consequence, not as informal comments.
Treat exceptions as controlled branches. If a specified model was substituted, link the approval, delivery record, final nameplate and recalculated input. If an address is abbreviated, add a documented site crosswalk rather than editing the source. A missing essential record cannot be cured by a retrospective assertion presented as contemporary evidence. Determine whether the applicable rules admit another source, whether the affected quantity must be reduced, or whether that portion cannot proceed, and preserve the rationale for the decision.
Close and hand over a reproducible dossier
At the documentary cut-off, freeze the matrix and the referenced package together. Resolve broken links, remove temporary paths, restrict personal data, and verify that every completed row opens the intended record. Produce separate lists for closed rows, accepted limitations and open blockers. The matrix version, dossier index and calculation version must agree. Any later addition should enter through a change log stating requester, reason, files affected, review performed and whether the calculation or verification scope changed.
Hand over a reproducibility test, not just a spreadsheet. Ask someone who did not assemble the dossier to trace a sample of eligibility conditions and calculation inputs without oral guidance. Record failed searches, ambiguous filenames and unexplained transformations, then correct the navigation. The matrix supports independent verification and later processing, but it does not create eligibility or guarantee issuance. The applicable sheet or methodology, current procedure and competent decisions remain controlling when an internal row conflicts with them.