Keep the Knowledge With the Building

What happens to a building’s knowledge when the person who knows it best leaves? We can have drawings, maintenance records, and years of work invested in a site, yet still depend on someone remembering where a valve is or which repair belongs to which room. The information exists, but the next person may have to start again to find it.

On The Matthew Byrd Podcast, I talked with Jeremy Pilgrim, Managing Director of Building Spatial Intelligence Limited, about his work on UK schools. His experience stretches from creating 2D floor plans to connecting information around building models. We spent time on scanners, AI, and the realities of growing a business, but the useful question underneath those subjects was how to make information work for the people who need it.

Good data starts in the field

Jeremy's first question about a drawing was whether its underlying information could be trusted: “What’s the point of a superbly structured CAD file if the data’s wrong?” Structure can help people use the result, but it doesn't correct a mistake made during capture. That gives the field team an important part in the eventual handoff. Start with what the next person needs to know, then make sure the collection process can support it.

Give every asset a shared reference

Jeremy’s early school work helped him see a drawing as more than a set of lines. A room’s use, size, and reference mattered because people needed to bring that information into management systems and make decisions with it. As he explained, “The words are what’s important, but what the lines do is give the words context.” A model can look impressive and still leave someone unsure what they’re looking at or how to connect it to their work.

He used a boiler to make the problem concrete. Calling three boilers one, two, and three becomes confusing if the numbering depends on where you’re standing. A dependable reference gives the maintenance record and the physical object a way to stay connected. The same question applies to windows, doors, rooms, and the information different departments keep about them. Before adding another layer of detail, can everyone identify the same thing?

That led to Jeremy’s point about bridging silos. Different teams have reasons to use different systems, and connecting their information doesn’t require pretending their responsibilities are identical. It does require a way to recognize that a help-desk entry, a maintenance schedule, and an object in the model refer to the same asset. If you’re trying to improve a building workflow, pick one recurring question and follow the information needed to answer it. Where does the connection break?

Match accuracy to the job

The next lesson is to be clear about what the data can support. Jeremy’s work changed when building access was restricted and his team needed a faster way to capture schools. Mobile scanning gave him a different way to collect information, but speed didn’t remove the need to explain accuracy. His carpet example makes that boundary easy to understand: a model could help someone get a good deal on carpet, but “just don’t cut the carpet to match the model.”

I asked about the other uses that might sit around an initial capture project. Could information collected for estate planning also serve construction or engineering? We talked about the additional time, cost, and accuracy that can come with that ambition. There isn’t one answer for every building. Define the job, consider what else the information might reasonably support, and make the limitations clear to the person receiving it.

Experience still checks the output

The same habit of asking questions matters when the software says the result is good. Jeremy described technicians accepting scanner output because the system reported an acceptable result, even when his understanding of buildings helped him spot a problem. We also talked about AI as a tool used alongside experience. A convincing answer still needs someone who knows what to look for and what to ask next. Faster output makes that review more valuable, rather than making it disappear.

Keep knowledge with the building

The third lesson is to make useful knowledge easier to pass on. Jeremy told a story about a school water shutoff hidden beneath grass, with a biscuit tin and a piece of wood covering it. The site manager knew where it was, but that didn’t mean the next person would. “There’s a lot of knowledge gonna go out the door with them,” he said of experienced staff approaching the end of their careers. Recording that knowledge against the building gives someone else a chance to find it.

Capturing the information once is only part of the work. Jeremy argued that spatial data needs someone responsible for it, just as the building does, and described an incremental approach to enriching it. That gives a team somewhere practical to begin. Ask the person who knows the site which questions they answer repeatedly, record one useful piece of information in a place others can access, and decide who will keep it current. The value comes from making it usable over time.

When Jeremy started talking about paper towels and the details of running his business, I told him I appreciated that level of care. It connected with the question I raised about helping a team become curious and solve problems themselves. A shared system needs people willing to notice what isn’t working and contribute what they know. The software alone can’t decide which missing detail is making someone’s day harder.

We came back to learning throughout the conversation. Jeremy still looks for useful ideas in books, discussions, and watching how someone does a job, even when the whole product or approach isn’t relevant to him. That’s a practical way to think about improving a building’s information too. Start with a real question, make the connection that helps answer it, and keep adding what the next person will need.

Catch the full conversation on YouTube, Apple Podcasts, or Spotify: Connect Your Data | School Digital Twins with Jeremy Pilgrim. You’ll also hear about Jeremy’s first computing role, the lessons of building his company, and why he keeps looking for better ways to work.

Watch the full conversation

Previous
Previous

Make the Technology Useful to the Work

Next
Next

Keep Adding Knowledge to Your Fire