# NetSuite Sandbox and Release Change Log Worksheet

> Source: https://netray.co/tools/netsuite-sandbox-release-change-log-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

An editable log of NetSuite changes across sandbox, release preview and production, with test status and hours spent, exportable to Excel.

## Category

netsuite

## Erp

NetSuite

## Audience

- NetSuite administrator
- IT manager
- Internal auditor

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Date

**Key:** date

**Type:** date

#### Environment

**Key:** env

**Type:** select

**Options:**

- Sandbox
- Release Preview
- Production

#### Change

**Key:** change

**Type:** text

#### Type

**Key:** type

**Type:** select

**Options:**

- Script
- Workflow
- Saved search
- Custom record
- Role or permission
- Bundle or SDF
- Integration
- Configuration

#### Owner

**Key:** owner

**Type:** text

#### Tested

**Key:** tested

**Type:** select

**Options:**

- Yes
- Partial
- No

#### Status

**Key:** status

**Type:** select

**Options:**

- Planned
- In test
- Approved
- Deployed
- Rolled back

#### Hours

**Key:** hours

**Type:** number

**Format:** number

**Unit:** h

**Rows:**

**Date:** 2026-10-12

**Env:** Sandbox

**Change:** Work order notifier user event script

**Type:** Script

**Owner:** Sam Patel

**Tested:** Yes

**Status:** Approved

**Hours:** 14

**Date:** 2026-10-14

**Env:** Release Preview

**Change:** Regression test of assembly build and work order close

**Type:** Configuration

**Owner:** Maria Chen

**Tested:** Yes

**Status:** Deployed

**Hours:** 9

**Date:** 2026-10-16

**Env:** Sandbox

**Change:** New Production Planner role permissions

**Type:** Role or permission

**Owner:** Daniel Ortiz

**Tested:** Partial

**Status:** In test

**Hours:** 5

**Date:** 2026-10-20

**Env:** Production

**Change:** Saved search: gauges due in 30 days

**Type:** Saved search

**Owner:** Maria Chen

**Tested:** Yes

**Status:** Deployed

**Hours:** 2

**Date:** 2026-10-22

**Env:** Sandbox

**Change:** Routing import via CSV, 40 operations

**Type:** Configuration

**Owner:** Priya Nair

**Tested:** No

**Status:** Planned

**Hours:** 0

**Totals:**

#### Total hours

**Key:** hours

**Agg:** sum

**Format:** number

#### Changes logged

**Key:** change

**Agg:** count

**Format:** integer

**Summary:**

#### Average hours per change

**Key:** avg_hours

**Expr:** sum_hours / count

**Format:** decimal

**Notes:** Add one row per change and update the status as it moves. Filter by environment in Excel after export to prepare release test evidence. The log is a record aid and does not connect to your NetSuite account.

## Content

**Intro:** Most NetSuite problems after a release come from changes nobody recorded. A simple log of what changed, where it was tested and who approved it is the cheapest control an administrator can keep.

**Sections:**

#### How to use the log

**Body:** Add a row for each change in the order it is made. Mark the environment, the type of change and the owner. Update Tested and Status when the change moves forward. Use the hours column to learn what testing really costs so you can plan releases. Export to Excel before each audit or release review and keep a dated copy.

**Bullets:**

- One row per change, not per task
- Record test status honestly, including Partial
- Mark rollbacks instead of deleting rows
- Export dated copies for evidence

#### Sandbox and release preview

**Body:** NetSuite provides sandbox accounts for testing and a release preview window ahead of each of its two major releases per year. Teams normally use sandbox for building and testing their own changes and the release preview account to run regression tests of critical processes, such as order to cash, procure to pay and work orders. Log the preview tests so you can show which processes you verified before the new release reached production.

#### Refresh planning

**Body:** A sandbox refresh replaces its data and customizations with a copy of production, so unreleased work in the sandbox can be lost. Log the planned changes before a refresh, export anything that should be kept, and re-check integrations, email settings and scheduled scripts afterwards so a refreshed sandbox does not send real messages.

#### Common mistakes

**Body:** Recording changes only after they reach production, skipping role changes, and treating configuration changes as too small to log. Another is leaving test status blank. A blank status looks like a test that did not happen and weakens your evidence for auditors.

**Cta:** If you want release regression tests drawn from your real NetSuite transactions, Netray can discuss a read-only test data approach.

**Faq:**

#### Is this log enough for audit evidence?

**Answer:** It is a good start but auditors usually also want approvals and ticket references. Add a ticket number to the Change text and attach approvals in your ticket system.

#### How often should I update it?

**Answer:** Update on each status change. A weekly review of Planned and In test rows keeps stale work visible and prevents forgotten items before a release.

#### Should I log saved searches?

**Answer:** Log those that feed reports, dashboards or scripts. Personal exploratory searches do not need an entry, but shared searches used by finance or operations do.

#### Can I track more than one sandbox?

**Answer:** Yes. Put the sandbox name in the Change text or add a note. You can also keep a separate exported copy per sandbox account.

## Search terms

netsuite change log template, netsuite sandbox refresh checklist, netsuite release preview testing log, netsuite change management excel, netsuite deployment tracker, netsuite sandbox testing tracker, netsuite change request log, netsuite twice yearly release test plan

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json