Reporting & assurance → Verification is where your organisation and its external verifier work on a verification engagement together: what is verified, which data the verifier sampled, the questions the verifier asked and your answers, and the findings.
EmitLedger records what both sides write and links it to the inventory data it is about. It does not decide anything: severity scales, materiality, sample sizes and coverage percentages are the verifier’s professional judgement, and nothing is built in.
Who can do what
| Who | What |
|---|---|
| Client admins and methodology owners | Create and edit engagements, assign verifiers and RFIs, respond to findings |
| Reviewers | See every engagement; answer and comment on RFIs |
| Data providers and country managers | See and answer the RFIs assigned to them |
| Executive viewers | See every engagement (read only) |
| External verifiers | Only the engagements they are assigned to: record samples, raise and decide RFIs, record and close findings |
External verifiers keep read-only access to the inventory data (dashboards, results, reports and the audit log). They never enter or change data, and they do not see other verifiers’ engagements.
Create an engagement
- Invite the verifier with the role External verifier in Settings → Members. Give the membership an end date: the verifier’s access ends when it expires.
- In Verification, click New engagement. Enter the Engagement name, the Verification body, the Verification standard (free text, optional) and the Verified period (from and to month, at most 36 months).
- Optionally enter Severity labels: the verifier’s own scale, separated by commas. No labels are built in.
- Choose the Assets in scope, or none for the whole organisation.
- Open the engagement and use Assign verifiers on the Overview tab.
The engagement status (Planning, Fieldwork, Findings, Closed) can be changed by a manager or an assigned verifier. A closed engagement is read-only until a manager reopens it.
The engagement page
The engagement page has four tabs:
- Overview: the verified period, standard, planned dates, sampling basis, severity labels, scope and assigned verifiers, and the review trail export.
- Sample: the samples the verifier recorded.
- RFIs: the requests for information, with their threads and evidence.
- Findings: misstatements and non-conformities.
People who only answer RFIs assigned to them see the RFIs tab, and the list RFIs assigned to me on the Verification page.
Sampling
The verifier chooses the Sampling unit (a source in a month, a source over the whole period, or an asset in a month) and the Method:
- Seeded random: the verifier enters the Sample size and, optionally, a Seed (one is generated when left empty). The same seed and the same data always select the same items, so the selection can be reproduced.
- Largest contributors: the verifier enters the Coverage (% of emissions). The largest items are selected until they reach that share of the total. There is no default percentage.
The population is the current results of the verified period and scope, in t CO₂e, on the engagement’s GWP set and consolidation basis. Preview shows the selection without recording it; Record sample stores it with its seed, parameters and a fingerprint (SHA-256) of the population, so a later change of the data is detectable. Recorded samples cannot be edited. From a sample item the verifier can Raise RFI directly.
Requests for information
The verifier raises an RFI about the engagement as a whole or about one object: an emission source, a reporting period, an emission result, an import or an evidence file. The object must be in the engagement’s scope and period.
- A client admin or methodology owner sets the Assignee (someone who can answer RFIs; a data provider only for an asset in their scope) and can change the Due date.
- The assignee attaches evidence and clicks Send response. The RFI becomes Responded.
- The verifier clicks Accept response, Reopen (with a comment) or Close RFI.
Both sides can comment at any time. The thread, including every status change, cannot be edited or deleted. Evidence is added while the RFI is Open and then stays with it (Evidence files).
The assignee, the verifiers and the managers are notified by email and on the mobile app when something needs their attention. Overdue RFIs are marked Overdue.
Findings
The verifier records each finding with its Type (Misstatement or Non-conformity), a Severity from the engagement’s labels, a description, the asset and the related RFIs.
A client admin or methodology owner writes the Client response and can link the Restatement that corrects the data. A finding never changes data by itself: the correction goes through a restatement (request, approval, reopen, correct, recalculate, re-lock). The verifier then closes the finding with a Resolution (Corrected, Not corrected or Withdrawn), or reopens it.
Review trail
On the Overview tab, Export Excel, Export CSV (ZIP) and Export JSON prepare the review trail of the engagement: the engagement and scope, the verifiers, the samples and their items, the RFIs with their threads and evidence file names and SHA-256 fingerprints, the findings, and the linked audit events. Download it from Reports when it is ready. Every action in the workspace is also recorded in the audit log.