RLB Digital

In just months since Rob joined to establish the practice, the team built a comprehensive Hub covering every ISO 19650 resource — the first time all these resources have been brought together in a single, connected platform. Where previously each IM resource existed as a standalone document with no connection to the others, data now flows from EIR through to acceptance reports without re-entry. The content duplication and version control problems that plague document-based approaches are eliminated entirely.

The template is duplicatable for any new project engagement, meaning a growing team of five to eight can serve multiple clients simultaneously without rebuilding from scratch. The website-like navigation and brand-aligned design make it accessible to non-technical users across all departments, while the ability to produce traditional PDF, CSV, XLSX, or Word outputs means RLB Digital can serve both digitally mature clients who want the full connected experience and traditional clients who still expect conventional deliverables. The CDE-agnostic connectivity — working with seven different platforms via API — ensures consistent information management regardless of which system a project uses. And beyond standard IM resources, the team is already building custom applications on top of Morta data, extending the platform into specific client needs and commercial workflows that would be impossible with a document-based approach.

Rob Jackson inherited an industry-wide problem that no existing tool had adequately solved. Every information management resource in the ISO 19650 lifecycle — Exchange Information Requirements, project information standards, MIDPs, acceptance reports — existed as an isolated Word, Excel, or PDF document. There was no way to create live links between an EIR and the MIDP it informs, or between the MIDP and the CDE tracking that monitors its delivery. Each document was a dead end that could not support automation or drive downstream processes.

The same information appeared in multiple places. Naming conventions defined in the EIR were repeated in the Project Information Standard and referenced again in the MIDP. When a convention changed, every document needed manual updating — and inevitably some were missed, creating inconsistencies that undermined the entire framework. Version control depended on file naming conventions, folder structures, and human discipline, a system that frequently broke down on complex projects.

Large IM documents ran to hundreds of pages with no way to filter content for different audiences. An architect, a structural engineer, and a project manager all had different information needs, but a static Word document presented the same wall of text to everyone. There was no capability to search, embed forms, or add interactive content. And with 140 offices across 40 countries, ensuring consistent approaches to information management was a significant challenge — document-based templates could be customised beyond recognition with no mechanism to enforce quality or maintain brand alignment. Yet despite all these limitations, many clients and regulatory bodies still expected traditional PDF or Word outputs, so any new approach had to produce those formats while being fundamentally different underneath.

Rob and his team built a comprehensive Hub powered by Morta, structured around seven core concepts drawn from ISO 19650: Specify, Procure, Deliver, Assure, Store, Present, and Exploit. Each concept maps to a stage in the information management lifecycle, and together they cover every resource for both appointing party and lead appointed party roles.

The critical difference from traditional approaches is that every resource is connected through table relationships. Requirements defined in the EIR flow into the Project Information Standard, which informs the MIDP structure, which connects to CDE tracking via integrations, which feeds acceptance reports that reference the original requirements to close the loop. Data is entered once and reused throughout the lifecycle, eliminating the content duplication that plagues document-based approaches.

The Hub is designed to look and feel like a website rather than a database. The front page provides intuitive navigation with colour-coded tables matching RLB brand guidelines, making the system accessible to people across all departments without requiring technical training. It connects to any CDE via API — Viewpoint, Aconex, Asite, SharePoint, ProjectWise, ACC, or Procore — so the same template works regardless of which document management system a client uses. And despite being database-driven, it produces traditional PDF, CSV, XLSX, or Word outputs when clients require them. The database is the source of truth; the documents are just views of that data. The team is also actively working on IDS export capability for machine-readable requirements that can be automatically validated against BIM models, closing the gap between specifying what’s needed and checking that it’s been delivered.

Rob started from a standing start — joining RLB Digital specifically to establish the information management and BIM consultancy service, building a team of five growing to eight, and immediately beginning development of the Hub as the foundation for all client engagements. Morta’s no-code platform allowed the team to build and iterate without requiring software development resources, which was critical given the pace required.

The approach was template-first from day one. Rather than building bespoke solutions for each project, Rob designed a master template covering all ISO 19650 resources for both appointing party and lead appointed party. New projects get a duplicated template with project-specific customisation layered on top, maintaining quality and consistency while allowing flexibility. The Hub was built with buildingSMART standards at its core — IFC, bSDD, BCF, IDS, and COBie — ensuring compatibility with the broader industry ecosystem. Rob is working closely with the Morta team on IDS export capability, which would enable machine-readable requirements that can be automatically validated against BIM models. With 140 offices across 40 countries, the Hub provides RLB Digital with a consistent, scalable approach that any office can deploy, and the website-like interface ensures teams can navigate the system without specialist training.