Engineer working on a Revit IFC export

IFC Export Settings in Revit: A Setup Guide for UK Teams

In Revit, the IFC export settings sit behind File > Export > IFC > Modify setup. For most UK coordination work, start from IFC2x3 Coordination View 2.0, check the category mapping, set the coordinate base deliberately, then save the setup so every export uses the same rules. The rest of this guide explains each choice and where exports usually go wrong. At Xponexus Engineering we embed civil and structural engineers in UK consultancies who handle calculations, drawings and BIM coordination, so a model that arrives in the wrong state costs our clients’ time as well as ours.

Xponexusengineering
xponexusengineering.com
Keep BIM Coordination on Track
Xponexus embeds civil and structural engineers into UK consultancy workflows, supporting BIM coordination alongside calculations and drawings.

Visit

TL;DR

  • Open the export from File > Export > IFC, then use Modify setup to change the settings. Changes made to In-Session Setup are not kept between sessions, so save a named setup.
  • IFC2x3 Coordination View 2.0 is the default certified choice and is generally supported by other systems. Use it for structural steel export too.
  • Check the category mapping, the coordinate base and the linked-file option before every issue, because these three cause most surprises.
  • Open the finished IFC in a viewer and inspect the file header before it goes to anyone.
  • Keep one saved setup per project or per company standard, so exports are repeatable.

Table of Contents

Where the IFC export settings are in Revit

The route is short. Click File > Export > IFC, choose the target folder and file name, select the setup you want and click Export. Revit writes the IFC file and an export log to the target folder, as described in Autodesk’s guide to exporting a model to IFC. Keep the log with the file. When a recipient says an element is missing, the log is the first place to look.

The settings themselves are in the setup dialog. Select a setup in the Export IFC window and click Modify setup. You can either edit the In-Session Setup or duplicate a built-in setup and change the copy. According to Autodesk’s IFC export setup documentation, In-Session changes are not saved between sessions. That detail catches many teams out: someone tunes the settings on Monday, reopens Revit on Tuesday and exports with the defaults.

The habit that fixes this is simple. Duplicate a built-in setup, give it a name that carries the project number and the purpose (for example, the issue stage), and export only from that named setup.

Where the IFC export settings are in Revit

What the dialog contains

The same Autodesk page lists the dialog’s areas: General, Exchange Requirement, Additional Content, Property Sets, Level of Detail and Advanced. Treat them as a sequence. General and Exchange Requirement decide what kind of file you are producing. Additional Content and Property Sets decide how much data rides along. Level of Detail and Advanced decide how the geometry and the edge cases behave.

Choosing the IFC version and model view

This is the setting that matters most, because it fixes what the receiving software can do with the file.

Per Autodesk’s documentation, IFC2x3 Coordination View 2.0 is the default certified version and is generally supported by other systems. IFC4 Reference View is intended as an unmodified reference model. IFC4 Design Transfer View may create ifcAdvancedBReps, which can reduce file size and export time.

Setup What it is for When a UK team would pick it
IFC2x3 Coordination View 2.0 Broadest compatibility with other systems Default for coordination with consultants whose software you do not control
IFC4 Reference View An unmodified reference model Issuing a model that others view but do not edit
IFC4 Design Transfer View Geometry that may export as ifcAdvancedBReps, reducing size and export time Heavy models where file size is the problem and the recipient supports IFC4
IFC2x3 COBie 2.4 Output described by Autodesk as required by the UK government’s 2016 Level 2 BIM mandate Asset-information handovers where COBie is specified

Structural steel

For structural steel export, Autodesk specifically instructs users to select the IFC2x3 Coordination View 2.0 setup. If your steel model goes to a fabricator or detailer, do not experiment with other views without agreeing it first.

IFC and the UK mandate

A common misunderstanding is that UK Level 2 BIM required IFC. Autodesk’s own Level 2 material states that IFC was commonly used for data sharing but was not specifically required; COBie was the government’s chosen information-exchange schema. In practice this means the schema is decided by your employer’s information requirements, not by habit. Read the exchange requirements in the appointment documents before you pick a setup.

If you want the wider picture of why clients now ask for open handovers, our piece on why UK clients want IFC 4.3 open BIM handovers covers it, and our IFC exchange checks article sets out three checks tied to ISO 16739.

Mapping Revit categories to IFC classes

Mapping decides which IFC class each Revit category becomes. It is the most common source of “why is my beam a proxy?” questions.

The current setup dialog includes Category Mapping. You select a mapping template or open the mapping manager to change the IFC classes and predefined types assigned to Revit categories (Autodesk).

Older workflows use a mapping file. Autodesk’s mapping-file procedure creates a file called exportlayers-ifc-IAI.txt from the Standard mapping, lets you load an existing file, and allows each category or subcategory to be given an IFC class and type, or set to Not Exported.

Two behaviours are worth knowing:

  • If a mapping row is left blank, Revit tries to work out the appropriate IFC category itself. If it finds no match for geometry, the object is exported as a proxy object, according to the same Autodesk page. A proxy is geometry without meaning: it shows up in a viewer but cannot be filtered, quantified or checked as a column or a slab.
  • Setting a category to Not Exported removes it from the file entirely. Use it for things such as annotation-heavy or helper categories that the recipient never needs.

After changing the mapping, open the result in a viewer and filter by IFC class. A quick count of beams, columns and slabs against the Revit schedule will show a mismatch in seconds.

Parameters and property sets

Property sets carry the data that makes an IFC useful: fire rating, material, load-bearing status, your own classification codes. Autodesk’s parameter-mapping guidance requires a UTF-8 text file in which property-set definitions or supported IFC property names are mapped to Revit parameters. You then select it through the Export user defined property set or Export parameter mapping table controls.

The UTF-8 requirement is easy to miss. A file saved in another encoding can fail silently, and the exported properties simply do not appear. Save as UTF-8 and test with one element before exporting the whole model.

Keep the property list lean. One IFC checking guide on common export mistakes is often cited for the tip that too many properties is easy to spot against the employer’s information requirements; the practical rule is to export what the exchange requirement asks for and no more. Larger files open slower and bury the properties people need.

Coordinates and positioning

A model can be perfect and still land in the wrong place. The Coordinate Base setting decides where the IFC origin comes from. Autodesk’s IFC exporter help lists four choices: Shared Coordinates, Survey Point, Project Base Point and Internal Origin. The projected-coordinate reference can carry a name, description, EPSG code, geodetic datum, eastings and northings. Autodesk recommends Project Base Point or Survey Point for a properly georeferenced export.

For UK work the question is whether the receiving team federates at national grid coordinates or at a local origin. A UK-focused IFC workflow guide from Graphisoft’s UKI team advises using shared-coordinate information when IFC models must be federated at global coordinates for contractor coordination in tools such as Solibri or Navisworks.

Agree this before the first issue. The simplest approach is a line in the BIM execution plan stating the coordinate base and the origin every discipline uses. Where fit-out designers receive structural IFC for test fits against BCO office space standards, the same rule applies: a shared origin and clear exchange requirements keep the layouts and the structure aligned.

Linked files and visible elements

Two checkboxes quietly change what leaves the building.

Linked files. Autodesk offers three behaviours: omit the links, export each linked file as a separate IFC with correct positioning relative to the host, or include the links in the same IFCProject or IFCSite (Autodesk). Separate files with correct positioning keep each discipline’s model clean and easier to update. Putting everything in one IFCProject gives a single file but makes later revisions harder to isolate.

Export only elements visible in view. When ticked, this exports the visible elements of the current view, including cropped elements and underlays, but temporarily hidden or isolated elements are not exported. Clearing it exports the whole model. Teams often leave this ticked from an earlier job and then wonder why half a floor is missing. Decide which you want, and export from a view that matches it.

Checking the export before it leaves your office

An export that has not been opened is an assumption. Autodesk’s IFC Manual recommends checking the exported IFC in a viewer, confirming element classifications and inspecting the file header for the IFC schema and model view definition. The header is a text line near the top of the file. If it does not name the schema and view you chose, you exported with the wrong setup.

A short check list:

  1. Open the file in an IFC viewer, not in Revit.
  2. Read the header for schema and model view.
  3. Filter by class and compare counts against your schedules.
  4. Check a few elements for their property sets.
  5. Confirm the model sits where it should against another discipline’s file.
  6. Read the export log for warnings.

Opening IFC back in Revit

If you receive an IFC rather than send one, link it rather than open it. The Revit IFC Manual says linking or referencing IFC is the preferred and most reliable method, because an updated IFC can be reloaded without being converted into editable native families. Opening converts the geometry into native families, but IFC remains primarily a coordination format with limited conversion and editing capabilities. The same manual identifies IFC2x3 Coordination View 2.0 as recommended for best results when opening IFC in Revit.

A repeatable export routine

Here is the sequence we would put in a project’s BIM execution plan, with where an embedded engineer from Xponexus fits.

  1. Read the exchange requirement. Find the schema, model view and coordinate base the appointment asks for. Where a consultancy is short of hands, our embedded engineers handle calculations, drawings and BIM coordination, so this reading is done by someone who works to UK standards and Eurocodes.
  2. Duplicate a built-in setup and name it. Never export from In-Session Setup alone.
  3. Set version and view. IFC2x3 Coordination View 2.0 unless the requirement says otherwise.
  4. Check category mapping. Look for blank rows and anything that would become a proxy.
  5. Attach property sets. Use the UTF-8 mapping file and export only the properties required.
  6. Set coordinates and links. Choose the coordinate base and the linked-file behaviour on purpose.
  7. Export from a controlled view. Match the visible-elements option to the view.
  8. Verify in a viewer. Header, classes, properties, position, log.
  9. Record the setup. Store the setup name and a note of its choices alongside the issue.

The routine is not long, but it is the discipline that matters. Each skipped step shows up later as a clash report that cannot be trusted. For wider coordination context, see our BIM coordination workflow mapped to ISO 19650.

Common mistakes and what they look like

Symptom Likely cause Fix
Elements appear as generic proxies Blank or unmapped category rows Assign an IFC class and type in the mapping
Half a floor missing Export only elements visible in view is ticked, or elements are temporarily hidden Clear the option or export from a suitable view
Custom properties absent Mapping file not UTF-8, or not selected in the setup Resave as UTF-8 and select it in the property set controls
Model sits far from other disciplines Different coordinate base Agree one base and re-export
Settings revert next session Only In-Session Setup was edited Save a named setup

Extra capacity for the export and coordination work

If your team is stretched, a clean IFC issue is exactly the kind of task that slips. Xponexus Engineering provides remote civil and structural engineers who work inside your workflow on calculations, drawings and BIM coordination, with outputs aligned to UK standards and Eurocodes. Kick-off is within 48 hours, NDA and non-compete protection are in place, and you keep direct control of your client relationship. See our CAD and BIM services or remote engineering support.

Xponexusengineering

If you want to see how embedded support runs in practice, the calculation and drawing coordination project shows the workflow.

Our perspective

Most failed IFC handovers we hear about are not software faults. They are decisions nobody owned: which view, which origin, who checks the file. The settings are documented and stable. What changes from job to job is whether someone has the time to apply them properly.

That is why we embed engineers in a client’s own workflow rather than working beside it. The person producing the calculations and drawings also sits close to the model, so the export reflects what the engineering actually needs, built to UK standards and Eurocodes. You keep the client relationship; we add the capacity without a permanent hire.

Our advice is to treat the saved setup as a project document. Name it, record it, and review it at each issue. It takes minutes, and it removes an entire category of argument at coordination meetings.

Mohammed

FAQ

How do I export an IFC file from Revit?

Go to File > Export > IFC, choose the folder and file name, select a setup and click Export. Revit writes the IFC and an export log to the target folder. To change settings first, use Modify setup and save the result as a named setup.

Which IFC version should I choose?

IFC2x3 Coordination View 2.0 is the default certified choice and is generally supported by other systems, and Autodesk specifies it for structural steel export. Choose IFC4 views only when the recipient’s requirements ask for them. Follow the exchange requirement in your appointment documents.

Why are my IFC settings not saved?

Changes made to In-Session Setup are not kept between Revit sessions. Duplicate a built-in setup, modify the copy and export from it. The named setup is then available every time.

How do I get custom parameters into the IFC?

Create a UTF-8 text file that maps property-set definitions or supported IFC property names to Revit parameters. Then select it with the Export user defined property set or Export parameter mapping table controls in the setup. Test on a few elements before the full export.

Sources


Comments

Leave a Reply

HTML Snippets Powered By : XYZScripts.com