An IFC viewer in Microsoft Teams lets project participants inspect the model in the same place they discuss delivery work. A useful review still needs an agreed model revision, clear questions, and a record of the resulting actions.
Set up the shared review
Add the Flinker IFC Viewer to the relevant team or channel, then configure its file links. The Teams setup guide covers the tab, file connection, and permissions. Tenant policies may require administrator approval before the application can access files.
Confirm that participants can open the configured IFC and BCF files. Access to a chat does not automatically provide access to every linked project file. Test with an external reviewer if the meeting includes one.
Before the session, record the model names, revisions, and review scope. Ask the responsible author to confirm that these are the intended files for coordination.
Inspect the information behind a question
During the review, navigate to the relevant area and select the elements under discussion. Inspect the properties actually present in the export, including their property-set names and units.
A missing property may reflect the authoring model, export settings, or the agreed exchange scope. Avoid treating the displayed information as a complete description of the design. Where an engineering decision depends on a value, refer the question to the responsible discipline.
Keep the conversation specific: identify the element, state the observed issue, and describe the decision or clarification required. This gives participants who were not in the meeting enough context to act.
Record actions with model context
Use a shared model reference for a focused discussion. Where your process uses BCF, the viewer supports loading topics and sharing a topic link with its saved viewpoint. The BCF sharing guide explains that workflow.
Assign an owner and due date in the project’s agreed issue register. A Teams message can provide useful discussion history, but sending a link does not by itself create a managed issue or an approval record.
Maintain context when models change
Record which revision was reviewed. A link to a project file may later open updated content, and an element reference depends on the target object remaining identifiable. Verify unresolved issues after a new model is issued and retain the earlier evidence where the project requires it.
Separate viewing from the specialist checks required by the project. Use the designated authoring, validation, or clash-detection process for those checks, then bring the relevant findings into the review.
Review deployment and data handling
Flinker’s architecture documentation distinguishes model processing from technical metadata used for authentication, licensing, support, and analytics. Review the product-specific data flow and any optional services with the administrator.
For a focused handoff after the meeting, see sharing model context with Teams deep links.