Architects learn early that a drawing makes promises its author may never have meant to make. I am Dr Sepehr Abrishami, I trained as an architect, and in this season of Reimagining AEC I am reading the ISO standards that decide how much a drawing or a model has to say. This episode is about level of information need, as ISO 7817-1 sets out its concepts and principles.
Take a building that does not exist. It is a two-storey community health centre, and it is hypothetical. The design is at Stage 3, Spatial Coordination, in the 2020 Plan of Work of the Royal Institute of British Architects, and the appointment contains one line about doors. All doors, LOD three hundred. LOD is a legacy grade, short for level of development, and the line reads like a specification. Now follow one fire door through the people who need it. The fire engineer preparing the fire strategy needs the door's fire resistance rating and its position on the escape route, and a plan symbol with one property would do. The accessibility reviewer needs the clear opening width, the threshold and where the handle sits, and has no interest in the rating. The cost consultant needs a door type and a count, will take both from a schedule, and needs neither geometry nor rating. Three people, three needs, one line. The architect now has to decide what the line means. Model every door in three dimensions with whatever properties the software exports, and the team pays for information nobody asked for, while the fire engineer may still not find the rating. Ask the client what the grade means, and there is no written answer to give, because the grade never lists its properties. Multiply that choice by every object in the building and you have the cost of a single number.
So the question for this episode is why a single number such as LOD three hundred specifies nothing, and what the standard puts in its place. By the end you will be able to write a specification for one object that another party can act on and check. You will set its four prerequisites, express it across three kinds of information, mark what the purpose does not need as not applicable, write it down in one of two forms, and state one check that proves it was delivered and one that proves it can be used.
There are five steps. First, what the grade was asked to carry, where it breaks, and which documents now govern. Second, the four prerequisites that sit beside every specification. Third, the three categories of information and the rule that lets any part of them be switched off. Fourth, writing the specification down, including what to do with a legacy schedule or a bloated requirement. And fifth, checking it, by a person and by a machine, with a short look at the parts of the series still in draft. The health centre stays with us throughout, through three of its objects, an external wall, a fire door and an air handling unit.
The first step is the grade itself, taken on its own terms, because it was a serious attempt at a real problem and many good projects were delivered under it. The grades have two lineages. The first is North American. In 2008 the American Institute of Architects issued a protocol exhibit that graded model content on a scale from one hundred to five hundred, and from 2013 an industry body, the BIMForum, developed that scale into a published specification and added an intermediate grade of three hundred and fifty. The second lineage is British. PAS 1192-2, a Publicly Available Specification published in 2013, paired a graphical level of detail with a non-graphical level of information and called the pair the level of model definition. That document was withdrawn when ISO 19650-2 took its place. So a UK appointment that says LOD three hundred today cites a North American grade the UK standards never adopted, inside a process that has moved on twice since. That explains the confusion. It is not a criticism of whoever wrote the line.
Consider what the one number was asked to carry. Geometry, meaning how detailed the shape is, in how many dimensions, where it sits and what it looks like. Information, meaning which properties are attached and how far their values can be trusted. And authorised use, the one people forget, meaning what a downstream party may rely on the content for, which in practice is a statement about liability. Three things, one ordinal number. The grade works only if all three mature together, in lockstep. They do not, and the standard's own examples show it. A pipe for quantity take-off needs only a centreline, because length is what the estimator measures, while the same pipe at the same milestone has to be a solid in its true position for clash detection, because volume is what clashes. And a planning submission during briefing may want documents and nothing else, which a grade has nowhere to put.
So the single number breaks in four places, and each break is structural. It cannot diverge, so whichever kind of information needs the most drags the others up with it, and that is the mechanism behind over-specification. At the health centre, the accessibility reviewer's need for a door in three dimensions drags the fire engineer and the cost consultant up to three dimensions too, because the line about doors has only one setting to give. It cannot say why, because it names an amount and never a purpose, so nobody can test whether the amount is right. It cannot be read the same way twice, because two firms interpret the same grade differently and the interpretation is almost never written into the appointment, so the ambiguity becomes contractual. The introduction to ISO 7817-1 makes that point internationally, that conflicting terms and usages have stood in the way of a common understanding. And it cannot be checked by a machine, because a number on a model names no property and no value a checking tool could test. Rewording the grades would fix none of the four.
What replaces the number is a framework, and the documentary position is short. The governing standard is ISO 7817-1, published in 2024 and adopted in the UK without change as BS EN ISO 7817-1. It superseded BS EN 17412-1 of 2020, which is withdrawn. The framework carried across largely intact. What changed was alignment, of the terms with the ISO 19650 series and of the checking clause with ISO 19650-4, and status, because the document is now an international standard. Clause numbers quoted from the withdrawn document are unreliable, and any template still citing it as current has not been maintained. Two documents connect the framework to delivery. ISO 19650-1 defines the term at clause three point three point sixteen. ISO 19650-2 places the level in the exchange information requirements at clause five point two point one b, and asks the appointing party to consider how it will be assigned in the project's information standard at clause five point one point four c. How it then flows into the delivery plans belongs to the episode The Delivery Plans.
One more thing about the name. The introduction to the standard says it is helpful not to shorten level of information need to an acronym, because an acronym oversimplifies the concept. This episode follows that request, and the advice for your own writing is the same. Use the full term in any specification another party has to act on, and when a shorthand turns up in a legacy document, translate it back and ask the questions of the second step, because the shorthand tends to arrive without them.
That settles the first step. The grade asks how much. The framework asks for what purpose, by which milestone, from whom to whom, about which object, and only then how much of each kind of information. That is a longer question, and it produces an answer someone else can check.
The second step is the four prerequisites, and they come with the distinction that carries the most weight in the standard. Clause five names them. Purpose answers why. The information delivery milestone answers when. The actor answers who provides and who receives. And the object within a breakdown structure answers what. Then clause five point one says something most people misread. The specification is informed by the four prerequisites, and it does not include them. Clauses five point two to five point five each repeat the point for their own prerequisite. Those four things are settled beside the level, and the level is set in their light. A specification that fixes its own milestone, or names its own deliverer, has confused the requirement with its context, and the next person who reuses it at another milestone will misapply it. Keep the requirement clean, and it can travel.
Purpose comes first, because clause five point two makes it the question every other decision answers to. The clause does four things. It requires, with a shall, that the purposes are considered before a level is set. It recommends that they are written down. It confines a level to the purposes it was written for, which quietly forbids lifting a specification from one job and reusing it on another without examining it again. And it states the boundary, that the level does not specify the purpose. The clause's own example is a door, where accessibility wants the opening and the handle, pricing wants the cost and a rendering wants the appearance. It also shows the pattern running the other way, with a block in concept design whose geometry and information serve both clash detection and quantity take-off. So the rule is not one level per purpose by decree. Purpose decides, and sometimes purposes coincide.
The note to clause five point two says where purposes come from. It points to the organisational, asset and project information requirements of ISO 19650-1, at clauses five point two, five point three and five point four, and to the project's own requirements at clause five point one point two of ISO 19650-2. That hierarchy belongs to the episode Information Management in ISO 19650 Part 1: Concepts and Principles. What this standard adds is the act of drawing a purpose from it. Find the decisions and approvals the brief has to win, because a report is not a purpose, and the decision it serves is. Trace each one to a requirement, because a purpose that traces to nothing is a wish, and wishes are how over-specification starts. Name it in the receiver's words, accessibility analysis rather than compliance. And decide whether it may be disclosed, because clause five point two allows a purpose to be withheld for security reasons, with only authorised actors told what it is.
At the health centre, that gives five purposes, four serving decisions at Stage 3 and one serving the building in use. Statutory approval, because building control approval has to be secured before construction starts. Accessibility analysis, because the primary care suite has to meet the access standard the appointing party has adopted. Cost estimation, because the cost plan is refreshed at the end of Stage 3 to release the next stage. Spatial coordination, because the federated model has to be clear of clashes before Stage 4. And maintenance planning, because the estates team will maintain the air handling unit after handover, which traces to an asset information requirement for the maintenance trigger event. All five are disclosed. The first four are active at Stage 3, and the fifth at Stage 6, which is the bridge to the second prerequisite.
Clause five point three, on the information delivery milestone, adds one sentence that closes a door the grades left open. At one milestone, different objects can carry different amounts of each kind of information. A grade set one level per stage for everything, whereas the framework expects the wall, the door and the air handling unit at Stage 3 each to carry a different level. Two examples in the clause pull in opposite directions. Accessibility analysis usually needs the same level at every milestone, because a clear opening width means the same thing at Stage 3 as at Stage 6, so its level can be predefined once and reused. Energy analysis wants massing and orientation early and fabric values and plant data late, so its level is set milestone by milestone. Clause six point one allows a predefined level to sit in a regulation, a standard, a plan of work or a client's standing requirements, and allows the milestone to be an agreed date where no stage fits. For a client, every purpose that a predefined level can serve is a specification it never has to write again.
Clause five point four, on actors, separates those who will use the information from those who will produce it, and the level names neither. Then comes the note that surprises people. Early in a project, nobody need be named as the producer. A client can ask for a given level for an object by an agreed date and leave the supply chain to decide who delivers it. That separation is what lets a level of information need be written into exchange information requirements before a lead appointed party has been appointed. The notes allow four combinations. One level can serve several users, as the fire door's position and rating serve both the fire engineer and the approving authority. Several producers can supply several levels for one purpose, as the architect's wall and the services engineer's air handling unit do for coordination. The producer can be left unnamed, as when the client asks for the clearance zone around the air handling unit without naming the discipline that models it. And responsibility can be split, as in the standard's example of a wall penetrated by a duct, where the services engineer sizes the duct and the opening so that the structural and architectural teams can complete the wall. A specification that hard-codes one actor per level can express none of these.
The fourth prerequisite, the object within a breakdown structure, is the one most often left out, because a model already has objects in it and so the object seems to arrive free. It does not. Clause five point five says a level cannot be written until the objects have been identified and the way the project has been broken into them has been made clear. Clause three point eight defines a breakdown structure as the decomposition of a defined scope into progressive levels, so the question is which objects, at which level of the decomposition, in which structure. A wall type, a single wall and the render on that wall are three different objects. A level can be set against construction results, such as spaces and elements, or against construction information, such as models and documents. The breakdown may follow classification, systems engineering or the project's federation strategy, and in the UK the classification system is Uniclass 2015.
Follow the three objects through three purposes. For cost estimation the breakdown is elemental, so the wall is a type measured by area, and the door and the air handling unit are types that are counted. For spatial coordination it is spatial, so the wall is located by grid line and level, the door by room on the escape route, and the air handling unit by plant room with its clearance zone. For maintenance planning it is a system breakdown, and the wall drops out altogether unless its render is a maintained finish, while the door becomes an asset in the fire safety system and the air handling unit an asset in the ventilation system, with its maintained components beneath it. The authoring model's own decomposition, perhaps one wall per storey, is none of these. It suits the modeller, not the receiver. And whatever a purpose does not need is recorded as left out, or somebody adds it back by habit.
The second step ends there. Four prerequisites, purpose first, each one decided and recorded beside the level and never inside it.
The third step moves to the level itself, at clause six, and it begins with the rule that changes how you read everything after it. Clause six point one describes the level through three categories, geometrical information, alphanumerical information and documentation, and a specification can be met by any combination of them, one alone or all three. It is not a number, so there is no single value to write against an object. It is not a scale, so nothing goes up. And it is not a grade, so nothing implies that more is better. Then the rule. Where an aspect is not relevant to the purpose, it can be recorded as not applicable. The standard's example is building permission during briefing, where geometry and alphanumerical information are both not applicable, because the authority wants documents and nothing else. Read the aspects with that rule in mind and they are a menu. Read them without it and they become a checklist, and a checklist asks for everything.
Geometrical information is information expressed through the shape, size and location of an object, and clause six point two gives it five aspects. They are independent, and the same object can need different settings of each for different purposes, so there is no such thing as more geometry. Detail asks how closely the shape approximates the real object, from simplified to detailed. Dimensionality asks whether it is represented as a point, a line, a surface or a body. Location asks where it is and against what, absolute against a reference such as a grid, or relative to another object. Appearance runs from symbolic, such as a pipe coloured to show water temperature, to realistic. And parametric behaviour asks whether the shape can still be driven by other information once delivered, fully, partially, or not at all.
Each aspect is set by asking which purpose is served. The standard's door runs from a hole in the wall for early structural analysis, to a simple box for asset management, to the leaf with threshold and casing for clash detection, because frames and thresholds are what collide, to the leaf with handle and glazing, which only visualisation wants. A pipe can be a line for quantity take-off inside a model that is fully three-dimensional, so dimensionality belongs to the requirement, not the model. A specification that says the model shall be three-dimensional has set the dimensionality of nothing. It has described the authoring software. For coordination, the standard says, the appearance of a pipe can be not applicable, because nothing about how a pipe looks helps anyone find a clash. And parametric behaviour, which the grades had no place for, depends on what the receiver will do next. A receiver who will keep editing the object with its own tools wants the shape to stay driven by its parameters. A receiver who needs a fixed record, as an estates team at handover usually does, is safer with plain explicit geometry and behaviour not requested.
Now follow the five aspects as they move independently on the fire door at Stage 3. For the fire strategy, detail is not applicable because a plan symbol will do, dimensionality is two, location is absolute on the escape route, appearance is not applicable and parametric behaviour is not requested. For the accessibility analysis, detail rises to the leaf, the threshold and the handle, dimensionality rises to three, and location becomes absolute to the grid. For spatial coordination, detail is the leaf and the frame, in three dimensions, at an absolute location. Across the three purposes, detail changed three times, dimensionality once and the location reference once, while appearance and parametric behaviour never moved. A grade could not have written any one of those specifications. One confusion is worth setting aside here. Accuracy, tolerance, reliability and status are not aspects of geometry. Clause six point one places them in metadata, set by the author and amended through approval and authorisation, so a tolerance written into the location aspect mixes up the requirement with the record of how well it was met.
Alphanumerical information, at clause six point three, has two aspects, and the distinction between them is finding and reading. Identification positions the object in its breakdown, through a name, a type, a classification code, a reference or a number. Information content is the list of required properties, which may be grouped to keep it manageable. A classification code is a finding property, so it belongs under identification, even where a project guide lists it beside material, performance or commercial data. A property can also filter, as when an estimator pricing the structure keeps only the objects whose load bearing property is set to true. The definitions of properties do not live in the specification. Clause six point three point one says alphanumerical information should be represented by, or linked to, a data template under ISO 23387, whose 2025 edition is current, with properties defined in a data dictionary under ISO 23386. A property called condition, with no definition and nothing to say what it is measured in, is a hope. Fire resistance rating, defined in minutes with a permitted set of values, is something a checker can test and a supplier can deliver. The episode Classification and Structured Data takes templates and dictionaries further.
At Stage 6, for maintenance planning, the balance shifts. The external wall is not in the maintenance breakdown, so its information content is not applicable, and that row is written rather than left blank. The fire door is identified by asset reference, classification and room, and carries what an inspector needs to keep it certified, its fire resistance rating and inspection interval among them. The air handling unit is identified by asset reference, classification, plant room and serial number, because four different systems will need to find it. Its content is whatever the maintainer needs to service it and to claim against its maker, from the manufacturer, model and duty to the filter type, the service interval and the date its warranty expires. One milestone later, for a different purpose, the properties are almost everything and the geometry has nearly gone.
Documentation, at clause six point four, is specified by naming documents, never by grading them. Each item is required or it is not, and a printed drawing or a printed schedule is itself a document. The fire door needs, for statutory approval at Stage 3, the fire strategy drawing on which it appears and the door schedule, and at Stage 6 its certificate and installation record. The air handling unit needs nothing at Stage 3, because its manufacturer has not been chosen, and at Stage 6 its operation and maintenance manual, commissioning record, warranty and filter schedule. Not one of those entries says developed or complete, because those words are grades.
Two rules hold the categories together. Clause six point five says each can be derived from another, so properties can be measured off geometry, drawings cut from it, geometry generated from a property such as a road's nominal width, and schedules pulled from properties. You can ask for one category and let the receiver derive another, provided you say which is the source. And clause six point one requires a clear hierarchy between information containers when their content overlaps or contradicts, so that one governs. For the wall's thickness, the model governs and the property is derived. For the door's rating, the property governs and the schedule is derived. For the duty of the air handling unit, the manufacturer's datasheet governs once it exists.
So the level itself comes to three categories and eight aspects, five for geometry, two for alphanumerical information and one set of documents, each set on its own against a purpose, any of them not applicable, with a stated hierarchy for when they disagree.
The fourth step writes the specification down, and then deals with two documents a specifier is often handed, a legacy schedule and a requirement that asks for too much. Annex B of ISO 7817-1 is informative, which makes it guidance rather than requirement. It writes one specification two ways. In both, the prerequisites come first, with the actor split into information receiver and information provider and the object split into the object and its breakdown structure, and the level follows in its three categories and eight aspects. The annex calls its tabular format indicative and open to modification, and it calls neither method correct.
The first method is tabular, one row per object for one purpose at one milestone, with six prerequisite fields, five geometrical fields, then identification, information content and documentation. Every row carries its own context, so it can be lifted and reused. Narrow fields force a decision on each aspect, so a blank shows up as a gap. And the whole thing sorts and filters, which is what a machine wants. The second method is the clause-based structure, a nested list that reads as a request. To enable a stated purpose at a stated milestone, a named provider gives a named receiver the following about a named object, and then the three categories follow with their aspects beneath. It reads well in an appointment and can be followed by someone who has never met the framework, but it does not scale. Ten objects at three purposes is thirty structures, and nobody reads thirty. So use the tabular form when many objects share a purpose and a milestone, or when a machine will check the result, and the clause-based form when one object needs a specification that stands alone, in prose, for a reader who needs the reasoning.
The fire door for statutory approval at Stage 3 shows both. As a row, it reads statutory approval, Stage 3, the architect providing, the approving authority receiving, the door reference, an elemental breakdown. Then detail not applicable, two dimensions, absolute location on the escape route, appearance not applicable, parametric behaviour not requested. Identification by door reference, classification and strategy drawing reference. Content of fire resistance rating, self-closing and position on the escape route. Documents, the strategy drawing and the door schedule. As a clause-based structure, the same content opens with a sentence. To enable statutory approval at Stage 3, the architect provides the approving authority with the following about the door. The row fits a schedule of forty doors. The structure fits a letter to the authority explaining what it will receive.
Now the two inherited documents. A legacy schedule is moved across by mapping, and mapping is a transition aid, not an equivalence. A project's conversion list may read a grade of three hundred as defined geometry, developed properties and developed documents, but no standard sets those correspondences, and every one is silent about purpose. Read the grade as three questions, about geometry, properties and documents. Ask the four prerequisite questions, and record whatever the appointment does not answer as unknown. Set each aspect, or record it as not applicable. Then write the residue, meaning everything the grade implied that the purpose does not need, and every decision the framework requires that the grade never made. At the health centre, an inherited line reading external walls, LOD three hundred, at Stage 3, leaves four items. The first is the purpose, which had to be inferred as spatial coordination, and an inferred purpose is a risk somebody should sign off. The second is over-specification, a layer build-up and an outline specification that the grade implied and coordination does not need. The third and fourth are the receiver and the breakdown, which were never named. The residue is the product, and a mapping that leaves nothing over has carried the grade's silences across as if they were decisions.
An over-specified requirement is critiqued from its purpose. Write the purpose at the top, and if the requirement did not state one, record the inference as your first finding. Then take each line and ask whether the purpose needs it. There are three answers. Yes. No. Or, needed by another purpose at the same milestone. Only the second is over-specification. The third is the combining rule of clause six point one, under which the aspects for every object at a milestone are combined so that every purpose at that milestone is met. Not applicable for the fire strategy is not the same as not applicable at Stage 3, because the accessibility review still needs the door in three dimensions. So you strike what no purpose needs, keep what this purpose needs, and defend what another purpose needs, naming that purpose beside it. Then re-express what remains in one of the two forms, so that the critique ends in a specification the provider can build to. Skip the defence, and over-specification turns into under-specification.
That resolves the fourth step. A specification is written in the form that suits its reader, and an inherited one is improved by naming what was never decided and defending what another purpose needs.
The fifth step is checking, because a specification that cannot be checked is a wish. Clause seven of ISO 7817-1 is the clause aligned with ISO 19650-4, and its two key words come from ISO 9000, the quality management vocabulary. Verification, at clause three point six, is objective evidence that what was specified has been delivered. Validation, at clause three point seven, is objective evidence that what was delivered will serve its intended use. The first asks whether it is present. The second asks whether it can be used for the purpose. Objective evidence rules out taking the provider's word for it.
Clause seven's own examples sit on a fire door. Verification checks that the fire resistance property is present on every object that requires it. Validation checks that its value is one the purpose can use, a time-based value or whatever the national rules require. A machine can run both, provided the permitted values are defined, which is where the data dictionary returns. A door whose property is present but reads to be confirmed passes verification and fails validation. A door whose correct rating sits in a free-text note fails both, because the checker cannot find it. And verification can cover the presence of objects, geometry, properties and documentation, so a checker that only counts properties has checked one category of three.
Checks run in two directions. The first checks the specifier. It asks whether the prerequisites were set, whether every aspect was set or marked not applicable, and whether the level reached the exchange information requirements and the delivery plan. The second checks the provider, once a deliverable arrives, against the specified level, the exchange information requirements and their acceptance criteria. That second direction is governed by ISO 19650-4, and clause seven points to its clause seven point six for the completeness of verification criteria. The episode Information Exchange in ISO 19650 Part 4 takes acceptance from there. A level that quietly failed the first check gives the second nothing precise to test against, and most disputes at acceptance start there.
Clause seven also asks for the level to be written so that a person and a checking tool can each read it, because a tool checks faster and makes fewer mistakes, and so that two readers cannot take one requirement two ways. Together those two sentences are the case against the grade. At the health centre, the specifications built in this episode support six checks a machine could run. For geometry, every object in the elemental breakdown has an absolute location against the grid, and no two objects in the coordination set occupy the same volume. For alphanumerical information, every fire door carries fire resistance rating, and every value is a permitted value in minutes. For documentation, a door schedule is present in the Stage 3 delivery, and it lists every door reference in the model with nothing unmatched either way. In each pair the first is a presence test and the second a usability test that depends on the purpose. None of it made the specification longer. It made it precise.
A short look forward, labelled as such. Two further parts of the ISO 7817 series are in development and not published. When this episode was prepared, Part 2, guidance for application, was a draft technical specification that had entered its approval ballot in September 2026, and Part 3, a data model and schema, was a draft international standard whose enquiry vote closed in May 2026. Neither is in force, both may change, and neither belongs in an appointment. The sensible response is to specify to Part 1, to write for the machine anyway, with named properties and explicit not applicable entries, and to watch the ISO register rather than conference remarks.
The fifth step resolves on one condition. A level of information need is finished when it can be verified and validated, and that is possible only if it was written precisely enough for a rule to find what it names.
Back, then, to all doors, LOD three hundred. The question was why a single number such as LOD three hundred specifies nothing, and what replaces it. The number specifies nothing because it bundles geometry, properties and authorised use into one setting, names no purpose, is read differently by every firm, and gives a checking tool nothing to test. What replaces it is a framework. Each specification sits beside four recorded prerequisites, purpose, milestone, actor and object within a breakdown, and specifies none of them. It is expressed across geometrical information, alphanumerical information and documentation, aspect by aspect, with not applicable wherever the purpose does not need something and a stated hierarchy for when the categories disagree. It is written in tabular or clause-based form, and it is precise enough to be verified and validated. At the health centre, all doors, LOD three hundred, becomes three short and different specifications for one fire door, each complete and each checkable. And the architect in the hook had a third option all along, neither modelling everything nor waiting for a definition nobody had written, which was to ask for the purposes and specify against them.
Three habits follow, and they reach well beyond doors. Write the purpose first, in the receiver's words, and treat a requirement with no purpose as unfinished. Use not applicable as a recorded decision, and before you strike any line, ask whether another purpose at the same milestone needs it. And test every specification by stating what a machine would check, because if you cannot name one verification and one validation, the receiver will not be able to either.
For reading, start with ISO 7817-1 itself, clause five for the prerequisites, clause six for the categories and the not applicable rule, clause seven for checking, and Annex B for the two forms. Then read clause three point three point sixteen of ISO 19650-1, clauses five point one point four and five point two point one of ISO 19650-2, and ISO 23387 and ISO 23386 for data templates and dictionaries. The episodes closest to this one are Information Management in ISO 19650 Part 1: Concepts and Principles, The Delivery Phase in ISO 19650 Part 2, Information Exchange in ISO 19650 Part 4, and Classification and Structured Data. The next episode, Security-Minded Information Management in ISO 19650 Part 5, is about how an organisation decides whether a project needs a security-minded approach, and what follows if it does.
Somewhere in a schedule you work with or study, a line still carries a single grade, and on Reimagining AEC I, Dr Sepehr Abrishami, would ask you to find it, in practice or in research, and write beside it the purpose nobody stated. That one sentence is where a specification another party can check begins.