Carbon Assurance
Long-cycle programs where regulation, capital, and grid reliability define the pace.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Outcome & Compliance Discovery
Align on reporting deadlines, target registries, stakeholders, decision criteria, and the success signals the assurance opinion must satisfy.
Discovery Questions
Reporting calendar and highest-stakes expectations
- Tell me the firm deadlines you must meet this year for GHG reporting, registry submissions, and investor disclosures
- Select the reporting outputs you expect to present with third-party assurance
- How many weeks before each filing does your finance or legal team need a final assurance report in hand
- Describe the concrete success signals the assurance opinion must include to avoid investor, regulator, or registry pushback
- Who within your organization has the final sign-off to publish the assurance opinion and associated disclosures
If the assurance shifts the headline, what happens next
- If an assurance opinion included a qualification on a material source, could you still meet your planned disclosure date
- Identify the inventory components, estimation methods, or project controls you expect will draw the most auditor scrutiny
- When was the last time an external assurance or audit caused you to change a public number or disclosure, and what happened
- Estimate the likely operational or market impact if a material qualification appeared right before an earnings call
- Which single potential finding would make you stop the engagement or delay publication immediately
Who needs this opinion and how will they use it
- Who is the primary external audience that must accept the assurance opinion for this engagement to succeed
- Select the internal stakeholders who will actively use the opinion in decision making
- Explain how your audit committee or board differentiates a qualified assurance opinion from an unqualified one in practice
- If investors insisted on reasonable assurance rather than limited assurance for a material Scope 3 category, can your timetable, budget, or data access accommodate that change
- Name the stakeholder whose rejection of the opinion would stop the deal from progressing
Where your numbers come from and where they break
- Walk me through the data flow from source meters, invoices, or models to the GHG numbers you include in reports
- List the primary systems, spreadsheets, or external feeds that hold the emission data we would need to test
- Point to the dataset, calculation, or assumption that feels least mature or is hardest to reproduce reliably
- Provide the frequency and named owner for each key data source you just listed
- Confirm whether your team can provide read-only access, API extracts, or signed data extracts for site-level evidence within four weeks of a fieldwork start
Operational readiness, constraints, and known gatekeepers
- Assuming your target registry or regulator will inspect methods, which internal approval or legal review must happen before fieldwork begins
- Do you have named data owners for each material emission source and will they be available for interviews during fieldwork
- Who within your IT or data team owns API access or extraction rights for the systems we would need to connect to
- Are there contractual, vendor, or confidentiality restrictions that could prevent sharing the raw evidence we need, such as meter logs or supplier invoices
- What single readiness gap, if unresolved within four weeks, would force us to postpone fieldwork
The other options you are weighing
- Identify the alternative routes you are actively evaluating instead of contracting an external assurance provider
- Which attributes of an incumbent or internal approach would have to remain true for you to stick with it rather than switch
- Have you already requested proposals from any of the following vendor types
- Provide any reference checks, prior assurance outcomes, or lessons from past engagements that have shaped your view of competitors
- If an internal solution promised complete control over timing but not independence, would that be acceptable to your investor audience
Timeline, budget, and decision triggers that move things quickly
- If the assurance opinion does not arrive before your next earnings call, what immediate consequence would that create for your team
- How much budget has been tentatively allocated for assurance in this cycle
- By when do you need a signed engagement letter to meet your target timeline
- List the decision criteria that would make you sign quickly after a readiness assessment shows sufficient data quality
- If a short pilot could demonstrate the numbers and controls, what would stop you from signing within one week
Final deal killers, authority, and next steps
- In your target timeline, which approvals or legal steps would immediately prevent the engagement from starting
- Provide the names, roles, and best contact method for the people who must approve the statement of work
- Do you have mandatory contract terms, insurance, or data protection clauses we must accept before starting
- Share any non-negotiable clauses or commercial conditions that would cause you to walk away from a proposed engagement
- If we can meet your timeline, budget band, and provide a sample opinion that aligns with your registry and investor needs, would you be prepared to authorize a pilot next week
-
Assurance Experience
Map how the assurance approach, standards, and fieldwork will address investor, regulator, and registry expectations using buyer-specific scenarios.
Assurance Experience
- Assurance Experience Session
- Confirm the current state and its cost
- You confirm the demonstrated assurance plan meets investor, regulator, and registry expectations for the selected reporting scenario.
- Deliver a tailored assurance approach memo that lists standards to be used, required evidence, proposed sampling plan, and a timeline keyed to your reporting deadline.
- You confirm the proposed fieldwork depth and evidence list represent an acceptable tradeoff between cost and disclosure risk.
- Map consequence to priorities
- Provide the final reporting deadline and one representative dataset or monitoring report for the selected scenario.
- You agree on the next concrete steps and a timeline required to lock scope and avoid deadline slippage.
- Walk through your selected reporting scenario
- Share any registry protocols, investor acceptance criteria, or RFP evaluation priorities that must be satisfied.
- Demonstrate how Scope 3 estimation and sampling will be handled
- Confirm a decision committee review date to finalize scope, fees, and authorization before fieldwork scheduling.
- Validate the mapped approach
- Assurance Experience Session
- Assurance Experience Deck
- Assurance Experience Brief
- meeting
- slides
- document
-
Engagement Scope
Define the assurance boundary, level of assurance, applicable standards, materiality, registries, and sampling approach.
Scope Configuration
- Limited assurance engagement — Scope 1 and Scope 2 emissions
- Limited assurance engagement — Scope 3 emissions categories
- Reasonable assurance engagement — Scopes 1, 2, and 3
- Assurance of regulatory ESG climate disclosures (SEC/CSRD)
- Registry-standard carbon credit project verification and validation
- Annual verification for recurring credit issuance
- Site visits and on-site emissions verification
- Source-to-report data sampling and calculations testing
- Testing of internal controls over GHG reporting
- Audit of GHG calculation models and emission factors
- Preparation and delivery of assurance opinion and management letter
- Independent review of science-based targets and net-zero claims
Scope Questions
Limited assurance engagement — Scope 1 and Scope 2 emissions
- Which standards will you require for this limited assurance (ISAE 3000, ISAE 3410, AA1000AS)?
- Identify the emission sources for Scope 1 you expect to include (for example: stationary combustion, mobile fleet, process emissions).
- Select the approach you want for Scope 2 accounting: location-based, market-based, or both.
- How many reporting sites or facilities are material for your Scope 1 and 2 inventory?
- List the source documents you can provide for fuel and electricity activity data (meter readings, fuel purchase invoices, utility bills).
- Describe your current GHG calculation tool or model used for Scope 1 and 2 (for example a spreadsheet workbook, ERP extract, or a vendor carbon-calculation tool).
Limited assurance engagement — Scope 3 emissions categories
- Identify the Scope 3 categories you expect to include using the GHG Protocol category names (for example: purchased goods and services, business travel, upstream transportation and distribution).
- How many Scope 3 categories are likely to be material based on your internal materiality threshold (estimate the count)?
- List the primary data sources that will support your Scope 3 estimates (for example supplier emissions factors, spend data exports, LCA datasets).
- Who in your organization owns supplier data collection and can provide supplier-specific emission factors?
- Describe the estimation methods you currently use or plan to use for material Scope 3 categories (spend-based, supplier-specific, hybrid, life-cycle assessment).
- Indicate any registries, investors, or reporting recipients that require assurance on Scope 3 categories (for example an investor requesting limited assurance on selected categories).
Reasonable assurance engagement — Scopes 1, 2, and 3
- Select the standard that should govern the reasonable assurance engagement (for example ISAE 3000 or ISAE 3410).
- Specify the materiality threshold you want applied for the opinion (for example a percentage of total tCO2e or an absolute tCO2e threshold).
- State how many reporting years you want covered under reasonable assurance (for example current year only, current plus prior year).
- Do you have management representation letters and governance documentation available for the assurance period?
- Estimate your approximate total annual tCO2e magnitude to help design sampling and materiality (choose range).
- Identify any high-risk sources that will require expanded testing under reasonable assurance (for example biogenic emissions, complex process emissions, major estimated Scope 3 categories).
Assurance of regulatory ESG climate disclosures (SEC/CSRD)
- Specify which regulatory regimes apply to your filings (for example U.S. SEC, EU CSRD, or a national regulator).
- Enumerate the disclosure artifacts that will require assurance (for example climate-related financial disclosures, GHG tables, Scope breakdowns, narrative sections).
- Who in your organization signs or approves regulatory climate filings (for example CFO, Head of Reporting)?
- When are your filing deadlines and how many months in advance must assurance be completed to meet external filing requirements?
- Provide any regulatory formats or submission schemas required for your filing (for example XBRL tagging, registry monitoring report templates).
- Explain how your ESG disclosure controls and evidence link to financial reporting controls (for example shared systems, reconciliations, or journal entry linkages).
Registry-standard carbon credit project verification and validation
- Choose the registries and registry standards the project will pursue (for example Verra VCS, Gold Standard, ACR).
- State the project type and methodology that applies (for example afforestation/reforestation, avoided deforestation, renewable energy, methane capture).
- Provide the expected credit vintage and issuance frequency for the project (for example annual issuance, multi-year).
- Enumerate the monitoring report and baseline documents you will supply for validation or verification (for example monitoring plan, project design document, baseline study).
- Indicate whether prior validation or verification statements exist for this project and provide the report dates if available.
- What evidence will validate successful registry verification (for example registry-issued verification statement, issuance of credits to the project account)?
Annual verification for recurring credit issuance
- Specify which months define your standard annual monitoring period for credit issuance.
- State how many issuance cycles per year you currently expect for this project.
- Do you require that prior year verification findings are closed before we perform the current-year verification?
- Describe the continuity or monitoring systems you use between years (for example continuous sensors, cumulative activity logs, telemetry).
- Who will act as the primary contact for scheduling recurring verification and coordinating annual evidence delivery?
Site visits and on-site emissions verification
- Estimate how many sites or facilities will require on-site visits and briefly list their primary emission activities.
- Specify the types of on-site evidence that will be available during visits (for example meter logs, fuel tanks, maintenance logs, emission control system records).
- Are there access constraints, safety requirements, or permits we must plan for before scheduling site visits (for example PPE, confined-space entry, security clearance)?
- When do you prefer site visits to occur relative to operations (for example during peak production, after maintenance, during representative operating conditions)?
- Who will coordinate site logistics and provide site owner names and local contacts for each facility?
Source-to-report data sampling and calculations testing
- Provide the populations that should be included in the sampling frame (for example meters, invoices, suppliers, vehicle odometer logs).
- Choose the sampling approach you expect us to apply (statistical sampling, judgmental sampling, stratified by emissions magnitude).
- Estimate the size of the source populations to be sampled (for example number of meters, number of invoices, number of suppliers).
- Provide the specific calculation models or spreadsheets we should test (for example named GHG calculation workbook, emission factor lookup table, ERP extract).
- How will you provide access to source data for sampling (for example secure file transfer, direct database query, API access)?
Testing of internal controls over GHG reporting
- Specify the control frameworks or internal policies that govern your GHG reporting processes (for example internal SOPs, ISO 14001, financial control framework).
- Who are the documented control owners responsible for data collection, reconciliations, and quality assurance?
- Confirm whether documented control narratives and process flowcharts exist for your source-to-report GHG processes.
- What acceptance criteria will confirm controls are operating effectively for the assurance period (for example no material exceptions in control tests, remediation of prior findings)?
- List any control remediation timelines that must be met prior to fieldwork and state the owners for each remediation.
- Are automated reconciliations in place between source systems and your GHG ledger or master calculation workbook?
Audit of GHG calculation models and emission factors
- Indicate the emission factor sources you rely on for calculations (for example national inventory factors, IPCC guidance, supplier-specific emission factors).
- How often are emission factors updated in your models and who in your organization approves updates?
- Provide the calculation model versions and change logs that will be supplied for audit testing.
- Are there custom assumptions or default conversion rates used for Scope 3 categories (for example spend-to-emission conversion factors)?
- Specify tolerance thresholds for calculation differences that would trigger remediation or rework (for example >5% variance by source).
Preparation and delivery of assurance opinion and management letter
- Which deliverables do you expect at engagement close (for example assurance opinion, signed management letter, observation catalogue)?
- When is the target report date and what is the hard deadline for issuing the assurance opinion?
- What evidence will validate opinion readiness for issuance (for example complete evidence package, signed management representation, resolution of material exceptions)?
- Who on your side will approve the final opinion and sign the management letter prior to publication?
-
Agreement & Authorization
Finalize commercial and legal terms, fees, timelines, deliverables, acceptance criteria, and data-access authorizations.
Agreement Modules
- Non-Disclosure Agreement (NDA)
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Fee Schedule & Payment Terms
- Data Access & Fieldwork Authorization
- Data Processing Agreement (DPA)
- Registry Submission Authorization
- Acceptance Criteria & Deliverable Sign-off
- Change Order Agreement
- Termination & Amendment Addendum
- Insurance & Indemnity Schedule
- Site Safety & Background Check Authorization
-
Execution & Fieldwork
Operationalize fieldwork scheduling, data access, and evidence collection to deliver the assurance opinion.
-
Pre-Fieldwork Readiness
Confirm data sources, internal controls, timelines, named owners, and remediation actions identified in the readiness assessment before scheduling fieldwork.
Pre-Fieldwork Questions
Environment and site access
- Are the production environments and source systems needed for fieldwork already accessible to the seller (so we can schedule visits)?
- If access is not complete, what is the targeted date when full access will be granted? (YYYY-MM-DD) — this date determines the earliest fieldwork start we can commit to.
- Which source system categories contain material inputs for the engagement? (select all that apply)
Data and configuration
- Has the field-mapping approach and sample-population method been finalized in the readiness assessment (so sampling can be locked)?
- Who is the single source-of-truth owner for GHG calculations and reporting (name and role) — this person will be our primary data clarifier during fieldwork.
- Are required data extracts or recurring reports automated for the fieldwork period, or will manual pulls be needed?
People and ownership
- Please confirm named owners for these workstreams: data owner, controls owner, registry liaison (enter 'TBD' for any unassigned role) — the deployment plan assigns tasks to these people.
- Have the high-priority remediation actions from the readiness assessment been assigned owners and target completion dates (so we can decide whether to proceed to fieldwork)?
Timing and constraints
- What is the earliest fieldwork start date the buyer can accommodate? (YYYY-MM-DD) — used to lock site visits and team availability.
- Are there blackout windows, financial close periods, or approval gates (e.g., audit committee or board approvals) that would block fieldwork during specific dates?
- Do you require registry-specific protocol selections or verification-standard confirmation before fieldwork begins (so we can align procedures)?
-
Fieldwork Logistics & Configuration
Lock site-visit dates, sample populations, evidence access credentials, registry protocol selections, and reporting cutoffs the team will use.
Fieldwork Configuration
Fieldwork Schedule — lock dates
- Primary site-visit start date (format: YYYY-MM-DD)
- Primary site-visit end date (format: YYYY-MM-DD). Default: same as start date — enter explicit date
Sampling Frame & Selection
- Canonical sampling population identifier (enter the exact name used in buyer systems, e.g., 'Fleet fuel logs 2025 Q1')
- Sample selection method (choose one)
- Planned sample size per population (integer). Default: 30 — enter an integer sample count
Evidence Access & Authentication
- Primary evidence access identifier (system name, shared‑folder path, or DB schema name — enter exact identifier as configured)
- Evidence access authentication method (choose one)
- Credential owner (who will upload the secret to your secrets manager) — enter as: Name — Role (do NOT paste any secret)
Registry Protocols & Reporting Cutoff
- Target protocol category for this engagement (select all that apply)
- Reporting cutoff date for evidence inclusion (format: YYYY-MM-DD). Default: reporting period end date — enter explicit date
-
Fieldwork & Verification
Execute sampling, site visits, source-to-report testing, management inquiry, and evidence collection, culminating in the assurance opinion and management letter.
-
-
Sustainment & Continuous Improvement
Review findings, track remediation and control improvements, manage registry submissions, and plan annual re-verification or follow-up assurance.
Success Reviews
- Go-live Health Check (weeks 1-4)
- First Measurement Review (weeks 4-10)
- Quarterly Operational Review
- Annual Re-verification Planning and Continuous Improvement
Issues & Enhancements
- Archive the year-end evidence package to the agreed retention location and document access controls for the next cycle.
- Agree the top backlog items to address in the next 90 days and the expected impact on the tracked metrics.
- Ensure the next scheduled registry submission has a clear checklist of required evidence and a completion date.
- Update and publish the prioritized remediation backlog with target completion dates for the next quarter.
- Produce a registry-submission readiness checklist for the next scheduled submission and circulate for validation.
- Run a controls test for one material data source and publish results ahead of the next quarterly review.
- Annual checklist completion and gap analysis
- Lock the re-verification window and confirm that planned re-verification lead time (days) provides sufficient buffer for registry deadlines recorded in Agreement & Authorization.
- Achieve agreement on the continuous improvement objectives that will materially reduce exceptions in the next cycle.
- Confirm the percent of annual verification checklist complete (%) and list remaining items with owners and completion dates.
- Publish the final re-verification calendar with provisional site-visit windows and required evidence submission cutoffs.
- Create the annual checklist closure plan showing outstanding items, owners, and target completion dates.
- Re-confirm delivery scope and owners
- Confirm final deliverables and evidence packages are accessible and complete against the items listed in Agreement & Authorization.
- Document and prioritize any early blockers with target resolution dates.
- Agree the cadence and owners for ongoing sustainment reporting.
- Publish a one-page handover checklist confirming which deliverables and evidence packages are complete and where they are stored.
- Create the initial open-issues register with description, temporary owner, and target resolution date.
- Enable access and confirm credentials for all named user roles who need evidence or report access.
- Determine whether remediation items closed (%) and average days to close remediation items (days) are trending toward the targets recorded in Agreement & Authorization.
- Present first-period outcome data
- Agree 2-4 named corrective actions with completion timelines to address the largest drivers of metric shortfall.
- Confirm the date for the next measurement checkpoint and required data to be provided beforehand.
- Publish the remediation-status dashboard export showing closed versus open items and average time-to-close for the review period.
- Prepare a short root-cause brief for the top two recurring exception types and proposed mitigations.
- Schedule the follow-up metric snapshot and confirm required evidence deliverables two weeks before that meeting.
- Quarterly metrics review
- Confirm whether remediation items closed (%) and registry submission acceptance rate (%) meet quarter targets recorded in Agreement & Authorization or require escalation.
- Deployment and evidence handover validation
- Control improvements status
- Re-verification scheduling and lead times
- Evidence quality and sample pass-rate check
- Registry submission and protocol updates
- Early adoption and usage signals
- Continuous improvement priorities for the next cycle
- Root-cause diagnosis for shortfalls
- Finalize evidence retention and archival approach
- Operational blockers and improvement backlog
- Agree corrective actions and timelines
- Open issues and blockers