Update 16.01.26

Thank you for the comments and questions that you’ve sent in following yesterday’s update. I completely understand how frustrating it is not to have a clear answer on whether we are in a position to submit to the Building Safety Registrar today.

At the moment, we are still waiting for the certificates from the manufacturer. Once these arrive, they must be reviewed by the Building Safety Team to confirm that they meet the requirements for submission. Until that review is completed, the Sales team genuinely cannot confirm whether the registration will be submitted today.

I appreciate why it feels like we should be able to provide an update today, and I’m sorry for the uncertainty this creates. To ensure the process is handled thoroughly and correctly, we have suggested providing a further update on Monday. This allows enough time for the documents to be received, checked, and for us to receive confirmation that the Building Safety Pack has been submitted. The fire safety door certificates are a new requirement that was not previously part of the Building Safety Pack, which is why this additional step has only now come into play. As you can imagine, building safety remains a top priority, and the registration process continues to evolve as new requirements are introduced.

I completely understand how important it is for you to have clarity on whether occupation will still take place in January. At the moment, I’m not able to give absolute certainty until the BSR documents have been fully submitted and accepted. What I can say is that we are still working towards an end‑of‑January occupation, but this remains dependent on the successful submission of the BSR documentation. I appreciate how unsettling the uncertainty feels, and we will continue to keep you updated as soon as we have confirmed information.

If we receive confirmation today that the registration has been submitted, we will let you know straight away.

Share Update 16.01.26 on Facebook Share Update 16.01.26 on Twitter Share Update 16.01.26 on Linkedin Email Update 16.01.26 link
#<Object:0x00007f6335319b70>