Section Cuts and Property Inspection: Reviewing a Structural IFC Model in the Browser

Structural models are the ones everyone downstream depends on and the ones fewest people actually open. The architect coordinates against them, the services trades route around them, the QS extracts from them, the site team builds from drawings cut from them — and yet, between issue and consequence, the model itself often goes unreviewed by anyone except its author, because "opening the structural model" sounds like it requires a structural licence.

It doesn't. A structural IFC review — the practical kind that catches coordination problems, data gaps, and geometry surprises before they become site problems — needs a viewer, a method, and about half an hour. Here's the method, runnable end-to-end in the free, browser-based BIM Model Viewer, where the model stays on your device throughout.

One boundary before we start: this is a coordination and completeness review, not an engineering check. Whether the beam is adequately sized is the engineer's professional territory. Whether the beam is in the model, in the right place, at the documented depth, with its data attached — that's reviewable by any competent project professional, and it's where most model problems actually live.

First pass: the tree tells you the structure's story

Load the IFC and, before orbiting anything, open the spatial tree. A structural model's tree should read like the building's structural logic: foundations at the bottom storey, then per level the vertical elements (columns, walls) and horizontal ones (beams, slabs), stairs and cores where they belong.

Walk it top to bottom asking three questions: Is anything missing? (A level with slabs but no beams; a building with no foundations because they live in a separate model nobody mentioned.) Is anything homeless? (Elements assigned to the wrong storey — a Level 3 beam living under Level 2 will corrupt every per-level schedule and quantity extraction downstream.) Is anything unexpected? (Architectural elements inside a structural export usually signal sloppy export scope.)

Five minutes, no engineering judgement required, and you've already screened for the failures that most reliably poison downstream uses of the model.

Structure hides inside architecture and inside itself — you cannot review what you can only orbit. Sections are the structural reviewer's primary instrument, and three cuts do most of the work:

The horizontal cut, walked upward. Place a horizontal section just above a floor level and you're looking at a live framing plan: column grid, beam layout, slab edges, openings. Drag the plane up through the building level by level and watch the structural story — where the grid shifts, where transfer structures appear, where the openings punch through. Compare what you see against the framing drawings; the discrepancies you catch this way (the missing beam, the opening that migrated) are the classic drawing-vs-model divergences.

The vertical cut through the critical bay. Slice through a representative bay and the section shows what plans can't: floor-to-floor heights, beam depths against ceiling zones, foundation levels, and the vertical stack — do the columns actually land on the columns below, and do they land on foundations? Column stacks that drift level to level, and walls that bear on nothing, are exactly the errors vertical sections expose in seconds.

The interface cut. Wherever structure meets something else — the podium-to-tower transition, the tunnel approach, the pit and its surrounds — cut there. Interfaces are where models disagree, because interfaces are where authorship changes hands.

Property inspection: the data is half the deliverable

Structural elements carry the data the whole supply chain runs on, and clicking through a sample is how you audit it. For each main category — columns, beams, slabs, walls, foundations — select a handful of elements and read:

• Identity: does the element's type/name match the drawing mark (C1, B203, F3)? Marks that don't match the schedules break the model-to-drawing thread everyone relies on.
• Material and grade: is concrete grade / steel section data present and plausible? Empty material fields on a structural model are a completeness failure worth flagging early — retrofitting data later costs multiples.
• Dimensions: spot-check a beam depth or wall thickness against the documented value. You're not checking design; you're checking that model and drawings tell one story.
• Load-bearing and structural flags: IFC carries these; elements marked wrong will be filtered wrong by every downstream tool that trusts the flag.

If project-required property sets are simply absent, the diagnosis is usually export settings rather than missing data — our guide to why a consultant's IFC export looks wrong covers the classic failure modes and exactly what to request in the re-export.

Thirty minutes, one structured note

Assembled, the review is: tree walk (5 min) → three families of section cuts (15 min) → property sampling across categories (10 min) — ending in a short note that lists, with element identities and tight screenshots: what's missing or homeless, where model and drawings diverge, and where required data is absent. That note, issued early in a coordination cycle, is worth more than any amount of clash-detection output later, because it catches the problems clash software can't see: the absent, the misplaced, and the undata'd.

No licences, no installs, and the confidential model never left your machine:

Open the BIM Model Viewer → — free, in your browser, sections and properties included.

This workflow supports coordination and completeness review only. Structural adequacy, design verification, and engineering acceptance remain the responsibility of the licensed structural engineer of record.