Establish the foundations.
Maps, plans, GIS layers or property schedules you can share. Source provenance, revisions and unresolved geometry questions. The journeys and decisions the spatial interface must support.
Strategy & discovery ↗Service 05 / Understand
Make geography and project information easier to explore, compare and act on through interactive maps and spatial applications.

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 ↗Keep the information connected to its place.
Where it fits
Local authorities, development projects, natural resources, estates and visitor experiences.
What we can deliver
System sketch / Illustrative spatial record model
Establish the geographic reference, scale and source quality before presenting a place as precise.
Illustrative service architecture. Detailed rules and responsibilities are agreed for each commission.
A useful starting point
Acceptance & handover
HandoverStructured spatial data, source references and documented map behaviour.
From requirements to operation
Maps, plans, GIS layers or property schedules you can share. Source provenance, revisions and unresolved geometry questions. The journeys and decisions the spatial interface must support.
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 ↗Record-to-map selection and source references. Scale, filters, navigation and narrow-device performance. Clear boundaries between supplied evidence and illustrative content.
Structured spatial data, source references and documented map behaviour.
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.
A related working example
A photographic estate atlas connecting places, stories, historic layers and an interactive garden walk.
Independent working study
Explore the project ↗We review coordinate systems, data licences, provenance and update responsibilities before connecting layers. Survey accuracy, planning status and ownership are not inferred from a map or a concept model.
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.