Loading Help…
How a role comparison identifies changes to linked profiles, index values and flow stages.
The comparison examines two roles, A and B. It identifies profiles added or removed, changed classifications and index values, and changes to the flow stages. Interpret these differences in the context of the work each role describes.
A profile is added when it appears on B only, removed when it appears on A only, and shared when it appears on both. These labels describe membership; they do not prescribe adding or removing competencies.
A shared profile may have a different classification in each role (e.g. supporting in A and primary in B). Read the before-and-after classifications alongside the role descriptions.
The Individual Responsibility Index (IRI) ranges from Not Required (0) to Required (4). For a shared profile, the difference is B minus A. The role-comparison total adds signed differences, so decreases offset increases. It describes importance to role performance, not a quantity of information.
The Individual Competency Index (ICI) ranges from No Competence (0) to Expert (4). For a shared profile, the difference is B minus A. The role-comparison total adds signed differences. These profile values do not establish an individual’s demonstrated competence.
Each role carries an ordered list of flow stages. The diff classifies each stage as added (on B not A), removed (on A not B), or reordered (on both with a different ordinal position).
Reorders are typically the most informative category for transformation framing — they show how the flow's centre of gravity moves. A future-ready BIM Manager that surfaces "information validation" before "model coordination" is a different kind of role than one that surfaces them the other way around.
The summary reports shared, added and removed profiles, classification changes, index differences and flow-stage changes. Read the detailed changes as well as the totals: an aggregate can hide differences that offset one another.
The calculation compares the selected role data. Its arithmetic does not establish that the roles describe equivalent work across jurisdictions. Check scope, sources and status before interpreting the result.
The RoleDiff package schema is at stability tier beta. The shape may evolve in minor versions until 1.0; breaking shape changes will bump the schemaVersion in the package envelope and the change will be called out in the change log.
