OCEANS™ VERIFY EVIDENCE

Keep every emissions result connected to its evidence

Trace reported emissions back to source records, activity data, emission factors, assumptions, and review decisions—all within one structured workflow.

Illustrative OCEANS™ Sustainability result connected to its calculation, emission factor, activity data, source document, assumptions, and review state Illustrative product view. Example data shown.

Know where each number came from, how it was calculated, and what still requires review.

Explore the platform

The image above traces a result back to its source. Read the other direction, the logical order is:

  1. Reported result
  2. Calculation
  3. Emission factor
  4. Activity data
  5. Source document

This example demonstrates connection and review readiness—not independent certification.

Reporting a number is easy. Defending it is harder.

Spreadsheet-based work often separates supporting documents and calculation notes from the final reported result. When someone asks a question about a number, the answer lives in someone's inbox instead of with the number itself.

Where did this value come from?

Who submitted and reviewed it?

Which emission factor was used?

Was the result measured or estimated?

What changed from the previous reporting period?

Is supporting documentation available?

OCEANS™ Sustainability keeps these answers connected to the reported information.

Transparent review

Verification begins with a visible evidence trail

Verify Evidence means organizing, tracing, and reviewing the information supporting a result. It helps your team assess whether required records are present, calculations are documented, assumptions are visible, and internal review steps are complete.

OCEANS™ Sustainability supports evidence preparation and traceability. It does not replace independent assurance or certify that customer-submitted information is factually correct.

Illustrative transparent-review workspace distinguishing OCEANS™ platform support from independent external assurance Illustrative product view. Example data shown.

Platform support (OCEANS™)

  • Organize

    Capture and link source records.

  • Trace

    Maintain calculation traceability.

  • Review

    Apply internal review and approvals.

  • Document

    Keep calculation and assumptions on record.

Independent assurance (external)

An external process performed by a qualified provider — not performed by OCEANS™. Its scope, criteria, and outcomes are determined by that provider, and its results are issued by the provider, not by OCEANS™.

Follow every result back to its source

Illustrative evidence lineage tracing an emissions result through source data, factor, method, assumptions, and review history Illustrative product view. Example data shown.

Source record

Invoice, bill, operational record, supplier file, or supporting document.

Activity data

Quantity, distance, spend, energy, mass, or another supported business activity.

Emission factor

Documented factor used to convert activity into emissions.

Calculation method

Formula, unit conversions, classifications, and methodology.

Assumptions and estimates

Exclusions, proxies, extrapolations, or limitations.

Review history

People, comments, states, decisions, and changes.

What is missing?

Gaps in the evidence chain are surfaced directly against the result, instead of being discovered later.

What changed?

When a value is revised, the prior version and the reason for the change stay attached to the result.

How it works

A consistent review process for every reporting period

Illustrative six-stage evidence review workflow with owners, issues, clarification requests, decisions, and internal reporting status Illustrative product view. Example data shown.
  1. 01

    Attach evidence

    Connect supporting records to submitted activity data.

  2. 02

    Check completeness

    Review required values, units, periods, entities, and documentation.

  3. 03

    Review the calculation

    Inspect category, factor, method, assumptions, and result.

  4. 04

    Request clarification

    Return incomplete or inconsistent records to the contributor.

  5. 05

    Record decisions

    Preserve review comments, explanations, and approved changes.

  6. 06

    Approve for reporting

    Mark internally reviewed information as ready for dashboards and reporting outputs.

Keep supporting records where they belong

Supporting documents stay associated with the relevant activity, calculation, entity, and period — including records such as:

  • Utility bills
  • Fuel invoices
  • Meter records
  • Procurement exports
  • Travel statements
  • Freight reports
  • Waste records
  • Supplier submissions
  • Renewable-energy documents
  • Methodology notes

When a stakeholder asks for supporting information, your team can locate the relevant record without reconstructing the calculation process.

Illustrative evidence workspace showing a utility bill connected to activity data and an emissions calculation, with unlinked records requiring attention Illustrative product view. Example data shown.
Illustrative internal review control center with accountable roles, outstanding actions, comments, and decision notes Illustrative product view. Example data shown.

Review and accountability

Make ownership and review status visible

Contributors, data owners, calculators, reviewers, and reporting approvers can each understand responsibility and outstanding work as a reporting period moves toward completion.

  • Contributors
  • Data owners
  • Calculators
  • Reviewers
  • Reporting approvers

Everyone can understand what requires attention, while the sustainability team retains oversight of the reporting process.

Find issues before information reaches a report

Examples of information a structured review can surface:

Illustrative review-flags queue for missing evidence, units, duplicates, period changes, assumptions, factors, approvals, and estimate disclosures Illustrative product view. Example data shown.
Missing evidence
Missing or invalid units
Possible duplicates
Unusual period changes
Incomplete organizational details
Unsupported assumptions
Unassigned factors
Calculations awaiting approval
Estimates requiring disclosure

A flag prompts review; it does not certify accuracy.

Make assumptions visible—not invisible

Estimates and proxies are sometimes necessary, particularly for Scope 3. Each one can carry the context needed to understand it:

  • Rationale
  • Method
  • Underlying source
  • Exclusion or limitation
  • Reviewer
  • Expected replacement date

Transparent uncertainty is more credible than unexplained precision.

Understand what changed, when, and why

Changes to source data, factors, assumptions, and structures can be investigated through the context retained alongside them, including:

  • Creation and modification dates
  • Previous and current values
  • Contributor and reviewer activity
  • Explanations for the change
Illustrative assumptions register and side-by-side change history showing methods, limitations, contributors, reviewers, and reasons for revision Illustrative product view. Example data shown.
Illustrative OCEANS™ Sustainability working session preparing source records, calculation documentation, factor references, assumptions, and review history for external scrutiny Illustrative product view. Example data shown.

Prepare for scrutiny

Organize information before an external review begins

Before an external review, your team can organize:

  • Source records
  • Calculation documentation
  • Emission-factor references
  • Assumption registers
  • Data-gap explanations
  • Review histories and period comparisons

OCEANS™ Sustainability supports evidence preparation and traceability. Independent verification or assurance must be performed by a qualified external provider where required.

Build confidence through transparency

Answer questions faster

Locate the source, method, and evidence behind a reported value.

Improve accountability

Make contributors, reviewers, and outstanding actions visible.

Surface reporting gaps earlier

Identify unsupported or incomplete information before publication.

Preserve institutional knowledge

Retain explanations in the workflow rather than individual inboxes.

Improve over time

Use documented gaps and assumptions to prioritize stronger data collection.

Evidence should remain connected throughout the process

Reported information retains its relationship to the operational records and calculation decisions behind it, through every stage of the workflow.

  1. Connect data
  2. Calculate emissions
  3. Verify evidence
  4. Prepare reports

Make your emissions information easier to trace and explain

See how OCEANS™ Sustainability helps your team connect supporting records, calculations, assumptions, and review decisions before information reaches stakeholders.