Check job descriptions against the levelling framework

The decision tree

6 typed decisions, each with an action for every answer

At fixed moments in a run, the engine puts one narrow question to a decision model. The decision model never writes text: it answers yes or no with a probability, picks from listed options, or gives a score, about a small slice of the material. The engine then does exactly what this tree says, which is what makes the run auditable. The thresholds are the template's design values, not measured results.

1. 1

   Planner, while planning

   Split or keep serialYes or no, with a probability

   While planning

   Do the job descriptions in this function fall into job families that can be checked against the framework without reading each other?

   Sees only: The function's list of job titles and families, with description lengths

   Why: Splits only where families are truly independent, so coordination cost is not paid for nothing.

   00.40 and 0.601

   • Yes: 0.60 or higher→thenSplit the work
   • Unsure: 0.40 up to 0.60→thenKeep serial
   • No: below 0.40→thenKeep serial
2. 2

   Split or keep serialYes or no, with a probability

   While planning

   Is this job description long enough, and the level's criteria separate enough, that each criterion should be checked as its own task?

   Sees only: One job description's outline and one level's list of criteria

   Why: Short descriptions are cheaper read once than split into many tiny tasks.

   00.40 and 0.601

   • Yes: 0.60 or higher→thenSplit the work
   • Unsure: 0.40 up to 0.60→thenKeep serial
   • No: below 0.40→thenKeep serial
3. 3

   Scope checkYes or no, with a probability

   Before work starts on a unit

   Is this document a description of a role, containing no information about a named person, their performance or their pay?

   Sees only: The first page of one supplied document

   Why: Keeps personal data out of the run; the job is about role texts only.

   00.60 and 0.851

   • Yes: 0.85 or higher→thenAccept
   • Unsure: 0.60 up to 0.85→thenSkip this unit
   • No: below 0.60→thenSkip this unit
4. 4

   After workers, the judge checks

   Evidence checkYes or no, with a probability

   After a worker answers

   Does the quoted sentence from the job description describe scope, autonomy or accountability at the standard this level criterion sets out in its own words?

   Sees only: One level criterion and the quoted job description sentence

   Why: Prevents a level mapping from resting on a sentence that only sounds senior.

   00.50 and 0.851

   • Yes: 0.85 or higher→thenAccept
   • Unsure: 0.50 up to 0.85→thenEscalate to a strong model
   • No: below 0.50→thenReject and retry
5. 5

   Reconciler, while merging

   Conflict checkYes or no, with a probability

   While reconciling

   Do these two job descriptions with the same title describe materially different scope against the same level criteria?

   Sees only: Two criterion-by-criterion summaries for one job title, with quotes

   Why: Surfaces title inconsistency, the finding the reward lead most needs, without deciding which is right.

   00.30 and 0.701

   • Yes: 0.70 or higher→thenMark unresolved
   • Unsure: 0.30 up to 0.70→thenEscalate to a strong model
   • No: below 0.30→thenAccept
6. 6

   Accountable person, before anything is settled

   Person decidesYes or no, with a probability

   Before anything is reported as settled

   Does this finding suggest that a role's assigned level, and so the pay range of the people in it, might need to change?

   Sees only: One job description's findings and its assigned level

   Why: Level changes affect pay, so the reward lead and function head decide, never the run.

   Accountable: The reward lead and function heads decide any level change. The run reviews role documents, never individuals.

   00.10 and 0.301

   • Yes: 0.30 or higher→thenAsk a person
   • Unsure: 0.10 up to 0.30→thenAsk a person
   • No: below 0.10→thenAccept