Example solutions
Ways of applying our services, not a catalogue of products.
Each one below is an example of the kind of problem our four services are meant to solve. Most combine more than one service, rather than standing alone as a separate product.
Jump to a solution
Electronic service portals
Citizens or customers often have no way to submit a request except on paper or through a personal inbox, and no way to see where it stands afterwards. Bringing submission, review, requests for missing information, approval and status tracking into one coherent process turns that into a portal people can use directly. A public-facing portal like this usually needs more than one service at once: custom development for the portal itself, a connection to the records it has to check, management reporting on how requests are progressing, and continuing support once people are relying on it.
Usually combines: Custom applications and platforms, Connecting existing systems, Data and dashboards, Operation and ongoing support
Case and request management
Once a request, application or case arrives, moving it through review, requests for missing information, approval and status tracking is often still done by hand, across emails and spreadsheets, without a shared view of where each one stands. Building that into one coherent process is usually custom application work, often needing information a department already holds elsewhere so staff are not copying the same details between screens, and reporting so a manager can see pending work, delays or exceptions that need attention.
Usually combines: Custom applications and platforms, Connecting existing systems, Data and dashboards
Document approvals
An approval is often just one step inside a longer process — sign-off that has to happen before a request, application or case can move forward. Building that approval into the same process as submission, review and status tracking, instead of handling it as a separate manual step, is usually custom application work connected to the records or identity systems that establish who is approving.
Usually combines: Custom applications and platforms, Connecting existing systems
Executive dashboards
A senior leader may need an overview of how a service is performing. A department manager may need to see pending work, delays, workload or exceptions that need attention. Producing that picture usually means bringing information together from the systems it already sits in and presenting it consistently, rather than assembling it by hand from each department.
Usually combines: Data and dashboards, Connecting existing systems
Mobile services
Field teams working away from a desk, and members of the public who expect to reach a service from their phone, are often left out when a system is built for a desk only. A mobile application is one of the ways a custom system can reach them, usually built alongside the same connections to existing systems, and needing the same ongoing maintenance and updates as any other application.
Usually combines: Custom applications and platforms, Connecting existing systems, Operation and ongoing support
Identity and access management
Semi-government and regulated organisations in particular need clear control over who can see or change what, and identity is one of the systems that connecting existing systems usually has to work with. Getting permissions and access right, and keeping them right as systems and staff change, is a recurring part of connecting systems and of looking after them once they are running.
Usually combines: Connecting existing systems, Operation and ongoing support
Sometimes only one part is needed.
An organisation with an established platform might need only a connection to the systems it already has, or clearer reporting on how it performs, rather than every service at once.
Tell us which of these is close to your problem.
Describe your organisation and the problem you're trying to solve. The contact page opens your own email app with the message ready to send.