Skip to main content
Issues may be created during reviews of project submissions to indicate non-compliance with requirements from the Isometric Standard, Protocols or Modules. Issues can be created during Pre-screen, Validation or Verification stages of a project’s validation and verification. All issues on a particular submission must be resolved before it can be validated or verified, unless the issue is a Forward Action Request.

​
Issue scope

Issues may be created for: Issues will be created by Isometric’s team during a pre-screen review, or by a project’s assigned verifier during validation or verification.

​
Issue types and statuses

Issues can have one of the following types as defined by the ISO-14064-3 standard for verification and validation of GHG statements:
  • Clarification Request
  • Error
  • Misreport
  • Misrepresentation
  • Nonconformity
  • Omission
The issue will show as either Open or Resolved, depending on the status.
Forward Action Requests: issues may be created as a Forward Action Request (FAR). This notes an action that is not required to be addressed at the current review stage, but will be at a future stage. Forward Action Requests will not block completion of a project submission validation or verification.

​
Log of Issues

All issues related to a project are documented in the Log of Issues section of a project. The Log of Issues can be filtered by status, type and who they are assigned to. Click on an issue to view details about the submission it was created on: for example, an individual requirement in the Project Design. The links at the top of the issue details will take you to the original submission in the product, where you can make any changes required to resolve the issue.
For Requirements on Project Designs or Feedstocks, the ownership of the requirement will pass between the supplier, Isometric and the assigned verifier depending on the review stage. The requirement owner designates the party responsible for the next action.After creating issues on a requirement that is owned by Isometric or a verifier, they will pass ownership back to the supplier by requesting changes to your submission. The submission will not be editable until changes are requested.Submissions in the Carbon Accounting part of the project (LCA, Project Emissions and GHG Statements), can be edited at any time and resubmitted for review.
Updates about issues will be sent by email, batched on a 24 hour basis, to all team members with Admin or Editor roles.

​
Responding to issues

When an issue is raised, you may edit the relevant submission and add a comment on the issue describing any change(s) made to resolve it. If the change requested in an issue is unclear you can also use the comment thread to ask for clarification. The reviewer assigned to your project will be notified of your comment and can re-review your submission.
When responding to an issue in your project’s carbon accounting you may have to delete a component or datapoint. Issues that were originally created for a component or datapoint will continue to exist and can be navigated to from the LCA issue sidebar or the Log of Issues. If the linked data has been deleted, they will be marked as ‘Disconnected’.
Once all issues on a submission have been resolved, the submission will be able to progress to the next stage.

​
Issue assignees

The issue assignee indicates who is responsible for the next action on the issue. Issues can be assigned to an organization as a whole, or to a specific user (within your own organization). When an issue is published, it will be assigned to the supplier organization to resolve. Once the supplier has resolved the issue, marking the issue as addressed will pass the issue back to the issue creator (Isometric or the verifier) for review. At any time, you can comment and reassign an issue to another party if seeking clarification.