NetSuiteFree worksheetPDF, Excel, Word exportNetSuite

NetSuite Script and Workflow Inventory Worksheet

After a few years most NetSuite accounts hold dozens of scripts, workflows and bundles that nobody fully remembers. An inventory is the first step to cleaning them up, documenting them and knowing what a release might break.

Download:

Name	Type	Record or purpose	Trigger or schedule	Owner	Runs per day	Average run time (min)	Daily run minutes	Risk	Documented
							6
							35
							4
							2
							30

Total daily run minutes

Automations listed

Daily automation run hours

1.2833

Fill from Customization, Scripting, Scripts and Customization, Workflow in your account. Run counts and times can come from the Script Execution Log or script deployment statistics. This is a planning aid and is not connected to your account.

Get help documenting NetSuite customizations

Optional: we can discuss an AI-assisted review of your scripts, workflows and bundles.

Optional. The tool and every export work without this. No spam.

How to use the inventory

Walk through the script list and workflow list in the Customization menu and enter one row per item. Add the owner, the trigger and an estimate of runs per day and average run time. Flag risk honestly: anything touching posting, inventory or approvals is at least Medium. Export to Excel and filter on Documented equal to No to find the biggest knowledge gaps first.

Include bundles, not only your own scripts
Capture the person who can explain the logic
Flag undocumented items that change financial data
Review the list each quarter

Reading the results

Daily run minutes help you see which automations consume the most processing time. A map/reduce job taking 35 minutes a day is not a problem on its own, but several heavy jobs scheduled in the same window can delay each other. Compare the totals to the schedule so heavy jobs do not all start at the same hour, and look at slow user events that run on every save.

Using it for release and upgrade planning

Before a NetSuite release, the inventory tells you which customizations to test in release preview. Items that touch work orders, assembly builds or inventory transactions deserve a regression check. Before a migration to another ERP, the same list becomes a scope document showing which logic must be rebuilt, replaced by standard features or retired.

Common mistakes

Listing only active scripts, ignoring workflows because they are point and click, and not recording the owner. Orphaned scripts keep running after their author has left. Another common issue is duplicate logic: a workflow and a script both setting the same field, with whichever runs last winning.

Frequently Asked Questions

Where do I find the list of scripts?

Use the Customization menu: Scripting, Scripts for script records and their deployments, and Workflow, Workflows for workflows. Saved searches on script and deployment records can also give a fuller export.

How do I get run times?

The Script Execution Log and the script deployment status pages show run history. For an estimate, sample a typical day and enter the average. Precision is less important than finding outliers.

What counts as high risk?

Anything that posts or edits financial or inventory records, drives approvals, or integrates with outside systems. Also rate undocumented logic higher because it is harder to fix when it breaks.

Should unused scripts be deleted?

Disable first, observe for a cycle such as a month-end, then remove. Keep the source in version control so you can restore it if needed.

If you need a faster way to document existing customizations, Netray can discuss an AI-assisted review of your scripts and workflows.

Talk to an Expert Explore More Free Tools

Related Tools

NetSuite

More NetSuite tools

See all

Back to All Tools