# NetSuite Script Deployment Inventory Worksheet > Source: https://netray.co/tools/netsuite-script-deployment-inventory-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Keep an inventory of every SuiteScript and deployment with its owner, status and review date, and export it to Excel. ## Category netsuite ## Erp NetSuite ## Audience - NetSuite administrator - NetSuite developer - IT manager ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Script ID **Key:** script_id **Type:** text #### Purpose **Key:** purpose **Type:** text #### Script type **Key:** stype **Type:** select **Options:** - User Event - Client - Scheduled - Map/Reduce - Suitelet - RESTlet - Mass Update - Workflow Action - Portlet #### API version **Key:** version **Type:** select **Options:** - 1.0 - 2.0 - 2.1 #### Deployment status **Key:** status **Type:** select **Options:** - Released - Testing - Not Scheduled - Scheduled #### Owner **Key:** owner **Type:** text #### Last review **Key:** review **Type:** date #### Errors last 30 days **Key:** errors **Type:** number #### Risk score **Key:** risk_score **Type:** number **Expr:** if(eq(errors,0),1,if(lt(errors,10),2,3)) **Format:** integer **Rows:** **Script id:** customscript_so_shipdate_ue **Purpose:** Set ship date on sales orders **Stype:** User Event **Version:** 2.1 **Status:** Released **Owner:** R. Mehta **Review:** 2026-09-12 **Errors:** 0 **Script id:** customscript_inv_sync_mr **Purpose:** Nightly inventory sync to WMS **Stype:** Map/Reduce **Version:** 2.1 **Status:** Scheduled **Owner:** S. Iyer **Review:** 2026-06-30 **Errors:** 14 **Script id:** customscript_po_approval_cs **Purpose:** Purchase order form validation **Stype:** Client **Version:** 2.0 **Status:** Released **Owner:** R. Mehta **Review:** 2025-11-04 **Errors:** 3 **Script id:** customscript_legacy_export **Purpose:** Legacy CSV export **Stype:** Scheduled **Version:** 1.0 **Status:** Testing **Owner:** Unassigned **Review:** 2024-05-20 **Errors:** 0 **Totals:** #### Scripts tracked **Key:** script_id **Agg:** count #### Total errors (30 days) **Key:** errors **Agg:** sum **Format:** integer **Summary:** #### Average errors per script **Key:** avg_errors **Expr:** sum_errors / count **Format:** decimal **Notes:** Risk score is a simple prompt for attention: 1 for no errors, 2 for under ten, 3 for ten or more. Add your own judgment for business criticality. Refresh the table from the Scripts and Script Deployments lists and the execution log in the account. ## Content **Intro:** After a few years most NetSuite accounts hold scripts nobody remembers writing. This worksheet is a lightweight inventory: one row per script with its type, version, status, owner and recent errors, exportable to Excel for audits and clean-up planning. **Sections:** #### How to use the worksheet **Body:** Open the script list in your account and enter one row per script, using the full script ID. Add the owner, the deployment status and the date it was last reviewed. Enter the number of errors seen in the execution log over the past month. The risk score column turns that into a quick rank, and the totals show how many scripts you carry and how many errors they generate. Export to Excel for the technical debt conversation. **Bullets:** - Use the exact script ID so searches match - Mark scripts with no owner clearly - Review the Testing status rows, since they may be dead or misdeployed - Record API version to plan 1.0 retirement #### What to do with the inventory **Body:** Sort by risk score and last review date. Scripts that error often, have no owner or are still on SuiteScript 1.0 are the first candidates for a decision: fix, rewrite, replace with a workflow or built-in feature, or retire. Also look for overlapping scripts on the same record, since order of execution can cause surprises. Keep the sheet in a shared location and update it with every release. #### Common mistakes **Body:** Inventories decay when they are built once and forgotten. Make updating the sheet part of your deployment runbook. Do not count a script as healthy just because errors are zero: a script left in Testing status or deployed to the wrong audience also produces no errors and no results. Check that each deployment reaches the users and records it was designed for. **Bullets:** - One-time inventory with no refresh - Treating zero errors as proof of health - No owner for inherited bundle scripts - Ignoring client scripts because they do not appear in the execution log **Cta:** If you want the inventory refreshed automatically from your account's script records and logs, Netray can help build a read-only view. **Faq:** #### Where do I find the list of scripts? **Answer:** In NetSuite, the Customization menu has script and script deployment lists. The execution log on each script deployment shows recent runs and errors. A saved search on scripts can also help with a bulk export. #### What does Testing status mean? **Answer:** A deployment in Testing status executes only for the deployment owner or the users selected for testing. It is useful in sandbox but usually wrong for production deployments meant for everyone. #### Should I include bundle scripts? **Answer:** Yes if they run in your account. You may not own the code, but you own the effect. Record the bundle vendor as the owner and a contact for support. #### How often should the inventory be reviewed? **Answer:** At least every quarter and at every release. Accounts with heavy customization benefit from a monthly look at errors and ownership. ## Search terms netsuite script inventory, netsuite customization inventory excel, netsuite script list, netsuite script audit template, suitescript deployment tracker, netsuite technical debt register --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json