What should our postcode look like?
Postcode design
A code people can read, systems can check and registries can govern.
You get
- Code structure and format
- Precision model
- Rules for renames, splits and mergers
Services
Six services, one team. For a national programme or a single business.
01What we do
What should our postcode look like?
A code people can read, systems can check and registries can govern.
What counts as an address here?
The rules that decide what an address is, who assigns it and how it changes.
Is our map data good enough?
Reliable boundaries in, validated address points out.
How do we manage this safely for decades?
A governed home for the data, where every change is reviewed and recorded.
How will others actually use it?
Services that let banks, couriers, utilities and public bodies find the same door.
How do we get from a design to a live service?
From a first pilot to a system your own team runs.
Check and complete addresses at checkout, onboarding and dispatch.
A coded address scheme for estates, campuses, ports and industrial zones.
Match, clean and migrate customer and asset addresses.
02Who we serve
Wherever the work depends on finding a person, a place or an asset.
TodayResidents are identified by description.
With an addressEvery household has a location you can verify.
TodayThe last mile runs on phone calls.
With an addressParcels are sorted and routed by code.
TodayNo proof of address, no account.
With an addressA customer's address is checked in seconds.
TodayMeters and faults are tied to vague descriptions.
With an addressEvery connection has a stable location.
TodayCrews search for the place.
With an addressCrews drive to the entrance.
TodayCheckout forms accept anything.
With an addressAddresses are validated as they are typed.
TodayEach census rebuilds its own map.
With an addressOne coded geography, reused every time.
TodayParcel, property and tax records disagree.
With an addressOne location reference across every register.
03How we work
Five phases. Each ends with something you can inspect.
01
Agree what the programme is for.
You getA brief and a data readiness assessment
02
Decide the code, the rules and who holds authority.
You getA postcode design and governance model
03
Prove it on real ground, in one district.
You getIssued codes and a working lookup
04
Turn the pilot into a platform.
You getA production system and its APIs
05
Scale up and hand over.
You getA trained team that runs it
01
One question, answered in writing.
02
One district or site, end to end.
03
Design through to operation.
04Technology and trust
Every record shows where it came from, who approved it and what changed.
Codes are computed from the location.
Every change is reviewed first.
Retired codes are kept, not reused.
Who, what and when.
People see only what they need.
Including infrastructure you control.
Start a conversation
Tell us where you are. We will tell you plainly how we can help.