The demand profile — three axes

Whoever covers a demand has to match on three questions. Two are qualitative, one is quantitative — and they are answered separately, because they lead to different actions.

1. Activity — what has to be done

What is needed is rarely “someone with skill X” but “someone who does this work”. And that work is already described in the model: as the accountabilities of a role.

A demand therefore usually requires a role (relationship type REQUIRES_ROLE); its accountabilities describe what has to be done. Where no suitable role exists, the activities can be written freely — a demand without a matching role must remain expressible.

Activity is not the optional extra, it is the first question. A demand that only names competences says what someone can do — not what they should do.

2. Skill — what has to be known for it

Via the relationship type REQUIRES a demand requires competences, each with a minimum level. The level sits on the relationship, not on the competence — only that way is the sentence “required is advanced, present is intermediate” expressible at all. More on this: Competences.

The comparison knows four verdicts, and they deliberately stay separate:

Verdict	Meaning	What follows
met	present, at least at the required level	fits
below level	present, but lower	develop
missing	not present at all	hire or train
not comparable	a level is missing	maintain the model

“Not comparable” is not a shortcoming of the person but of the model. Counting it as a gap would flood every tenant working without levels with false positives.

3. Availability — whether there is any time at all

The third axis stands on equal footing with the first two. Without it, a planning tool reliably proposes the best-fitting and most heavily loaded person.

Available is not the same as contractually present: absences and non-working days are deducted from the baseline. Where each figure comes from and how it is maintained is described in Demand & Resource Planning and — once available — on the capacity page.

Who may cover it

A demand states whether a human, an AI agent or both may cover it. Agents are role- and competence-capable in the model just like people, and are judged on the same axes. Restricting a demand to “human only” is the deliberate decision — for anything involving a signature, personnel matters or governance.

No overall score

There is deliberately no aggregated score. A single number would destroy exactly the distinction that makes the proposal useful: someone who fits professionally but has no time is something entirely different from the reverse.

Related

• Demand & Resource Planning — Overview of demand, plan and coverage
• Running operations and initiatives — The two kinds of demand
• Roles — Roles as bundles of activities
• Competences — Competences and their levels