Back to site
AI organisation

Your organisation

Units, positions, people and roles, taken from the system that already holds them and resolved at the moment a process needs an answer instead of written into it

Where it comes from

Nothing exotic here. The structure is not something to re-enter: it comes from wherever it already lives.

Today: an export. Units, positions, employees and who reports to whom, out of your HR or HCM system as a CSV. Load the same structure again and it converges, so keeping it current is a repeated step and not a clean-up.

Soon: a direct connection. Connectors to the usual HCM systems - BambooHR and its neighbours - are close, and they will keep the structure in step without anybody exporting anything. What the CSV loads is the same structure the connector will keep updated, so today's path is not a dead end.

Groups are the normal case, not the exception: a holding with four companies, a shared services function, people who belong to one entity and work in another, a contractor who appears in the structure without being on the payroll.

You describe that here, which matters because everything downstream resolves against it. An approval that must stay inside one legal entity, a report that must span all of them, a person whose manager is in a different company: those are ordinary configurations, not exceptions somebody codes around.

Roles resolve at the moment they are needed

This is the property that keeps everything else correct.

A route does not name Ivan. It says "the head of the requester's department", and who that is comes from the structure at the moment the question is asked. Somebody is promoted, a team moves under a different director, a department is split - and the processes stay correct without anybody editing them.

A role can be resolved several ways, and a real company needs all of them:

  • From the structure - the head of a unit, the owner of a position, the director of a legal entity.
  • From a field on the record - whoever was named as responsible manager becomes the assignee.
  • From a group - anyone in finance may pick this up, so a queue belongs to a team instead of a person who might be away.
  • As a watcher - people who need to see something go past without being asked to act on it.

Absence, substitution and delegation

Somebody being away is a normal state of an organisation, not an exception to discover at the worst moment.

Substitution puts a stand-in into the chain that resolves roles, so the work reaches them without the process being edited and without anybody re-assigning by hand. Delegation moves authority deliberately and for a period - a director handing approvals to a deputy for a fortnight - and it is recorded as what it is, so the audit trail says who acted and on whose authority.

What it changes downstream

Because there is one structure, the same answer is used everywhere:

  • Processes route to real people, and keep routing correctly. See Processes.
  • Forms hold real employees, positions and legal entities as field values, not typed text. See Forms and records.
  • Access is decided by who somebody is and where they sit, not by a list maintained per application. See Roles and access.
  • Reports group by department, region or entity because those are real dimensions, not strings.
  • AI employees resolve against the same structure - the manager they answer to, the people they escalate to, the scope they inherit. See AI employees.

Next

AI employees - the other half of the organisation.