# Workflows: from a model to fixed issues

Three flows by role, from a model to fixed issues, for an author before handover, a client or coordinator checking a delivery, and a requirement owner publishing a test. Each step links to the article that shows it.

Updated 1 November 2026

Client and author run the same checks. Pick the flow that matches your role. New to IFC, IDS or BCF? Start with [What are BIM and openBIM?](https://ifcchecker.com/help/what-is-openbim/).

## Workflow map

1. Add a model
2. Pick a test
3. Run the check
4. Read the index and results
5. Export BCF or a spreadsheet
6. Fix in the authoring tool
7. Check again

Then back to the start with the fixed model.

## Author before handover

This flow covers stages 1 to 7.

1. Export IFC from the authoring tool, and [add the model on Check](https://ifcchecker.com/help/add-models/).
2. [Pick the client's IDS file, or a predefined test and its stage](https://ifcchecker.com/help/pick-a-test/).
3. [Keep **Model health** ticked](https://ifcchecker.com/help/model-health/), to check the file itself as well.
4. [Run the check and read the index with its untested count](https://ifcchecker.com/help/model-correctness-index/).
5. [See why elements fail: Empty, Wrong or Other](https://ifcchecker.com/help/read-the-results/#empty-wrong-other), and [find the failing values in Extended data](https://ifcchecker.com/help/extended-data/).
6. [Download the BCF issues, or Excel for a list](https://ifcchecker.com/help/export-results/). In [BCF topics](https://ifcchecker.com/help/bcf-topics/) you can close what is not an issue and send only some topics.
7. Fix the model in the authoring tool, export it again and [check it again](https://ifcchecker.com/help/check-a-model/#check-it-again). Optionally [save the results and send the link](https://ifcchecker.com/help/save-and-share/) with the delivery.

## Client or coordinator checking a delivery

This flow covers stages 1 to 5.

1. [Add the delivered model](https://ifcchecker.com/help/add-models/).
2. [Pick your requirements: your IDS file, or the predefined test written into the contract](https://ifcchecker.com/help/pick-a-test/).
3. [Keep **Model health** ticked](https://ifcchecker.com/help/model-health/).
4. Run the check, and [read the index and the untested count, or the reason it is withheld](https://ifcchecker.com/help/model-correctness-index/#withheld).
5. [Look at the untested elements](https://ifcchecker.com/help/untested-elements/#outside-or-missing): outside the requirement, or missing from it? If missing, the IDS needs a rule.
6. [Download BCF to send the issues back, and Excel for your records](https://ifcchecker.com/help/export-results/).
7. [Save the results and share the link](https://ifcchecker.com/help/save-and-share/) with the team.

## Requirement owner publishing a test

This flow covers stage 2.

1. [Open the IDS editor and choose a start](https://ifcchecker.com/help/write-an-ids/#starts).
2. [Tighten the rules in the table](https://ifcchecker.com/help/ids-rules/).
3. [Load a reference model and watch the live counts](https://ifcchecker.com/help/ids-live-counts/).
4. [Clear the IDS checks until **Download IDS** is enabled](https://ifcchecker.com/help/write-an-ids/#download), and keep the `.ids` file.
5. Put the `.ids` file into the EIR, tender or BEP, so authors and clients [check their models against it](https://ifcchecker.com/help/your-own-ids/).

[Workflows and help](https://ifcchecker.com/help/)