Silhouetted figures in conversation behind fluted glass
Levelwork
CONSTAT

Evidence for how organizations really work.

Role analysis for companies of 20 to 250 people
01The gap

The week everyone assumes.
And the week that happens instead.

Role, as designed
Mon
Tue
Wed
Thu
Fri
081216
Weekly kickoffFocus timeFeature dev
Team syncFeature dev1:1
Team syncFocus timeArchitecture
Team syncFeature devClient meeting
Team syncTest automationWrap-up
The same role, four weeks later
Mon
Tue
Wed
Thu
Fri
081216
Weekly kickoffTicket triageSupport escalationAd-hoc reporting
Team syncOnboarding helpVendor callStatus update
Team syncLegacy fixesFeature devLegacy fixes
Team syncFirefightingStatus decksReporting
InterviewsTest automationClient meetingTicket triage
Core work Invisible overhead Displaced

Every role exists twice: on paper, and in reality.

Extra tasks. Silent overhead. Core work pushed aside. Everyone feels it. Nobody can prove it.

02What Constat does

From assumption to evidence.

Constat overlays the role as designed with the work as it actually happens, and makes the difference measurable.

Expected

What the role is designed to be. Captured from the job profile and role definition.

Actual

What actually happens in the working day. Captured in one structured interview.

Deviations

Where reality and role diverge. Recorded neutrally, not judged.

F-01
F-02
F-03
F-04

Findings

Evidenced findings with context. Only here does interpretation begin: problem, opportunity, or decision.

A deviation is not a verdict. It's a finding.

03How it works

One conversation.
One comparison.
Evidenced findings.

AI supports the analysis. It doesn't invent anything. No evidence, no finding.

Analysis framework  /  Tasks · Competencies · Accountability
01

Capture.

The role profile and one structured conversation about the real working week form the data basis. Led by an interviewer, or by the system itself. Nobody is ever asked to rate themselves.

02

Compare.

The system compares tasks, competencies, and accountability between role and reality, and marks every deviation.

03

Evidence.

Every finding stays linked to its source. Observation and hypothesis are reported separately.

The same interview, whether one role or two hundred.

04The proof

A single conversation.

Example from a Constat role analysis. One role, one structured conversation, sixty minutes.

26
evidenced findings
15
classified as critical
12 : 5
task areas lived versus planned — 240% of the intended role scope

Figures from a single case example, not an industry average.

“Everyone somehow knew he was the hub. But only once it was written down did it become clear: this is too much.”
F-07 Critical
SourceInterview passage 14:22
StatusObservation, evidenced
TypeDeviation from role profile

Cross-team coordination absorbs a substantial share of the working week. Not part of the role profile. Not visible to anyone but the person.

05Who it's for

Not a dashboard about people.
Findings about work.

Constat examines the relationship between role, work, and organization. Not the performance of individuals.

For employees

The work they actually do becomes visible, and gets recognition and room.

For managers

Workload distribution across the team rests on facts, not gut feeling.

For HR and leadership

Role design, onboarding, and retention risk get an evidenced basis.

Classic HR analyticsConstat
Self-ratings on scales.Structured interviews, led by a person or by AI.
Aggregated dashboards.Evidenced individual findings.
Rating people.Analyzing roles and structures.
A conversation in low light, faces turned away from the camera
One role, one conversation, sixty minutes.
The first step is smaller than you think

Start with one role.

We take one role from your organization, capture the profile and the reality, and show you the difference. Then you decide whether the whole team should follow.

get@levelwork.ai