Industrial & Manufacturing Energy, Utilities & Sustainability Carbon & Climate Reporting

Carbon Accounting

Long-cycle programs where regulation, capital, and grid reliability define the pace.

Persefoni Watershed Salesforce Net Zero Cloud South Pole
Inside this journey
  1. Pre-Discovery

    Align the room on outcomes, decision process, and constraints before deeper discovery.

    1. Stakeholder Alignment

      Confirm decision roles, timeline, data owners, and what 'audit-ready' outputs must satisfy for each stakeholder group.

      Alignment Questions

      Start Here: Why This Inventory Matters to You

      • What's the primary reason you're investing in a new GHG inventory process right now? Options: Regulatory compliance (existing or upcoming), Investor / ESG reporting, Net‑zero or public commitment, Operational/risk management, Cost or energy efficiency, Other
      • Which internal teams will actively use the inventory outputs in the next 12 months? Options: Sustainability/ESG, EHS/Compliance, Finance/Accounting, Procurement/Supply Chain, Operations/Facilities, IT/Data, Legal/Governance, Other
      • How do you currently publish or share your annual inventory (what outputs/formats do stakeholders expect)? Options: PDF summary reports, Detailed reconciled spreadsheets, Internal dashboards, Regulatory filings, XBRL/SEC templates, We don't publish consistently, Other
      • What's the most important deadline tied to this initiative (fiscal year-end, regulatory date, investor roadshow, etc.)? Options: Fiscal year-end reporting, Regulatory filing deadline, Investor / rating agency deadline, Board review / audit window, Internal target cadence, No firm deadline yet, Other
      • If we delivered a verification-ready inventory, how would you describe success for your role in one sentence?

      Who Holds the Keys — and Who Decides?

      • If we built a perfect inventory, would the people who sign off be the same ones who control the data—and if not, where does the gap live? Options: Yes—same people, No—different sign-off vs. data owners, Unclear / mixed, We have a governance committee
      • List the roles (not names) that must approve the inventory and their primary concern (e.g., Finance: reconciliation; Sustainability: methodology). Options: Sustainability/ESG - methodology, Finance - reconciliation & controls, EHS - regulatory alignment, Procurement - supplier data, IT - access & security, Legal - disclosures & liability, Other
      • Who is the budget owner for this project and what is their tolerance for risk or scope change? Options: Sustainability/ESG, Finance, Operations, IT, Corporate Development/Strategy, No single owner / cross-funded, Unsure
      • How does your internal approval process usually work (single sign-off, committee, staged gating)? Options: Single executive sign-off, Cross-functional committee, Stage-gate approvals, Finance-led controls, Ad hoc / depends on scope, Unsure
      • Which groups have historically slowed or blocked climate data projects, and what were their reasons?
      • How comfortable are your approvers with third‑party verification and external auditors accessing your evidence? Options: Very comfortable, Somewhat comfortable, Reluctant but possible, Not comfortable / non-starter

      Tell Me Where the Data Lives (and Who's Tired of Chasing It)

      • What's the single biggest friction in your current data collection—manual spreadsheets, delayed bills, supplier silence, or something else? Options: Spreadsheet consolidation, Delayed utility/bill data, Supplier non-response, Inconsistent site templates, Lack of integration/APIs, Other
      • Which systems and raw sources are feeding your current inventory (select all that apply)? Options: ERP (SAP/Oracle), Utility portals, Energy management systems (EMS), Procurement/spend system, Travel & T&E platforms, Custom spreadsheets, Supplier surveys, Other
      • Who owns day‑to‑day responsibility for collecting and validating emissions data (role or team)? Options: Facility managers, Sustainability team, Finance/Cost accounting, Operations/Plant leads, Procurement, Third‑party consultant, Other
      • How decentralized is data ownership across locations/business units—centralized, semi-centralized, or fully distributed? Options: Centralized (single team), Semi-centralized (regional leads), Distributed (local owners at each facility), Hybrid
      • Typical lag between activity and data availability (e.g., bills, procurement records)? Options: Real-time or near real-time, Monthly (1–2 weeks lag), Quarterly, 6+ weeks / irregular, Variable by source
      • Do you have current API access or system integrations available for automated ingestion? If yes, which systems and who can enable access?

      If Auditors Knocked Tomorrow, Would We Pass?

      • How confident are you that your current inventory would stand up to a verification review without major clarifications? Options: Very confident, Somewhat confident, Not confident, We haven't tried verification yet
      • What pieces of evidence do you currently retain for calculations (invoices, meter data, supplier attestations, emission factor documentation)? Options: Invoices/utility bills, Meter logs / EMS exports, Supplier survey responses, Procurement transaction records, Calculation workbooks, Methodology documentation, We keep little formal evidence
      • Have you ever completed a third‑party verification or assurance engagement? If so, what were the top findings or gaps called out? Options: Yes—minor findings, Yes—significant findings, No—we haven't pursued verification, Verification in progress / planned
      • Which calculation methodologies or standards must we align to for your stakeholders (GHG Protocol, ISO 14064, CDP, SEC/ISSB requirements)? Options: GHG Protocol, ISO 14064, CDP, TCFD / ISSB, SEC climate rules, Internal methodology, Other
      • Where do you anticipate the biggest evidence gaps auditors will ask for (supplier data, site boundaries, allocation rules, assumptions)?
      • Who in your organization will shepherd the verification process and assemble supporting evidence? Options: Sustainability/ESG, EHS/Compliance, Finance, Operations, External consultant, Undecided / TBD

      Hidden Costs: What Keeps You Up at Night?

      • What's the one scenario that would make this project politically or operationally painful for you?
      • Which of these risks do you judge most likely to occur during implementation? Options: Supplier non-response, IT delays / security concerns, Budget cuts, Scope creep, Data quality surprises, Internal stakeholder turnover, Other
      • For each high‑risk item you selected, how severe would the impact be on timelines or outcomes? Options: Critical—would derail project, High—major delay or rework, Medium—manageable with extra resources, Low—minor inconvenience
      • What capacity do you have internally to absorb extra work (data cleansing, supplier outreach, reconciliations)? Options: Dedicated sustainability team with bandwidth, Shared resources with limited capacity, Rely on external consultants, No capacity—need vendor to lead
      • Are there governance or legal constraints (data residency, confidentiality, supplier NDAs) that could restrict evidence sharing? Options: Yes—significant constraints, Some constraints, manageable, No major constraints, Unsure

      Map the Timeline That Will Make or Break This

      • If we miss your most important milestone, what is the immediate consequence for your team or reporting obligations?
      • What target go-live or delivery window do you need for the Scope 1/2 reconciliation and verification-ready report? Options: 4–6 weeks, 6–8 weeks, 2–3 months, 3–6 months, No firm target
      • Do you plan a phased rollout (Scope 1/2 first, then Scope 3 pilot)? If so, what would you like included in the first phase? Options: Scope 1 & 2 only, Scope 1/2 + limited Scope 3 categories, Full Scope 1/2/3, Pilot with select facilities/suppliers
      • Are there internal blackout periods, audits, financial closes, or board meetings we must avoid during implementation? Options: Yes—multiple blackout windows, Yes—one main blackout period, No major conflicts, Unsure
      • What is the longest acceptable delay before stakeholders escalate concerns? Options: 1 week, 2–4 weeks, 1–2 months, Longer than 2 months
      • Which milestone would you consider a 'quick win' to build confidence early in the project? Options: Automated utility ingestion, Reconciled facility-level spreadsheet, Supplier survey launch, First draft verification workbook, Executive summary for board

      Who Needs What — and How Loudly?

      • Would a single consolidated report satisfy all stakeholders, or will different audiences demand different formats and levels of detail? Options: One consolidated report works, Different formats needed by audience, A summary + detailed appendices preferred, Undecided
      • For each stakeholder group, what is the primary output they need (e.g., Sustainability: verification-ready inventory; Finance: reconciled trial balance)? Options: Verified annual inventory, Reconciled spreadsheets for audit, Regulatory reporting package, Supplier engagement summary, Executive dashboard / KPIs, Granular facility-level exports, Other
      • Which file formats or data models do your internal teams require for downstream systems (CSV, Excel, API, XBRL, other)? Options: CSV/Excel exports, Direct API integration, PDF/Board report, XBRL/Tagged reporting, Custom data schema, Other
      • How much granularity do stakeholders expect—facility level, asset level, or aggregated by business unit? Options: Asset-level detail, Facility-level, Business unit aggregation, Organization-level only, Mixed depending on audience
      • Are there internal KPIs or reconciliation controls finance expects us to meet (materiality thresholds, rounding rules, audit trail requirements)?
      • Which stakeholder would you prioritize when trade-offs are required, and why? Options: Finance - controls, Sustainability - credibility, EHS - compliance, Operations - feasibility, IT - security

      Let's Agree Next Steps — Quick Wins and Non‑Negotiables

      • What would you be willing to commit today to get the project started (e.g., grant API access, share sample spreadsheets, approve pilot scope)? Options: Grant API / system access, Share sample spreadsheets, Approve pilot facility list, Allocate internal resource hours, Sign statement of work, Not ready to commit
      • What are the non‑negotiable constraints for this engagement (data residency, budget cap, vendor restrictions, audit protocol)?
      • Who will be our day‑to‑day contact and who is the executive sponsor (role titles are fine)?
      • What prework can we do to accelerate onboarding (sample data mapping, facility list, supplier contact list)? Options: Provide sample data exports, Facility and site list with boundaries, Supplier contact list for pilot, Existing calculation templates, No prework available
      • How would you like us to communicate progress and escalate blockers (weekly standup, biweekly steering, Slack/email, portal)? Options: Weekly standup meetings, Biweekly steering committee, Asynchronous updates in portal, Slack or Teams channel, Email summaries only, Other
      • What acceptance criteria will you use to sign off a verification‑ready report (reconciliation thresholds, audit evidence completeness, stakeholder approvals)?
    2. Current State Mapping

      Document existing inventory methods, data sources, system integrations, and material Scope 3 categories and gaps.

      Current State

      Getting to Know Your Current Inventory

      • How do you currently produce your annual GHG inventory? Options: In-house spreadsheets, Third-party consultant, SaaS carbon accounting platform, Hybrid (spreadsheets + tools), We don't have one yet
      • How many years have you produced a formal inventory (including informal/spreadsheet versions)? Options: This is our first year, 1–2 years, 3–5 years, 6–10 years, 10+ years
      • Who is currently responsible for assembling and owning the inventory on a day-to-day basis? Options: Sustainability/ESG, EHS, Finance, IT, Facilities/Operations, Procurement, Shared team, Other
      • Which existing systems or sources do you pull emissions-related data from today? (select all that apply) Options: ERP (SAP/Oracle/Other), Utility bills / Utility management system, Fuel logs / fuel cards, Travel & expense system, Procurement / P-Card / AP data, IoT / meter data, Manual spreadsheets, Supplier surveys, None of the above, Other
      • Walk me through a recent inventory cycle—what parts felt smooth and which parts felt like triage?

      Are You Confident in What’s Missing?

      • If a regulator or investor asked for evidence that your inventory is complete, would you feel comfortable providing it today? Options: Fully confident, Mostly confident with evidence gaps, Would need time to pull evidence, Not confident at all
      • Which pieces of evidence do you currently have tied to emissions entries? (select all that apply) Options: Original invoices/utility bills, Meter readings, Supplier attestations, Purchase orders / line-item spend, Travel itineraries/expense receipts, None consistently available, Other
      • Which Scope 3 categories do you already include in your inventory? Options: Purchased goods & services, Capital goods, Fuel-and-energy-related (upstream), Upstream transportation & distribution, Waste generated in operations, Business travel, Employee commuting, Use of sold products, End-of-life treatment, Other/We don't track Scope 3
      • Where do you see the largest gaps today—lack of data, methodology uncertainty, supplier non-response, or something else? Options: Data availability, Methodological clarity, Supplier engagement, System integrations, Internal resourcing, Other
      • Typically, how long does it take your team to assemble a reconciled inventory from start to finish? Options: Under 2 weeks, 2–4 weeks, 1–2 months, 2–3 months, 3+ months

      What’s Getting in the Way?

      • Which manual workaround in your inventory process would you least want an auditor to see?
      • How often do your reconciled totals differ materially from the prior year, and what usually explains the delta? Options: Rarely (within margin), Occasionally (1–5%), Often (5–10%), Frequently (>10%), We don't track variance reasons
      • When mismatches appear, where do they most commonly originate—data ingestion, mapping, emissions factors, or manual adjustments? Options: Data ingestion errors, Incorrect mapping/GL codes, Outdated emission factors, Manual adjustments/assumptions, Other
      • How do decentralized sites or business units typically respond when asked for clarifying data? Options: Responsive and timely, Slow but cooperative, Require follow-ups and escalation, Unresponsive or inaccurate, We centralize this ourselves
      • Tell me about a recent instance where a data or process issue cost extra time or credibility—what happened and how did it feel for the team?

      What Would Perfect Actually Feel Like?

      • If you could snap your fingers and have a verification-ready inventory, what would change immediately in your organization?
      • Which of these outcomes would move the needle most for your stakeholders? (select up to three) Options: Verified annual inventory, Regulatory readiness / compliance, Comprehensive Scope 3 coverage, Investor-ready disclosures (CDP/TCFD/ISSB), Operational emissions tracking, Reduction target tracking
      • What is your realistic target timeline for achieving a first verification-ready inventory for Scope 1 & 2? Options: 6–8 weeks, 2–3 months, 3–6 months, 6–12 months, No target / exploratory
      • Which success signals would make you say the project succeeded beyond the report (examples: automated year-over-year reconciliation, evidence library, supplier onboarding)?
      • Who needs to feel reassured by the result for you to call it a success (name roles, not just departments)?

      What Would Change Look Like in Practice?

      • What single belief about your current process would you be most willing to challenge if we showed a better alternative?
      • Which internal constraints worry you most when introducing a new platform—budget, IT/security, stakeholder buy-in, or training? Options: Budget, IT/security approvals, Stakeholder alignment, Change management/training, Legal/compliance, Other
      • Which integrations would be essential to automate for you to consider the rollout successful? (select all that apply) Options: ERP (GL / POs / spend), Utility billing / meter API, Travel & expense systems, Procurement systems, IoT / meter feeds, Supplier portal / survey APIs, None are essential
      • Do you currently have API access or export capabilities for those systems? Options: Full APIs available, Partial APIs/exports, Only manual exports, No access / IT blocked, Unsure
      • How would you like ownership to shift after deployment—centralized in one team, shared center of excellence, or remain distributed? Options: Centralized (Sustainability/EHS), Shared COE with Finance & IT, Distributed to business units, Undecided

      Scope 3 — The Needle-Mover Conversation

      • If you could resolve one Scope 3 category this year that would change stakeholder confidence overnight, which would it be and why?
      • What procurement or supplier data do you currently have at the supplier level? Options: Line-item spend with supplier detail, Aggregated spend by vendor group, Only GL code level spend, No supplier-level procurement data, Other
      • Have you ever run supplier surveys or data collection pilots? If so, what response rates and quality did you see? Options: No surveys run, Yes — high response (>60%), Yes — moderate response (30–60%), Yes — low response (<30%)
      • Which calculation approaches are you comfortable using for Scope 3 (select all that apply)? Options: Spend-based (EEIO), Activity-based (units/quantities), Supplier-specific emissions, Hybrid approaches, Unsure / need guidance
      • What incentives or leverage do you have to improve supplier data quality (procurement clauses, preferred supplier status, support resources)?

      Verification and Trust — What Will Convince Your Auditor?

      • What would make you comfortable publicly stating that your inventory is verification-ready?
      • Which acceptance criteria must be included in a verification-ready report for your organization? (select all that apply) Options: Reconciled totals to prior inventory, Supporting evidence for 100% of Scope 1/2, Documented methodology aligned to GHG Protocol, Sampled evidence trail for Scope 3, Third-party auditor sign-off, Clear facility boundaries and allocation rules
      • What variance from last year’s totals would you consider acceptable before stakeholders ask for an explanation? Options: Within 1%, 1–5%, 5–10%, Above 10%, Unsure
      • Have you engaged third-party verifiers before, and if so, what were their main findings or concerns? Options: No previous verification, Yes — minor findings, Yes — significant findings, Yes — process-level gaps
      • How would you like evidence and audit trails packaged—single shared folder, platform evidence library, or auditor portal access? Options: Platform evidence library, Shared secure folder (SFTP/Drive), Auditor portal access, Combination, Undecided

      What Would It Take to Move Forward?

      • What would you need to see in our pilot or proposal to confidently recommend moving forward to your stakeholders?
      • What is the budget range you have earmarked (or expect to need) for an initial Scope 1/2 implementation and a follow-on Scope 3 pilot? Options: <$25k, $25k–$75k, $75k–$150k, $150k–$300k, >$300k, Undisclosed / TBD
      • What is your procurement decision timeline? Options: Immediate (weeks), This quarter, Next quarter, Later this year, Undetermined
      • Who are the key decision-makers and technical approvers we should include in the conversation for a pilot? (list roles)
      • What concerns or objections do you anticipate from IT, Finance, or legal that we should proactively address?
      • If everything aligned, what would be your ideal kickoff month for the initial rollout? Options: Immediately, Next month, Within 2–3 months, In 3–6 months, Later than 6 months
  2. Outcome Discovery

    Define target outcomes (verified annual inventory, regulatory readiness, Scope 3 coverage), success signals, and timeline.

    Discovery Questions

    Setting the North Star: What Success Really Looks Like

    • Which single outcome matters most for your next GHG inventory (pick the primary driver)? Options: Regulatory compliance (upcoming rule or permit), Investor/disclosure readiness (CDP/SEC/ISSB), Third-party verification / assurance, Internal target tracking and reductions, Operational / EHS permitting, Other
    • Who will veto or sign off on this inventory being ‘good enough’ (role or names)?
    • What timeline do you have in mind to call the inventory ‘complete’? Options: < 3 months, 3–6 months, 6–12 months, > 12 months, Dependent on pilot results, Unsure
    • If we delivered a verification-ready report next quarter, what immediate business question would you expect to answer with it?
    • What internal team will own ongoing maintenance after launch (sustainability, EHS, finance, IT, other)? Options: Sustainability/ESG, EHS/Environmental, Finance, IT/Data, Operations/Facilities, Cross-functional team, Other
    • What would make you feel the platform paid for itself in the first year?

    Are We Settling for ‘Good Enough’?

    • When you think about your current inventory, what hard-to-ignore gap would you fix first if you could?
    • How confident are you that your current Scope 1 and 2 calculations would pass a technical audit today? Options: Very confident, Somewhat confident, Not confident, I don’t know
    • Which part of your current process causes the most rework late in the cycle? Options: Data collection, Emission factors and methodology, Facility boundaries and allocation, Consolidation/roll-up, Stakeholder reconciliation, Other
    • Tell us about the last time you compared platform/pilot results to your spreadsheets—what surprised you?
    • How much time (person-hours) does your team spend each year preparing the inventory today? Options: < 50 hours, 50–200 hours, 200–500 hours, > 500 hours, Unsure
    • Which emotion best describes how your team feels at the end of inventory season? Options: Relieved, Exhausted, Proud, Frustrated, Skeptical of accuracy, Neutral

    Who's Really Holding the Keys?

    • If the success of this project depended on three people saying 'go', who are they and why?
    • Which groups must be consulted or provide data for the inventory (select all that apply)? Options: Facilities/Plant Managers, Procurement/Sourcing, Finance/Accounting, IT/Data Engineering, Travel & Mobility, HR/Commuting, Investments/Portfolio teams, Other
    • Who currently controls the data we’ll need (names/roles and where data lives)?
    • How do budget and procurement decisions get made for vendor/platform purchases in your organization? Options: Central procurement, Business unit buys, Finance-led approvals, Cross-functional committee, Other
    • What IT or security reviews would a vendor integration require (e.g., SOC 2, data sharing agreements)? Options: SOC 2 / security audit, Data processing agreement (DPA), API credentialing, VPN / network setup, No formal review, Other
    • How quickly can your identified owners commit time to a pilot (hours/week) over the next 8 weeks? Options: 0–2 hours/week, 3–5 hours/week, 6–10 hours/week, >10 hours/week, Unsure

    What Would a Verifier Notice First?

    • Imagine a verifier opened your file—what single issue would they flag first?
    • Which outputs do you need to be verification-ready (select all that apply)? Options: GHG inventory CSVs by facility, Methodology documentation, Emission factor source list, Data lineage and raw evidence, Uncertainty and QA/QC notes, Third-party verification statement, Other
    • Do you have formal acceptance criteria for a verification-ready report today? Options: Yes—documented checklist, Informal agreement between teams, No, but we have examples, No
    • What level of assurance are you targeting (if any)? Options: No assurance, Internal review only, Limited assurance, Reasonable assurance, Regulator-specific audit
    • What documentary evidence can you already provide (e.g., invoices, bills of lading, meter reads, supplier attestations)?
    • Where do you anticipate the highest pushback from stakeholders during verification (finance, operations, suppliers, regulators)? Options: Finance, Operations, Suppliers, Regulators, Executive leadership, Other

    The Scope 3 Wake-Up Call: Where Truth Hides

    • Which Scope 3 categories would make you lose sleep if an auditor asked for evidence today? Options: Purchased goods & services, Capital goods, Fuel & energy related activities, Upstream transportation & distribution, Waste generated in operations, Business travel, Employee commuting, Use of sold products, Investments, Other
    • Which of these best describes your current Scope 3 approach? Options: No Scope 3 work, Spend-based estimates only, Mix of spend and activity-based, Supplier-specific data for some categories, Comprehensive supplier engagement, Unsure
    • How many suppliers/partners would need to be surveyed or integrated for a meaningful pilot? Options: < 20, 20–100, 100–500, > 500, Unsure
    • What percent of your Scope 3 emissions do you expect to come from your top 10 suppliers? Options: < 25%, 25–50%, 50–75%, > 75%, Unsure
    • Which supplier data types are available now (select all that apply)? Options: Specific activity data (kWh, tonnes), Purchase order / spend data, Supplier-reported emissions, E-invoices with line-item detail, None of the above, Other
    • If you could pilot one Scope 3 category first, which would it be and why?

    Signals of Victory: How You’ll Know We’re There

    • Describe the top three success signals that would make leadership say ‘this worked’.
    • Which quantitative KPIs will matter most (select up to three)? Options: % data completeness, Reduction in manual person-hours, Number of facilities integrated, % of Scope 3 with supplier data, Inventory accuracy vs prior year, Time to produce inventory
    • What stakeholder sentiment would you need to secure (e.g., Finance trusts totals, Operations finds it useful)?
    • What is an acceptable margin of methodological defensibility for your team (e.g., full GHG Protocol alignment, internal methodology with crosswalk, other)? Options: Full GHG Protocol alignment, GHG Protocol with documented deviations, Internal methodology with external references, Not defined
    • How will the output be used beyond reporting (target setting, carbon pricing, procurement decisions, investor engagement)? Options: Target setting, Internal carbon pricing, Supplier engagement/prioritization, Investor reporting, Regulatory filings, Other
    • What timeline for seeing these signals feels realistic to you (pick one)? Options: Within 3 months, 3–6 months, 6–12 months, 12+ months, Dependent on pilot

    Commitment & First Moves: What Will It Take to Start?

    • If we could guarantee one thing by the end of a pilot, what guarantee would make you sign off?
    • Which resources can you commit in the next 8 weeks (select all that apply)? Options: Data owner time (hours/week), IT support for integrations, Procurement/supplier outreach, Finance review time, Budget for pilot, Executive sponsor availability, None of the above
    • What are your non-negotiables for scope, deliverables, or SLA before we start?
    • Are there internal review gates that would block deployment (compliance committee, legal, data privacy)? Options: Yes—compliance/ethics, Yes—legal, Yes—data privacy, No formal gates, Unsure
    • What would count as a clear reason to pause or roll back a pilot? Options: Major data security concern, Inability to access core data, Critical calculation discrepancy, Stakeholder refusal, Budget constraint, Other
    • Realistically, when could your team be ready to begin a pilot (select one)? Options: Immediately, Within 2 weeks, 2–6 weeks, 2–3 months, Longer / need planning
  3. Solution Experience

    Walk through how the platform, using the customer’s sample data and scenarios, delivers a GHG inventory that reconciles with current spreadsheets and supports verification.

    Experience Meetings

    • Solution Experience: Prep & Alignment (Must-have Preconditions)
    • Live Data Ingestion & Reconciliation Workshop
    • Calculations, Assumptions & Verification Evidence Review
    • Scope 3 Scenario Walkthrough & Edge Case Resolution
    • Verification Readiness Review & Acceptance

    Issues & Enhancements

    • Agree explicit gap-handling rules and escalation paths for missing supplier data.
    • Schedule follow-up if significant methodological differences require policy-level decisions.
    • One-sentence Future State Reconnect
    • Prove calculations are GHG Protocol-aligned and traceable to source documents.
    • Validate emission factor sources and versioning approach meet audit requirements.
    • Deliver a preliminary verification evidence pack and identify any gaps.
    • Obtain explicit feedback from the customer's verifier or verification lead on remaining evidence needs.
    • Seller to produce the verification evidence bundle (zipped) including mapping logs and calculation trace.
    • Customer to share verifier contact or checklist for direct validation, if available.
    • Seller to update factor provenance notes and register any methodological deviations for formal approval.
    • Customer to review and confirm whether package satisfies internal audit/finance requirements.
    • Seller to document edge-case resolutions and update the pilot playbook.
    • Customer to provide target supplier contacts and priority spend segments.
    • Material Category Recap & Objective
    • Prove the platform's Scope 3 approach produces defensible, verifiable outputs for material categories.
    • Introductions & Objective
    • Resolve priority edge cases and lock the method to be used in the pilot.
    • Confirm pilot scope and data collection responsibilities for suppliers.
    • Customer to approve the final Scope 3 pilot method list and gap-handling rules.
    • Seller to configure supplier survey templates and pilot roll-out list.
    • Recap Success Criteria
    • Obtain explicit customer acceptance that the inventory reconciles and the evidence pack meets the agreed verification criteria.
    • Capture any outstanding risks and agree mitigation and owners before verification.
    • Agree the next milestone (verification kickoff or full deployment) and confirm schedule and owners.
    • Ensure a clear transition plan for annual updates and Scope 3 improvements is in place.
    • Customer to sign the verification-readiness acceptance form or provide documented exceptions.
    • Seller to hand over the final evidence bundle to the customer and, optionally, to the verifier.
    • Schedule the verification kickoff meeting or full deployment start date and assign owners.
    • Establish annual update cadence and Scope 3 improvement milestones in the shared project plan.
    • Capture clear, one-sentence current state, consequence, and future state to anchor the Solution Experience.
    • Confirm exact sample data files, access, and delivery timeline needed for the live walkthrough.
    • Agree concrete success criteria and verification acceptance metrics for the pilot.
    • Assign owners and finalize scheduling for the live ingestion and reconciliation workshop.
    • Customer to deliver named sample spreadsheets, system extracts, and a data dictionary by agreed date.
    • Seller to provision a sandbox environment and confirm ingestion endpoints and mapping template.
    • Customer and Seller to co-sign the success/acceptance checklist for the Solution Experience.
    • Schedule the Live Data Ingestion & Reconciliation Workshop with required stakeholders.
    • Recap Preconditions (1-sentence refresh)
    • Demonstrate the platform reproduces the customer's inventory totals or clearly explain the reasons for any differences.
    • Produce an actionable list of reconciliation exceptions with owners and timelines.
    • Obtain validation from the customer that the platform's traceability meets their audit needs.
    • Confirm any immediate mapping/configuration changes and re-run to prove fix effectiveness.
    • Seller to apply agreed mapping fixes and deliver a reconciliation exceptions report.
    • Customer to provide clarification or missing source documents for items flagged as 'missing data'.
    • Seller to re-run reconciliations for corrected items and publish before/after evidence.
    • One-sentence Current State
    • Present Final Reconciled Inventory
    • Data Mapping Walkthrough
    • Calculation Walkthrough (end-to-end)
    • Supplier Survey Ingest & Mapping
    • Emission Factor Provenance & Version Control
    • Spend-based vs Activity-based Comparison
    • Live Ingestion of Sample Files
    • Verification Evidence Bundle Review
    • Explicit Consequence Statement
    • Outstanding Items & Residual Risk
    • One-sentence Future State
    • Materiality, Allocation & Uncertainty Methods
    • Reconciliation Dashboard: Platform vs Spreadsheet Totals
    • Gap-handling Rules & Conservative Defaults
  4. Solution Scope

    Define phased scope (Scope 1/2 rollout, Scope 3 pilot), integrations, supplier surveys, deliverables, and verification outputs.

    Scope Configuration

    • Ingest Utility Bills and Meter Data
    • Ingest Fuel and Fleet Fuel Records
    • Integrate ERP Spend and Procurement Data
    • Integrate Travel and Business Trip Data
    • Map Facilities and Configure Organizational Boundaries
    • Deploy Supplier Emissions Survey and Intake
    • Apply Spend-Based Scope 3 Calculations
    • Apply Activity-Based Scope 3 Calculations
    • Map Supplier-Specific Emissions to Procurement
    • Execute Scope 1 Emissions Calculations
    • Execute Scope 2 Calculations (Location and Market)
    • Generate Verification-Ready Inventory Report (GHG Protocol, CDP, SEC)
    • Update and Maintain Emission Factor Library

    Scope Questions

    Ingest Utility Bills and Meter Data

    • Do you receive utility bills electronically for most facilities? Options: Yes, No, Partial
    • Which utility types should be ingested for this scope? Options: Electricity, Natural Gas, Water, Steam/Heat, Other
    • Are bills organized per facility (site-level) or at a central organizational account? Options: Facility-level, Central account, Mixed
    • What is the typical billing frequency and date format (e.g., monthly, quarterly)? Options: Monthly, Quarterly, Annual, Irregular/Varies
    • Do you have interval meter / AMI data available or only monthly billing totals? Options: Interval (sub-hourly), Daily, Monthly totals only, Not sure
    • If electronic bills exist, what formats or ingestion methods are preferred or available (API, CSV, PDF, email intake)? Options: API, CSV/Flat file, PDF upload, Email ingestion/IMAP, FTP/SFTP, Other

    Ingest Fuel and Fleet Fuel Records

    • Do you track fuel consumption centrally or by individual vehicles/equipment? Options: Central fuel ledger, Per-vehicle telematics/odometer, Per-site tank/fuel card, Mixed
    • Which fuel types and mobility categories are in scope (diesel, gasoline, LPG, LNG, biodiesel, CNG, e-fuels, aviation fuel)? Options: Diesel, Gasoline, LPG, LNG, CNG, Aviation/Jet Fuel, Biodiesel/HVO, Other
    • Are fuel records available as card/merchant reports, telematics exports, or manual logs? Options: Fuel card exports, Telematics, Manual logs/spreadsheets, Vendor invoices, Other
    • Do you want combustion emissions for owned fleet only, leased vehicles, or business partner fleets included? Options: Owned fleet, Leased (operating) vehicles, Third-party/partner fleets, All applicable
    • How frequently should fleet/fuel data be ingested and reconciled (daily, weekly, monthly)? Options: Daily, Weekly, Monthly, Quarterly
    • Are fuel densities, purchase units (liters/gallons/kg), or odometer-to-fuel conversion rules already defined?

    Integrate ERP Spend and Procurement Data

    • Which ERP or procurement systems should we connect to for spend data? Options: SAP, Oracle, NetSuite, Workday, Coupa, Other
    • Do you have spend data tied to supplier IDs and purchase order lines that can be mapped to procurement categories? Options: Yes, fully mapped, Partially mapped, No, requires mapping
    • What level of granularity is available: GL-level, cost center, SKU/line-item, or aggregated spend? Options: GL-level, Cost center, Line-item/SKU, Aggregated
    • Do you require currency conversion and historical FX rate handling for multi-currency spend? Options: Yes, No, Only current year
    • Are there existing supplier classifications (NAICS, UNSPSC, custom categories) to map against Scope 3 categories? Options: Yes - standard codes, Yes - custom mapping, No
    • Please describe any custom procurement workflows, approval layers, or data latency constraints that affect data availability.

    Integrate Travel and Business Trip Data

    • Which travel booking / expense systems hold your corporate travel data? Options: Concur, Egencia, SAP Concur, Chrome River, Expense/Corporate Cards, Other
    • Do travel records include class of travel (economy/premium/business), distance, and passenger count? Options: Yes - all fields, Partial (e.g., distance only), No - needs enrichment
    • Should employee commuting and business ground transportation (rideshare, rental cars) be included? Options: Include commuting, Include business ground transport only, Both, Neither
    • Do you prefer to calculate aviation emissions via distance-based factors, ticket-based data, or vendor-supplied emissions? Options: Distance-based, Ticket/vendor emissions, Hybrid
    • How often should travel data be ingested and reconciled (real-time, monthly, quarterly)? Options: Real-time/near real-time, Monthly, Quarterly
    • Are there data privacy or PII constraints for travel records we should account for? Options: Yes, No, Not sure

    Map Facilities and Configure Organizational Boundaries

    • Do you want organizational boundaries defined by Operational Control, Financial Control, or Equity Share? Options: Operational Control, Financial Control, Equity Share, Hybrid/Custom
    • How many facilities/sites will be included in the initial rollout? Options: 1-10, 11-50, 51-200, 200+
    • Do facility records include geo-coordinates, site IDs, site contacts, and production metrics? Options: Yes - all present, Partial metadata, No - requires collection
    • Are there shared facilities (multiple business units reporting to same site) that need cost/allocation rules? Options: Yes, No, Some
    • Will boundaries require sub-facility breakdowns (production lines, meters, buildings)? Options: Yes - meter/building level, No - site level only, Conditional
    • Please list any regulatory facility identifiers or permit numbers that must appear in reports.

    Deploy Supplier Emissions Survey and Intake

    • How many suppliers will you target in the initial survey/pilot? Options: 10-50, 51-200, 201-1,000, 1,000+
    • What percentage of spend do you want covered by supplier responses in the pilot? Options: Top 20% spend, Top 50% spend, All material suppliers, Other
    • Which survey delivery methods are acceptable (email link, portal, API, assisted collection)? Options: Email survey link, Supplier portal, API/EDI, Phone/assisted collection
    • Do you require supplier data validation rules (unit checks, required fields, attachments like fuel receipts)? Options: Yes, No, Limited validation
    • Should surveys be multilingual or formatted for specific regions/currencies? Options: Yes - multilingual, Yes - currency localized, No
    • Do you plan to incentivize supplier participation or couple the survey with contractual requirements? Options: Yes, No, Undecided

    Apply Spend-Based Scope 3 Calculations

    • Which Scope 3 categories do you intend to calculate using spend-based methods? Options: Purchased goods & services, Capital goods, Fuel-and-energy-related (upstream), Upstream transportation, Other
    • Is spend data available at supplier-level, category-level, or only aggregated? Options: Supplier-level, Category-level, Aggregated
    • Which spend-to-emission factor sources do you prefer (EEIO, country-specific spend factors, vendor-provided)? Options: EEIO tables, Country-specific factors, Vendor-supplied, Custom factors
    • Do you require normalization by production metrics (e.g., per unit produced) or report only absolute tCO2e? Options: Absolute tCO2e, Normalized by production, Both
    • How should outliers or unusually large spend lines be treated (cap, manual review, exclude)? Options: Manual review, Cap at threshold, Exclude with justification
    • Are there known materiality thresholds for including spend categories in the inventory?

    Apply Activity-Based Scope 3 Calculations

    • Which categories will be activity-based (e.g., downstream transportation, waste, product use)? Options: Transportation & distribution, Waste, Product use/end-of-life, Employee commuting, Other
    • Are activity units available (km, tons transported, kWh used, pieces sold) and at what granularity? Options: High granularity (per shipment/transaction), Aggregated monthly/annual, Not available
    • Do you have preferred conversion factors or should we apply standard GHG Protocol/IPCC factors? Options: Use our factors, Use standard GHG Protocol/IPCC factors, Hybrid
    • What estimation rules should be applied for missing activity data (proxies, averages, extrapolation)? Options: Use proxies, Interpolate from similar sites, Request supplier estimates, Custom rules
    • Is there a need to link activity-based results to product SKUs or customer accounts? Options: Yes, No, Maybe / later phase
    • Please describe any specific calculation boundaries or emissions (e.g., refrigerant leak rates) that must be included.

    Map Supplier-Specific Emissions to Procurement

    • Do you have supplier IDs in procurement data that can be matched to supplier survey responses or external datasets? Options: Yes - consistent IDs, Partial matchability, No
    • Should supplier-specific emission factors be applied at invoice/PO line-level or aggregated at category level? Options: Line-level (PO/Invoice), Aggregated category-level, Hybrid
    • Do you require reconciliation between supplier-submitted emissions and spend-based estimates with exception workflows? Options: Yes - require reconciliation flows, No - accept supplier values, Conditional
    • Are supplier emissions provided as intensity metrics (e.g., tCO2e per unit) or absolute totals? Options: Intensity metrics, Absolute totals, Both
    • How should confidential supplier data be handled if suppliers share proprietary emissions info (restricted access/auditor-only)? Options: Restricted access, Auditor-only, Full visibility
    • Please describe any procurement system constraints (e.g., lack of supplier master data fields) that impede mapping.

    Execute Scope 1 Emissions Calculations

    • Which fuel combustion sources are in scope (stationary combustion, mobile combustion, process emissions, fugitive emissions)? Options: Stationary combustion, Mobile combustion, Process emissions, Fugitive emissions, Other
    • Do you have measured fuel consumption data or will you rely on purchase/consumption invoices? Options: Measured consumption (meters), Purchase/invoice-based, Estimate from activity data, Mixed
    • Which GHG species should be included (CO2, CH4, N2O, HFCs, PFCs, SF6)? Options: CO2, CH4, N2O, HFCs/PFCs/SF6, Other
    • Do you have predefined emission factors you must use or should standard IPCC/GHG Protocol factors be applied? Options: Use our factors, Use standard factors, Hybrid
    • Are there measurement uncertainty requirements or data quality tiers you want captured (measured, calculated, estimated)? Options: Yes - use tiers, No
    • Please detail any regulatory reporting formats or permit templates that must be supported for Scope 1 outputs.
  5. Mutual Commit

    Agree commercial terms, SLAs, data access responsibilities, and acceptance criteria for verification-ready reports.

    Agreement Modules

    • Non-Disclosure Agreement (NDA)
    • Master Services Agreement (MSA)
    • Statement of Work (SOW)
    • Commercial Terms & Pricing
    • Payment Schedule & Purchase Order
    • Service Level Agreement (SLA)
    • Data Access & Security Agreement
    • Data Processing Agreement (DPA)
    • Acceptance Criteria & Verification Plan
    • Roles & Responsibilities (RACI) Module
    • Integration & API Access Schedule
    • Supplier Data Consent Addendum
    • Pilot Go/No-Go & Success Criteria
    • Change Order & Scope Management
    • Termination, Exit & Data Portability
    • Third-Party Verification Support Agreement
    • Renewal & Ongoing Support Plan
  6. Deployment

    Operationalize rollout with readiness checks, enablement, and outcome validation.

    1. Pre-Deployment Readiness

      Confirm data availability, API credentials, facility boundaries, supplier engagement plans, and risk controls prior to execution.

      Readiness Questions

      Quick Temperature Check — Where Are We Right Now?

      • Which best describes your current readiness to start the deployment phase? Options: Ready to start within 2 weeks, Ready within 1–2 months, Need 2–3 months to prepare, Not sure / need internal alignment
      • Who on your side will be the primary day-to-day contact for technical and data questions (name, role)?
      • Which stakeholders must sign off before we can run production integrations and a Scope 3 pilot? Options: Sustainability/ESG, EHS/Operations, IT/Security, Finance, Procurement, Legal/Compliance
      • Do you already have an existing GHG inventory and, if so, when was it last finalized? Options: No existing inventory, Draft inventory (not finalized), Finalized within last 12 months, Finalized 12–24 months ago, Older than 24 months
      • If you have a prior inventory, what feels most fragile about it—data gaps, methodology, stakeholder buy-in, or something else?

      What Would Stop This Project Cold?

      • If we tried to start integrations tomorrow, what single obstacle would most likely prevent a successful launch? Options: Data access/credentials, Facility boundary ambiguity, Supplier non-response, IT/security approvals, Lack of internal owner, Other
      • How often have those kinds of obstacles derailed past projects for you? Options: Frequently (multiple times), Occasionally (once or twice), Rarely, Never
      • What is the typical internal response when a deployment is blocked—do stakeholders escalate, pause, or try workarounds? Options: Escalate to leadership, Pause until resolved, Implement manual workarounds, Proceed with reduced scope
      • Who would be empowered to remove that obstacle quickly (name or role) and how long would their intervention typically take?
      • If we proposed a mitigation (temporary manual ingestion, scoped pilot, or alternate supplier outreach), which would you prefer we try first? Options: Temporary manual ingestion, Smaller scoped pilot, Alternate data sources, Delay until resolved

      Where Does Your Data Really Live — And Who Guards It?

      • Tell us bluntly: which data sources are absolutely required for a verification-ready inventory and do they exist today? Options: Utility bills, Fuel/fleet logs, Procurement/spend data, Travel & employee commuting, Supplier emissions data, Other
      • Which systems currently contain that data (ERP, utility portal, fuel cards, procurement system, spreadsheets, other)? Options: ERP (e.g., SAP, Oracle), Utility billing portal, Fuel/fleet management, Procurement/P-card system, Custom databases, Spreadsheets
      • For those sources, do you have a named data owner and an estimate of how complete historical records are (months available)? Options: Named owner + >24 months, Named owner + 12–24 months, Named owner + <12 months, No named owner / ad hoc records
      • Are there known data quality concerns (missing meters, inconsistent units, aggregated invoices) and if so, which are highest priority to resolve? Options: Missing meters, Inconsistent units, Aggregated invoices, Vendor-level only data, Time-lagged reports, None known
      • How comfortable is your team sharing a small sample (anonymized if needed) so we can validate ingestion and mapping before full roll-out? Options: Very comfortable, Can share with NDA, Prefer limited fields only, Not comfortable

      Are Boundaries Something We Fight Over or Lock Down Together?

      • When you think about facility and organizational boundaries, what's been the hardest part to agree on internally? Options: Legal entity vs operational control, Meter-to-facility mapping, Shared sites / joint ventures, Outsourced operations, Other
      • Do you currently use a single canonical facility list (with site IDs and coordinates) or are lists scattered across business units? Options: Single canonical list, Multiple lists per BU, No formal list - spreadsheets only, We have a GIS/facility database
      • How often do facility boundaries change (acquisitions, divestitures, site consolidations) and how quickly can you provide updated boundary information? Options: Quarterly or more, Annually, Rarely (<1/year), Unclear
      • Are submeters or aggregated site meters the norm—do you have meter-to-facility mappings for most sites? Options: Submeters with mapping, Aggregated meters without mapping, Mixed, Unknown
      • If we find boundary mismatches during validation, who should own the correction and what SLA would you expect for resolution?

      Can We Plug In — Or Will Your IT Team Make Us Work For It?

      • What kind of system access is realistic in the near term: API credentials, SFTP feeds, vendor portals, or manual uploads? Options: API credentials, SFTP/secure file transfer, Vendor portal access, Manual spreadsheet uploads, Other
      • Do you have an internal security or procurement process that requires a vendor security review, and how long does that typically take? Options: No review required, Standard security review (2–4 weeks), Extended review (>4 weeks), Unknown / depends on vendor
      • Are there particular authentication methods we must support (OAuth2, SAML, API keys, VPN) to integrate with your systems? Options: OAuth2 / OpenID, API Keys, SAML, VPN / private network, SFTP with key
      • Would your IT team prefer a sandbox environment and test credentials before production access is granted? Options: Yes, sandbox required, Prefer but not required, No, can provide production creds
      • What's the usual lead time to get credentials from your vendors or portals once IT approves the request? Options: <1 week, 1–2 weeks, 2–4 weeks, >4 weeks, Unknown

      Will Suppliers Play Ball — Or Hide Behind Procurement?

      • Which best describes your supplier engagement approach for Scope 3 data collection? Options: Direct outreach by our team, Supplier engagement via procurement, Third-party survey vendor, We do not currently engage suppliers
      • What's a realistic response rate you expect from suppliers for a first-round survey (percent range)? Options: >70%, 50–70%, 30–50%, <30%
      • Which incentives or levers have worked for you to improve supplier response (contract clauses, training, simplified forms, financial incentives)? Options: Contractual requirements, Training/webinars, Simplified one-page surveys, Assistance from procurement, No incentives used
      • If supplier response is low, which fallback method would you prefer we use for material categories—spend-based estimation, proxy suppliers, or targeted data purchase? Options: Spend-based estimation, Proxy suppliers / benchmarks, Targeted data purchase, Limit to supplier-provided data
      • Do you have a nominated procurement lead who can help with supplier outreach and data validation? Options: Yes — name and contact provided, Yes — role but contact TBD, No dedicated procurement lead

      If Things Go Sideways — What’s The Fail-Safe?

      • What contingency plan would you want in place if a critical integration fails during the pilot? Options: Switch to manual ingestion, Pause pilot and fix integration, Use a reduced-scope pilot, Use alternate data sources
      • What level of rollback capability do you require—full data purge, staged rollback, or versioning with audit trail? Options: Full data purge, Staged rollback, Versioning + audit trail, No rollback required
      • What SLA do you expect from us for incident response during deployment (initial response time and target resolution window)? Options: Initial response <1 hour, resolve <24 hours, Initial response <4 hours, resolve <72 hours, Initial response <24 hours, resolve <1 week, Flexible / depends on issue
      • Who on your side will be on the escalation list for deployment incidents (names/roles)?
      • How much evidence of controls and data lineage will your third-party verifier expect at the end of the pilot? Options: Detailed logs + source files, Summary evidence + samples, High-level reconciliation only, Unsure / need guidance

      Picture Day One — What Will Make You Say 'This Worked'?

      • If we handed you a verification-ready inventory for the pilot scope tomorrow, what three things would make you confident it was right?
      • Which acceptance criteria matter most for you: numerical reconciliation, documented data lineage, stakeholder sign-off, or verifier readiness? Options: Numerical reconciliation, Documented data lineage, Stakeholder sign-off, Verifier readiness
      • What minimal supporting artifacts do you require with the report (raw source files, calculation workbook, methodology note, audit trail)? Options: Raw source files, Calculation workbook, Methodology note aligned to GHG Protocol, Full audit trail / logs
      • How would you prefer we demonstrate reconciliation to your historical inventory—side-by-side dashboard, variance report, or narrated walkthrough? Options: Side-by-side dashboard, Detailed variance report, Narrated walkthrough session, Combination
      • When would you like a readiness review meeting scheduled—after initial ingestion, after validation, or right before verification handoff? Options: After initial ingestion, After validation, Right before verification handoff, At multiple milestones
    2. Deployment Enablement

      Schedule and execute integrations, supplier survey rollouts, and the Scope 3 pilot with clear owners, milestones, and rollback plans.

    3. Validation Checklist

      Reconcile results against prior inventory, verify GHG Protocol-aligned calculations, and assemble evidence for third-party verification.

      Validation Questions

      Opening: What’s top of mind about your inventory?

      • What is the single most important emissions-related goal you must deliver in the next 12 months? Options: Complete annual GHG inventory, Produce verification-ready report, Meet regulatory filing requirements, Publish targets for investors, Scope 3 coverage improvement, Other
      • Who on your team will be the day-to-day owner of this effort (role/title)? Options: Sustainability Director, EHS Manager, ESG Analyst, Finance Lead, IT/Integration Lead, Other
      • Which stakeholders must sign off before you can consider the inventory complete? Options: Sustainability, EHS/Operations, Finance, Legal/Compliance, Procurement/Supply Chain, Executive/Board
      • How do you feel about your ability to meet this goal right now? Tell us in a sentence.
      • What target month or deadline are you working toward? Options: Next 4 weeks, 1–2 months, 3–6 months, 6–12 months, No fixed date

      Are you sure your numbers mean what you think?

      • When you compare last year’s inventory to your current spreadsheets, where do you see the biggest unexplained differences?
      • How often do you reconcile platform outputs or third-party results against your internal spreadsheets? Options: Monthly, Quarterly, Annually, Only during audits, Never
      • What tolerance would you accept between the platform’s calculated inventory and your historical numbers before you’d investigate further? Options: <1%, 1–5%, 5–10%, 10–20%, >20%
      • Describe a recent instance where an inventory discrepancy caused internal concern—what happened and who raised it?
      • If a reconciliation uncovered a systematic issue, how quickly could your team mobilize to inspect source data? Options: Within days, 1–2 weeks, 1 month, Longer than a month

      Who really owns the data (and the headaches)?

      • Which systems or data sources currently feed your inventory work (pick all that apply)? Options: ERP (finance/procurement), Utility bill portal, Fuel/fleet telematics, Travel/expense systems, Procurement/spend data, Supplier surveys, Manual spreadsheets, Other
      • For each of those sources, which team or role is responsible for providing access and verifying correctness?
      • How often are those source data refreshed or audited today? Options: Real-time/API, Daily, Weekly, Monthly, Quarterly, Ad hoc
      • Do you have API credentials, shared folders, or other connection mechanisms already in place for these systems? Options: Yes, for most systems, Yes, for some systems, Only manual files, No access established yet
      • When data look wrong, whose decision is it to override or correct the inventory? How does that feel to you?

      Where do the biggest blind spots hide?

      • If you had to name two Scope 3 categories you feel least confident about today, which would they be? Options: Purchased goods & services, Capital goods, Fuel- and energy-related activities, Upstream transport & distribution, Waste, Business travel, Use of sold products, Other
      • Which method do you currently use most for those categories (spend-based, activity-based, supplier-specific, other)? Options: Spend-based, Activity-based, Supplier-specific data, Hybrid, We don’t track this
      • Roughly what percentage of your Scope 3 emissions are supported by supplier-provided data vs. estimates or proxies? Options: 0–10%, 10–30%, 30–60%, 60–90%, 90–100%
      • What has been your typical supplier survey response rate and how long have you been running surveys? Options: >75%, 50–75%, 25–50%, <25%, We haven’t run surveys
      • Which procurement or supplier relationships would be most open to a pilot that requests actual activity data?

      If a verifier read your files tomorrow, what would make them raise an eyebrow?

      • Do you currently have documented calculation methodologies and data lineage that align to GHG Protocol for each scope? Options: Fully documented, Partially documented, High-level only, Not documented
      • What types of evidence can you produce today to show how an emissions value was derived (invoices, meters, telemetry, survey responses, assumptions log)? Options: Invoices/utility bills, Meter/telemetry data, Supplier responses, Procurement records, Assumptions & calculations log, None of the above
      • Have you previously gone through third-party verification or an audit of your inventory? If yes, what were the main findings? Options: Yes—minor findings, Yes—material findings, No, never verified, Currently undergoing verification
      • Which calculation areas worry you most for defensibility (emission factors, scope boundaries, allocation rules, temporal alignment)? Options: Emission factors, Boundary definitions, Allocation approaches, Data completeness, Temporal mismatches, Other
      • How would you describe your current documentation and audit trail—robust, adequate, fragile, or non-existent? Options: Robust, Adequate, Fragile, Non-existent

      What would it feel like to stop redoing spreadsheets every year?

      • On average, how many person-hours does your team spend consolidating and reconciling GHG data each reporting cycle? Options: <40 hrs, 40–120 hrs, 120–300 hrs, >300 hrs
      • How many facilities or business units must contribute data to your inventory? Options: 1–10, 11–50, 51–200, 200+
      • Which manual tasks eat the most time today (data cleaning, survey follow-ups, factor lookups, reconciliation, report formatting)? Options: Data cleaning, Survey follow-ups, Emission factor research, Reconciliation, Report preparation, Other
      • When automation has failed in the past, what was the root cause—technical, people, data quality, or process? Options: Technical/integration, People/roles, Data quality, Unclear processes, Other
      • If we could eliminate one recurring manual step for you, which would create the largest relief and why?

      Where would a small win create huge momentum?

      • If you were to pilot our platform, which scope or category would you prefer we tackle first to demonstrate value? Options: Scope 1 (fuel/onsite combustion), Scope 2 (purchased electricity), Scope 3—Purchased goods, Scope 3—Business travel, Custom category
      • What concrete success signals would convince your leadership this pilot is worth scaling (time saved, % coverage, verification readiness, cost avoided)? Options: Time saved, % Scope coverage, Verification readiness, Improved data quality, Cost savings, Other
      • Which internal champion or sponsor would help clear obstacles during a pilot? Options: Sustainability Lead, Finance Sponsor, IT Sponsor, Procurement Lead, Ops/Plant Manager, Other
      • What integrations would be highest priority to prove during a pilot (ERP, utility portal, telemetry, travel/expense)? Options: ERP, Utility portal, Telematics/IoT, Travel & expense, Procurement/spend, None—manual files only
      • How long would you be willing to run a pilot before deciding to proceed to full rollout? Options: 2–4 weeks, 4–8 weeks, 8–12 weeks, Longer than 12 weeks

      Agreeing the next honest step

      • What is the decision-making timeline for choosing a platform and vendor? Options: Immediate (this month), 1–2 months, 3–6 months, 6–12 months, Undecided
      • What procurement, security, or legal approvals are typically required for a software pilot and how long do they take?
      • Do you have a budget allocated for this initiative this fiscal year? Options: Yes—fully allocated, Partially allocated, No, need approval, Unsure
      • What would you need to see in a demo or pilot to confidently recommend moving forward? Options: Reconciled inventory vs spreadsheets, Verification-ready report sample, Live integration with a key system, Supplier survey workflow in action, Security & compliance documentation, Other
      • Who else should be on the follow-up call to remove blockers (names/titles)?
      • Are there any open concerns we haven’t covered that would prevent you from starting a pilot in the next quarter? Options: Yes—budget, Yes—data access, Yes—internal bandwidth, No major concerns, Other
  7. Success

    Review delivered inventory, confirm verification readiness, and maintain a shared channel for annual updates and Scope 3 improvement plans.

    Success Reviews

    • Delivered Inventory Review (Reconciliation & Validation)
    • Verification Readiness Assessment (GHG Protocol & Verifier Checklist)
    • Evidence Assembly Workshop (Hands-on Documentation)
    • Annual Update & Scope 3 Improvement Planning
    • Stakeholder Acceptance & Handover

    Issues & Enhancements

    • Create and share the annual inventory timeline (data cutoffs, internal review dates, verifier windows).
    • Determine and document whether the inventory is verification-ready against the provided checklist.
    • If not ready, produce a prioritized remediation plan with owners, deadlines, and impact on verification timing.
    • Confirm technical alignment with GHG Protocol for material calculation methods.
    • Platform team to produce a verification-readiness scorecard mapping each checklist item to evidence and status.
    • Customer to secure any missing contractual data (supplier attestations, invoices) and upload to the shared evidence folder.
    • Schedule a pre-audit call with the third-party verifier (if progressing) and provide the readiness scorecard.
    • Pre-work review
    • Complete the evidence mapping for all material inventory lines or document agreed exceptions.
    • Populate the shared evidence repository with proper naming and tagging conventions for verifier use.
    • Assign clear owners and deadlines for any remaining evidence items.
    • Customer teams to upload identified missing documents (supplier attestations, source invoices, meter calibration records) into the shared channel.
    • Platform team to apply tags and generate a downloadable evidence index for the verifier.
    • Schedule a secondary evidence review checkpoint one week before the planned verifier engagement.
    • Pre-work: materiality & baseline
    • Approve an annual update calendar and a single shared channel with access and tagging rules for evidence and updates.
    • Endorse a prioritized Scope 3 improvement roadmap with pilots, milestones, and KPIs.
    • Assign governance and owner responsibilities for ongoing supplier engagement and data collection.
    • Pre-work check
    • Launch the Scope 3 pilot with the selected supplier cohort and provide the survey templates.
    • Define and publish KPI dashboard for coverage and data quality to the shared channel.
    • Pre-work verification sign-off packet
    • Obtain formal stakeholder acceptance (or documented conditional acceptance) of the verification-ready inventory.
    • Complete operational handover with clear owners, SLAs, and escalation paths for ongoing maintenance.
    • Confirm the annual cadence and schedule the next kickoff and quarterly checkpoints.
    • Circulate signed acceptance or conditional acceptance document and store in the shared channel.
    • Onboard the customer's operational owners to the platform support process and share SLA matrix.
    • Create calendar invites for the next annual kickoff and quarterly check-ins with agendas.
    • Confirm the delivered inventory reconciles to the customer's records for material line items or document specific, agreed exceptions.
    • Identify and prioritize outstanding gaps that block verification readiness with owners and deadlines.
    • Obtain stakeholder agreement on which variances require remediation versus accepted adjustments.
    • Customer to upload final prior-year spreadsheets, source meter files, and exception notes to the shared channel.
    • Platform team to produce a variance report showing calculation lineage for each material delta.
    • Assign owners and due dates for each unresolved variance item and schedule the Evidence Assembly Workshop.
    • Pre-work confirmation
    • Current state summary (one sentence)
    • Current state in verification terms (one sentence)
    • Review delivered outcomes vs. acceptance criteria
    • Future state (one sentence)
    • Evidence checklist walkthrough
    • Annual cadence & shared channel design
    • Decision-maker sign-off
    • Top-line reconciliation
    • Line-item evidence mapping (interactive)
    • Consequence & risk framing
    • Populate shared channel & tagging standards
    • Methodology and calculation alignment checks
    • SLA, support, and escalation path
    • Scope 3 improvement roadmap
    • Root-cause review of variances
    • Mock verifier walkthrough
    • Supplier engagement and incentives
    • Handover to operational owners
    • Proof: calculation spot-checks
    • Evidence sufficiency review
    • Consequence discussion
    • Owner commitments and deadlines
    • Governance, KPIs, and reporting
    • Decision and acceptance criteria
    • Schedule next-year kickoff and recurring checkpoints
First-Party AI

1-2 minutes please — Your AI agent is working

First-Party AI™ can make mistakes. Always check important information.