Establish the foundations.
Information categories and responsible owners. User roles, retention needs and known concerns. Existing controls and required specialist assurance.
Strategy & discovery ↗Service 07 / Protect
Build access controls and data handling into the system from the beginning, proportionate to the information and risks involved.

The commission / an interactive walkthrough
Explore how this service moves from your starting information through a scoped build to testable acceptance and handover.
Your starting material
We start with the users, records, constraints and decisions that the commission must respect.
Share a representative example with private records removed; detailed access follows an agreed secure process.
Specific deliverables, assurance and acceptance depend on the agreed brief.
Explore our delivery process ↗Make access and accountability part of the design.
Where it fits
Staff systems, confidential records and services with different user permissions.
What we can deliver
System sketch / Illustrative permission boundary
Establish the user or service identity before deciding what information or actions it can access.
Illustrative service architecture. Detailed rules and responsibilities are agreed for each commission.
A useful starting point
Acceptance & handover
HandoverAccess matrix, data-handling decisions and agreed security review findings.
From requirements to operation
Information categories and responsible owners. User roles, retention needs and known concerns. Existing controls and required specialist assurance.
Strategy & discovery ↗Implement the agreed scope in reviewable increments. Check user journeys, integration boundaries and failure conditions against the requirements, with unresolved decisions kept visible.
Review the delivery stages ↗Allowed and denied actions for each agreed role. Audit visibility and proportionate retention. Recorded findings, ownership and remediation priorities.
Access matrix, data-handling decisions and agreed security review findings.
Working examples and archive captures show their stated maturity. The service scope is a commissioning capability, not a claim that every listed system has been deployed for a client.
Institutional delivery
For public-sector and enterprise commissions, we agree the deployment approach, responsibilities, acceptance evidence and operational handover against the actual requirements.
Government & institutional capabilities ↗We establish the authoritative sources, mapping rules and access boundaries first. Migration and integration scope includes reconciliation, error handling and recovery responsibilities; production writes and cutover require an agreed review.
Yes, where access and integration are authorised. We first establish ownership, documentation, dependencies and the boundaries of any replacement or connection. A commission does not require abandoning a system that already works.
We prioritise complete user tasks rather than an arbitrary feature count. Scope, exclusions, dependencies and acceptance scenarios are agreed before implementation, with review points for changes.
We identify data owners, information categories and permitted actions during discovery. Controls, retention, specialist assurance and any data-processing responsibilities are scoped against the actual service. A studio credential does not certify your future system.
Documentation, access ownership, training and operating responsibilities are agreed before release. Maintenance, incident coverage and further development have an explicit scope; they are not assumed to be unlimited.
Scope, assumptions, dependencies and changes recorded against the brief.
User journeys, permissions, failure conditions and operating requirements reviewed before release.
Source, documentation, training and recovery responsibilities agreed as part of handover.
Start a conversation
Bring the brief, the source material and the constraints. We will help define the scope and the right next step.