A governance and assessment platform for a workforce of 4,000
Multi-gate approval, field-level audit, access control decided on the server, evidence management and portfolio reporting.
What it is
A business-critical platform for a workforce of about 4,000. It runs a process in which people assess, approve, attach evidence and report, and in which every step has to stand up to audit.
What was built
- Multi-gate approval, so nothing moves forward without the right sign-off.
- Field-level audit, recording who changed what, and when.
- Access control derived from role and from live data, decided on the server.
- Evidence management, keeping the supporting documents with the record they support.
- Portfolio reporting across the whole body of work.
Underneath that sit 20 custom data tables, 35 custom APIs, 14 automated flows, two custom React front ends running inside Power Platform, and an Azure function app.
An AI assistant, with limits
The platform includes an assistant that answers employees’ questions.
- Sensitive answers are given word for word from approved sources.
- Everything else is drafted and sent to a person for review.
- The assistant was included in the penetration test, alongside the rest of the platform.
How it was delivered
One senior engineer built it in six months, on our own equipment and environments.
- About 2,100 automated tests: 1,014 server-side, 544 unit and 548 browser end-to-end.
- 75 tagged release builds, each one promoted through Dev, Test and Production pipelines.
- 254 documents, including the functional specification, the architecture and the security model.
- Independent penetration testing.
Four design decisions worth knowing about
A journey-shaped front end on a model-shaped database. The data stays strict. The user sees one screen for one task. Most Power Platform projects make the user work around the shape of the data; this one put a purpose-built front end on top of it.
Access decided on the server. What a person can see and do is worked out on the server from live data. It is never a matter of hiding things on the screen.
Release discipline that answers an auditor. Every release is a tagged build that went through the same Dev, Test and Production pipelines, so there is a record of what was released and when.
A handover someone else can pick up. The client received a paper setting out the skills needed to support, maintain and extend the system, and a guide to provisioning production.
What it shows
A scope that would usually call for a team was carried by one senior engineer, and the result was tested, documented, security-tested and handed over. That is the way we work on every project.
Visitors, wifi and membership in one CRM
An upgrade to Dynamics 365, secure access over the internet, and public wifi sign-ins and membership cards feeding straight into the CRM.
A portal where foster carers keep their diaries
An upgrade from Dynamics CRM 2011 to Dynamics 365, then a portal on top of it for foster carers to log diaries and receive support.
Start with a delivery health check.
One to two weeks on your Dynamics 365 or Power Platform estate, ending in a written report and a costed plan.