What needed to change
Project requests and investment decisions sat across a rigid content system and manual steps. Teams faced repeated entry, limited visibility into status, and inconsistent handling of validation, escalation and version history.
Utilities · Low-code delivery
All case studiesBringing water-utility project decisions into one workflow
A fragmented investment-request process called for clearer approvals, validation and visibility across project teams.
How the solution was shaped
The documented solution used Appian to create a single view of requests, decisions and reporting. Dynamic forms guided input; OPEX and CAPEX checks supported validation; approval paths, audit tracking and document output made the process easier to follow. SAML single sign-on and SharePoint integration via Microsoft Graph connected it to the existing environment.
What this makes possible
For decision-makers, the useful shift is from scattered request handling toward a traceable process: a shared record, defined decision steps and reporting that helps teams see where work stands.
Capability in focusThe building blocks
The building blocks
behind the work.
The right combination depends on your systems, users and governance requirements.
- 01Appian dynamic request forms
- 02Investment validation and approval paths
- 03Audit trail and reporting
- 04SharePoint and identity integration
Continue exploringWhere could this approach
RELATED SERVICEExplore low-code and automationWhere could this approach
help your organisation?
Tell us about the process or data challenge you are working through. We can discuss the context before recommending a delivery path.
Talk through a similar challengeMore use cases
See every case study
