Improvements in and relating to building safety

Abstract

System (100, fig .1) and method for managing building safety data comprises providing 201 a web-based portal (102, fig. 1) having a user interface (110, fig. 1) and displaying 202 a plurality of data

Description

FIELD OF THE INVENTION The present invention relates to building safety management. In particular, the present invention relates to systems and methods for managing building safety data and identifying safety risks associated with a building. BACKGROUND TO THE INVENTION It is important that buildings are regularly monitored to identify any potential safety risks such as the risk of fire or structural failure, so that these risks can be mitigated and reduced as much as possible. At worst, failure to identify and manage risks may lead to catastrophic fire or structural failure of the building which may lead to injury or loss of life to any occupants. This is at present an extremely pertinent risk associated with high-rise residential buildings. Building safety legislation and regulations contain provisions intended to secure the safety of people in or about buildings and to improve the standard of buildings. Such legislation (such as the Building Safety Act 2022 in England) may require information about a building to be recorded, risks to be identified and monitored, and mitigation measures to be put in place. An audit trail may be required for regulatory purposes, often by means of a report, which may be used as evidence to a regulatory body (such as the Building Safety Regulator in England) to demonstrate the level of compliance with regulations over time. Conventional approaches to complying with such regulations typically rely on manual record keeping and report generation, which can involve considerable numbers of different records and documents which must be maintained and updated. Such methods are time consuming, rely on a comprehensive understanding of the regulations, and are prone to omissions or mistakes. Against that background, it is an objective of the present invention to overcome at least one problem associated with the prior art, whether referred to herein or otherwise. SUMMARY OF THE INVENTION According to a first aspect of the invention there is provided a method for managing building safety data for a building, the method comprising: providing a web-based portal having a user interface; using the user interface, displaying a plurality of data entry fields, each data entry field corresponding to a predetermined building safety requirement; receiving from a first user, in at least one of the data entry fields, an entry providing building safety data for the corresponding building safety requirement, said building safety data representing physical properties of one or more elements of the building; providing access to the at least one entry, via the portal, to a second user, to enable the second user to assess the building safety data provided by the first user; receiving, for each data entry field, a risk score determined by the second user based on the building safety data provided by the first user, the risk score representing a risk level associated with the respective predetermined building safety requirement to which the data entry field corresponds; using a processing module, generating a report based on least one of: a) the or each entry received from the first user and b) the or each risk score received from the second user. The report may be for assessing compliance with said building safety requirements. In this way, the present invention provides a method for identifying, assessing and / or managing safety risks associated with a building. The method may also be considered as a method of managing a building. Preferably, receiving the or each entry from the first user comprises receiving an entry providing access to building safety data stored externally from the portal. In this way, the security of building safety data provided by the first user is improved, since the building safety data is not stored by the portal. Preferably the or each entry provided by the first user comprises a hyperlink which targets a document comprising the building safety data. Preferably the report indicates a degree of compliance with the building safety requirements. For instance, the report my comprise, for each building safety requirement, a numerical score or other measure indicating an extent to which the building safety requirement is complied with. The report may comprise a digital report such as a document. The processing module may be linked with the portal. The portal, or a server on which the portal is hosted, may comprise the processing module. The processing module may comprise one or more processors. Each risk score may be received via a user interface, which may be the user interface for receiving entries from the first user. Preferably however, an alternative, second user interface is provided for the second user. The or each user interface may be a graphical user interface. Generating the report may comprise generating a building safety report document based on the risk scores and / or the entries and / or building safety data provided by the first user. The building safety report document may indicate a degree of compliance with the predetermined building safety requirements. The building safety report document may comprise a digital document. The building safety report document may comprise the risk scores for the predetermined building safety requirements. The report may contain the hyperlinks. This may enable a third party to access the building safety data using the report. The third party may be a third user of the portal. The method may comprise using the processing module, identifying at least one of said elements of the building which requires modification in order to reduce said risk score. The method may comprise subsequently modifying the identified element of the building. In this case the method may comprise subsequently receiving from the first user an entry providing access to updated building safety data representing said modified element. The method may comprise updating the report based on the received updated building safety data. The method may comprise removing a first identified element from the building and / or adding a second element to the building and / or replacing the first element with a second element. For instance, the method may comprise replacing a faulty smoke detector or repairing a structural element. The method may comprise using the user interface to display to the first user a prompt based on a corresponding building safety requirement and receiving from the first user a response to the prompt. For example, the portal may be configured for collecting some building safety data from the first user by presenting to the first user via the user interface a prompt or question to which the first user can provide a basic (e.g. binary) response. For instance, the prompt may ask whether a physical building characteristic (e.g. cladding) is present and the user interface may be configured to present a checkbox for receiving a yes / no response from the first user. In other examples, the response may be a number provided by the first user, for example in response to a prompt asking the number of storeys of the building. The method may comprise receiving building safety data from the first user in the form of a data file uploaded to the portal. In this way, some building safety data may be stored in the portal (in addition to the building safety data stored externally form the portal). In this case the data uploaded directly to the portal may be a floorplan or photograph of the building. The method may comprise, using the processing module, identifying at least one of the predetermined building safety requirements for which building safety data is absent or incomplete. In this way the method may be used to produce a gap analysis report. The method may comprise causing an indicator to be displayed in the user interface for indicating to the first user the absence of building safety data for the at least one identified building safety requirement. The method may comprise using the processing module to determine, based on the building safety data, a testing interval for testing at least one of said elements of the building. The at least one element may be subsequently tested by the first user. The method may comprise testing the at least one element to obtain test data. The at least one element may comprise a sensor, detector and / or alarm, such as a smoke detector, fire alarm, or carbon monoxide detector. The at least one element may comprise an automatic fire suppression system and / or sprinkler system. The building safety data may comprise test data from testing of safety equipment of the building (e.g. smoke detector test data). The method may comprise, based on the testing interval, generating an alert or reminder to be displayed in the user interface for alerting the first user to a deadline for testing the at least one element. In this case the method may comprise subsequently receiving from the first user an entry providing building safety data in the form of test data obtained from testing the at least one element. The method may comprise updating the report based on the received test data. According to a second aspect of the invention there is provided a system for managing building safety data, the system comprising: on one or more servers, a web-based portal having a user interface, wherein the user interface is configured to: display a plurality of data entry fields, each data entry field corresponding to a predetermined building safety requirement; receive from a first user, in each of the data entry fields, an entry providing access to building safety data stored externally from the portal, said building safety data representing physical properties of one or more elements of a building; provide access to said entries, via the portal, to a second user, to enable the second user to assess the building safety data provided by the first user; receive, for each data entry field, a risk score determined by the second user based on the building safety data provided by the first user, the risk score representing a safety risk associated with the respective building safety requirement to which the data entry field corresponds; a processing module linked with the portal and configured to generate a report based on at least one of: a) the or each entry received from the first user and b) the or each risk score received from the second user. Preferably the processing module is configured to generate a building safety report document based on said risk scores, the building safety report document indicating a degree of compliance with the predetermined building safety requirements. The building safety report document may comprise the risk scores for the predetermined building safety requirements. Preferably the portal comprises a second user interface and access to the received entries from the first user is provided to the second user via the second user interface. The portal may comprise a third user interface for providing access to said entries to a third user, to enable the third user to assess the building safety data provided by the first user. The portal may be configured for the first user to control (e.g. allow and restrict) access by the third user to the entries provided by the first user. In some examples, the third user may access the user interface only if permitted by the first user. 5 The second and / or third user interface may be configured such that the second user cannot edit the entries provided by the first user. The first user interface may be configured such that the first user cannot edit the risk scores provided by the second user. In this way, independent risk scores provided by the second user cannot be inadvertently or deliberately changed by the first user. 10 Also provided is a method of modifying one or more elements of a building, the method comprising, generating a report using a method according to the first aspect of the invention or using the system of the second embodiment of the invention, identifying from the report one or more elements of the building which require 15 modification, and modifying the one or more elements of the building. In this case, the method may comprise removing a first element from the building and / or adding a second element to the building and / or replacing the first element with a second element. BRIEF DESCRIPTION OF THE DRAWINGS Embodiments of the present invention will now be described by way of example only, with reference to the accompanying drawings, in which like reference numerals indicate like features and in which: Figure 1 is a schematic view of a system according to a preferred embodiment of the invention; Figures 2, 3, 4, 5, 6 and 7 are examples of part of a user interface provided by the system of Figure 1, each showing examples of a plurality of data entry fields corresponding to building safety requirements; Figure 8 is schematic example of part of a report generated by the system of Figure 1; and Figure 9 illustrates steps of a method according to preferred embodiment of the invention. DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention relates to computer-implemented systems and methods for managing building safety data for the purpose of identifying, assessing and managing safety risks associated with a building (such as fire and structural risks). The present invention involves providing a portal having a user interface which provides a plurality of data entry fields for which an entry providing building safety data may be made by a first user, wherein the data entry fields are based on predetermined building safety requirements. The building safety data represents physical attributes and / or features of the building. The building safety data is assessed by a second user of the portal to determine an individual risk score for one or more of the corresponding building safety requirements. In preferred embodiments, the present invention provides a web-based portal which is configured to present to a first user the plurality of data entry fields via a user interface, and to receive hyperlinks provided by the first user which link to building safety data which is stored externally from the portal. In this way, sensitive data may be stored by the first user and readily updated by the first user, and need not be stored by a second user or owner of the portal. A risk score may be determined for each building safety requirement, based on the provided building safety data. Based on these individual risk scores, and / or on the entries provided by the first user, the portal is configured to generate a report which indicates a degree of compliance with the respective building safety requirement. An overall building risk score, representing a degree of safety risk associated with the building, may also be determined based on the individual risk scores. In this way a degree of compliance with the building safety requirements may be determined based on the provided building safety data. The portal provides a live building management system, in which data from the user may be updated over time, and a report, and / or a building risk score for the building may be conveniently updated at any time, for example as changes are made to the building. The portal is preferably configured to generate a building safety report based on the provided building safety data, so that an assessment of safety risks for the building can be made (for example by a relevant authority) when required. A system 100 for managing building safety data according to a first embodiment of the invention is illustrated in Figure 1. In this embodiment, the system 100 comprises a web-based portal 102 which may be hosted on one or more servers 104. In the present embodiment, the system 100 is configured to be used by a first user 106 and a second user 108. The first user 106 may be the owner of a building 2, or another person accountable for monitoring safety risks associated with the building, such as a freeholder or management company of the building 2. The second user 108 may be a fire engineer, structural engineer or other qualified person or team of people qualified to assess data related to building safety. In this example the second user 108 is also an owner or manager of the portal 102, who defines the building safety requirements and data entry fields. The portal 102 preferably comprises a website and the first and second users 106, 108 each have a user account / login for the website to enable them to access the user interface 110 in order to use the system 100. The portal 102 is configured to provide a user interface 110, which in this example is a web-based user interface 110, to allow the first user 106 to submit information relating to the safety of a building 2. The user interface 110 is configured to display to the first user 106 a plurality of data entry fields which are based on predetermined building safety requirements. The building safety requirements may be determined by the second user 108 (or by another user of the portal) based on legal requirements with which the building 2 must comply, and for which compliance is to be demonstrated by the first user 106. In this way, the plurality of data entry fields help to guide the first user 106 to provide data which is legally required to demonstrate compliance with the legal requirements. Figures 2, 3, 4, 5, 6 and 7 show schematic examples representing parts of the user interface, showing data entry fields 120 in which the first user 106 may provide entries for such building safety requirements. In the examples in Figures 2 to 7, the data entry fields 120 are populated with entries (in this case hyperlinks) provided by the first user, or, where no entry has been provided by the first user 106, the data entry fields 120 are automatically populated with the text ‘no data available’. In the present example, the building safety requirements are based on legal requirements which may specify types of information which must be provided by a building owner or other person, for example as set out in The Building Safety Act 2002 (England). For example, a legal requirement may specify that the building owner must have up-to-date records of smoke detector testing, or a structural survey. The building safety requirements, and thus the data entry fields displayed by the user interface, represent physical characteristics of a building. The data entry fields 120 (which are based on the building safety requirements) therefore correspond to physical characteristics of the building 2 for which building safety data must be provided by the first user 106 to allow identification of risks and an assessment of compliance with the building safety requirements. The physical characteristics may be substantially any physical attributes or features of a building, such as dimensions of the building, number of smoke detectors, wall construction materials, cladding properties, and many others. The data entry fields may be determined by the second user 108, who may create or input the data entry fields so that the user interface displays the data entry fields to the first user. The user interface presented to the second user may differ to the user interface presented to the first user. The portal may be configured to display a first user interface to the first user 106, permitting submission of entries into the data entry fields, and the portal may present a second user interface to the second user 108, in which the entries provided by the first user 106 can be viewed, and a risk score inputted by the second user 108. Preferably the first user 106 is not able to input a risk score, or to edit the risk scores input by the second user 108. In this way, independent risk scores provided by the second user 108 may not be tampered with by the first user 106, who may have a bias or interest in the risk scores. Access to the different user interfaces may be managed using different user accounts, which may be managed by the first and / or second user. The building safety requirements are diverse and may relate to many different types of physical characteristics of a building. For example, a building safety requirement related to fire safety may specify that, for a building of given size (e.g., height, number of storeys, number of residential rooms) the building must have a minimum number of stairways via which occupants may escape the building in the event of a fire. Accordingly, the data entry fields shown by the user interface 110, for which the first user 106 may provide an entry, may include physical characteristics such as: height of the building, number of residences (e.g. flats), number of ‘means of escape’ stairways and the like, as can be seen in Figure 2. In the present example, another building safety requirement (determined by the second user based on a legal requirement) is that the presence or absence of external cladding must be identified, along with physical characteristics of the cladding, such as the extent of combustible cladding over a surface of the building, and / or a material composition of the cladding. In this case, the data entry fields include: presence or absence of external cladding, extent of cladding, and cladding material specification fields, as can also be seen in Figure 2. The first user 106 may therefore submit an entry to provide data for each of these fields. By way of further example, for a building safety requirement which specifies that cladding materials are identified, the corresponding data entry field may be labelled ‘cladding materials’ and the first user may be provide a hyperlink to a specification document which details the materials of which the cladding is composed. In another example, a building safety requirement may require identification of fire suppression systems, in which case the user interface may display a data entry field labelled ‘location of fire suppression systems’ and the first user may provide a hyperlink to a plan or other document indicating the location of any fire suppression systems within the building in question. Figures 3, 4, 5, 6 and 7 illustrate further examples of data entry fields which may be presented by the user interface, and for which data entries may be provided by the first user and risk scores may be assigned by the second user. Figures 3 and 4, for example, show further data entry fields for a plurality of building safety requirements, which in this example are based on legal requirements (which may be referred to as ‘Golden Thread’ information in England). Figure 5 illustrates further examples of data entry fields corresponding to building safety requirements related to systems testing, such as alarm system testing, sprinkler system testing and the like. Figures 6 and 7 illustrate further date entry fields which may be displayed by the user interface, and which correspond to building safety requirements related to risk and incident reporting and resident engagement. In the present embodiment, each data entry field comprises a text field such as a single line text field to allow the first user to provide an entry in the form of text. Preferably, building safety data is provided by the first user 106 entering, into a respective data entry field, an entry in the form of a hyperlink which targets stored building safety data. For example the hyperlink may target a database, plan or technical drawing, spreadsheet, image, video, report or other document containing building safety data relevant to the data entry field. In this way each entry provides access to building safety data. Referring again to Figure 1, the building safety data is stored externally to the portal, i.e., the building safety data is not stored by or on the server 104 on which the portal is hosted and the owner or manager of the portal (who may be the second user) is not responsible for storage of the building safety data. For example, the building safety data may be stored by the first user on a server 112 or other storage belonging to the first user 106, or in third-party storage (e.g., Dropbox or similar) used by the first user 106. In this way, building safety data (which may be confidential or sensitive data) need not be sent or uploaded via the user interface 110 and remains under the ownership of the first user 106. The use of hyperlinks to access stored information, permits users to update information on their own storage system, which can help to remove risks associated with data protection and the like. Also, with this arrangement, the first user 106 can update the building safety data at any time (for example in the first user’s records systems) and the updated data will be immediately available to the second user 108 via the hyperlink. Once the first user 106 has provided hyperlinks allowing access to building safety data in at least some of the data entry fields, the building safety data may be assessed by the second user 108 to determine an individual risk score for each building safety requirement. In the present embodiment, the second user 108 assigns an individual risk score to each building safety requirement, as illustrated in Figures 2 to 6. In this example, the user interface 110 of the portal 102 is configured for the second user 108 to provide a numerical score for each building safety requirement, from one to five, with one indicating a low risk, and five indicating a high risk. A default individual risk score may be assigned automatically for a building safety requirement for which no hyperlink to data has been provided. For example, as shown in Figure 2, where the first user 106 has not provided a hyperlink to data indicating the number of means of escape stairways in the building, the portal may automatically assign a score of five (high risk score) for the associated building safety requirement, because the absence of data may indicate a high risk. The portal 102 is preferably configured to identify building safety requirements for which no data has been submitted, and / or for which a determined risk score is high (corresponding to a higher safety risk) in spite of data having been provided by the first user. This process may be referred to as a ‘gap analysis’. The portal 102 is preferably configured to produce a gap analysis report which indicates to the first user 106 (and optionally to other users of the portal) those building safety requirements for which data must still be provided and / or where a high risk is present. This enables the first user 106 to identify easily data which must be provided and / or modifications which may need to be made to the building 2. In this way the system helps to identify safety risks. The user interface 110 and / or gap analysis report may display an indicator (e.g. a visual indicator) to indicate the absence of data to the first user 106. For example, where building safety data is absent, the corresponding data entry field may be highlighted in a certain colour. In addition, an overall building risk score for the building 2 may be calculated based on the individual risk scores. For example, the sum of the individual risk scores may provide a building risk score, such that a lower building risk score indicates fewer safety risks associated with the building 2, and a higher building risk score indicates more safety risks associated with the building 2. Each individual risk score, and the building risk score, may be updated following new building safety data being provided by the first user 106. The individual risk scores, and thus the building risk score, may be updated periodically, following a request made by the first user 106, or the portal may be configured to prompt the second user 108 to update one or more individual risk scores following input of a new, or updated hyperlink by the first user 106. In some cases, building safety data may have been updated in a document stored remotely, but the hyperlink to this document may not need to be updated, as the hyperlink may still provide access to the updated document. In this way, the first user need not resubmit hyperlinks to the portal 102 when new building safety data is recorded. In this case, an individual risk score determined from the building safety data may only be updated when the second user reviews the updated data, which may be done periodically, or following a request from the first user. In some examples, the portal 102 may be configured to detect when data provided by the first user 106 is updated (even if the hyperlink is not updated) and to prompt the second user to review the risk score for the respective building safety requirement. New safety data may be provided by the first user 106 following a first collection of data from the building 2, for example where the first user 106 had not yet provided building safety data for a particular building safety requirement. Updated building safety data may be provided by the first user following changes being made to the building 2, such as installation of a new fire suppression system, installation or removal of cladding, renovation of part of the building 2, structural building work and the like. With these arrangements, the portal 102 is configured to provide a live building risk score which may be updated regularly to reflect changes in building safety data provided by the first user. In this way, the first user 106, and optionally third parties having an interest in safety risks associated with the building 2, can view the building safety risk score for the building by accessing the portal. In some examples, the entry provided by the or each user may be a response to a prompt or question presented by the user interface. For example, based on a building safety requirement relating to cladding, a data entry field may be provided which prompts the user to state whether or not cladding is present on the building. For instance, the user may complete a checkbox, or click a button to provide the response. In some examples, the user may enter a date (such as a date at which a most recent test or inspection was completed). In some cases, the first user 106 may upload some data directly to the portal 102. For example, the user interface 110 may be configured for the first user 106 to upload an image such as a floor plan or photograph of the building, and / or for the first user to input simple data such as the number of storeys of the building. In some examples the portal 102 may be configured to determine, based on the number of storeys of the building, a middle storey of the building, and to prompt the first user to provide a floorplan for the highest, lowest, and middle storeys of the building. The portal 102, or a processing module linked to the portal 102, is also configured to generate a building safety report (which may also be referred to as a building safety case report) using the provided building safety data and / or the determined risk scores. A schematic example of part of a building safety report is shown in Figure 8. Preferably the building safety report is in the form of a document which includes information required by a regulatory body such as a building safety regulator. In the present embodiment, the building safety report is based on the risk scores, and includes an indication of the extent to which the building complies with the corresponding building safety requirements, for example by including the risk scores assigned to each building safety requirement. A building safety report can be generated at substantially any time and provided to a third user (for example a regulatory or statutory body) as required. The ability to produce a building safety report on demand is particularly useful where there may be a legal requirement to provide such a report on request at relatively short notice (e.g. 28 days or 1 month). In some examples, the portal is configured such that the first user can permit, and remove, access to the third user to building safety data via the portal. Access granted to the third user is preferably ‘read only’ so that the third user cannot edit any data input by the first user. With reference to Figure 8, in preferred embodiments, the processing module is configured to sort or rank the building safety requirements based on the risk scores, and to present the ranked risk scores in the report in order of risk and / or in groups according to the risk score. In the present example, the processing module is configured to produce a building safety report which presents the building safety requirements having the highest risk scores (e.g. a score of 5) in a first group (e.g., a high priority group). This first group indicates to the users of the portal those building safety requirements for which action must be taken as a priority, and / for which outstanding data must be provided or updated. For instance, data regarding the number of escape stairways may be absent, or a smoke detector test may be overdue, or a structural component may need to be repaired. The report comprises a second group (e.g., medium priority group) of building safety requirements having intermediate risk scores (e.g., 3 or 4), for which action is still required, but less urgently than for the first group. The report further comprises a third group (e.g. low priority group) of building safety requirements where action is needed less urgently than for the second group, or for which no action is required. In this way the system is configured to provide an action plan for the first user to assist the first user in prioritising actions to improve the safety of their building. In some embodiments, the portal may be configured to provide access to a fourth user, to allow the fourth user to access at least some of the entries provided by the first user. For example, the fourth user may be a resident (or group of residents or occupants) of the building. In this way, the fourth user may be able to view building safety data for the building and so be aware of building safety risks associated with the building. Figure 9 illustrates steps of the method described generally above. In the present example, the method comprises a first step 201 of providing a portal (such as webbased portal 102) having a user interface 110, and then displaying (step 202) a plurality of data entry fields 120 based on predetermined building safety requirements. Entries (e.g. hyperlinks) are received (step 203) from the first user 106 via the user interface 110, each entry providing access to building safety data. The portal provides access (step 204) to the second user 108, who reviews and analyses the provided building safety data and assigns a risk score for each data entry field (and thus for each building safety requirement). The assigned risk score is input by the second user and thus received (step 205) via the user interface. In a subsequent step 206, the method comprises generating a report, based on at least one of the entries received from the first user and / or at least one of the risk scores received from the second user. As described above, the report may identify building safety requirements for which data is absent / incomplete, and / or the report may indicate a degree of compliance of the building with each building safety requirement. The report may be generated automatically by a processing module of the portal. The report may be determined by analysing the presence or absence of a data entry for each building safety requirement. For example, where an entry has not been provided for a building safety requirement, the absence of an entry is presented in the report, for example (as mentioned above) by assigning a high risk score (e.g. a numerical score), or visual indicator (e.g. colour indicator) to the building safety requirement. Also as mentioned above, in preferred embodiments, the method comprises ranking the building safety requirements based on the assigned risk scores. The report generated may therefore present the ranked building safety requirements in order of risk score, or grouped by risk score. In some examples, the portal is configured to provide a reminder to the first user to prompt the first user when updated building safety data is required. For example, based on a test or inspection date previously entered by the first user, the portal may be configured to generate a reminder when the next text or inspection is due. The reminder may be presented to the first user in the user interface. With the arrangements described above, the present invention provides a convenient and secure system and methods for managing safety data and safety risks for a building. The present invention provides a live building management system that provides data on how a building is performing in terms of its fire and structural-related risks for the purpose of meeting specific requirements. The system identifies areas for improvement, alerts users to document and system testing deadlines, and generates a bespoke safety case report for the user's building. The present invention allows building safety data to be accessed via a central portal by interested parties, helps to improve identification and monitoring of safety risks for a building, and enables compliance with building safety requirements to be assessed and reported efficiently, resulting in improved building safety.

Claims

1. A method for managing building safety data, the method comprising:- providing a web-based portal having a user interface;- using the user interface, displaying a plurality of data entry fields, each data entry field corresponding to a predetermined building safety requirement;- receiving from a first user, in at least one of the data entry fields, an entry providing building safety data for the corresponding building safety requirement, said building safety data representing physical properties of one or more elements of a building;- providing access to the at least one entry, via the portal, to a second user, to enable the second user to assess the building safety data provided by the first user;- receiving, for each data entry field, a risk score determined by the second user based on the building safety data provided by the first user, the risk score representing a risk level associated with the respective predetermined building safety requirement to which the data entry field corresponds;- using a processing module, generating a report based on at least one of: a) the or each entry received from the first user and b) the or each risk score received from the second user.

2. The method of Claim 1, in which receiving the or each entry from the first user comprises receiving an entry providing access to building safety data stored externally from the portal.

3. The method of Claim 2, in which the or each entry provided by the first user comprises a hyperlink which targets a document comprising the building safety data.

4. The method of any preceding claim, in which generating the report comprises generating a building safety report document, the building safety report document comprising the risk scores for the predetermined building safety requirements.

5. The method of Claim 4 when dependent on Claim 3, in which the report document contains the hyperlinks to enable a third party to access the building safety data using the report.

6. The method of any preceding claim, comprising using the processing module, identifying at least one of said elements of the building which requires modification in order to reduce said risk score.

7. The method of Claim 6, comprising subsequently modifying the identified element of the building.

8. The method of Claim 7, comprising subsequently receiving from the first user an entry providing access to updated building safety data representing said modified element.

9. The method of Claim 8, comprising updating the report based on the received updated building safety data.

10. The method of any preceding claim, comprising, using the processing module, identifying at least one of the predetermined building safety requirements for which building safety data is absent or incomplete.

11. The method of Claim 10, comprising causing an indicator to be displayed inthe user interface for indicating to the first user the absence of building safety data for the at least one identified building safety requirement.

12. The method of any preceding claim, comprising using the processing module to determine, based on the building safety data, a testing interval for testing at least one of said elements of the building.

13. The method of Claim 12, comprising, based on the testing interval, generating an alert to be displayed in the user interface for alerting the first user to a deadline for testing the at least one element.

14. The method of Claim 12 or Claim 13, comprising subsequently receiving from the first user an entry providing building safety data in the form of test data obtained from testing the at least one element.

15. The method of Claim 14, comprising updating the report based on the received test data.

16. The method of any preceding claim, comprising using the user interface to display to the first user a prompt based on a corresponding building safety requirement and receiving from the first user a response to the prompt.

17. The method of any preceding claim, comprising receiving building safety data from the first user in the form of a data file uploaded to the portal.

18. A system for managing building safety data, the system comprising:- on one or more servers, a web-based portal having a user interface, wherein the user interface is configured to:display a plurality of data entry fields, each data entry field corresponding to a predetermined building safety requirement;receive from a first user, in each of the data entry fields, an entry providing building safety data, said building safety data representingphysical properties of one or more elements of a building;provide access to said entries, via the portal, to a second user, to enable the second user to assess the building safety data provided by the first user;receive, for each data entry field, a risk score determined by the second user based on the building safety data provided by the first user, the risk score representing a safety risk associated with the respective building safety requirement to which the data entry field corresponds;- the system further comprising a processing module linked with the portal and configured to generate a report based on at least one of: a) the or each entry received from the first user and b) the or each risk score received from the second user.

19. A system according to Claim 18, in which the or each entry provides access to building safety data stored externally from the portal.

20. A system according to Claim 18 or Claim 19, in which the processing module is configured to generate a building safety report document, the building safety report document comprising the risks scores for the predetermined building safety requirements.

21. A system according to any of Claims 18 to 20, in which the portal comprises a second user interface and access to the received entries from the first user is provided to the second user via the second user interface.

22. A system according to any of Claims 18 to 21, in which the portal comprises a third user interface for providing access to said entries to a third user, to enable the third user to assess the building safety data provided by the first user, and wherein the portal is configured for the first user to control access by the third user.

23. A method of modifying one or more elements of a building, the methodcomprising, generating a report using the method of any of Claims 1 to 17 or using the system of any of Claims 18 to 22, identifying from the report one or more elements of the building which require modification, and modifying the one or more elements of the building.

Images