What procedures do you all use to manage projects and changes to NetSuite? I'm looking for a good way to make sure the developers, testers, and all the stakeholders and decision makers are on the same page, in a way that's super easy and quick for everyone involved to access, set their requirements and expected outcomes, and contribute their authoritative sign-offs/approvals. This is so projects that are 99% complete don't get stuck in limbo waiting on the next person who has more important things to do than review the details of the project and try to figure out whether it's their turn to do something.

Depending on your size. You could keep all objects in source control, and require signoffs on the pull request. Reviewers can see what issues are awaiting their approval.

I'm the only developer. We have several accounting and procurement, etc. kinds of people that need to do user testing and approval before we deploy changes to NS Production. So they try things out, tell me if it's working the way they need it to and if they were able to make it break or found any bugs we missed before user acceptance tests, and they or their supervisor give it the green light to go to production. They don't usually want to see the suitescript, XML, etc. involved, and they usually have dozens of other teams and things they have to sign in to so as to do their jobs. Some of them don't even have NetSuite login access, and I might be sometimes be involved in a project that's wider scope and involves other systems than NetSuite. We have MS Teams, Outlook, and SalesForce. Maybe I should use SalesForce to make this stuff happen? That depends on whether everyone involved actually uses SalesForce every day.... I'll talk to my manager and see what they feel would be most reachable and present-of-mind for everyone, but yes, source control is something I meant to get going last year, though in my case I think it would solve a different problem than the one I'm talking about, due to probably little to no user adoption. I think I need to put it in front of them using a system they're already using every day. Maybe I could just build it in NetSuite, have a little set of change log record types where I set up the anticipated approval chain and business requirements, etc., and it could send automatic emails to the person who's next, since I get a little lost keeping track of all the stuff we have in flight, and they probably do too. I just don't want it to get buried under all the other emails they have to deal with. Signal-to-noise ratio.

you can build a custom record for change management and manage those changes that way.