The SORA Method
The system behind every coordinated project.
We do not execute services. We apply a method. The difference between coordinating and managing chaos is, in every case, the difference between having a system and not having one.
The problem we solve
Most projects fail because of how they manage information, not how they design.
In high-complexity projects — data centers, hospitals, industrial plants — there is a gap that few organizations name correctly. It is not a lack of drawings. Not a lack of models. It is a lack of a system that governs how information is produced, verified, distributed and preserved throughout the project lifecycle.
That gap generates on-site clashes, costly rework, loss of traceability and digital assets that no one can use after construction. The SORA Method exists to close that gap, project by project.
Information exists in abundance. The problem is that no one can find it, verify it or trust it when it matters most.
Resolving clashes after they reach the site is not coordination. It is damage management. Real coordination happens before the problem exists.
Project information must survive the project. The information model is the beginning of the asset operational life, not the end of work.
Fundamental principles
Three principles that are non-negotiable.
These are not procedural rules. They are philosophical decisions that determine how SORA works on every project, regardless of type or scale.
Governance before geometry.
A 3D model without information governance is an expensive illustration. SORA establishes first who produces what information, under what state, at what moment and at what level of detail. The model is the consequence of that system, not the system itself.
System before tool.
Revit, Navisworks, Autodesk Construction Cloud — tools are means, not methods. The SORA Method defines processes, approval flows and delivery protocols before selecting the technology that will support them. Tools change. The system remains.
Asset before project.
All information produced during the project exists to serve the built asset throughout its operational life. This is not a declaration of principles — it is a design constraint that determines what information we produce, with what properties, and in what delivery format.
The working framework
Four phases. One continuous cycle.
The SORA Method is not a linear process. It is a cycle applied at the start of each project and repeated across every design, coordination and delivery phase. Each iteration produces information of greater maturity.
Definition
AIR · EIR · BEP · TIDP
Before producing a single information element, we define what information is needed, who produces it, under what protocol and at what maturity level. The Asset Information Requirements and BIM Execution Plan are not compliance documents — they are the architecture of the project.
Entregables de esta fase
Relationship with ISO 19650
ISO 19650 is not a certification. It is the architecture of the method.
The SORA Method is built on ISO 19650 requirements, but interprets them operationally, not documentally. Each phase of the framework — Definition, Production, Verification, Delivery — maps directly to the processes defined in ISO 19650-2. The method documents (AIR, EIR, BEP, MIDP, TIDP) are not compliance templates: they are governance instruments that determine how information flows through the project.
Conceptual framework for information management
Asset delivery process during design and construction
Information management during the operational phase of the asset
Security requirements in information management
The SORA ecosystem
The method connects knowledge with the system.
The SORA Method does not operate in isolation. It is the convergence point between the technical knowledge body SORA produces and publishes, and the platform that supports its systematic application.
Knowledge body
SORA Knowledge
Operational framework
The SORA Method
System infrastructure
SORA OS
Want to understand how the SORA Method would apply to your project?
We start with a free technical assessment to map the current state of information management in your project and define how the method can be applied.