8 real coordination scenarios. Not "spot the clash" — spot the correct priority action.
You'll be graded against how a working BIM Coordinator would actually triage these, in Navisworks/Revizto-style workflows.
I've hired, mentored, and occasionally had to let go of BIM staff for over a decade now, and the one question every student asks before "which software should I learn" is really about the paycheck.
Every batch I've trained has at least a few site engineers and design office civil engineers who feel stuck — good technical grounding, but no clear path upward.
I get asked this in nearly every counselling call, usually phrased more bluntly: "Will this actually get me a job, or am I wasting money?" Fair question.
We rewrote our plan descriptions recently because, frankly, the old copy was confusing even to us.
This question comes up so often that I think most students don't actually want a comparison — they want permission to skip one of them.
Half the students I meet have heard the name "BIM 360" without really understanding what it does versus Revit.
Worksets are one of those Revit features everyone touches but few people set up deliberately — and a badly structured arrangement is one of the most common causes of project chaos.
Short, honest answer: basic proficiency in 6-8 weeks, job-ready competence in 3-4 months, real fluency in 1-2 years of actual project work.
Students often picture BIM as "modeling, then clash detection, then done" — the reality spans several distinct stages, each with different goals and different LOD requirements.
Students often picture this job as quietly modeling alone with headphones on all day. The reality involves a lot more coordination than that.
Scroll horizontally to flip through ←→