BIMINAM GOLDEN THREAD TASK WORKSTREAM MEETING, 11-08-2026
MEETING SUMMARY
Golden Thread Tasks Workstream
Meeting: 11 August 2026, 10:02 AM
Duration: 1 hour 27 minutes
Purpose: Project briefing, scope clarification and volunteer mobilisation
Sources: Microsoft Teams transcript and 27-message meeting chat
Executive summary
The workstream agreed to move from the nine high-level activities in the Golden Thread white paper and benefits spreadsheet to a practical, reusable library of finite tasks. The current project will focus on tasks that produce, verify, validate or consume digital information containers across planning, creation, operation and maintenance. Physical construction tasks and detailed analysis of the contents inside each container are outside the immediate scope.
Volunteers will enter tasks in Morta using a common structure. The data will then be normalised and deduplicated before one or more findings reports are produced. The intended value is greater consistency across clients, delivery teams and software, with better-quality information for safety, sustainability, risk reduction and asset operation.
The meeting exposed several design items that must be settled before or during launch: a usable responsibility list, an applicable standards library, the distinction between responsibility and accountability, treatment of jurisdictional differences, bulk import options, peer review, and a clear map showing how this and other BIM4Housing workstreams contribute to the wider vision.
Purpose and agreed scope
- Output focus. Create a reusable task database and a findings report; detailed benefits, costs and risk quantification may follow in later work.
- Built-environment coverage. Buildings and infrastructure are included. The legal Golden Thread context for higher-risk buildings is the starting point, but the work is intended to support the wider built environment.
- UK-first scope. Initial terminology, regulation and standards work will be UK-oriented. Participants flagged that legal applicability differs across England and Wales, Northern Ireland and other jurisdictions, so applicability must be checked and recorded.
- Task definition. A task is narrow, finite, output-focused and time-bound, expressed as a verb plus an output. It is the lowest granularity adopted for this project.
- Information tasks only. In scope are tasks that produce, verify, validate or consume data and information containers such as drawings, models, reports, EIRs and delivery plans. Physical outputs such as building a wall are excluded.
- Controlled depth. The first pass will identify the containers and related tasks, not inspect every data element inside each container. Nested container lists will need later analysis.
Common task record
Each Morta entry is expected to capture six metadata fields:
- Parent activity - one of the nine activities from the existing Golden Thread work;
- Responsibility - the role expected to perform the task;
- Applicable regulation or standard - the regulation or standard governing the task, where applicable;
- Input information - the information needed before the task can be performed;
- Stage - the relevant RIBA stage; and
- Comments - free text for observations, assumptions and suggestions.
Parent activity, responsibility, regulation/standard and stage are intended to use controlled selections. Input information and comments will be free text, which makes input-output matching, terminology normalisation and duplicate detection important parts of the analysis.
Delivery approach
- Phase 1 - collect. Volunteers add raw task records in Morta. Existing organisational task plans can be used as evidence, but only the tasks that directly support the Golden Thread activities should be mapped.
- Phase 2 - analyse and clean. The coordination team reviews entries during collection, resolves duplicates and synonyms, links outputs to inputs, and normalises terminology.
- Phase 3 - report. The project produces one or more reports describing the task library, gaps, inconsistencies, standards issues and opportunities for follow-on work.
The next data-collection phase was discussed in terms of approximately three to four weeks, and report preparation was also estimated at three to four weeks. These were explicitly presented as provisional estimates dependent on volunteer participation, data quantity and data quality.
Key discussion and chat contributions
- Make data consumable. Julie Carrick stressed that clients need a clear statement of what data is required, in what format, why it is collected and how it will support maintenance and lessons learned. Gordon Pringle added that simple client-facing toolboxes and traffic-light presentation can make structured operational data usable.
- Standardise the structure. Participants supported standardising task names, compliance tracking and templates across institutions and organisations. Mark O'Reilly noted in chat that unrestricted spreadsheets often destroy interoperability; a controlled structure can enable consistent datasets, even if it requires discipline.
- Do not over-centre the TIDP. Peter Monaghan and Grant Bezuidenhout prompted a useful clarification: the TIDP is an example, not the sole focus. The project is identifying Golden Thread tasks and their information outputs, while detailed requirements and container contents remain separate or later work.
- Track decisions and accountability. Kevin Bayliss emphasised recurring review tasks, change decisions, continuing compliance and an audit trail across lifecycle stages. His chat question about responsibility versus accountability remains important, particularly from a legal and governance perspective.
- Design for the whole supply chain. The approach must work for smaller or less digitally mature supply-chain organisations, especially in repair and social-housing contexts. Instructions and interfaces should therefore be simple, role-appropriate and supported by examples.
- Preserve provenance. Morta records the contributor for each task, enabling follow-up when entries appear duplicated or ambiguous. A question-resolution and review process still needs to be made explicit.
- Use AI with oversight. AI is expected to assist volunteers during collection and help identify duplicates or inconsistencies during analysis. Chat participants stressed human oversight. A participant also suggested contacting Professors Pieter Pauwels and Pieter Demian for BIM-specific AI expertise.
- Maintain a standards watchlist. Chat participants flagged ISO 19650 terminology and alignment points, including information-container delivery under Part 2 and a possible move from TIDP terminology to Information Production Plan (IPP). These points should be verified against the current standards before the data dictionary is finalised.
Actions and commitments
| Action | Owner | Timing / status |
|---|---|---|
| Rationalise the Uniclass role list into a manageable responsibility dropdown for Morta. | Franco Pittoni / steering group | Before volunteer launch |
| Compile the applicable regulation and standards code list. Mark offered to help; Franco will contact him separately. | Franco Pittoni and Mark O'Reilly | Before or alongside launch |
| Issue Morta access invitations and a short instruction file to attendees. Acceptance of the invite will confirm participation. | Project coordination team | Next step |
| Add relevant Golden Thread tasks, mapped to the nine activities and completed with the six metadata fields. | All confirmed volunteers | Initial input: about 1-2 hours each |
| Review Morta and contribute tasks from Wheatley's building-safety and housing-provider perspective. | Connor Stevenson | After access is issued |
| Review and share the current client-side process so the group can test and refine it across project management, engineering, M&E and energy perspectives. | Julie Carrick | During collection/review |
| Contribute project-management and supply-chain standardisation experience. | Jac Parry | During collection |
| Arrange a short discussion on a vision document that shows how the workstreams and outputs combine; include Richard Freer. | George Stevenson with Kevin Bayliss and Richard Freer | 5-10 minute follow-up |
| Share the requested white paper, benefits spreadsheet and presentation slides with participants. | George Stevenson / project team | Requested follow-up |
| Send a concise body-of-knowledge summary from Aqua Matters for possible standards and task-library input; Siddharth also requested a copy. | Karl Willemen | Follow-up |
Actions combine explicit spoken commitments with relevant chat follow-ups. Timing remains provisional unless stated otherwise.
Open questions and risks
- Responsibility model. Should the governance field record responsibility, accountability or both, and how will this align with legal duties?
- Efficient ingestion. Will existing TIDP or other task lists be supported through bulk upload, or must volunteers enter records individually?
- Quality assurance. What formal peer-review or validation process will be applied before tasks are accepted into the reusable library?
- Data normalisation. How will free-text inputs be matched to other contributors' outputs and how will synonyms, duplicates and nested containers be handled?
- Standards currency. Which standards and current terminology should populate the controlled list, and how will jurisdictional applicability be represented?
- Portfolio alignment. A concise vision map is needed to show how this workstream relates to information requirements, as-built definitions, safety-critical assets, AI/data engineering, water, health and safety files, and other BIM4Housing work.
- Participation and evidence. Volunteer attrition, uneven sector coverage, small sample size and poor-quality entries could reduce the value of the analysis.
- Scope discipline. The scope must remain controlled: expanding immediately into international standards or every data element inside every container could delay or derail the current project.
Overall conclusion
The group broadly supported progressing to practical data collection. The strongest shared theme was that the Golden Thread will only become useful at scale if tasks, roles, inputs, outputs and standards are described consistently while remaining understandable to clients and the full supply chain. The immediate priority is therefore to finish the Morta dictionaries, issue access, gather representative task records and establish a transparent review process.
Source note: Prepared from the 11 August 2026 Teams transcript and meeting chat. Automated notetaker messages were used only as corroboration; the summary prioritises the human discussion and direct commitments. Participant statements about law, standards and future terminology are recorded as meeting points and should be independently verified before formal adoption.