A New Standard: Developing a Concise, Yet Comprehensive, Statement of Work
A New Standard: Developing a Concise, Yet Comprehensive, Statement of Work
DownloadConsider this hypothetical scenario. You accept a job with a new local government that has been struggling with an enterprise resource planning (ERP) project. The project is delayed. Staff aren’t confident with the new system. You are confused as to why there are so many issues with features you assumed would be standard with modern technology—user-friendly reporting, pre-built interfaces, automated business processes, and public-sector-focused applications to manage new Governmental Accounting Standard Board standards and recognized best practices. You start asking staff how the organization got into this situation and find there isn’t a simple answer. You do learn, though, that despite the challenges, your government has signed multiple change orders, increasing the price of the project. This leads you to look at the contract and statement of work (SOW) that was signed with the ERP vendor, hoping to get some clarity. Unfortunately, it is no help. It’s full of buzzwords, technical jargon, sales messages, and the description of a generic implementation methodology. There is nothing specific that holds the vendor accountable for outcomes, or a clear definition of what is included in the scope of services for the project.
Publication Date: February 2026
