Every standard cited in a contract was current on the day somebody typed it, and not necessarily on any day since. I am Dr Sepehr Abrishami, and writing three books taught me to check a reference before I lean on it, a discipline this season of Reimagining AEC brings to the ISO standards. This episode is about the UK BIM Framework, now called the IMI Framework, and about the move from the PAS 1192 documents to the ISO 19650 series, as the transition guidance PD 19650-0 of 2019 mapped it, guidance the British Standards Institution has since withdrawn and which I cite here as history. The case is hypothetical, and it starts inside a council. You have just joined Stourleigh District Council as its information manager, and the tender for a new primary school, funded with public money, goes out in a fortnight. The invitation already says two things about information. The first is that the project shall comply with the UK BIM Framework. The second is that it will follow the Construction Playbook and comply with ISO 19650. Behind those two sentences sits the council's information pack, carried over from a vehicle depot it built in 2016. It holds an employer's information requirements document written to PAS 1192-2, PAS being a Publicly Available Specification, a naming procedure written to BS 1192, a requirement for a COBie file at each volume under BS 1192-4, COBie being construction operations building information exchange, a level of detail schedule, a security clause citing PAS 1192-5, and a health and safety clause citing PAS 1192-6. Every standard it cites has since been withdrawn. So you have a choice with no obvious answer. Issue the pack as written, and every bidder prices an old process, against documents that nobody will be able to produce a current copy of when a dispute arrives. Revise it, and you spend the fortnight on paperwork while the programme waits, with no certainty that you will catch everything. The question for this episode is what the UK BIM Framework is and is not, and how a legacy document set like the Stourleigh pack maps onto the standards in force today. By the end you will be able to turn a clause that asks for compliance with the framework into a requirement a bidder can price, route any question to the document that answers it, say what the UK editions add, and state the current position of every item in a legacy pack, with a date and a reason. There are five steps. First, what the framework is, who built it and who looks after it now. Second, how to find an answer inside it and record where it came from. Third, the UK layer, meaning the National Foreword, the National Annex and the public policy that makes them a procurement condition. Fourth, the supersession map at the level of whole documents. And fifth, mapping at the level of clauses and words. Stourleigh stays with us in every step. The first step starts with a gap that every country meets when it adopts an international standard. A published standard is a consensus document. Its requirements have survived scrutiny by committees in many countries, which makes them precise and portable, and also thin on worked detail. BS EN ISO 19650-2 tells an appointing party to establish the project information standard. It does not show you one. It does not say which UK classification system to point at, or how the requirement sits inside a public procurement route. The UK filled that gap with a body of guidance. That body of guidance was launched in October 2019 as the UK BIM Framework, BIM being building information modelling. Three organisations built it together. The UK BIM Alliance was an open industry body. BSI, the British Standards Institution, is the national standards body and publishes the standards. The Centre for Digital Built Britain was a government funded research centre at the University of Cambridge. Industry brought people who knew where the standards broke, BSI brought authority, and the research centre brought funding and rigour. Volunteers wrote much of the guidance. Two of those three founders have changed, and this catches people out. The Centre for Digital Built Britain closed at the end of September 2022, when its five year mission ended, so anything hosted on its site has not been added to since. The UK BIM Alliance renamed itself nima in 2022, having concluded that the acronym in its name made it read like a technical club, and that its work had grown into information management across the whole life of an asset. BSI remains the publisher. Then the framework itself was renamed. In November 2024 the Construction Leadership Council launched the Information Management Initiative, with nima's support, and in May 2025 the framework was rebranded as the IMI Framework. The old web address redirects to the new one, and nima maintains the guidance with BSI's support. Recognise both names, because contracts and search engines still use the old one, and cite the current one in anything someone else will read. Hold its contents as rings. At the centre sit the standards, the BS EN ISO 19650 series in its UK editions. Around them sit two series of guidance documents, taken in the second step. Beside those sit summary resources, including a one page infographic that maps practitioner questions onto the guidance. And underneath sits supporting material, including the transition guidance for anyone moving across from the older UK documents. Then the three things the framework is not. It is not a standard. It carries no requirements and cannot be complied with, so a clause demanding compliance with the UK BIM Framework does not oblige anyone in the way its author intended. It is not a mandate either. Government policy requires its use in some settings, as the third step shows, but the framework is what the obligation points at, not the obligation. And it is not BIM Level 2 renamed. The transition guidance said that the ISO 19650 series does not provide a definitive or exhaustive definition of Level 2. The concepts overlap, but the documents and the maturity model behind them differ. So return to the first sentence of the Stourleigh invitation. Leaving the phrase in and letting each bidder work out what it means is the wrong answer. The right answer takes three moves. Name the actual requirement, which for a delivery phase project is BS EN ISO 19650-2, and write it into the invitation. Identify what the framework contributes, which is guidance on meeting those requirements in the UK, together with the National Annex that supplies the UK content the international text leaves open. And say whether a policy obligation sits behind the instruction, because a public client is working to something more specific than a preference, and its bidders need to know what that is. Three moves turn a vague clause into a scope. The second step is finding the answer. Six published parts and a dozen or so guidance documents, each revised on its own cycle, are more than anyone holds in their head. A competent practitioner holds a map instead, and writes down where each answer came from. The map starts with the shape of the guidance. It is published as two parallel series, and the split tells you where to look first. The numbered series follows the life cycle, with concepts, then the delivery phase with its parties, teams and processes, then the operational phase. The lettered series cuts across the life cycle by subject, covering the information management function and its resources, open data with buildingSMART and COBie, the common data environment, developing information requirements, tendering and appointments, and information delivery planning. A question tied to a stage goes to the numbered series. A question about a subject that runs across stages goes to the lettered one. That one distinction settles most searches before you open anything. Then route the question in four decisions, in this order. First, is it about a requirement, or about how to meet one? A requirement lives in the standard, and the guidance only interprets it. Second, if it is about how, is it tied to a stage or to a subject? That chooses the series. Third, is there a UK specific element, such as a code, a naming rule, a classification system or a procurement obligation? If so, the National Annex comes in. Fourth, and only if an older document or practice is involved, go to the transition guidance. The infographic helps here. It runs in the order the work runs, from setting out what information is wanted, through tendering, delivery planning and delivery, to acceptance, and against each stage it puts a plain language question and names the clauses and guidance that carry the detail. That takes you from a client's phrasing to a clause number in one move. Stourleigh gives us three questions to route, all put to you in your first days. The council's project manager asks which naming convention the school's information containers should use. That is a UK specific rule, so the answer is in the National Annex to BS EN ISO 19650-2, not the international text. A colleague in the property team asks who will carry out the information management function on each appointment. That subject runs across every stage, so it goes to the lettered series, to the guidance on the function and its resources. And the procurement officer asks what the tender response requirements have to cover. That is a requirement tied to a stage, so it goes to the standard first, to clause five point three of ISO 19650-2, where the appointing party sets the tender response requirements, with the numbered guidance beside it. All three answers name a document and a place, not a recollection. The set moves, though. Each document carries its own edition and is revised on its own cycle, and the set was restructured alongside the 2025 rebrand. In June 2026 the framework added guidance on health and safety information under ISO 19650-6. So "the guidance says" is not a citation. Every time you answer from these documents, record four things. The document by its full title. Its edition or version. The clause or section. And the date you looked. Those four fields let a colleague check your answer, let you re-check it after a revision, and give an auditor evidence. So the second step resolves. Route the question before opening anything, and record every answer in a form somebody else can check. The third step is the UK layer, and it starts with two editions of the same standard. ISO publishes a standard. When BSI adopts it, it becomes a BS EN ISO document, and the core text is identical word for word, because that is what adoption means. The UK edition adds material at the front and at the back. Buy the plain ISO edition and you get a technically complete international standard with every UK question left open. That is why the second sentence of the Stourleigh invitation, which cites ISO 19650 rather than BS EN ISO 19650, needs correcting before it goes out. At the front sits the National Foreword, which most readers turn past. It names the UK committee responsible, which for this series is BSI committee B/555. It records the amendment history, including any corrigendum. And it records what the document supersedes or replaces, which makes it the primary source for the fourth step. At the back sits the National Annex. Its role is to clarify how the standard is implemented in one country without cutting across the international agreement. It answers the questions the international text leaves to each country, such as which classification system applies, what the status codes mean, and how an information container is named. The answers differ by country, and a project cannot run a common data environment without them. The annex to Part 2 is the one most people mean, carrying the container identification fields, the status and revision codes and the classification requirement. Part 4 carries an annex too, relating its review requirements to UK practice. Their contents belong to The Common Data Environment: Process Before Platform, and to Information Exchange in ISO 19650 Part 4. One fact from this layer to carry away. BS EN ISO 19650-2 was issued in 2018 and reissued in February 2021 incorporating a corrigendum, with a revised National Annex. The international text did not change. The UK annex did. Two copies both correctly labelled 2018 can carry different UK rules, and someone working from an older download can apply status codes the current annex treats differently. When you cite Part 2, say whether your copy incorporates the February 2021 corrigendum. Documents on their own oblige nobody, so the layer ends with policy. The 2011 Government Construction Strategy set the direction for public work, and what the industry called the 2016 BIM mandate followed, written in the vocabulary of Level 2 and the 1192 suite. A mandate that points at a withdrawn standard obliges nothing useful, so the policy moved with the standards. The restatement is the information management mandate, published by the Infrastructure and Projects Authority on the thirteenth of September 2021, inside Transforming Infrastructure Performance, Roadmap to 2030. Read it as six obligations on a public client. Be able to do the work, building the capability to carry the information management function through its own people or a representative. Know what it wants, writing its requirements at organisational, asset and project level, and at exchange level for each appointment. Judge whether the work is sensitive, using the assessment method in ISO 19650-5. Buy the work properly, so that procurement and contracts reflect the framework standards. Hold what it receives in systems built for the job. And keep governing that information for as long as the asset lasts. The Construction Leadership Council has since reviewed the mandate, and the Information Management Initiative is the approach that review produced. Beside the mandate sits the Construction Playbook, the government's guidance on how public works are bought, from delivery models and contract forms to risk allocation and pricing. It points its readers at the framework as the route to working against the right standards. So when a public client says a project follows the playbook, information management obligations come with it, and they point at the framework. Government Soft Landings belongs here in a paragraph. Its 2019 guidance, revised to sit alongside the series, asks the client to set measurable performance targets and plain language questions at the outset, and those become project information requirements and then exchange information requirements. It then asks for aftercare of up to three years, with post-occupancy evaluation. It is not a separate discipline. It is the reason a public client wants the information at all. Now put the layer together on Stourleigh's second sentence. Establish the edition, which for a UK delivery phase project means BS EN ISO 19650-2 incorporating the February 2021 corrigendum, and state it in the invitation. Establish what the annex settles, because naming, status codes and classification are annex questions, and the project information standard should adopt the annex or record where it departs from it. And establish the policy obligation, by deciding which requirements of the information management mandate the council passes down into this appointment, and saying so. That resolves the third step. The UK edition, its annex and the policy behind it are what turn a citation into an obligation. The fourth step turns backwards, because most practitioners work with a contract from 2016, a procedure from 2018, a template inherited from a previous employer. The Stourleigh pack is exactly that kind of inheritance. The check is the same every time. Take the standard number, find the publisher's record, read the status and the date, and if it is withdrawn, find out what took over the subject, and whether anything did. One distinction makes that check work. Withdrawn is a status. It means the publisher has taken the document out of its catalogue, and it carries a date. Superseded is a relationship. It means another document has taken over the subject. Usually they travel together, but not always. A document can be withdrawn with nothing replacing it, leaving a gap the project must fill by its own decision. Or its subject can be split across several new documents with no single successor. Record both facts for every item, the status with its date, and the successor or its absence. The episode Information Management in ISO 19650 Part 1: Concepts and Principles tells the withdrawals as a history. Here they are a sorting job, because the Stourleigh pack resolves in five different ways. The first way is one to one. The security clause cites PAS 1192-5, withdrawn on the first of July 2020 and superseded by ISO 19650-5. The pack also carries a clause on asset information in operation, written to PAS 1192-3, which went the same way, withdrawn on the eighteenth of August 2020, with ISO 19650-3 taking over. The second way is distributed. BS 1192 and PAS 1192-2, which carry the naming procedure and the employer's information requirements, were both withdrawn in January 2019 and superseded by Parts 1 and 2 of the series, but not part for part. The transition guidance said plainly that there is no one to one relationship. Content from BS 1192 on the common data environment and on naming landed in both parts and in the National Annex. So a clause reference cannot be translated by arithmetic. It has to be looked up, which is the fifth step. The third way is a later move. The health and safety clause cites PAS 1192-6, withdrawn on the twenty-third of January 2025, when ISO 19650-6 took over the subject. The pack holds one more item of this kind. Someone updated it in 2021, carefully, by adding a reference to BS EN 17412-1 for level of information need. That reference is now withdrawn too, because ISO 7817-1, published in 2024, superseded and withdrew BS EN 17412-1. Doing the right thing once does not make a reference permanent. The fourth way is a change of concept rather than document. Level of detail and level of information were never standards of their own in the way the 1192 documents were. The level of development schemes behind them came from North America and entered UK practice by adoption. The series replaced the idea, not a document, and the transition guidance treated the older levels as specific examples of level of information need rather than equivalents of it. So the pack's level of detail schedule needs a new method, not a new reference, which is the subject of Level of Information Need in ISO 7817-1. The last way breaks the pattern. BS 1192-4, the code of practice for COBie, was withdrawn on the sixteenth of September 2022, the same month the British edition of Part 4 was published, and the records disagree about what followed. The BSI catalogue names no successor. Other records, including the NBS publication index and the National Foreword to Part 4, name Part 4. Record both. Neither changes the practical position, because Part 4 deals with information exchange in general and carries no COBie content. So Stourleigh does not have to drop COBie. It has to stop pointing at a code of practice that no longer exists, and settle its exchange format in its own information standard. That spread is the point of the fourth step. The withdrawals run from January 2019 to January 2025, so a document written in that window can be partly right and partly stale. A document from 2020 that mixes ISO parts with surviving PAS parts may have been correct when written. A single rule of thumb would be wrong more often than right. A dated record for each item is not. The fifth step goes down a level, because legacy documents rarely cite whole standards. They cite clauses, in vocabulary that has since moved. The tool is PD 19650-0, the transition guidance, which came into effect on the thirty-first of January 2019, prepared by the committee that oversees the series. It was a published document, not a standard, so it was never to be quoted as a specification. It was written for people who already knew the UK documents, and it answers one question better than anything else, which is where a piece of the old standard went. I said at the start that this guidance has been withdrawn, and the detail is worth having. The BSI catalogue, checked for this episode, records PD 19650-0 as withdrawn from the twenty-fourth of June 2024, with no successor named. It still holds the clause map for the move, and it is still worth opening. But cite it as withdrawn guidance, use it to find where to look, and never treat it as the authority for what is there. Its working part is Annex A, which mapped BS 1192 in one sequence and PAS 1192-2 in another. Each entry gives you five pieces of information, in order. The legacy clause number. A short description of its topic, in the old vocabulary, which means you can search by the words your legacy document uses. Where the topic now sits in Part 1. Where it sits in Part 2. And a pointer into the transition guidance itself, where a topic needed explaining. Treat that last pointer as a signal. Where it is filled in, something changed. Each entry resolves in one of four shapes, and reading the shape is most of the work. A direct move, one topic to one clause. A split, across several clauses and sometimes both parts. A move out of the standard into the National Annex, which is where most naming and coding content went. Or not applicable, meaning no successor in the series at all. The first three call for a reference. The fourth calls for a decision. Three items from the Stourleigh pack show the shapes. The first is a direct move, to an unexpected place. The pack's employer's information requirements name a task information manager for each task team, and repeat the old requirement, at clause seven point five point one point three of PAS 1192-2, that roles are not to be confused with job titles. Annex A sent that clause to clause seven point one of Part 1, with nothing against Part 2, and the explanation pointer filled in. Read the shape. The requirement moved from the delivery process into the concepts, so the series treats it as a principle. And something changed, because the series takes no role based approach at all. It has an information management function, assigned to whoever is best placed to carry each part of it. The successor sits in a different part of the series, and the named post has gone. Roles and the Responsibility Matrix takes that further. The second item, the naming procedure, is a split, and one of its destinations is the annex. The procedure cites the clause of BS 1192 that listed the standard methods and procedures a project needs, covering roles, names, project codes, spatial coordination, the common data environment and hierarchy. That one clause maps to four clauses in Part 1 and to five or six places on the Part 2 side, the annex among them. Updating it leaves a choice. Cite the full set, which is accurate and unwieldy in a contract, or cite the clause that carries the obligation you mean and record why you narrowed it. Both are defensible. Picking one silently is not. The third, the COBie file at each volume, is not applicable. Annex A marked that very requirement so, along with a pointer to industry documents the old standard relied on. They are not hidden elsewhere. They are gone. If the council still wants the thing, it must require it itself, in its information standard or its exchange information requirements, openly, rather than reaching for the nearest similar clause. Clauses are only half the translation, because the words changed too. Some changes are straight swaps. Contract became appointment. Employer became appointing party, with lead appointed party and appointed party below it, and supplier went the same way. Suitability became status. Others need care. Level of model definition, level of detail and level of information all resolve to level of information need, which is a broader idea, not a rename. And the responsibility matrix keeps its name while the series also speaks of an assignment matrix, so the old term is not simply wrong. One term is a trap. Under the old suite, EIR stood for employer's information requirements. Under the series, it stands for exchange information requirements. Same three letters, different meaning. The old term named one document issued by one employer. The new term names the requirements attached to each appointment, and a project has many. Every other retired term announces itself. This one reads as current. When the Stourleigh pack says that the supplier shall respond to the EIR, it is either correct or a survivor from 2013, and the acronym will not tell you which. Here it is the survivor, so the clause needs rewriting, not just relabelling. Last, the transition guidance has aged, and not only in its catalogue status. Its account of the standards suites recorded that no work item had been agreed for an ISO equivalent of the health and safety document, and ISO 19650-6 was published in 2025. That was accurate in 2019, and the same holds wherever it calls a part of the series under development. So find where a topic went in Annex A, then confirm the destination clause in the current edition. The map tells you where to look. The standard tells you what is there. Put together, the method has five moves for any legacy item. Confirm the source document's status and date. Find its topic in Annex A by the words the legacy document uses. Read which of the four shapes the entry has. Confirm the destination in the current edition. And record the legacy reference, the current reference, the shape and the action. That record makes the work checkable, and it resolves the fifth step. A legacy clause is mapped by its shape and confirmed against the current text, never translated by a rule. So back to the pack on the information manager's desk. The question was what the UK BIM Framework is and is not, and how a legacy document set maps onto the standards in force. The framework is guidance, now the IMI Framework, maintained by nima with BSI. It interprets the BS EN ISO 19650 series and is not a standard, a mandate or Level 2 renamed. The obligations sit in the UK editions with their forewords and annexes, and on public work in the mandate and the playbook. A legacy set maps item by item, each with its status and date, its successor or the absence of one, and at clause level its shape, its new words and a confirmed destination. For Stourleigh that means revising the pack before it is issued, naming BS EN ISO 19650-2 with its 2021 corrigendum, saying which mandate requirements reach this appointment, and attaching a dated map of what each reference in the pack now means. That spends part of the fortnight, and it spares every bidder from pricing a process nobody can now produce. Three things are worth keeping. When a clause asks for compliance with the framework, point it at the standard and use the framework to interpret it. When you answer anything from these documents, record the title, the edition, the clause and the date. And when you inherit a legacy document, sort each reference by its shape before you change a word, because a single rule will mislead you more often than it helps. For reading, start with the National Foreword and National Annex of BS EN ISO 19650-2, then Annex A of PD 19650-0, withdrawn guidance now read as history, for the move from the 1192 suite. The roadmap that carries the mandate, the Construction Playbook and the 2019 soft landings guidance are all free to read. For the content of the annex, go to The Common Data Environment: Process Before Platform. For the withdrawals as a history, go to Information Management in ISO 19650 Part 1: Concepts and Principles. The next episode, The BIM Execution Plan, is about how one plan serves both the tender and the appointment. Dr Sepehr Abrishami signing off from Reimagining AEC, with one reference-checking job for you. Pull out an older document you still rely on, at work or in your research, and give every standard it cites a status, a date and a successor before you trust it again.