[Discipline/firm type — e.g., a structural subcontractor team on a large infrastructure project]. [An X-person modeling team] under deadline pressure to produce construction-stage drawings.
Client kept anonymous.
Drawings weren't printing the way the model was built. [Specific symptom — elements displaying incorrectly, inconsistent line weights, wrong layers on output] — the kind of issue that looks cosmetic until it starts costing real production time.
The team had already spent [X hours/days] trying to isolate the cause internally. It touched every drawing sheet they produced, which meant the problem wasn't going away — it was compounding with every new sheet.
A BIM Global consultant — George White — was brought in on a single support call. Rather than treating it as a one-off glitch, he traced the issue back to its root: a display-rules misconfiguration — a setting most modelers never get properly trained on, because it doesn't cause visible problems until it does.
This is the pattern behind most of the "mystery" issues teams call about: not a software bug, but a modeling-hygiene gap that nobody flagged because nobody was trained to look for it.
The consultant diagnosed and corrected the display-rules setup live on the call — walking the team through why it broke, not just how to fix it, so the same mistake wouldn't resurface on the next project.
Client kept anonymous.
Most support calls like this aren't really about the printing error, or whatever symptom surfaced first. They're about a gap in how the team was originally trained — the kind of gap that keeps resurfacing in new forms until someone actually closes it.
That's the difference between a support call that patches a symptom and one that fixes the habit behind it.