Introduction

This guide outlines the implementation process for Sumday’s software. To be used by Sumday partners when deploying the solution for their clients. The implementation plan is designed to ensure a smooth transition and maximise the benefits of Sumday for client organisations.

1. Project Kickoff and Initial Setup (8-10 hours)

Goal: Establish a clear roadmap for implementation by defining goals, timelines, and responsibilities.

• Initial Discovery Meeting:
  • Identify key stakeholders from the consulting firm and the client.
  • Determine the client’s carbon accounting goals and required emissions reporting.
  • Review current systems in use (ERP, accounting platforms, etc.), focusing on data availability and quality for carbon accounting.
  • Define the scopes (Scope 1, 2, and 3 emissions) and categories that need tracking.
  • Determine controls required around the carbon accounting and reporting process.
• Documentation of Structure & Existing Processes:
  • Review the client’s existing data collection and carbon accounting processes.
  • Document controls.
  • Collect historical emissions data and any existing emissions factors (EFs) or methodologies.
  • Map out clients consolidated structure (unless only one entity required)

Deliverable: A documented implementation plan including key milestones and responsibilities.

2. System Configuration and API Integration (10 - 12 hours)

Goal: Integrate Sumday with the client’s existing systems and ensure secure data access.

• API Setup and Integration:
  • Set up APIs to link Sumday with the client’s ERP or accounting systems (such as NetSuite, Oracle, or other custom systems).
  • Configure automated data pulls for ongoing transaction imports.
• Single Sign-On (SSO) Configuration:
  • Enable SSO to streamline user access for large teams.
  • Ensure SSO integration is compliant with the client’s internal security protocols.
• Reporting Structure Setup:
  • Set up a customisable reporting structure to allow for consolidated and business unit-level reporting.
    • If client works on a consolidated basis, then suggest tracking categories as a means to still track for multi-entity reporting.
    • If a client has multiple reporting requirements at different levels then you could suggest multiple Sumday instances for each entity.
  • Agree on review processes for carbon accounting, determining which teams require access for review and adjustments.

Deliverable: Fully integrated system with secure access, automatic data import, and a custom reporting structure.

3. Training and Change Management (10-15 hours)

Goal: Equip the client’s team with the knowledge and tools necessary to use Sumday effectively.

• Training Needs Assessment:
  • Identify key personnel requiring Sumday access and tailor training programs to different roles (e.g., sustainability team vs. finance team).
  • Break down training into phases, with initial focus on key users, followed by a broader rollout to ensure system-wide adoption.
• Sumday Academy Training:
  • Use Sumday’s Academy resources for staff training, ensuring that all relevant personnel understand how to input data, reconcile transactions, and generate reports.
  • Lias with Sumday support team to provide status reports at a intervals defined previously.