A SuiteScript governance error is usually the first visible symptom, not the whole problem.
The units matter. You still have to know which API calls are expensive, which script type you are in, and whether the job belongs in scheduled or Map/Reduce territory.
But the harder question is usually more basic:
What does this script actually touch?
When a script starts hitting limits, the fix depends on context. Is it updating invoices during approval? Is it firing on every edit? Is it mutating related records? Is a finance workflow depending on the side effect nobody remembers anymore?
That is where documentation stops being nice-to-have.
Before volume goes up, every important script should have a plain-English page that explains purpose, execution flow, side effects, risk, and related records or workflows.
CSDocs helps with that by turning live NetSuite metadata into private documentation your team can actually read. Not a feature checklist — just a clearer answer to what is running, why it exists, and what could break if it changes.