Every coordination team eventually has the report-format argument. Someone wants the clash list in Excel because they live in pivot tables. The project manager wants a PDF for the record. The facade consultant's team runs BIMcollab and wants "something we can actually import."
They're all right — for their own job. Excel, PDF, and BCF aren't competing formats; they're answers to three different questions. The mistake isn't picking the wrong one, it's using one format for all three jobs.
Here's the honest comparison.
Excel — when the data still needs work
Excel is the format for clash data that isn't finished being data. Filtering to one discipline pair, pivoting counts by level, building a punch list for one consultant, checking rule coverage across a matrix — that's spreadsheet work, and pretending otherwise just means someone rebuilds the spreadsheet manually from whatever you sent instead.
Strengths: universally openable, endlessly manipulable, ideal for consultants who track their own workload and for coordinators doing analysis the dashboard doesn't cover.
Weaknesses: it's a snapshot with no connection back to the model. The moment it's emailed it starts drifting from reality, and nothing a recipient types into it flows back anywhere. No geometry, no viewpoints — a row can tell you what clashed but can't show you.
Use it for: working data. Never for the official record, and never as a one-way street to a team that has a BIM tool of its own.
PDF — when the record matters more than the data
A PDF clash report is frozen on purpose. That's its entire value: it's the artifact you attach to meeting minutes, issue to the client, or file for the audit trail. Nobody can re-sort it, mis-filter it, or accidentally paste over row 40.
Strengths: formal, portable, readable by absolutely everyone including the people who will never install any AEC software. With snapshots included, a non-technical stakeholder can see each clash rather than read coordinates.
Weaknesses: dead weight for anyone who needs to act on the data. A consultant working through 60 assigned clashes from a PDF is retyping your report into their own tracker — pure waste.
Use it for: meeting records, client-facing issues, and formal distribution. In ClashWise, coordination session minutes come out this way automatically: decisions, action items, and every clash change recorded during the session, as a PDF nobody had to write.
BCF — when another tool takes over
BCF (BIM Collaboration Format) is the one of the three that isn't really a report — it's a handoff. A BCF 2.1 export packages each clash as a coordination topic: the issue details, its comments, a snapshot image, and a 3D viewpoint that a compatible tool can restore, camera position and all.
That last part is the killer feature. The recipient doesn't scroll a list; they open the topic in BIMcollab, Solibri, or their CDE's issue board, and their own tool takes them to the clash in their model.
Strengths: machine-readable, tool-neutral, no lock-in — the open standard means your coordination results outlive any single platform. Comments and status travel with the issue.
Weaknesses: useless to anyone without BCF-capable software, and overkill for a status summary. It answers "work on these" — not "how are we doing."
Use it for: handing coordinated clashes to teams running their own BIM issue tools. ClashWise exports BCF 2.1 directly from a published clash set — all clashes, the current filter, or a hand-picked selection, each with a live count before you commit.
Side by side
| Excel | BCF 2.1 | ||
|---|---|---|---|
| Job | Work the data | Freeze the record | Hand off the issues |
| Audience | Coordinators, consultants who track in sheets | PMs, clients, the file | Teams on BIMcollab / Solibri / a CDE |
| Geometry | None | Snapshots | Snapshot + restorable 3D viewpoint |
| Flows back? | No | No | Yes, via the recipient's tool |
| Fails when… | used as the official record | someone must act on it | recipient has no BCF tool |
The formats that didn't make the list
A few report requests come up often enough to address:
CSV. Functionally Excel's plainer sibling — same snapshot problem, none of the formatting. It earns its place when the destination is a script, a Power BI model, or another system's importer rather than a human. ClashWise exports it with the same scope options as Excel, so treat the two as one category: data out.
The native Navisworks HTML report. It ships with Clash Detective, and it shows: viewpoint images wrapped in early-2000s markup, no filtering after the fact, no connection to anything. Fine for a one-off archive; painful as a weekly deliverable.
Screenshots in PowerPoint. The most expensive format in construction. Every slide is minutes of manual work that's stale before the meeting starts. If the audience needs pictures and narrative, that's what the PDF report with snapshots is for — generated, not assembled.
Pick per audience, export from one source
The trap is exporting once and forcing every audience through the same format. The fix is cheap: keep one live source of truth and export each format from it on demand.
That's how the ClashWise pipeline works — the published clash set is the record, and Excel, PDF, and BCF are all views of it. Same clashes, same numbers (#N identities that stay stable across re-runs), no manual reconciliation between what the PDF said and what the spreadsheet says. Report generation shares the same export pipeline, so the formats can't drift from each other either.
Start a free 14-day trial and export your own clash test all three ways — deciding which format goes to whom takes about a minute once producing them stops being work.
BCF export and the report pipeline are part of Clash Management — see plans and pricing for what's in each tier. All of it is included in the trial.
Try ClashWise free for 14 days — no credit card, cancel in-app.