Starting Together: Why Scope 3 Is Now a Priority

• How did Scope 3 disclosure become a priority for your team?
• When did the investor letter or SBTi commitment set your first reporting deadline? Options: Within 3 months, 3 to 6 months, 6 to 12 months, More than 12 months, No fixed deadline yet
• Describe the top three commodity categories or supplier types you believe drive most of your Scope 3 impact Options: Raw materials, Packaging, Contract manufacturing, Transportation and logistics, Retail/distribution partners, Other
• Which internal stakeholders will need final signoff on published Scope 3 numbers? Options: Head of Procurement, Director of Supply Chain Sustainability, CFO/Finance, General Counsel/Legal, Investor Relations, Other
• Who currently manages supplier communications and data requests for sustainability initiatives? Options: Procurement team, Operations/supply chain, Sustainability team, Vendor management office, A combination of teams, Other

Where the Numbers Come From Today

• If you published Scope 3 based primarily on spend-based averages, what specific investor or reputational consequence worries you most? Options: Activist investor scrutiny, Auditor pushback, Customer complaints, Regulatory challenge, Media exposure, Other
• Tell me exactly how your team currently calculates supplier emissions for your top two commodity categories
• List the supplier-level data points you already collect or could access within 30 days Options: Annual production volume, Material composition, Energy consumption per site, Transportation distances, Purchase order line-level spend, None readily available
• Which of your current methods would have to remain true for your team to keep using them instead of adopting primary supplier data? Options: Cost is lower, Integration is simpler, Audit acceptance, Familiarity for stakeholders, Sufficient accuracy for disclosure, Other
• What cadence do you currently use or expect for supplier-facing surveys or data calls? Options: Ad hoc for reporting, Quarterly, Biannual, Annual, Never run supplier surveys

What's Blocking Reliable Supplier Data

• What single operational failure in supplier outreach would make this project fail?
• Walk me through the last time your team sent a supplier sustainability questionnaire, from invitation to closed response
• How many suppliers in a typical pilot cohort can procurement actively manage communications for in a month? Options: Fewer than 10, 10 to 25, 26 to 50, 51 to 100, More than 100
• Who in your organization would be the point person for troubleshooting low response rates during a pilot? Options: Procurement lead, Supplier relationship manager, Sustainability lead, IT/system owner, Third-party vendor, No one assigned yet
• Which typical supplier barriers do you expect us to face in your categories Options: Language and localization, Limited internal data at supplier, No sustainability team at supplier, Data format variance, Legal concerns about sharing, None of the above

The Other Options on Your Table

• Why would your team choose to keep the current approach rather than adopt a platform that collects primary supplier data? Options: Lower short term cost, Familiar process, Better internal control, Concerns about supplier burden, Skepticism about vendor claims, Other
• Name the specific alternatives under consideration, including incumbent platforms, consultancies, or internal projects Options: Incumbent platform, Sustainability consultancy, Internal build, Other vendor platform, No alternatives considered yet
• If you stayed with the incumbent, what conditions around cost, integration, or auditability would need to hold true?
• Has anyone on your team proposed solving this without an outside vendor, and if so who and why? Options: Yes, procurement proposed, Yes, IT proposed, Yes, sustainability proposed, No internal proposal to build, Other
• What would have to be true about your current approach for you to make no change this year?

Acceptance Criteria That Turn Pilots Into Commitments

• Should the pilot prove supplier primary data is materially different from spend-based estimates, what single outcome would make you sign a rollout within two weeks?
• Rate the minimum supplier response rate you would accept from a 50-supplier pilot to move forward Options: 20% or less, 21% to 40%, 41% to 60%, 61% to 80%, 81% to 100%
• List the data quality thresholds your assurance partner has indicated they need for disclosure-ready numbers Options: Completeness per supplier, Traceable activity data, Documented emissions factors, Independent assurance statement, Other
• Identify the single approver whose authorization would accelerate contracting after pilot success Options: Head of Procurement, CFO, General Counsel, Director of Sustainability, Procurement Committee, Unknown
• What timeline for pilot-to-production would your organization consider acceptable if acceptance criteria are met? Options: Immediate (within 30 days), 30 to 90 days, 3 to 6 months, Longer than 6 months, Unsure

Integration Reality Check and Operational Constraints

• What integration failure or missing connector would cause you to pause or cancel the deployment?
• Describe the third-party systems that must connect for supplier-level data to feed your disclosure process, for example ERP, supplier portal, or MDM
• Identify the team or role that owns API keys and whether they can provide test credentials within four weeks Options: IT integrations team, Procurement systems owner, Sustainability data team, No one assigned yet
• Are your procurement and supplier master datasets consolidated in a single system or split across multiple systems? Options: Single ERP or master system, Split across ERP and procurement tools, Multiple regional systems, No centralized supplier master
• When access to supplier contact information requires legal review, what is the fastest path to approval and how long does that typically take?
• Which security or compliance approvals must be completed before we can accept supplier files into the platform Options: Data privacy review, Security assessment, Vendor risk assessment, Legal data sharing agreement, No approvals needed

Pilots That Prove the Numbers

• Imagine a pilot shows supplier-level emissions 20% different from spend-based estimates, how quickly would your finance team accept that as credible for reporting purposes? Options: Immediately, After one reconciliation cycle, After external assurance, They would not accept it
• Name the supplier cohorts you want included in a pilot to represent both spend and risk Options: Top spend suppliers, High-emitting commodities, Strategic suppliers, Geographically concentrated suppliers, Random stratified sample
• Please enumerate the acceptance metrics you will track during the pilot besides response rate Options: Data completeness, Consistency vs spend-based estimates, Time to validate responses, Integration success rate, Supplier satisfaction
• Will your assurance partner need raw supplier-level files, sample-level attestations, or summarized outputs to validate the methodology? Options: Raw files, Sample attestations, Summarized reports, Combination, Not sure yet
• Should the pilot fall below your response threshold, what contingency would cause you to stop further investment? Options: Scale back scope, Extend pilot duration, Pause and rework supplier outreach, Cancel project, Other

Deployment and Rollout Expectations

• Are you confident your team can complete supplier onboarding and integrations for a full rollout within six months if the pilot succeeds? Options: Yes, Probably, Unlikely, No
• Provide the names and types of integration endpoints your team expects to map for go-live, for example ERP supplier API or procurement CSV export
• Explain the process by which the platform will receive supplier contact lists and which team controls that export
• Specify the verification checkpoints you require before switching to platform-based calculations in production Options: Parallel run results within tolerance, Third-party assurance signoff, Stakeholder review meeting, No switch without CFO approval
• Assuming acceptance criteria are met, what procurement signoff sequence and toolchain would complete an enterprise purchase order within your organization?

Success, Governance, and Next Steps

• Define the governance role that will own ongoing data quality and emissions reporting after rollout Options: Director of Sustainability, Head of Procurement, Data governance team, Cross-functional committee, Not defined yet
• State the frequency your team will require supplier data refreshes for disclosure-ready reporting Options: Quarterly, Biannual, Annual, On-demand for key suppliers, Other
• Provide the KPIs you will monitor to validate disclosure readiness over time Options: Supplier response rate, Data completeness, Variance vs spend estimates, Integration uptime, Assurance findings
• In the event a quarterly report reveals hotspots requiring procurement changes, what budget authority is available to act and on what timeline?
• What immediate next step would move this conversation forward if we can show a pilot plan aligned to your constraints? Options: Schedule pilot scoping workshop, Share pilot statement of work, Run a short feasibility check, Put on hold for later

• Solution Experience — Supplier Data, Methodology, and Integration

• Confirm the current state and what it is costing you
• You confirm the demonstrated supplier-data workflow collects primary data for the sample commodity and removes the manual rework you described.
• Deliver a pilot configuration proposal for 50 suppliers across two commodity categories, including localized questionnaires, emissions-factor mapping, and an integration endpoint checklist.
• You confirm the lifecycle methodology and emissions-factor mapping approach aligns with your assurance expectations or surface any remaining objections.
• Walk through supplier data collection using your real scenario
• Provide a sample list of pilot suppliers and two target commodity SKUs, including the supplier IDs used in your supplier management system.
• Demonstrate lifecycle methodology and emissions-factor mapping on your commodity
• Complete the field-mapping template with one API endpoint example and sample payloads for the integration test.
• You confirm the integration approach maps to your supplier management constraints and will not create a separate data collection channel.
• Show the procurement integration using your supplier identifiers
• You agree on pilot success metrics, including target suppliers, commodity cohorts, response-rate goals, and data-quality thresholds.
• Produce a short comparison report from the session showing the sample supplier-collected data versus spend-based estimates and the observed delta.
• Present side-by-side comparison: supplier-collected data vs spend-based estimates
• Agree pilot acceptance criteria and next steps
• Forced validation, confirm this maps to what you described

• Solution Experience — Supplier Data, Methodology, and Integration
• Solution Experience Deck
• Solution Brief

• meeting
• slides
• document

• Onboard Suppliers and Provision Portal Access
• Deploy Localized Industry-Specific Questionnaires
• Import Supplier Master Data
• Integrate with Procurement System
• Map Emissions Factors to Materials and SKUs
• Add Custom Emissions Factors and Database Extensions
• Configure Calculation Methodologies and Scopes
• Calculate Product and Corporate Carbon Footprints
• Run Parallel Spend-Based vs Primary Data Calculations
• Validate Supplier Data and Flag Anomalies
• Automate Supplier Reminders and Escalations
• Generate Disclosure Reports Aligned to Frameworks
• Provide Audit-Ready Data Exports and Lineage
• Train Suppliers on Reporting Templates and Submission

Onboard Suppliers and Provision Portal Access

• How many suppliers do you plan to include in the pilot cohort (by count)? Options: Less than 50, 50-200, 201-1,000, More than 1,000
• Which supplier cohorts should be included (e.g., direct raw material suppliers, contract manufacturers)?
• Who in your team will approve portal user invitations and supplier access roles?
• When do you expect suppliers to receive portal access after kickoff? Options: Within 1 week, 1-3 weeks, 3-6 weeks, After 6 weeks
• Do you require single sign-on integration for supplier portal access? Options: Yes, No, Prefer optional SSO

Deploy Localized Industry-Specific Questionnaires

• List the primary supplier data fields your questionnaires must capture (e.g., material weights per SKU, process energy use in kWh, transportation distances).
• Identify the two commodity categories you want localized questionnaires for during the pilot.
• Specify localization needs for questionnaires including languages, units of measure such as kg versus lb, and local terminology for material grades.
• Provide examples of 3 representative SKUs per commodity that will be used to test questionnaire mapping.
• Select desired languages for pilot questionnaires. Options: English, Spanish, Portuguese, Mandarin, Other

Import Supplier Master Data

• Provide examples of supplier master data fields available for import (supplier ID, legal name, primary contact email, commodity tags, annual spend).
• How will you handle missing supplier identifiers or taxonomy tags during import (manual mapping, default categories, supplement from procurement)? Options: Manual mapping by buyer team, Default to generic category, Supplement with procurement data, Other
• Which supplier cohorts in your supplier master will be flagged for pilot import (provide tag names or counts)?
• Confirm whether your supplier master export supports API access or only file exports. Options: API access available, File export only (CSV/Excel), Both available
• Are there privacy, NDA, or supplier consent requirements that affect importing contact or contract data? Options: Yes, No, Some suppliers restricted

Integrate with Procurement System

• Describe your current procurement system type and version used to manage purchase orders and supplier records.
• Confirm API endpoint types available for integration with the procurement system (REST, SOAP, bulk SFTP). Options: REST, SOAP, SFTP, No API available
• List the specific procurement endpoints you need the platform to read or write (supplier master, PO line items, invoice line items).
• Outline responsibilities for integration testing and sandbox credentials provision between your IT team and the integration owner.
• When do you expect integration testing to begin relative to pilot start? Options: Before pilot, During pilot, After pilot

Map Emissions Factors to Materials and SKUs

• Explain mapping rules you currently use to map materials or commodity codes to emissions factors (match by material name, HS code, product category).
• Which commodity categories require custom emissions-factor mapping for the pilot?
• Are there materials or specialized alloys in your bills of materials that likely lack coverage in standard emissions-factor databases? Options: Yes, No, Unknown
• Who will own final approvals for emissions-factor overrides and custom mappings within your procurement or sustainability team?
• How should product-to-SKU-to-material mapping be validated before calculations (buyer QA, supplier confirmation, sampling of BOMs)? Options: Buyer QA, Supplier confirmation, Random sampling, Third-party validation

Add Custom Emissions Factors and Database Extensions

• Identify acceptable sources for custom emissions factors (industry life cycle assessment studies, supplier-specific LCAs, internal lab data).
• What format must custom emissions factors be supplied in (per kg CO2e per unit, kg CO2e per m2, with lifecycle stage annotation)? Options: kg CO2e per kg, kg CO2e per unit, Other
• Who will maintain custom-factor mappings after go-live and how frequently will they be reviewed (monthly, quarterly, annually)? Options: Vendor-managed monthly, Buyer-owned quarterly, Hybrid
• Confirm required export formats and metadata fields your assurance partner will need for factor provenance (CSV with source DOI, reference to ISO 14067, supporting LCA report links).
• Describe any contractual restrictions on storing supplier-specific emissions factors or LCA reports in the platform.

Configure Calculation Methodologies and Scopes

• Choose which calculation standards or frameworks to align with for the pilot (GHG Protocol Scope 3, Product Category Rules, SBTi guidance). Options: GHG Protocol Scope 3, Product Category Rules (PCR), SBTi-relevant guidance, Other
• Estimate the minimum supplier response rate you require to consider the pilot representative of spend. Options: >70%, 50-69%, 30-49%, Less than 30%
• Indicate desired duration for parallel runs comparing spend-based versus primary-data calculations. Options: 2 weeks, 4 weeks, 8-12 weeks, Quarterly cycle
• How will methodology changes or calculation assumptions be communicated to suppliers and internal stakeholders?
• Which assurance partner checklists or validation steps must the methodology configuration satisfy during pilot review?

Calculate Product and Corporate Carbon Footprints

• Provide example SKUs and the bill-of-materials granularity required for product footprints during the pilot.
• What acceptance criteria will confirm pilot success for calculation outputs (for example aggregated-category delta thresholds versus spend-based estimates and minimum data coverage percentages)?
• When should production rollout begin after pilot calculations meet acceptance criteria? Options: Immediately after pilot, After 1 month stabilization, After 3 months monitoring
• Describe the reporting cadence and templates required for product and corporate footprint updates (monthly, quarterly, and annual disclosure-ready outputs). Options: Monthly, Quarterly, Annual, Custom
• Confirm any required audit fields in footprint outputs such as line-item mapping to supplier response, factor source, and calculation version.

Run Parallel Spend-Based vs Primary Data Calculations

• Indicate the scope including time period and spend buckets for parallel run comparisons.
• Estimate percentage of total category spend you expect the pilot suppliers to represent. Options: <10%, 10-30%, 31-60%, >60%
• How will you treat suppliers with no primary data in parallel calculations (use spend-based estimates, proxy from peers, or flag as gap)? Options: Use spend-based estimates, Proxy from peers, Exclude from calculation, Other
• What evidence will validate supplier data quality versus spend-based estimates (for example line-item mass balance, energy receipts, third-party LCA reports)?
• Do pilot suppliers require live training on the questionnaire or will written guides suffice? Options: Live webinars, Written guides, Both, Neither

Validate Supplier Data and Flag Anomalies

• Describe the validation rules you expect the platform to run on supplier responses (completeness checks, unit consistency, mass-balance screening).
• Identify third-party data sources you want used to cross-check supplier submissions (invoices, freight manifests, certified LCA studies).
• Are there numeric thresholds that should trigger anomaly flags such as energy per unit beyond a multiple of the category average? Options: Yes, No, Define during scoping
• Specify escalation paths and owners when anomalies require supplier follow-up or audit.
• Provide a sample of expected data ranges for key fields (for example kg raw material per SKU, kWh per unit) to tune anomaly rules.

Automate Supplier Reminders and Escalations

• What reminder cadence should be used for pilot supplier questionnaire nudges (days between reminders)? Options: Every 3 days, Every 7 days, Every 14 days, Custom
• Specify escalation owners and channels for nonresponse escalation (email, procurement platform task, phone outreach). Options: Email, Procurement task, Phone outreach, Account manager outreach
• Do you require reminder personalization by supplier segment or commodity during the pilot? Options: Yes, No
• How will escalation outcomes be recorded and closed in your supplier management workflow?
• Estimate the expected uplift in response rate from automated reminders for the pilot. Options: <10%, 10-30%, 30-50%, >50%

Generate Disclosure Reports Aligned to Frameworks

• Choose which disclosure frameworks to align pilot reports with (GHG Protocol Corporate Standard, CDP-format, SBTi reporting requirements).
• What file formats and templated fields are required for your corporate disclosure team (CSV, XLSX, XML, platform dashboard snapshots)? Options: CSV, XLSX, XML, Dashboard access only
• When should validated disclosure outputs be handed to finance and investor relations for annual reporting? Options: Immediately after pilot, Next quarter, End of fiscal year
• Describe any public disclosure restrictions or embargoes that affect when results can be published.
• Are there internal sign-off gates such as legal, procurement, or investor relations required before publishing disclosure-ready reports? Options: Yes, No, Some groups only

• desired_state
• current_state
• stakeholders
• gaps
• success_criteria
• decision_readiness
• desired_state
• decision_readiness
• current_state
• success_criteria
• gaps
• stakeholders
• gaps
• desired_state
• decision_readiness
• stakeholders
• current_state
• success_criteria
• decision_readiness
• current_state
• success_criteria
• decision_readiness
• decision_readiness
• decision_readiness

• Subscription Agreement
• Order Form
• Master Services Agreement (MSA)
• Statement of Work (SOW) — Pilot & Implementation
• Data Processing Agreement (DPA)
• Pilot Acceptance Addendum
• Rollout Schedule & Milestone Commitment
• Change Order Agreement

• Go-live Health Check (weeks 1-4)
• First Measurement Review (weeks 4-10)
• Acceptance Gate Decision (around day 90)
• Monthly Operations Check-in (post-acceptance, monthly)
• Quarterly Success Review (ongoing)

• Update the remediation backlog status with new ETAs and publish to the shared channel.
• For any failed criteria, have a remediation plan with scope, target dates, and verification steps to reach acceptance.
• Confirm the plan and timeline for decommissioning or retaining the incumbent tool and archiving migrated data.
• Publish the acceptance decision document with per-criterion pass/fail status and the buyer signatory captured.
• If remediation is required, publish the remediation backlog with owners, milestones, and verification tests tied to each failed criterion.
• Execute the incumbent wind-down tasks including contract termination steps or read-only retention policy and data archive confirmation.
• Operational KPI snapshot
• Keep supplier response rate and integration error rate within agreed operational tolerances and record deviations for escalation.
• Drive the remediation backlog toward closure with clear near-term deliverables for the next 30 days.
• Document any outstanding assurance questions and the evidence the platform will supply to address them.
• Re-confirm success criteria and owner matrix
• Produce a short assurance packet addressing current methodology exceptions and circulate for reviewer comment.
• Confirm supplier outreach schedule for the next 30 days to raise response rates for any underperforming cohorts.
• Trend analysis vs Solution Scope targets
• Validate whether the realized coverage and data-quality metrics are aligning with the Solution Scope targets and identify any persistent gaps.
• Agree a prioritized enhancement list and mitigation plan for systemic risks to preserve disclosure readiness.
• Capture and publish lessons learned that will reduce repeat issues in supplier onboarding and data collection.
• Publish the quarter's performance dashboard and the prioritized enhancement backlog with target delivery quarters.
• Document mitigation actions for the top two systemic risks and assign target completion dates.
• Circulate the lessons-learned summary and update the supplier onboarding playbook accordingly.
• Confirm deployment readiness or have a documented remediation plan with owners and dates for any defects.
• Re-validated success criteria and owner assignments as documented in Solution Scope.
• Established a shared channel and cadence for reporting go-live issues and progress.
• Publish the go-live issue log with owners and target resolution dates to the shared channel within 24 hours.
• Update API credential inventory and confirm with the integration team that endpoints remain stable for the next 7 days.
• Present supplier response rate and spend coverage
• Determine whether supplier response rate and spend coverage are trending toward the Solution Scope targets and record any variances.
• Identify the top 3 root causes for metric gaps and agree corrective actions with concrete timelines.
• Confirm the timeline to the acceptance gate and what will be re-evaluated there.
• Publish a corrective action plan covering questionnaire localization fixes, supplier outreach cadence adjustments, and integration mapping corrections with target completion dates.
• Prepare an updated dataset comparing primary emissions to spend-based estimates for the acceptance gate meeting.
• Restate acceptance criteria and numeric targets
• Produce a documented acceptance decision for the pilot, with pass/fail recorded per criterion and a named buyer signatory if accepted.
• Risk review: emissions-factor gaps and methodology issues
• Present outcome data against each criterion
• Open issues triage and burn-down
• Data quality comparison versus spend-based estimates
• Deployment and integration validation
• Pass/fail determination and signatory capture
• Integration reliability and error review
• Enhancement request prioritization
• Assurance partner feedback and methodology exceptions
• Early adoption and usage signals
• Root-cause analysis for shortfalls
• Define remediation plan for any failed criteria
• Lessons learned and process improvements
• Enhancement and configuration requests review
• Blockers and open defects triage
• Confirm next-month operating priorities
• Incumbent system wind-down confirmation
• Agree immediate remediation actions and communication plan
• Agree corrective actions and acceptance timeline