BCF Issue Tracking for MEP Coordination
Screenshots in emails get lost. BCF keeps each coordination issue tied to the exact spot in the model.
The BIM Collaboration Format (BCF) is an open standard from buildingSMART International for communicating issues in BIM models. It lets teams share issues, such as clashes or questions, with model viewpoints, comments and status, across different software. It's widely used in MEP coordination.
What BCF contains
A BCF issue, often called a topic, typically includes:
- A title and description
- A viewpoint, showing the camera position and relevant elements
- A snapshot image
- References to model elements, using their IFC identifiers
- Comments
- Status, priority and assignee
Why BCF is useful
- Works across different BIM tools
- Links issues to exact locations in the model
- Keeps issue history in one place
- Separates issue communication from the model itself
BCF files and BCF API
BCF can be exchanged as files, using the .bcfzip format, or through the BCF API, which connects software to shared issue servers. Many coordination platforms support one or both.
Typical workflow
- A coordinator finds an issue in a model review or clash test
- They create a BCF topic with a viewpoint and description
- The topic is assigned to the responsible discipline
- The discipline opens the topic in their authoring tool, which takes them to the location
- They resolve the issue and update the topic
- The coordinator checks and closes it
Writing good issues
- Use a clear, specific title
- Describe the problem and the required action
- Include the location, such as level and grid
- Assign one responsible party
- Set a priority and due date
Grouping issues
Group related clashes into one issue when they share a cause. This avoids long lists of near-identical topics.
Closing issues
Close issues only when the fix is confirmed in an updated model. Closed issues stay in the history for reference.
Software support
Many tools, including Revit through plug-ins, Navisworks through add-ins and various BIM coordination platforms, support BCF. Check that your team's tools can read and write the BCF version you're using.
Combine with meetings
BCF issues work well alongside regular coordination meetings. Meetings focus on difficult issues, while BCF tracks everything.
Keep it tidy
Archive or close resolved issues regularly, and review overdue items. A tidy issue list is easier to manage.
- 01What BCF contains
- 02Why BCF is useful
- 03BCF files and BCF API
- 04Typical workflow
- 05Writing good issues
- 06Grouping issues
Agree statuses
BCF gives MEP coordination a shared, software-neutral way to track issues from discovery to resolution.
If your team needs extra production capacity for work like this, take a look at our Architectural production services, or tell us about your project.
Related articles

Clash Detection With Navisworks: A Practical Guide
Setting up useful clash tests and reports in Navisworks.
Read more →
IFC and OpenBIM: Sharing Models Between Platforms
How IFC lets different BIM tools share information, and how to export it well.
Read more →
Running Effective MEP Coordination Meetings
Agendas, model reviews and actions that keep coordination moving.
Read more →