Development Working Group Meeting 25-05-2026

BIM4HOUSING DEVELOPMENT WORKING GROUP MEETING 25-06-2026

Meeting Summary

Date: 25 June 2026

Duration: 1 Hour 28 Minutes

Meeting Objective

The meeting focused on practical experiences of delivering High-Risk Building (HRB) projects through the Building Safety Regulator (BSR) Gateway 2 process. Shap shared lessons learned from two large residential developments, highlighting strategies for improving compliance, reducing delays, and managing documentation throughout the design and approval process.

Key Discussion Points

    1. Early Design Review and Specialist Involvement

A major lesson learned was the importance of involving specialist consultants as early as possible during Stage 3 design.

Early collaboration with fire engineers, structural engineers, smoke control specialists, suppression system designers, and MMC specialists helped identify design issues before detailed design began, reducing costly redesigns later in the project.

  1. Planning Gateway 2 Submissions

Large developments should be carefully planned before submission to the BSR.

The discussion covered:

  • Staged Gateway 2 submissions for complex developments. 
  • Coordinating life safety dependencies across multiple buildings. 
  • Creating clear submission strategies for phased construction. 
  • Allowing additional programme time for specialist reviews and approvals. 

Proper planning significantly reduces delays during the approval process.

  1. Key Gateway 2 Documentation

Three documents were identified as the most critical for successful Gateway 2 submissions:

  • Compliance Statement 
  • Fire and Emergency File 
  • Stage Submission Strategy 

These documents should:

  • Clearly demonstrate regulatory compliance. 
  • Be concise and well structured. 
  • Explain design decisions rather than simply referencing regulations. 
  • Be easy to maintain throughout the project lifecycle. 
  1. Fire and Emergency File

The Fire and Emergency File was highlighted as one of the most important documents reviewed by the Building Safety Regulator and the London Fire Brigade.

The file should:

  • Contain all essential fire safety information in one location. 
  • Explain operational assumptions and emergency procedures. 
  • Avoid relying on references to external documents. 
  • Remain useful throughout the building's operational life. 

A well-prepared Fire and Emergency File helps reduce Requests for Information (RFIs) during the review process.

  1. Managing the BSR Review Process

The speaker shared practical experience of working with the Building Safety Regulator.

Key recommendations included:

  • Arrange pre-application meetings wherever possible. 
  • Discuss submission structure before uploading documents. 
  • Maintain a master tracker for all RFIs. 
  • Allocate sufficient resources to respond to multiple review teams. 
  • Hold regular meetings to clarify concerns rather than relying solely on written responses. 
  1. Common Compliance Challenges

Several recurring issues raised by the BSR included:

  • Evacuation lift strategies. 
  • E-bike storage and fire safety. 
  • Roof-mounted photovoltaic systems. 
  • Waste storage distances. 
  • Emergency communications for fire services. 
  • Door recess requirements. 
  • Structural fire performance. 
  • Coordination between different design disciplines. 

Most issues could be resolved through early planning and better collaboration.

  1. Managing Consultant Collaboration

An important lesson was that technical disagreements should focus on understanding and reducing actual risks rather than debating interpretations of guidance.

Successful projects relied on:

  • Open discussions between consultants. 
  • Clear understanding of regulatory intent. 
  • Collaborative problem solving. 
  • Shared ownership of compliance. 
  1. Digital Information Management

The discussion highlighted the importance of maintaining clear, accessible documentation throughout the building lifecycle.

Key recommendations included:

  • Maintain complete audit trails. 
  • Use document management systems effectively. 
  • Ensure long-term accessibility of safety information. 
  • Avoid relying on fragmented documentation stored across multiple systems. 

Best Practice Recommendations

  • Engage specialist consultants early in the design process. 
  • Plan Gateway 2 submissions well before construction begins. 
  • Produce concise, structured compliance documentation. 
  • Maintain a comprehensive Fire and Emergency File. 
  • Keep detailed records of RFIs and design decisions. 
  • Encourage collaborative discussions focused on managing risk rather than interpreting guidance. 
  • Build document management systems that support the building throughout its entire lifecycle. 

Key Takeaways

The meeting demonstrated that successful Gateway 2 submissions depend on early multidisciplinary collaboration, well-planned documentation, effective communication with the Building Safety Regulator, and strong information management. Projects that invest time in planning, maintain clear compliance records, and adopt a collaborative approach are more likely to achieve faster approvals, reduce design changes, and create safer, more maintainable buildings.