Skip to main content
Skip table of contents

Executive Approvals

POLICY NAME

Executive Approval

VERSION NO.

4.0

EFFECTIVE DATE

01/20/2021

DATE OF LAST REVISION

10/27/2025

ADMINISTRATOR RESPONSIBLE

Vaibhav Bansal

EMAIL

vaibhav.bansal@wenergysoftware.com

APPLIES TO

GROUP 1

Client Operations

GROUP 3

CloudOps

GROUP 2

Services

GROUP 4

Development

 

REVISION HISTORY

Date

Version

Description of Change

Author(s)

01/20/2021

1.0

Current Published Version

Jenny Hays
Michael Ferrante

 10/17/2023

 

Added SOC Violation Form to the page.

Erik Frazier

 11/1/2023

2.0

 Current published version

Erik Frazier

04/17/2024

3.0

Updated Roles and Responsibilities

Vaibhav Bansal

10/27/2025

4.0

Updated Roles and Responsibilities

Vaibhav Bansal

 

APPROVAL HISTORY

Date

Version

Approved By

01/20/2021

1.0

Michael Tetzlaff

10/19/2023

2.0

Vaibhav Bansal

04/17/2024

3.0

Vaibhav Bansal

10/27/2025

4.0

Vaibhav Bansal

SCOPE

Changes to a hosted client’s accounting application environment or data must follow an approval process that includes getting executive approval for the following: Scripts, Code Deploys, and Config changes. This document outlines the process for Executive Approval for these changes.

Audience

The policy and/or procedure outlined here applies organization wide and must be available to all employees to review and understand.

EXECUTIVE APPROVAL

Purpose of the Policy

Short description of the policy as described above.

Procedures

This document will outline the various procedures around changes to a hosted clients’ environment or data. They include PROD restores from backup, scripting, code deploys, and config changes.

PROD Restore from Backup

A PROD restore from backup is a special case that is outside normal business practices. As such, additional approval and explanation is required to get it authorized.

  1. Provide detailed explanation of the reasoning for requesting a PROD restore from backup.

  1. Explain why in app functionality or standard scripting cannot be used to resolve the issue.

  1. Provide notes of what process has been done to validate which data may have changed since backup and how that data will be addressed after restoring.

  1. Verify exact database backup date and time that will be restored.

  1. Provide client approval.

  1. Requires internal Approval from the Head of Product and/or Engineering.

  1. Client approval must include the detailed explanation above as to get informed consent of the request from the client.

  1. Utilize the JIRA portal to obtain executive approval on the above two items to the Dev Planning Committee/ELT

 Scripts, Code Deploys and Configuration Changes

Executive Approval is needed for script, Code deploys and Configuration changes to a Live Client Prod environment.

Change Control Procedure - Verification

The W Energy Software Team completes the following steps before entering the story and will mark tasks corresponding to the following verifications as completed.

  1. Create the request/script using the correct environment.  Typically, this is the latest copy of the production database on the code version that is in the PROD environment.

  1. Run the scripts or changes in the test or internal environment.

  1. Perform the data validations of the expected outcome from the changes applied within the database and application.

  1. Once confirmed the changes are what is to be expected, provide the client a request via their issue in JIRA.  Attach the script or changes in the JIRA communication as an attachment.

  1. When the client approves the changes, seek internal ELT approval (reference roles and responsibilities table below)

  1. Once approve, add the approval to the JIRA ticket and proceed with the PROD change.

Exceptions

Direct-to-PROD exceptions can be approved in urgent circumstances for scripts and config change deploys.

NOTE: The client must give explicit direct-to-prod deploy approval via the ticket in JIRA.  If it is obtained outside of JIRA (example in an e-mail). attached it to the deploy ticket in JIRA.

Breach of Policy

Any breach to this procedure will be noted and the person who breached the policy will be directed to review the procedure documentation.

Fill out the SOC Incident Report Form with the details of the violation.

E-mail the Incident Report Form to erik.frazier@wenergysoftware.com and attach it as an internal note in JIRA.

 TERMS AND DEFINITIONS

Define any acronyms, jargon, or terms that might have multiple meanings or need clarification for the consumer of this document.

TERM

DEFINITION

Script

Any sql query that changes Client data within the database. This can include insert, update, delete, and other various sql commands.

·       Sql queries to just retrieve data do not need executive approval.

Code Deploy

A deploy of either the existing or new release version to the Client PROD environment.

Config Change

A change to the config.yml file that can change the behavior of the Client environment. All PROD config changes require approval

ROLES AND RESPONSIBILITIES

The following people are responsible for ensuring this policy and procedures are enacted.

ROLE

RESPONSIBILITY

Michael Stein

Kelsi Flores

Vaibhav Bansal

Executive approver who ensures all steps have been taken before approving a PROD action.

Vaibhav Bansal

Executive approver who must be engaged for PROD restores or for any action that adds additional costs at AWS.

Vaibhav Bansal

Executive approver who ensures all steps have been taken before any PRODUCTION REFRESHES

  SOC Incident Violation Form 2023.docx

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.