ISO 19650 for Revit Teams: A Practical AEC Guide
- Steve Fagan
- Jul 27
- 13 min read
ISO 19650 is an information-management framework that tells your Revit team how to produce, share, and hand over model data, not just what to model. For most AEC firms, that translates to three immediate actions: stand up a Common Data Environment (CDE), define status rules for every Revit file, and lock in a naming convention backed by shared parameters. Do those three things first and the rest of the standard falls into place around them.
Your first moves:
Set up a CDE (Autodesk Construction Cloud, BIM 360, or equivalent) and map its folder states to WIP, Shared, Published, and Archived.
Write a one-page status code table for your Revit central files and link it to your BIM Execution Plan (BEP).
Draft a naming string for central files, families, and sheets, then test it against Revit schedules before the project kicks off.
Getting this right reduces rework, clarifies what each discipline owes at each milestone, and gives clients and contractors a single authoritative source of information instead of a pile of emailed PDFs.
Table of Contents
What does ISO 19650 actually mean for Revit workflows?
ISO 19650 is an international standard for organizing and managing information about built assets using BIM, covering the full asset lifecycle from concept through operation. It does not prescribe which software to use. What it does prescribe is a structured process: who requests information, who produces it, how it is verified, and where it lives at each stage.
For Revit authors, the shift is conceptual before it is technical. The standard moves project delivery from drawing-centric to information-centric. A Revit model is no longer just a source of sheets; it is an information container that carries geometry, metadata, classification, and status simultaneously. That reframe changes how you set up templates, how you name files, and how you publish.
Five concepts are non-negotiable to understand before touching a project template:
Information requirements (EIR/AIR): what the client needs and when.
Information containers: any named, versioned file or dataset, including Revit models.
Verification and acceptance: a formal check before information moves to the next state.
Appointed roles: who is accountable for producing and approving information.
Common Data Environment (CDE): the agreed, controlled repository for all project information.
COBie (Construction Operations Building Information Exchange) enters the picture as the data-exchange reference for operational handover, typically exported from Revit at project completion. U.S. firms have been slower to adopt ISO 19650 than their UK counterparts partly because of its origins in BS 1192, but adoption is accelerating as cross-border and federal projects increasingly require a common information language.
How is ISO 19650 structured across its six parts?
The standard currently spans six parts. Not all are equally relevant to every project, but knowing what each covers prevents you from applying the wrong section to a problem.
Part | Title (short) | Core focus | Revit implication |
ISO 19650-1 | Concepts and principles | Defines information management framework, roles, CDE, and lifecycle | Set up information requirements; treat Revit models as information containers |
ISO 19650-2 | Delivery phase | Production, verification, and exchange of information during design and construction | Central model policy, BEP, publishing cadence, IFC/COBie export rules |
ISO 19650-3 | Operational phase | Asset information management post-handover | COBie output, asset metadata in shared parameters, AIR compliance |
ISO 19650-4 | Information exchange | Guidance on exchange requirements and formats | IFC export settings, COBie mapping, format specifications in EIR |
ISO 19650-5 | Security-minded approach | Protecting sensitive asset information | Access controls in CDE, permission tiers for sensitive models |
ISO 19650-6 | Health and safety | Information for health and safety during design and construction | Safety-relevant data in model parameters and handover packages |
For most U.S. design and construction teams, Parts 1 and 2 are the daily working documents. Part 3 becomes critical when a client requires an operational BIM or COBie handover. Part 5 matters on government or infrastructure projects with security classifications.
COBie and IFC export requirements typically surface in Part 2 workflows, specifically at the Published state when information is formally issued to the client or contractor. In Revit terms, that means your shared parameters must be mapped to COBie fields before the first issue date, not retrofitted at practical completion.
On versioning: ISO 19650-2 expects revision codes to be embedded in the file name and tracked through the CDE. For Revit central and cloud-workshared models, that means your naming convention must carry a revision field, and every formal issue must create a new named version in the CDE rather than overwriting the previous file.
How do the four CDE states map to your Revit files?
A CDE is not a shared drive with a password. ISO 19650 defines it as the agreed source of information with distinct states that enforce verification before information moves forward. The four states are WIP, Shared, Published, and Archived, and each maps directly to what happens inside and around your Revit environment.
WIP (Work in Progress)
Local Revit files or cloud-workshared models being actively edited.
Access restricted to the authoring team; no other discipline should be coordinating against WIP files.
Naming typically carries a WIP status code (e.g., S0 or WIP) in the file name or CDE metadata.
Shared
The central model or a published NWC/IFC has been synced and made available for cross-discipline coordination.
Other teams can reference and clash-check against Shared files, but they cannot edit them.
In Autodesk Construction Cloud, this maps to a controlled folder with read-only permissions for non-authoring disciplines.
Published
Formally issued PDFs, COBie spreadsheets, IFC files, or native Revit models delivered to the client or contractor.
Must pass a verification check (QA review, clash report, naming audit) before promotion.
A new CDE version is created; the previous Published version moves to Archived.
Archived
Superseded versions retained for audit and legal purposes.
In practice: a locked folder in your CDE that no one edits, ever.
A practical folder structure might look like this:
/Project-12345/
/WIP/
/Architecture/
/Structure/
/MEP/
/Shared/
/Federated/
/Published/
/Issue-001/
/Issue-002/
/Archived/
/Issue-001-superseded/
Pro Tip: Use CDE platform permissions to enforce state transitions automatically. In Autodesk Construction Cloud, configure folder-level permissions so only the BIM manager role can move files from Shared to Published. This removes the human error of someone accidentally issuing an unreviewed model.
What must your EIR, BEP, and AIR specify for Revit work?
These three documents are the contractual backbone of an ISO 19650 project. Missing or vague content in any of them creates ambiguity that costs time at handover.
Employer’s Information Requirements (EIR)
The EIR is the client’s wish list, made specific. For Revit deliverables it must state:
Required file formats at each milestone (native RVT, IFC 2x3 or IFC 4, COBie, PDF).
Level of Development (LOD) or Level of Information Need (LOIN) per element type and phase.
Naming convention the appointed party must follow.
Metadata fields required in Revit shared parameters (asset tag, manufacturer, warranty period, etc.).
Whether a federated model is required and who federates it.
BIM Execution Plan (BEP)
The BEP is the appointed party’s response. It should define:
Roles: who is the Information Manager, who are the discipline leads, who runs QA.
Verification steps before each publish: clash tolerance, naming audit, parameter completeness check.
Publishing cadence tied to project milestones.
Model federation rules: which software federates, which file format, and who holds the master.
Revision and status code table for all Revit deliverables.
Asset Information Requirements (AIR)
The AIR translates operational needs into Revit metadata. If the client runs a CAFM or CMMS system, the AIR should list every data field that system needs, mapped to a Revit shared parameter. COBie is the most common exchange format for this data. Your Revit shared parameter file must be configured before modeling starts so that asset data accumulates naturally rather than being entered manually at handover.
A quick checklist for negotiating or writing these documents:
[ ] File formats specified per milestone
[ ] LOD/LOIN defined per element and phase
[ ] Naming convention referenced or appended
[ ] Shared parameter list attached or linked
[ ] COBie/IFC export requirements stated
[ ] Verification criteria and responsible party named
[ ] Revision code table included
What do ISO-aligned naming conventions look like inside Revit?
The ISO 19650 naming structure follows a field-based pattern: Project, Originator, Volume/System, Level/Location, Type, Role, Number, Suitability, Revision. Adapting that to Revit requires mapping each field to a Revit parameter or property.
Example central file name:
12345-ARC-Z1-L1-M3-A-00001-S2-P01.rvt
Where: 12345 = project number, ARC = originator, Z1 = zone/volume, L1 = level, M3 = model type, A = architectural role, 00001 = sequence, S2 = shared status, P01 = revision.
Example sheet name (in Revit Sheet Properties):
12345-ARC-Z1-L1-DR-A-10001
The sheet number field in Revit carries fields 1 through 7; suitability and revision live in custom shared parameters that feed the title block.
Naming rules to lock down:
No spaces, no special characters except hyphens between fields (Revit rejects /, \, ?, *, ", <, >, | in file names and some parameter values).
Family file names follow the same project-originator-type convention so they are traceable in the CDE.
Shared parameter names use underscores, not spaces, for schedule compatibility (e.g., ISO_Originator, ISO_Zone, ISO_Level).
Metadata and shared parameters:
Store your ISO naming parameters in a shared parameter file attached to the project template. Key parameters to create:
ISO_Originator (text, project information)
ISO_Zone (text, sheet properties)
ISO_Level (text, sheet properties)
ISO_Type (text, sheet properties)
ISO_Role (text, project information)
ISO_Suitability (text, sheet properties)
COBie_Type, COBie_Component, COBie_Space (for asset handover)
Pro Tip: Before rolling out your naming convention firm-wide, build a test Revit schedule that pulls every ISO parameter. If a parameter name breaks the schedule filter or sorts incorrectly, fix it in the shared parameter file before the project starts. Retrofitting parameter names mid-project breaks data exchange and wastes hours.
Who does what on an ISO 19650 Revit project?
ISO 19650 defines roles at a process level. Mapping them to the people on a typical Revit project clarifies accountability and prevents the common failure mode where everyone assumes someone else is managing model states.
The primary roles:
Appointing party: The client or employer. Sets the EIR and AIR, approves deliverables at each milestone, and owns the CDE at handover.
Lead appointed party: The main contractor or lead consultant (often the architect on design-led projects). Responsible for the BEP, federated model, and coordinating task teams.
Task teams: Individual discipline consultants (structural, MEP, civil) who author their Revit models and deliver to the lead appointed party.
Information Manager / BIM Manager: Enforces naming, manages CDE permissions, runs verification checks, and controls the publish workflow. May sit within the lead appointed party’s firm or be an independent appointment.
A practical coordination workflow:
Model authoring: Task teams work in WIP. Daily syncs to the central model or cloud-workshared file.
Federated model checks: BIM manager federates discipline models (Navisworks or Autodesk Construction Cloud) and runs clash detection on a defined cadence (weekly or per milestone).
Issue management: Clashes and information gaps logged in the CDE or a connected issue-tracking tool. Assigned to responsible discipline with a resolution date.
Sign-off and publish: BIM manager runs a naming and parameter audit, confirms clash tolerance is met, and promotes files from Shared to Published in the CDE.
Handover coordination checklist:
[ ] All shared parameters populated and verified against AIR
[ ] COBie export generated and validated
[ ] IFC exported and checked against EIR format requirements
[ ] All sheets issued with correct suitability and revision codes
[ ] CDE archive created for superseded versions
[ ] Client sign-off recorded in CDE audit trail
Revit setup checklist: templates, worksharing, and publishing
Getting your Revit environment configured correctly at project start is far cheaper than fixing it mid-delivery. The sequence below follows the order that prevents downstream problems.
Step-by-step initial configuration
Project template: Start from a firm template that already contains your ISO shared parameter file, title block with ISO fields, and a pre-built sheet list schedule. Lock down view templates and browser organization so they cannot be changed without BIM manager approval.
Enable worksharing: On the first day of the project, enable worksharing in Revit (Collaborate tab > Worksets) and save the central model to the CDE’s WIP folder with the correct ISO file name. Never save a central model to a local drive.
Workset structure: Create worksets by discipline and by building system (e.g., Architecture-Shell, Architecture-Interiors, Structure, MEP-Mechanical). Assign ownership at project kickoff.
Shared parameter file: Attach the firm’s shared parameter file to the project template. Confirm all ISO and COBie parameters are present before any modeling begins.
Naming audit schedule: Build a Revit schedule that lists every sheet with its ISO parameter fields. Run it at each milestone to catch naming errors before publishing.
Linked model coordination: Set up linked models using the correct coordinate system (shared coordinates, not project north). Use Copy/Monitor for grids and levels across disciplines.
Automated exports: Configure export settings for IFC (use the IFC exporter add-in for Revit, set to IFC 4 or IFC 2x3 per EIR) and COBie (use the COBie extension or a BIM manager script). Save export configurations in the project template.
Publishing script or workflow: Define the publish sequence: sync central model, run naming schedule check, export IFC/COBie, upload to CDE Published folder, log version in CDE.
Pro Tip: Use Autodesk Construction Cloud’s automated transmittal features to timestamp every publish and generate a distribution record automatically. This creates an audit trail that satisfies ISO 19650-2 verification requirements without manual logging.
Setup item | Revit location / action | ISO 19650 requirement addressed |
Shared parameter file | Manage > Shared Parameters | Metadata, COBie, naming fields |
Central model in CDE WIP | Collaborate > Save to Cloud / Save As | CDE WIP state |
Worksharing enabled | Collaborate > Worksets | Multi-author coordination |
IFC export config | File > Export > IFC (saved config) | ISO 19650-4 exchange format |
Naming audit schedule | View > Schedules | Naming convention compliance |
Linked model coordinates | Manage > Coordinates > Shared | Cross-discipline coordination |
How long does ISO 19650 adoption realistically take?
Firms that try to adopt ISO 19650 firm-wide in one sprint almost always stall. A phased approach works because it lets you learn on a contained project before committing every team.
Phase 1: Pilot project over a few weeks to a couple of months
Pick one active project with a cooperative client. Configure the CDE, write a BEP, apply the naming convention, and run the full WIP-to-Published workflow at least once. Document every friction point.
Phase 2: Scale to projects over several months
Apply lessons from the pilot to two or three concurrent projects. Refine the firm template, shared parameter file, and publishing scripts based on real feedback. Train discipline leads on CDE permissions and status codes.
Phase 3: Firm-wide adoption usually takes close to a year
Update all project templates, onboard all project teams, and make ISO-aligned workflows the default. At this point, the BIM manager’s role shifts from setup to enforcement and continuous improvement.
Major cost areas to plan for:
CDE subscription (Autodesk Construction Cloud, or equivalent platform).
Template and standards development: typically several dozens of hours of BIM manager time for a mid-size firm.
Training: discipline leads and project architects need at least a half-day session on CDE workflows and naming rules.
BEP and EIR development: 8–16 hours per project for the first few projects, dropping as templates mature.
Low-cost steps you can start this week:
Update your Revit project template with ISO shared parameters.
Write a one-page naming convention and circulate it for comment.
Run a single project through the WIP-to-Shared workflow in your existing cloud platform.
Decision points for leadership:
Are clients or contractors already requiring ISO 19650 compliance on bids?
Are coordination errors and rework costs high enough to justify a structured information process?
Does the firm have cross-border or federal project ambitions where a recognized BIM standard is expected?
Key Takeaways
ISO 19650 compliance in Revit depends on getting the CDE, naming, roles, templates, and exports right before modeling begins, not after.
Point | Details |
CDE is the foundation | Set up WIP, Shared, Published, and Archived states in your CDE before the first model file is created. |
Naming must be tested | Validate your ISO naming convention against Revit schedules and prohibited characters before project kickoff. |
Documents drive deliverables | EIR, BEP, and AIR must explicitly list file formats, LOD, COBie/IFC requirements, and verification criteria. |
Roles need named individuals | Assign the Information Manager role to a specific person; the function cannot be shared informally across the team. |
S15studio accelerates adoption | S15studio’s worksharing course and training programs give Revit teams the practical skills to implement ISO-aligned CDE and publishing workflows from day one. |
Why ISO 19650 changes Revit practice more than most teams expect
Most Revit teams assume ISO 19650 is a documentation exercise: fill in a BEP template, rename a few folders, and carry on modeling. That assumption is where adoption fails.
The real shift is cultural. ISO 19650 asks your team to treat the Revit model as the authoritative source of information, which means non-Revit stakeholders need to be able to review and approve model information without opening Revit. That is a harder change than any naming convention. Clients and contractors who have spent careers reviewing PDFs do not naturally trust a model viewer, and getting them there requires deliberate effort: cloud viewer access, training, and a BIM manager willing to push back when someone asks for “just a PDF” instead of engaging with the model.
The other underestimated friction point is the verification step before publishing. Teams that skip it, or treat it as a formality, end up with Published models that contain naming errors, missing parameters, or unresolved clashes. Once a model is in the Published state, correcting it requires a new revision and a new issue, which costs time and erodes client confidence. Building the verification habit early, even on the pilot project, is what separates firms that make ISO 19650 work from firms that abandon it after one difficult handover.
The payoff, when the process is followed, is real: fewer coordination surprises at construction, cleaner COBie handovers, and a CDE audit trail that protects everyone when disputes arise.
S15studio can help you put this into practice
If ISO 19650 has made one thing clear, it is that Revit proficiency and process knowledge have to develop together. Knowing how to model is not enough; your team needs to know how worksharing, CDE publishing, and shared parameters actually behave under project conditions.
S15studio’s Revit worksharing course covers exactly the skills this guide describes: central model setup, workset management, cloud collaboration, and the publishing workflows that underpin ISO-aligned delivery. For teams starting from scratch, the Revit introduction course builds the foundation before tackling BIM standards. Every course is built by Autodesk Certified Trainer Steve Fagan and designed around real project scenarios, not abstract theory. Check the course catalog at S15studio and pick the program that matches where your team is right now.
Useful primary sources and references
Source | Why it matters |
ISO 19650-1 (ISO.org) | The primary standard document; revision in progress. Authoritative reference for concepts and principles. |
ISO 19650 for U.S. firms (Revizto) | Practical overview of why U.S. AEC firms are adopting ISO 19650 and how it differs from earlier UK standards. |
Benefiting Revit users from ISO 19650, Part 1 (Autodesk Forums) | Practitioner-level guidance on treating Revit as an information container; covers CDE workflows and naming. |
ISO 19650 for Revit users, Part 2 (Autodesk Forums) | Covers cloud collaboration, stakeholder review, and moving from drawing-centric to information-centric delivery. |
BIM naming convention based on ISO 19650-2 (BIMicon) | Practical naming examples and warnings about Revit-prohibited characters; directly applicable to central files and sheets. |
ISO 19650 drawing naming templates for Revit (BIMLead) | Field-by-field breakdown of the ISO naming structure with Revit parameter mapping and downloadable templates. |
ISO 19650 changes (Rebim) | Commentary on recent and upcoming revisions, including closer alignment of CDE and operational lifecycle workflows. |
Autodesk University article on building BIM standards for Revit; covers templates, object libraries, and workflow integration. |
Recommended
Comments