How to Set Up Job Architecture

Steps

Open Job Architecture

Go to Settings → Setup → Foundation. Job Architecture sits below Departments, in the Job Families & Roles, Bands, Skills Taxonomy, and Responsibilities sections. If you don’t see them, ask your Customer Success contact to turn Job Architecture on for your account.

Define job families, roles, and bands

Group roles into job families, and give your organization’s own title to each fixed seniority band, from individual contributor through leadership.

Define departments, job families, and bands

Populate skills clusters and responsibilities

Build your skills taxonomy in clusters and set the responsibilities that distinguish one band from the next. Regulated organizations can also enable an overlay for compliance-specific dimensions.

Link roles back to the architecture

When you create a job, the Job Architecture panel on Add Job Details lets you pick the job family, role, band, and regulated overlay, so the job resolves against this structure.

Publish and version

Publish the architecture. Editing a published architecture creates a new version rather than overwriting the old one.

Best practices

Job Architecture is the shared structure every role uses, and it is what keeps scores comparable between teams.

Do this	Avoid this
Set up departments, job families and bands once, for the whole organization.	A per-role structure. Roles stop being comparable the moment each one invents its own bands.
Give the fixed seniority bands your own labels, so they match how your org talks about level.	Leaving default band names nobody internally uses.
Link each role back to the architecture.	Roles built outside the structure. Their scores cannot be compared to anything else.
Publish a version when you change it.	Changing it without publishing. Nobody can tell which version a past score used.

​Steps

​Best practices

Steps

Best practices