> For the complete documentation index, see [llms.txt](https://docs.riskbase.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riskbase.uk/performing-an-assessment/door-and-other-asset-based-surveys.md).

# Door and other asset-based surveys

Door and other asset-based surveys

*A part of a building that can be assessed - e.g., a fire door, smoke detectors, emergency lighting etc. - is referred to as an **‘asset’**.*

*Assets within a building require check ups at varying intervals - for example, fire doors are checked quarterly, while smoke detectors are checked monthly.*

*RiskBase provides a framework to conduct assessments on any individual assets within a building. It makes it easy to then conduct repeat assessments when each asset requires a check-up.*

*Though there are many assets to choose from, this is an example of a **communal fire*** ***door survey**:*

Within a door survey, information needs to be recorded about each door. For example, an image, its location, size, gaps between the frames, what kind of closer it has etc. These pieces of information are called **‘fields’**.

When filling in the field information, there is the option to upload photos of the door, pin it on a floor plan, and even attach it to a unique QR code (which is then placed on the door).

This means that each door is easily identifiable in the future when it is checked in the next required period: simply scan the QR code and the door will be added onto the new assessment along with all its information.

Once a door has been created and its information recorded using fields, the next step is to document its condition. An effective way to do this is using **‘checklists’**; these are a series of statements which can be agreed (or disagreed) with, for example:

✅ ❌ Gaps around the frame are within tolerance.

✅​​ ❌ An effective device closes the leaf from 5 degrees or 75mm.

✅ ❌ Fire door signage correctly identifies door operation.

RiskBase provides ready-to-go checklists which are already designed to complete door surveys to a compliant standard. There are individual checklists available for each type of asset which can be checked in a building.

However, these checklists are completely customisable. For example, to use certain language or include particular statements to be agreed or disagreed with. For more information on how to create checklists, see Checklists and Questions.

When a statement is disagreed with - e.g., the gaps are too wide around the frame - a suggestion for how to fix this problem will appear on the app. This suggestion is called an **‘action’**.

Actions can then be selected to appear on the final .PDF report. Additional information can be recorded, for example, how quickly it needs to be completed, or a due date for its completion etc. For more information, see Actions and Controls.

Any actions that were raised in previous assessments will also appear under each door. These can then be marked as ‘In progress’, ‘Completed’, or ‘Cancelled’. This avoids a confusing build up of the same actions being repeatedly raised on the same door each quarter, and also ensures those actions are being reviewed.

The history of all actions associated with each door is therefore safely recorded on the app and easy to review and update - in other words, a **‘Golden Thread’** of information is created.

This process of checking a door - recording information, documenting its condition, raising actions etc. - can be applied to any kind of asset within a building. To see how these assessments are carried out step-by-step, see Performing a Door Survey or Performing a Compartmentation Survey.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.riskbase.uk/performing-an-assessment/door-and-other-asset-based-surveys.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.