Junior, senior: how to define BIM skill levels that make sense

Two years of seniority do not guarantee two years of real progression in Revit — you can easily repeat the same task for two years without ever touching a project template or a parametric family. Yet “junior” and “senior” are still often defined by seniority alone. A grid of observable criteria completely changes the picture.

The trap of “X years of experience = level Y”

Seniority measures time spent, not what was learned during that time. A draughtsperson who has modelled housing for five years may be completely at a loss faced with a complex public-access building; a young employee coming from a demanding firm may already master skills that a senior has never had the opportunity to practise. Setting levels on seniority alone amounts to guessing, not assessing.

A grid per skill, not a single overall level

An employee is almost never “junior across the board” or “senior across the board”: they may master architectural modelling while still building up their IFC interoperability skills, or the other way round. Breaking the assessment down by skill rather than giving a single overall level makes it possible to see precisely where each person stands — and therefore which training would really be useful to them, rather than a generic “intermediate level” course.

What an observable criterion looks like

The difference between a useful grid and a vague one comes down to a single principle: a level must describe a behaviour that can be seen or verified, not an impression. A few examples of observable criteria, from the simplest to the most advanced:

• Creates worksets according to a consistent logic (by trade, by level, by party), instead of simply knowing what a workset is
• Sets up a family with constraints and types, instead of only inserting existing families
• Detects and documents clashes in Navisworks, instead of simply opening the software
• Exports an IFC by configuring the options for the recipient, instead of using the default settings without understanding them

With this type of criterion, two different people assessing the same employee reach the same conclusion — which is almost never the case with a simple impression like “he's rather good” or “he's still junior”.

A level must describe a behaviour that can be seen or verified, not an impression.

What this changes in the annual review

A per-skill grid also transforms the annual review: instead of a general discussion about the year gone by, it provides a concrete basis — “you have gone from 1 to 2 in cross-discipline coordination, here is what is missing to reach 3”. The employee knows exactly what to work on, and the manager can track that progression from one year to the next rather than starting from a fresh impression at each review.