When an information management task on a project goes undone, which organisation has failed to do it? I am Dr Sepehr Abrishami, I sit on journal editorial boards, where every decision on a paper carries the name of the editor who made it, and on Reimagining AEC, in its season on the ISO standards, that question gets an answer clause by clause. This episode is about roles and the responsibility matrix as ISO 19650 Part 1 and Part 2 set them out, from the parties and the information management function to the two matrices that record who answers for what. The project is hypothetical. Denholm District Council is building the Ferrybank Community Hub, a two-storey community building, and the design has reached the end of Stage 3 of the RIBA Plan of Work, RIBA being the Royal Institute of British Architects. Its project management consultant, Wyvern Project Services, carries part of the council's information management work under a delegation. Marrow and Vale Architects leads the design, with a structural engineer, Kirkwall Structures, and a building services engineer, Penhale Building Services, appointed beneath it. Every name is invented. Now suppose the architects' information model for the end of Stage 3 arrives for the council to accept. The council forwards it to Wyvern, because everyone assumed the consultant had this in hand. Wyvern replies that review and acceptance sit outside its scope of services. Both sides are sincere. The design team waits, and the council has to choose between paying for a variation, finding someone of its own, or letting the model sit. So the question for this episode is who answers for each information management task on Ferrybank, and how you would prove it in writing. By the end you will be able to name an organisation's role once for each appointment it holds, read a duty in the standard to the party it binds, tell the two responsibility matrices apart and say which one the standard requires, fill in an allocation from the clause text, and defend a contested row in four moves. There are six steps. The first three deal with parties and people, meaning the four parties and the one function they share, the difference between a role and a job title, and a reading of the Ferrybank team against the standard. The last three deal with the matrices, telling the two apart, filling one in, and defending it when somebody disagrees. The first step is vocabulary. A scope dispute on a project is rarely a dispute about the standard. It is a dispute about who agreed to do what, carried on by people who use the word role in two senses. One means a job title on an organisation chart. The other means a party in an appointment. The standard allocates duties to parties, never to people or to job titles. Parties are organisations joined by appointments. The appointing party sits at the top of the chain and receives information. A lead appointed party is appointed directly by the appointing party. An appointed party is appointed by a party above it, at any tier below the lead. Teams are groupings of those organisations. A delivery team is a lead appointed party with all its appointed parties. A task team delivers one information task, usually a discipline team inside one firm. The project team is the appointing party with every delivery team. Parties hold obligations. Teams hold work. So when someone asks who is responsible, the honest first question is which party, not which team. Two points are widely misread. There is no limit on the number of lead appointed parties, and nothing requires one of them to lead the others. In UK practice the client usually appoints its consultants separately, so a project can carry five or six lead appointed parties, including the cost consultant and the project manager. The transition guidance, PD 19650-0 of 2019, since withdrawn and cited here as history, made that point against the older model in Publicly Available Specification 1192-2, known as PAS 1192-2, which suggested only a design lead and a construction lead. And roles attach to appointments, not to organisations. A design consultancy appointed by the client is a lead appointed party, and also an appointed party, because its own staff produce information inside its delivery team. When someone asks what role their firm has, the answer is one word per appointment. PAS 1192-2 spoke of employer and supplier, and it named information management roles. ISO 19650 replaced both. The international drafting group could not use employer, which outside the UK usually means someone who employs staff, so appointment became the root word. And instead of named roles, duties attach to parties through a single information management function. The UK guidance on the function and its resources, Guidance Part A, defines it as the whole of the responsibility and authority that Part 2 attaches to its information management process, held collectively. It is a body of duties, not a post. Every party holds a share of it, and each party then assigns its share to named individuals with the competence and the time to carry it. Delegation follows two clauses of Part 2. Under clause five point one point one, the appointing party may nominate its own people, or ask a third party or a prospective lead appointed party to carry all or part of the function, and if it delegates it has to set out a scope of services covering the tasks, the authority delegated and the competence needed. Clause five point three point one gives a prospective lead appointed party the same route, and adds probity arrangements where conflicts of interest may arise. Guidance Part A then states the sentence to keep. Responsibility can be delegated. Accountability stays with the party the clause names. The responsible organisation does the work. The accountable organisation answers for it and holds the authority to say yes or no, and only one organisation can be accountable for any task. That resolves the first step, and it already explains the hook. Denholm moved work to Wyvern. It did not move answerability. If the model is not accepted, the council is the party that failed to accept it. The second step is the principle that a role is not a job title. Think of the titles you meet on projects, information manager, BIM manager, BIM coordinator, digital delivery lead, BIM here being building information modelling. Every one is real. None appears as a defined role in Part 1 or Part 2. Each describes how one organisation has chosen to staff its share of the function. The duty still sits with a party, defined by an appointment. The source is clause seven point one of Part 1. It treats clarity of function, responsibility, authority and scope as essential, and then states that functions and responsibilities are not to be confused with job titles or with professional or other designations. It expects functions to be written into appointments, as a schedule of services or under the wider obligations an appointment carries. It accepts that on small work one person may carry several functions, alongside project management or design team leadership. And it says information management functions should not reach into design responsibilities, a boundary worth defending when a scope drifts. The principle is older than the standard. PAS 1192-2 said much the same in 2013, and PD 19650-0 mapped that passage forward to clause seven point one and recorded that the series includes no information management roles. It is still the commonest error in the subject. What Part 1 does describe is functions at three levels, asset, project and task, each a body of work allocated to parties by suitability rather than a post. So an information manager is a job title given to a person who carries part of one organisation's share. It is useful, and nobody needs to stop using it. It is not a fifth party. Two firms on Ferrybank can each employ an information manager, and those two people can have almost nothing in common, because their duties come from their employers' appointments. The error is easiest to see in a typical roles guide from a template pack sold to consultancies, left unnamed because the pattern matters more than the publisher. It teaches five roles, the appointing party, the lead appointed party, the task team, the information manager and the BIM coordinator, uses them as the columns of its matrices, and tells the reader that Part 1 defines the last two as functional roles. Three problems follow. First, the template in Annex A of Part 2 has four columns, appointing party, third party, lead appointed party and appointed party. The guide drops the appointed party, which produces most of the information, and the third party, the very column that shows a delegated function. Second, the attribution is wrong, since clause seven point one says close to the opposite, and a bid writer who repeats it has misstated a published standard in a document someone will evaluate. Third, a job title in the accountable column takes the duty out of the appointment structure. An individual cannot be accountable in the standard's sense, so when that person moves on the duty seems to leave with them, and the matrix becomes an organisation chart with letters on it. The commercial form of the same error is familiar. A firm agrees to provide a coordinator, and three months later it is providing three functions at the rate it quoted for one. A scope written in job titles prices a person. A scope written in tasks prices work, which is why Guidance Part A builds a third party's scope from the tasks to be performed, listed precisely, over a stated timescale. So the second step resolves. Job titles belong to contact lists, reporting lines and recruitment. Parties and functions belong to anything that allocates a duty, and trouble starts when a document written in one language answers a question asked in the other. The third step turns that principle into a procedure on the Ferrybank chart. Six people. A head of property services at the council. A project information manager at Wyvern. A digital delivery lead and a BIM manager at the architects. A BIM coordinator at the structural engineer. A technical director at the building services engineer. From the titles alone you cannot tell which organisation answers for anything. The method starts by putting the chart down. List every appointment and name the party on each side. Only then place each individual against the party that employs them. Written out this way, Wyvern appears in three appointments. It is a lead appointed party for its own project management services, because it produces information in response to requirements, as Guidance Part A describes for a client's project manager. It is a third party for the council's delegated information management work. And it holds a separate appointment to host and support the common data environment. Marrow and Vale is a lead appointed party, with Kirkwall and Penhale beneath it as appointed parties, and also an appointed party inside its own delivery team, because its architects produce information too. So Wyvern's role has three answers. As a lead appointed party it owes its own plan and delivery planning, even with a delivery team of one. As a third party it carries out what the council delegated, while the council stays accountable. As host it delivers a service under a third appointment. Ask which appointment first and which duty second, and the question has an answer. Ask it the other way round and it starts an argument. The map shows three defects, which tend to arrive together. The first is a title spanning two roles. Okonkwo, one of the two people at the architects, has a job description covering the delivery team's information management function, meaning confirming the plan, establishing the detailed responsibility matrix and aggregating the delivery plan, and also authoring architecture containers inside the architecture task team. One is lead appointed party duty, the other is production as an appointed party. The standard allows that on smaller work. The trouble is that it is invisible, so under pressure the delivery team duties slip first, having no separate name and no separate budget. The second is a title that misdescribes the work. Iqbal is called a BIM manager, which most readers take to mean information management across the delivery team. The work described is model coordination inside the architecture task team. The council reads that title in the tender return and assumes the delivery team function has a named person. It does, but the person is Okonkwo, alongside production work. Two organisations now hold different beliefs about the same work. The third defect is the hook. Wyvern's delegated scope covers the council's tasks through procurement, planning and appointment, and stops there. Three appointing party duties after appointment sit in no scope at all. Reviewing and accepting the information model is clause five point seven point four. Archiving the project information model is clause five point eight point one, and compiling lessons learned is clause five point eight point two. Nobody at the council is named against any of them. Guidance Part A warns about exactly this. Scope a third party without mapping the tasks across the whole project team, and you leave gaps in the function. A finding only counts if someone can act on it. To say that roles are unclear is a mood. To say the project needs a proper information manager asks for a hire before anyone has agreed the work. A usable finding names the task by clause, names the party accountable for it, and says what covers it today and what does not. Raised at mobilisation, the Ferrybank gap is a conversation. Found at the first exchange, it is a claim. That resolves the third step. The fourth step is the name that two documents share. The standard gives you a template for the matrix it does not require, and requires a matrix for which it gives you no template. The first document is the information management assignment matrix, in Annex A of Part 2. Annex A is informative, so the matrix is offered rather than imposed, and it is noted at clause five point one point one, where the appointing party decides how to resource its function. Its rows list the activities of the process by clause, from five point one point one in assessment and need to five point eight point two at project close-out. Its four columns are the four party positions. Every cell in the published version is empty, on purpose, because allocation is a project decision. The note at clause five point one point one offers it as a way to build the scope of services a delegation needs, so it is a procurement instrument. It also shows gaps for free. Once every activity is allocated, the activities nobody has been asked to carry are the only blank rows left. At Ferrybank, that is where acceptance would have shown up. The second document is the responsibility matrix for information deliverables, and it is required, in three steps. At clause five point three point two, a prospective lead appointed party puts a high-level responsibility matrix into its pre-appointment plan, saying who is responsible for each part of the information model and its key deliverables. At clause five point four point one, when the plan is confirmed, that matrix is updated as required. At clause five point four point two, the lead appointed party refines it into the detailed responsibility matrix, which answers three questions. What information is produced. When each item is exchanged, and with whom. And which task team produces it. Guidance Part 1 on the concepts of the series confirms that the series includes no template for it. This matrix feeds everything downstream. Clause five point four point four has each task team take account of it in its task information delivery plan, and clause five point four point five has the lead appointed party take account of it in the master information delivery plan. A vague matrix fails at a milestone, when two task teams each assumed the other was producing something. The episode The Delivery Plans covers those plans, and the episode The BIM Execution Plan covers the plan the high-level matrix sits in. The difference matters most in a tender. Say you produce a high-level matrix at tender and refine it on appointment, and you can point to clauses five point three point two and five point four point two. Say that ISO 19650 requires a detailed assignment matrix of tasks, and there is nothing to point at, because Guidance Part A says in terms that developing one is not a requirement of the series. Any party may still expand Annex A, and that is useful practice, but it is not a mandate. The confusion has an honest source. Both documents get called the responsibility matrix, and PD 19650-0 mapped the older term onto both. The test takes a few seconds. Does the document allocate tasks, or deliverables? Tasks means Annex A. Deliverables means clause five point four point two. Both means two documents that someone has merged, which is worth unpicking before anyone signs. That question resolves the fourth step. The fifth step fills in the empty assignment matrix for Ferrybank. First the four letters, because loose use is where matrices go soft. Accountable is the one organisation ultimately answerable, holding the authority to say yes or no. Responsible is the organisation that completes the task. Consulted is a party whose view is sought while the work is done, two-way, with a real chance to change the output. Informed is told the outcome afterwards, one way only. Each letter has a test. If this is not done, who has failed? Who does the work? Whose input changes the output? Who has to know afterwards? So every row asks which task, by clause, and every column puts those four tests to one party position. Two rules do most of the work. Rule one is that the accountable column is fixed by the clause. Every activity in Annex A is a clause of Part 2, and every one names the party it binds in its opening words. The appointing party shall. The lead appointed party shall. Each task team shall. That party is accountable. Guidance Part A says the same of the assignment matrix tool published by the UK BIM Framework, which was renamed the IMI Framework in May 2025, after the Information Management Initiative. In that tool the accountable allocations follow the shall clauses and should not be changed. Moving one is not tailoring the standard. It is departing from it. So fill that column first, which is quick and rarely argued over. Rule two is that the other three columns are project decisions. Responsible follows the appointments, which is why the third step mapped appointments before people. Consulted and informed follow the flow of information, and they are the columns most often left blank. Several parties can be responsible. Only one can be accountable. Where a party is both, record both. Now Ferrybank, in three blocks. In assessment and need and the invitation to tender, every clause opens with the appointing party, so the council is accountable throughout. At clause five point one point one it is also responsible, because appointing individuals to its own function is the act it cannot hand away. Clause five point one point two, establishing the project's information requirements, shows the pattern for a delegation. The council column reads accountable. The third party column reads responsible, because Wyvern does the work under its scope. The lead appointed party is informed, because the requirements shape what it will deliver. The appointed party column stays empty, because no appointed party exists yet. Without a third party column, Wyvern would have to be misfiled as a lead appointed party, or its work would vanish. In the tender response and appointment, the clauses open with the lead appointed party, so the architects are accountable. At clause five point three point one they are also responsible, and Duarte Digital, an information management consultant the architects engaged, is responsible for the part delegated to it, a second delegation on one project. At clause five point four point two the detailed responsibility matrix is the architects' to establish, with the appointed parties consulted, because a matrix written without the people who must deliver against it rarely survives its first month. The exception is clause five point four point four, which opens with each task team, so the appointed parties are accountable for their own plans. In production and delivery, clause five point six point four has each task team review and approve its own information before sharing, so the appointed parties are accountable and responsible. At clause five point seven point two the architects review and authorise the model. At clause five point seven point four the council reviews and accepts it, and the hook returns. The council is accountable, the third party cell is empty because Wyvern's scope stopped at appointment, so the council is responsible by default, and nobody there is named. The matrix did not create that problem. It made it impossible to ignore. One row is genuinely open. Clause five point one point seven binds the appointing party to establish the project's common data environment, covering implementing, configuring and supporting it. The same clause allows a third party to be appointed to host, manage or support it, preferably separately and before other procurement, and recommends a specification of functional and non-functional requirements. Denholm delegated the clause to Wyvern under one scope and bought hosting and support from Wyvern under another. One defensible position gives responsibility to Wyvern, because the scope covers the clause and the same firm runs the platform, so splitting them leaves nobody able to configure it. The other keeps responsibility with the council and limits Wyvern to hosting, because establishing the environment means deciding that it serves the project, which the clause ties to the requirements specification, and the clause treats hosting as separable. What cannot be defended is either position asserted without its argument, or any entry that moves accountability off the council. The episode The Common Data Environment: Process Before Platform covers what that specification should contain. Two practical points close the step. The full list runs to about forty rows, too many for one legible page, so split it by process stage and keep the column order identical in every part. And the recurring errors reduce to two principles. Some destroy answerability, such as two accountable entries on one row, accountability moved to whoever does the work, or a job title in a party column. Others leave the matrix inert, such as consulted and informed left blank, or an allocation copied from another project that contradicts your own appointments. So the fifth step resolves. The accountable column comes from the clause, and everything else comes from this project's appointments. The sixth step is the moment someone disagrees. The same matrix scopes an appointment before procurement, prices a tender during it, and settles disputes during delivery, and the last is the hardest test, because it has to survive a reader who was not in the room and has an interest in reading it the other way. Recall the coordinator who became three functions. Fixing the definition in the appointment and treating extra duties as variations works only if the definition is written in parties and tasks. A written defence makes four moves, in order. Cite the clause, not the standard, because ISO 19650 as a whole says nothing about your row. Name the party that clause binds, which is why the accountable entry sits where it does. State what was delegated, under which appointment, and what was retained, which is where most disputes are settled. Then say what would change your mind. That shows you understand the counter-argument, and it stops you holding a wrong line for two months before anyone checks the clause. Apply it to the Ferrybank row. Clause five point one point seven binds the appointing party to establish the common data environment, so the accountable entry stays with the council. The clause allows a third party to host, manage or support it. On this project the council delegated the clause and separately bought hosting, and neither the requirements specification nor the decision that the environment serves the project was transferred. The position would change if the delegated scope had included that specification, in which case responsibility would sit with Wyvern, and accountability would still sit with the council. Some things offered as defences are not. This is how we always do it cites nothing anyone can check. ISO 19650 requires it is almost never true of a single row. It was in the matrix we issued is circular, because the matrix is what is disputed. And the information manager owns that puts a job title where the argument needs a party. In the room, take one disputed task at a time, because a row has a clause, a party named in it, and an appointment that covers the work or does not. Settle the accountable entry first, which usually takes a minute once someone reads the clause aloud. What is left is responsibility, a commercial conversation rather than a compliance one, and a far better one to be having. Then record the outcome as a variation or an agreed amendment and reissue the matrix, because an agreement that lives only in a meeting note will be reopened at the next exchange. One forward look, labelled as such. Draft revisions of Parts 1 and 2 were open for public comment from March to May 2026, and a draft revision of Part 3 followed, open for comment until July 2026. According to a webinar run by the British Standards Institution and nima, the party names would stay the same, an information management team would be introduced at organisational and project level, and one process would run across delivery and operation. None of that is in force, no publication date has been announced, and the 2018 editions of Parts 1 and 2 are the ones to cite. So the sixth step resolves. A boundary holds when it is argued row by row, from the clause, in writing, and recorded. So to the question the episode opened with, which was who answers for each information management task on Ferrybank, and how you would prove it. The answer is the party the clause names in its opening words, and the proof is a matrix whose columns are party positions and whose accountable entries come from those clauses. Denholm District Council answers for accepting the information model, archiving it and compiling lessons learned, whatever it delegated to Wyvern, because responsibility moved and accountability did not. Who at the council does that work is a staffing decision, and the matrix exposes the gap early enough to close it cheaply. Three practices follow. Name your organisation's role once for each appointment, and write any scope of services in tasks by clause, never in job titles. Know which matrix you are holding, because the deliverables matrix at clauses five point three point two and five point four point two is required and has no template, while the assignment matrix in Annex A has a template and is not required. And when a row is challenged, argue it in four moves, clause, party, delegation and what would change your mind, and raise any unowned task at mobilisation. For reading, start with clause seven point one of ISO 19650-1, then clauses five point one point one, five point one point seven, five point three point one, five point three point two and five point four point two of ISO 19650-2, with its Annex A. Read PD 19650-0, withdrawn guidance now read as history, for the move away from named roles. Guidance Part A sets out the function and the accountability position, and Guidance Part 1 describes the two matrices. For the three levels of function, go to Information Management in ISO 19650 Part 1: Concepts and Principles, and for where each task falls among the eight activities, The Delivery Phase in ISO 19650 Part 2. This episode closes the season on the ISO standards, and every episode in it can be heard in any order. Cover every personal name on a matrix from a project you work on or study, and see whether each row still tells you which organisation would have failed. I am Dr Sepehr Abrishami, and I made this episode of Reimagining AEC so that your answer would be yes.