> ## Documentation Index
> Fetch the complete documentation index at: https://docs.realtimelca.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Prepare Export

> Where to configure the required IFC settings in your authoring tool.

This page shows where to configure, per authoring tool, the settings described in [IFC Requirements and Preferences](/user-guide/integrations/ifc-file-upload/requirements) — schema version, quantity sets, the type identifier, and classification.

<Tabs>
  <Tab title="Revit">
    * Export using the **IFC4.3** setup (or a custom export setup based on it) rather than IFC4 or IFC2x3.
    * On the **Property Sets** tab of the export options, enable **Export base quantities**.
    * If you're using a regular property instead of `IfcClassification` for classification (see [Classification](/user-guide/integrations/ifc-file-upload/requirements#classification)), make sure that custom property is also included in the export — Revit does not export custom/shared parameters by default, so it must be explicitly added to the property sets in the export setup. To do so, add custom properties in the property mapping (see example below).

    <Frame caption="Adding a custom property in the Revit IFC export property mapping">
      <img src="https://mintcdn.com/real-timelca/pRME66UjptmqMW0C/images/user-guide/RevitCustomProperty.png?fit=max&auto=format&n=pRME66UjptmqMW0C&q=85&s=6e7d1c1d55ebe4135419ad0567b2da79" alt="Revit IFC export setup with a custom property added to the property mapping so it's included in the export." width="940" height="554" data-path="images/user-guide/RevitCustomProperty.png" />
    </Frame>
  </Tab>

  <Tab title="ArchiCAD">
    * Use an **IFC4x3** translator/preset rather than IFC2x3.
    * In the IFC Translator settings, make sure quantity export is enabled so base quantities are written to the file.
    * For multi-layered elements (e.g. composite walls or slabs), prefer exporting as a single element rather than splitting each layer into its own `IfcBuildingElementPart`. Individual parts are still supported, but a single composite element groups and maps more cleanly.
    * If you work with the classification manager, make sure the classification system name matches the classification parameter — see the [naming requirement](/user-guide/integrations/ifc-file-upload/requirements#classification). You can also export the classification code as a regular property. In this case, make sure to export it to a property with the exact naming as defined in  [Speckle model's Parameter Mapping](/user-guide/project/project-settings#classification).
  </Tab>
</Tabs>