> For the complete documentation index, see [llms.txt](https://docs.betterbuilding.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betterbuilding.io/sign-up-and-plans/news-and-updates/2026/new-data-management-system.md).

# New Data Management System

Coming in November

<figure><img src="https://2129322768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfKJnzF2TwHA3APPbiCpF%2Fuploads%2FAPiQuZTUTYS3NVhcnFoF%2Fdata%20(Small).png?alt=media&amp;token=987e7563-5b01-496a-9281-f2feae680d25" alt=""><figcaption></figcaption></figure>

Over the next couple of weeks, you’ll start seeing some new front-end changes to manage material data. We know changes like this are never painless, so thanks for bearing with us while we move to the new data management system.&#x20;

So why are these changes happening? Better Building has had a bit of a material data management problem.

When we started the platform almost eight years ago, specification was front and centre. Sustainable design folks needed to get their requirements into the model, and that mattered a lot.&#x20;

Back then we were still called Speckel (The ‘spec’ was based on the ‘spec’ in ‘specification’), and the platform was pretty humble: R-values and U-values for walls, roofs, floors, and windows.

We’ve evolved since then of course, and we’ve had to face the possibility that we built the system around materials the wrong way. Material data today is far more varied and tangled than it was. It runs from simple thermal properties for moisture, embodied carbon, cost, acoustics, and plenty more.

### Connecting Material Data

Materials get created, duplicated, shared, and modified over time, and every design team has to manage that churn. Generic data and supplier data are useful, and we’re not walking away from them. But there’s still a gap.

If the generic data doesn’t have what you need, you end up duplicating a material, and while we’ve enabled editing of thermal properties, that doesn’t fully solve the problem. Once you change a material, you have to account for much more, and that’s especially true for sensitive parameters that feed our hygrothermal solver.

So we’re changing direction. We’re moving away from the simple generic-and-supplier model and toward giving you the tools to build your own catalogues.

### More Control

In practice, that means your team gets real control over its material data. You’ll still be able to use supplier data, and you’ll also be able to create supplier data of your own for products that aren’t on the platform yet.&#x20;

You’ll be able to attach data points such as hygrothermal, carbon, or cost values to those materials, so each material record reflects what your team has actually agreed on.&#x20;

Those records can then be managed over time instead of being frozen at the moment someone duplicated them. You can also attach flags for things like red-list status, environmental attributes, or building code references.

We think this is a material management system you won’t find anywhere else, and we want it to be the most effective and time-efficient option you have.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.betterbuilding.io/sign-up-and-plans/news-and-updates/2026/new-data-management-system.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
