The work that leaves no trace

C LEVEL TWIN

A large part of real work leaves no trace in the systems. It happens in calls, meetings, e-mails and in the use of tools. The share grows with seniority. This work uses real time, but it appears neither in job descriptions nor in transactional systems. The C LEVEL TWIN brings it into the model.

Observation starts at C-level, where this share is highest. It then extends to every level of the organization, and it covers formal and informal activities.

From signals to potential tasks

Illustrative example. Only data inside the authorized perimeter enter. Nothing enters the model without a human decision.

The cycle

Setup. The known tasks are loaded from job descriptions, interviews and documents. This is the declared AS IS.
Continuous observation. Within the perimeter authorized for each person, AI analyzes e-mail, calendar, calls, chat and the use of tools. The results go to an observation area. Nothing enters the model at this stage.
Proposal. The AI submits the tasks it found, with their evidence and their confidence.
Human decision. HR, with the consultant, reviews each proposal and decides whether to accept it. No observation is ever written into the model automatically.
Refined AS IS. Accepted tasks enter the model. Then observation continues. The cycle does not end.

Perimeter and legal basis

Observation is not a switch. For each person the model records which sources are active, at which level of detail, on which legal basis, under which authorization and for how long.

Metadata by default: with whom, when, for how long. This is enough to identify tasks.
Content only with a separate authorization, for knowledge and decision reasons.
The filter works at collection: data outside the perimeter never enter the system.
The legal reference varies by country. Without it, observation cannot start.
A person can revoke. Collection stops, and observations not yet accepted are deleted or anonymized.

In depth

The twin describes the present

A task discovered by observation is not a change. It is work that already existed and was not visible. For this reason it enters the AS IS, not a TO-BE. In a TO-BE it would inflate the benefit of a transformation by exactly the work that was only hidden before.

Where an accepted task goes

If several people with the same JOB show the same task, the task belongs to the JOB: the job description was incomplete. It is added to the JOB and applies to everyone who holds it. If only one person shows it, it is an individual variance and stays with that person.

How mature the twin is

Every task records its origin: declared or observed. The model computes the share of observed tasks by JOB, unit and function. A finance function observed at 80% and an operations function observed at 10% give different confidence on loads, costs and automatability. The model shows the difference.

Revocation and the JOB

When a person revokes, tasks already added to the JOB remain: they now describe the position, not the person. Tasks kept as individual variances follow the revocation.

Who decides

The AI proposes. HR, with the consultant, decides. The model records who proposed, who decided, on which evidence and from which date.

Where it applies

The C LEVEL TWIN observes real people in real companies. It does not apply to training environments, where the data are standard by design.

What it gives

Real workloads of managers, measured instead of declared.
Visibility of work the organization carries without governing it.
Job descriptions that match reality.
A base for agentization: a task can be handed to an agent only once it is known.