About
Buildings change. The record should keep up.
CircuitMap puts every board, breaker and circuit onto a building's own floor plans. It exists because of a pattern every maintenance team knows: the handover pack was right once, the drawings are three refurbishments old, and the only reliable record is in one person's head.
- Independent
- UK
- Self-hosted by design
It always fails the same way. The paperwork is produced at handover, filed, and then quietly drifts away from the building. Small works never get drawn up. Contractors leave site before the paperwork lands. Someone starts a spreadsheet with the best of intentions and abandons it on a shared drive. A few years on, finding out what a breaker feeds means asking whoever was there when it went in, and hoping they still work for you.
CircuitMap is the alternative. The electrical record sits on your own floor plans as data, not as drawings that need a CAD licence and a translator: distribution boards, circuits, rooms, assets, maintenance dates and documents. One searchable record, cheap to update, readable by the whole team, and printable as a compliant board schedule the moment anyone asks.
We build for the people who carry the can: maintenance managers, facilities and estates teams, operations leads, building owners and compliance managers. Electricians and contractors work in it too. But the record belongs to the organisation, not to whoever happens to hold the knowledge this year.
Dan Smith
Founder, CircuitMap
CircuitMap started with a question that should have taken thirty seconds and took most of an afternoon: what does this breaker actually feed?
The paperwork existed. It had been right once. But it had been photocopied, scribbled on, overtaken by a refit nobody wrote up, and finally replaced by the only record that was reliably current — the memory of one engineer three years off retirement. That is not unusual. In most buildings it is normal.
So the whole thing is built against one test: when that engineer leaves, does the building still know itself? A feature either helps the next person pick up where the last one stopped, or it does not ship. That is why the schedule prints straight from the live record, why a contractor can update a circuit standing at the board, and why you can export everything you have put in, at any time, without asking us.
If you are weighing this up, I would rather show you your building than our sample one. Bring a floor plan to the call and we will map a real board on screen.
Live pilot
CircuitMap is in pilot at Fenwick, Newcastle — a working retail building with decades of alterations behind it, exactly the sort of place where the drawings and the boards stopped agreeing a long time ago.
Principles
What we build for
Six rules that decide what gets built and, more often, what does not.
The record must outlive the person
Every decision gets tested against the same scene: the one engineer who knows the building hands in their notice. If a feature does not help the next person pick up where they left off, it does not ship.
The smallest edit sets the ceiling
How accurate the whole thing stays is decided by what the cheapest change costs. That is why circuit entry runs as a survey, why bulk edits exist, why the phone works with no signal, and why there is a QR label on the board door.
The whole team, not just electricians
Electrical records fail when only one trade can read them. A facilities coordinator, an estates manager and an operations lead should each be able to look at the plan and understand what they are seeing.
Your data, plainly
Building records outlive software companies. Everything you put in exports in standard formats, at any time, with nothing to negotiate. The install is single-tenant on your own server, so there is nothing for anyone else to switch off.
Say what is not built yet
The features page lists what this release does not do. A buyer who finds out on the call trusts you less than one who read it on the website, and overclaiming is a short-term trick with a long-term bill.
Boring engineering, on purpose
Signed releases, migration preflight, health gates, tested rollback, verified encrypted backups, published SBOMs, coverage thresholds and automated accessibility checks. None of it is exciting. All of it is why the thing still works in year three.
Come and pull it apart
Bring the awkward questions — the roadmap, the company, the data, or what happens if we get hit by a bus. Better answered now than left nagging at you come renewal.
No pitch deck. No credit card. No follow-up sequence.