Seerene
Software Production Governance for the AI Era

The Digital Boardroom for Enterprise Software Production.

Your strategy runs through your software production. Seerene gives the CTO, CIO, CXO and board one independent, read-only view of cost, capacity, quality and risk across every production line — with AI impact as the current lens.

  • Read-only · code stays in place
  • Teams and systems, never individuals
  • Hasso Plattner Institute origin
  • First baseline ≈ 30 days from data readiness
How it connects
Connect portfolio priorities to engineering action — with evidence at every management level.
Management pyramid — one view per level: C-level, top, mid-level
Seerene Analytics Layer — fuses the signals into one definition
Software Evidence Layer · Software Map — one shared information base for all lines
Software production lines 1…N — requirements → code → build → test → run
Tool knowledge — read-only signals from the existing toolchain
Customers creating value with Seerene
SAPAudiContinentalBMWHenkelErste BankHeidelberger DruckRaiffeisenbank ÖsterreichBundesagentur für ArbeitPing An
01Today’s starting point

Condensed status can look green while production is already red.

Useful signals exist today: flow and value-stream metrics, engineering productivity, code and architecture intelligence, delivery metrics. Each illuminates its own stage with its own definitions. Condensed into one status for the board, the connections between them disappear.

Why it happens+

Every condensation step removes context. A green status says the plan is met. It does not say what capacity that took, where it was borrowed from, or which line will slip next. Research on project status reporting found 60 % of reports biased, more than twice as often optimistic as pessimistic.*

What leadership needs+

Not more status, but one yardstick for every production line and an answer no report gives today: are we getting better or worse as a whole — and where? Read per production line, across the portfolio and at every management level, traceable to the evidence.

* Studies summarized in MIT Sloan Management Review, 2014.

What is missing is the connection along the development flow, across production lines and through the management layers: the three axes of the governance gap.

Production line
As reportedQ3 board pack
Observed in productionsame quarter · capacity per line
Line 1
Customer portal
On trackBudget as planned
No risks open
One sprint behind

Release waits on the shared platform. The delay is real, but not yet in any status.

Line 2
Payments platform · shared
On trackBudget as planned
No risks open
Rework 34% of capacity

Rework has been rising for two quarters. Two teams borrowed from Line 3 keep the milestones green.

Line 3
Partner API
On trackBudget as planned
No risks open
A third of capacity lent

Capacity lent to Line 2 since July; the roadmap is unchanged on paper.

Condensed from management dashboard, PMO status and delivery metrics, each with its own definitions.
New valueReworkWaiting or lent
One connected cause
Line 2 rework → capacity lent from Line 3 → Line 1 release slips. Three green rows, one cause that no single status shows.
Three production lines, one quarter · a scenario, not a customer result.
What leadership can decide

Validate the shared constraint with engineering, then prioritize the structural work and review the capacity mix and delivery impact.

A possible decision in this scenario, to be validated with engineering; not a reported customer result.

Inside the Digital Boardroom
Capacity flow by production line

The view shows how much of 100 % funded developer time remains for value-add and which friction types absorb the rest, per production line. Open to enlarge.

See the capacity view behind this question →
Why now

AI moves the bottleneck from writing code to governing it.

AI assistants raise code output faster than review, integration and portfolio decisions can absorb it. The 2025 DORA report finds AI adoption near-universal, throughput up and delivery stability still down; a 2026 industry survey reports 85 % of respondents locating the bottleneck at review and validation, and 80 % having introduced tools faster than rules. The governance task exists without AI; AI makes it urgent — and many organizations do not yet measure its effect on one definition.

Sources: DORA, State of AI-assisted Software Development 2025 · GitLab/Harris Poll, AI Accountability Report, June 2026.

How AI impact is measured on one definition →
Throughput up, stability still down

AI adoption near-universal; delivery stability negative.

DORA 2025
85 %locate the bottleneck at review and validation

80 % introduced tools faster than rules.

GitLab/Harris Poll, 2026
02The governance gap

Three questions you cannot answer independently today.

Your production lines are run well — each for itself. What no line can give you is the view across them. Along three axes, today’s answer comes from reports that were condensed, translated and interpreted on their way up.

Seerene connects the three axes into one evidence layer: one comparable view, one evidence path for every management level — the structure of everything the Digital Boardroom shows.

How the view is built →
X · DEVELOPMENT FLOW requirements → code → build → test → run Y · PRODUCTION LINES line 1 … line N, one definition Z · MANAGEMENT LEVELS teams → management → board
Three-axes model: X along one production line, Y lines 1…N, Z from teams to the board.
03The result · the Digital Boardroom

One view per management level, on the same information space.

Select a management level to see its views. Every figure stays traceable to the evidence beneath it, and the same question can be followed down to the system and the code.

Digital Boardroom views per management level. Select a level to see its views.
How the view is built, read-only, from the traces your tools already record →
Management question
Where does our capacity go, and where does AI pay off end-to-end?
Who asks

CXO, CTO, CIO

Seerene makes visible

Portfolio priorities: the capacity mix per production line.

Reading the view

Capacity flow, read left to right: from 100 % of developer time to the share remaining for new value. The colored outflows are the shares absorbed by below-the-radar work, defect fixing, rework after review, work in complex code and ad-hoc tickets — shares of total developer time, on one definition for every production line.

A possible decision

Validate the largest outflows with engineering, then prioritize the structural work behind them and review the capacity mix at the next pulse.

Capacity flow by production line · Digital Boardroom view · open to enlargeLevel · C-level
Systems, not peopleNo individual monitoring; works-council reviews documented in DACH.
Read-only by designSource code stays in place; Seerene reads metadata from the existing toolchain.
About 30 daysBaseline typically about 30 days from data readiness, coordinated by one technical contact.
Next step

Bring the decision you have to defend next.

A 30-minute Executive Briefing with Seerene’s leadership: one management question, the evidence that would settle it, a written summary you can forward.

04How it is used · the condition

One executive impulse in, connected evidence back — review after review.

Leadership sets the question; Seerene connects the signals from the existing systems and aggregates them upward, traceable at every level. The loop closes only when the executive who set the impulse reads the answer: 15 minutes per executive review with your direct reports, aligned with your management cadence, one verified view, three decisions — where are we off track, who acts next, what changes before the next review. The technical validation can be delegated; the decision cannot.

The first four to six rounds are guided by Seerene, because the first deviations always raise objections. That is the mechanism working, not failing: every deviation gets the team’s explanation before it is decided.

  • Debates end faster. One verified picture moves the meeting from “whose number is right?” to “what do we do next?”

  • Priorities become defensible. Modernization, technical-debt reduction and AI investment follow measured impact.

  • Accountability without blame. The system is measured, never the individual. Teams act on evidence at their own level.

THE LOOP STARTS WHERE THE DECISION IS OWNEDCXO / CTO / CIOVP levelHead of engineeringIMPULSE ↓EVIDENCE ↑CXO / CTO / CIOthe questionthe answer,traceableBoard reportingconsistent viewsame evidenceVP levelpriority andscopeportfoliocomparisonHead of engineeringfocus persystemaggregated persystemTeamsaction, ownedtraces perteamToolchainreaches thesourceread-onlymetadata
One closed loop: the CXO, CTO or CIO sets the question; the impulse enters every level and reaches the toolchain, and connected evidence returns to the executive who asked — traceable at every level. The board receives a consistent view of the same evidence.
Traceability · from the board question to the Software Map

A number can be argued with. A map of the code it comes from cannot: every figure opens to the production line, the system, the component and its change history — without source code leaving your environment.

01Management question
Leadership · the question

Where is capacity absorbed before it reaches the product?

02Portfolio view
Observation · portfolio

Flow of funded capacity

03Production line
Observation · production line

Capacity mix per production line

04System
Technical interpretation · system

Structural indicators per system

05Software Map
Technical interpretation · code

The component, its size, complexity and risk

Digital Boardroom views and Software Map. Observation, technical interpretation and leadership decision are kept apart; causes are expressed at team and system level, with no individual attribution.
05Every seat at the table

One evidence baseline. Five leadership questions.

Different questions, one reality. ERP and CRM gave operations and sales one trusted fact base; software production still lacks it. Choose a seat to see its question, what becomes visible and the decision it supports.

Capacity flow: funded capacity to product work · Digital Boardroom view
Management question
Which of our production lines will absorb new budget before it reaches the product?
Seerene makes visible

Capacity per product line split into product work and work bound by rework, dependencies and knowledge concentration, on one definition across teams and vendors.

Your decision

Where to invest, where to fix structure first, and what to tell the board about both.

Level · C-levelFor CTOs and CIOs →

The CTO or CIO owns the view. CEO, CFO and board read the same evidence; engineering leadership works on the causes at its own level. The one-page Executive Brief to forward internally →

06Origin and proof
Dr. Jürgen Müller
“When software becomes the core of enterprise value creation, governing its production with the same rigor we apply to financial capital is a strategic imperative.”
Dr. Jürgen Müller
5+ yrs CTO, SAP SE · Hasso Plattner Foundation · Ambassador
Research origin

A Hasso Plattner Institute spin-off, built on 15+ years of research in software visualization and analytics.

Used where oversight is strict

Large, regulated organizations in the DACH region; no individual monitoring, works-council reviews documented.

Nothing leaves the house

Read-only connection to the existing toolchain; source code stays in place; team and system level only.

07Software Excellence Network

Where senior leaders shape the future of software production.

A confidential peer forum for C-level and engineering leaders, founded by Seerene and run with the Hasso Plattner Institute and the German Deep Tech Group: peer exchange off the record, masterclasses with practitioners, early research from academia and sector forums.

Members and gatherings of the Software Excellence Network
In depth

Questions leaders ask before a briefing.

Short answers, each with the page that goes deeper. The full argument is in the Executive Brief.

What is Software Production Governance?

The management discipline of steering software production on one independent evidence base: cost, capacity, quality, delivery, risk and AI impact, comparable across all production lines, teams and vendors. ERP gave finance and CRM gave sales a shared fact base; software production has lacked one. Seerene’s Digital Boardroom is that governance layer.

The platform
What does Seerene read, and what does it not read?

Metadata from the toolchain you already run: work items, commits, builds, tests, defects and incidents, read-only. Source code stays where it is, no tool is replaced and no workflow changes. Evidence reaches code level — the component and its change history — without source code leaving your environment. Systems and teams are measured, never individuals.

Enterprise readiness
How is this different from engineering dashboards or DORA metrics?

Point tools illuminate one stage of one production line with their own definitions. Seerene connects the stages along the development flow, makes production lines comparable with each other and carries one view up every management level, so that a board figure stays traceable to the engineering evidence beneath it.

How it works
What do we see after the first 30 days?

An independent baseline on the management question agreed in the briefing: where funded capacity reaches the product and where it is absorbed by rework, dependencies and knowledge concentration, per production line and per system, validated with your engineering leads — and a decision to continue, expand or stop. Day 30 is an evidence review, not a contractual exit.

The engagement step by step
How is the impact of AI-assisted coding measured?

On the same definitions as everything else: the share of capacity that reaches new functionality, rework after review, change concentration and risk on the Software Map, compared before and after AI adoption and per production line. Code volume is not the measure.

For CTOs and CIOs
Which roles work with the Digital Boardroom?

CEOs, CFOs and supervisory boards for investment effectiveness and risk; CTOs and CIOs for portfolio, modernization and sourcing decisions; engineering leadership for improvement actions per system. Every level sees its own view of the same evidence.

Views per management level
How does an engagement start?

With a 30-minute Executive Briefing on your management question, followed by a technical validation call and a scoping with the sponsor. The independent baseline then takes typically about 30 days from data readiness and ends in a management review with you.

Request an Executive Briefing
How are IT security and co-determination handled?

Access is read-only and limited to metadata; nothing is attributed to individuals, which is the basis for works-council agreements. Documentation for IT security questionnaires and review processes is part of the engagement.

Security and reviews
Can we build this ourselves from the tools we already have?

You can combine an engineering-analytics platform, a code-analysis tool, a BI layer and an internal team. That gives you two pictures instead of one, an integration project to maintain, and no routine in which leadership reads the same evidence as engineering as part of your management routine. Seerene delivers one evidence layer, one map and the governance routine as one engagement; the comparison in time and money is part of the Executive Briefing.

Why this is not another engineering dashboard
How much of my time does this take?

15 minutes per executive review, aligned with your management cadence. With your direct reports, on one verified view, with three decisions. Technical validation and the first review are led by your engineering lead and Seerene; the decision stays with you. The first four to six rounds are guided.

The review rhythm
09How to start

From a 30-minute Executive Briefing to your first management review.

  1. 01 Executive Briefing ~30 minutes

    Clarify the relevant management question and the expected insight.

  2. 02 Technical validation call with your engineering lead

    Data sources, access, coverage and prerequisites; one technical contact.

  3. 03 Scoping with the sponsor decision question · success criterion

    Confirm and fine-tune the question and the success criterion; specific proposal.

  4. 04 Independent baseline ~30 days from data readiness

    Organization-wide, read-only metadata; findings validated with engineering.

  5. 05 Management review with you

    Findings, options, owned actions, and a date for the impact review.

The question is not whether to govern software production. It is when you begin.

Choose one management question. Start with an independent baseline. Use the evidence to decide what comes next. The first step is an Executive Briefing of about 30 minutes, peer level, with Seerene’s leadership.

What you get

A peer-level conversation on one management question, with the relevant product views, and a written summary you can forward internally.

Which question

One question on cost, capacity, quality, risk or business value, often with AI impact as the lens: where capacity is bound, which production lines need attention, where risk actually falls.

How much time

About 30 minutes with Seerene’s leadership. Scope, prerequisites and effort are clear by the end of the call.

The Digital Boardroom for Enterprise Software Production.

Software Production Governance for the AI Era The Digital Boardroom for Enterprise Software Production. Your strategy runs through your software production. Seerene gives the CTO, CIO, CXO and board one independent, read-only view of cost, capacity, quality and risk across every production line with AI impact as the current lens. Request an Executive Briefing See the product views How it connects Connect portfolio priorities to engineering action with evidence at every management level. Management pyramid one view per level: C-level, top, mid-level Seerene Analytics Layer fuses the signals into one definition Software Evidence Layer Software Map one shared information base for all lines Software production lines 1…N requirements code build test run Tool knowledge read-only signals from the existing toolchain On this page The problem Product views How it is used Who it is for How to start

Condensed status can look green while production is already red.

01 Today’s starting point Condensed status can look green while production is already red. Useful signals exist today: flow and value-stream metrics, engineering productivity, code and architecture intelligence, delivery metrics. Each illuminates its own stage with its own definitions. Condensed into one status for the board, the connections between them disappear. Why it happens Every condensation step removes context. A green status says the plan is met. It does not say what capacity that took, where it was borrowed from, or which line will slip next. Research on project status reporting found 60 % of reports biased, more than twice as often optimistic as pessimistic.* What leadership needs Not more status, but one yardstick for every production line and an answer no report gives today: are we getting better or worse as a whole and where? Read per production line, across the portfolio and at every management level, traceable to the evidence. * Studies summarized in MIT Sloan Management Review, 2014. Why it happens Every condensation step removes context. A green status says the plan is met. It does not say what capacity that took, where it was borrowed from, or which line will slip next. Research on project status reporting found 60 % of reports biased, more than twice as often optimistic as pessimistic.* What leadership needs Not more status, but one yardstick for every production line and an answer no report gives today: are we getting better or worse as a whole and where? Read per production line, across the portfolio and at every management level, traceable to the evi

AI moves the bottleneck from writing code to governing it.

Why now AI moves the bottleneck from writing code to governing it. AI assistants raise code output faster than review, integration and portfolio decisions can absorb it. The 2025 DORA report finds AI adoption near-universal, throughput up and delivery stability still down; a 2026 industry survey reports 85 % of respondents locating the bottleneck at review and validation, and 80 % having introduced tools faster than rules. The governance task exists without AI; AI makes it urgent and many organizations do not yet measure its effect on one definition. Sources: DORA, State of AI-assisted Software Development 2025 GitLab/Harris Poll, AI Accountability Report, June 2026. How AI impact is measured on one definition Throughput up, stability still down AI adoption near-universal; delivery stability negative. DORA 2025 85 % locate the bottleneck at review and validation 80 % introduced tools faster than rules. GitLab/Harris Poll, 2026

Three questions you cannot answer independently today.

02 The governance gap Three questions you cannot answer independently today. Your production lines are run well each for itself. What no line can give you is the view across them. Along three axes, today’s answer comes from reports that were condensed, translated and interpreted on their way up. Seerene connects the three axes into one evidence layer: one comparable view, one evidence path for every management level the structure of everything the Digital Boardroom shows. How the view is built Three-axes model: X along one production line, Y lines 1…N, Z from teams to the board. X-Axis · development flow Where in the flow from requirement to running software is capacity lost — across tool boundaries? Today: partial. Inside one line a tool sees its stage, sometimes the next one; the definitions differ from tool to tool. Y-Axis · production lines Where do my production lines stand against each other — on the same yardstick, despite different languages, methods and systems? Today: lines are compared through reports that were produced on different yardsticks. Z-Axis · management levels Can I follow a management figure down to its cause in the code — or do I have to believe the report? Today: a figure that reaches the board has been condensed several times; the trace back is gone.

One view per management level, on the same information space.

03 The result the Digital Boardroom One view per management level, on the same information space. Select a management level to see its views. Every figure stays traceable to the evidence beneath it, and the same question can be followed down to the system and the code. How the view is built, read-only, from the traces your tools already record Management question Who asks Seerene makes visible Reading the view A possible decision Digital Boardroom view open to enlarge Level Use cases Compare delivery partners Prioritize improvements Review critical application risk All four use cases Systems, not people No individual monitoring; works-council reviews documented in DACH. Read-only by design Source code stays in place; Seerene reads metadata from the existing toolchain. About 30 days Baseline typically about 30 days from data readiness, coordinated by one technical contact. Where does our capacity go, and where does AI pay off end-to-end? Portfolio priorities: the capacity mix per production line. Capacity flow by production line Capacity flow per production line · Digital Boardroom view · Open to enlarge. Capacity flow, read left to right: from 100 % of developer time to the share remaining for new value. The colored outflows are the shares absorbed by below-the-radar work, defect fixing, rework after review, work in complex code and ad-hoc tickets — shares of total developer time, on one definition for every production line. Validate the largest outflows with engineering, then prioritize the structural work behind them and review the capacity mix at the next pulse. VPs and

Bring the decision you have to defend next.

Next step Bring the decision you have to defend next. A 30-minute Executive Briefing with Seerene’s leadership: one management question, the evidence that would settle it, a written summary you can forward. Request an Executive Briefing Read the Executive Brief

One executive impulse in, connected evidence back review after review.

04 How it is used the condition One executive impulse in, connected evidence back review after review. Leadership sets the question; Seerene connects the signals from the existing systems and aggregates them upward, traceable at every level. The loop closes only when the executive who set the impulse reads the answer: 15 minutes per executive review with your direct reports, aligned with your management cadence, one verified view, three decisions where are we off track, who acts next, what changes before the next review. The technical validation can be delegated; the decision cannot. The first four to six rounds are guided by Seerene, because the first deviations always raise objections. That is the mechanism working, not failing: every deviation gets the team’s explanation before it is decided. . One closed loop: the CXO, CTO or CIO sets the question; the impulse enters every level and reaches the toolchain, and connected evidence returns to the executive who asked traceable at every level. The board receives a consistent view of the same evidence. Traceability from the board question to the Software Map A number can be argued with. A map of the code it comes from cannot: every figure opens to the production line, the system, the component and its change history without source code leaving your environment. Digital Boardroom views and Software Map. Observation, technical interpretation and leadership decision are kept apart; causes are expressed at team and system level, with no individual attribution.

One evidence baseline. Five leadership questions.

05 Every seat at the table One evidence baseline. Five leadership questions. Different questions, one reality. ERP and CRM gave operations and sales one trusted fact base; software production still lacks it. Choose a seat to see its question, what becomes visible and the decision it supports. Digital Boardroom view Digital Boardroom Effort trend Mar Aug Digital Boardroom view Management question Seerene makes visible Your decision Level The CTO or CIO owns the view. CEO, CFO and board read the same evidence; engineering leadership works on the causes at its own level. The one-page Executive Brief to forward internally Which of our production lines will absorb new budget before it reaches the product? Capacity per product line split into product work and work bound by rework, dependencies and knowledge concentration, on one definition across teams and vendors. Where to invest, where to fix structure first, and what to tell the board about both. Does our software production convert speed into business value? Effort by product line and initiative against stated priorities, with quality and rework shown alongside throughput. Whether to hold course, re-allocate or change how work is prioritized. What share of our engineering spend reaches the product? Capacity per production line split into product work and work absorbed by rework, dependencies and knowledge concentration, in developer-days and budget on one basis. Where additional budget would be absorbed and where structure has to be fixed first. Is our software investment reaching the product and the strategy? Capacity by pro

Origin and proof

06 Origin and proof “ ” Research origin A Hasso Plattner Institute spin-off, built on 15+ years of research in software visualization and analytics. Used where oversight is strict Large, regulated organizations in the DACH region; no individual monitoring, works-council reviews documented. Nothing leaves the house Read-only connection to the existing toolchain; source code stays in place; team and system level only. See what our customers say

Where senior leaders shape the future of software production.

07 Software Excellence Network Where senior leaders shape the future of software production. A confidential peer forum for C-level and engineering leaders, founded by Seerene and run with the Hasso Plattner Institute and the German Deep Tech Group: peer exchange off the record, masterclasses with practitioners, early research from academia and sector forums. The Network Events and recordings

Two recent perspectives on governing software production.

08 Insights Two recent perspectives on governing software production. All Insights

Questions leaders ask before a briefing.

In depth Questions leaders ask before a briefing. Short answers, each with the page that goes deeper. The full argument is in the Executive Brief . What is Software Production Governance? The management discipline of steering software production on one independent evidence base: cost, capacity, quality, delivery, risk and AI impact, comparable across all production lines, teams and vendors. ERP gave finance and CRM gave sales a shared fact base; software production has lacked one. Seerene’s Digital Boardroom is that governance layer. What does Seerene read, and what does it not read? Metadata from the toolchain you already run: work items, commits, builds, tests, defects and incidents, read-only. Source code stays where it is, no tool is replaced and no workflow changes. Evidence reaches code level — the component and its change history — without source code leaving your environment. Systems and teams are measured, never individuals. How is this different from engineering dashboards or DORA metrics? Point tools illuminate one stage of one production line with their own definitions. Seerene connects the stages along the development flow, makes production lines comparable with each other and carries one view up every management level, so that a board figure stays traceable to the engineering evidence beneath it. What do we see after the first 30 days? An independent baseline on the management question agreed in the briefing: where funded capacity reaches the product and where it is absorbed by rework, dependencies and knowledge concentration, per production line and per syste

From a 30-minute Executive Briefing to your first management review.

09 How to start From a 30-minute Executive Briefing to your first management review. Request an Executive Briefing The engagement in detail

The question is not whether to govern software production. It is when you begin.

The question is not whether to govern software production. It is when you begin. Choose one management question. Start with an independent baseline. Use the evidence to decide what comes next. The first step is an Executive Briefing of about 30 minutes, peer level, with Seerene’s leadership. What you get A peer-level conversation on one management question, with the relevant product views, and a written summary you can forward internally. Which question One question on cost, capacity, quality, risk or business value, often with AI impact as the lens: where capacity is bound, which production lines need attention, where risk actually falls. How much time About 30 minutes with Seerene’s leadership. Scope, prerequisites and effort are clear by the end of the call. Schedule a 30-minute briefing Request an Executive Briefing

Questions leaders ask before a briefing

What is Software Production Governance?

The management discipline of steering software production on one independent evidence base: cost, capacity, quality, delivery, risk and AI impact, comparable across all production lines, teams and vendors. ERP gave finance and CRM gave sales a shared fact base; software production has lacked one. Seerene’s Digital Boardroom is that governance layer.

How is this different from engineering dashboards or DORA metrics?

Point tools illuminate one stage of one production line with their own definitions. Seerene connects the stages along the development flow, makes production lines comparable with each other and carries one view up every management level, so that a board figure stays traceable to the engineering evidence beneath it.

How is the impact of AI-assisted coding measured?

On the same definitions as everything else: the share of capacity that reaches new functionality, rework after review, change concentration and risk on the Software Map, compared before and after AI adoption and per production line. Code volume is not the measure.

Which roles work with the Digital Boardroom?

CEOs, CFOs and supervisory boards for investment effectiveness and risk; CTOs and CIOs for portfolio, modernization and sourcing decisions; engineering leadership for improvement actions per system. Every level sees its own view of the same evidence.

How does an engagement start?

With a 30-minute Executive Briefing on your management question, followed by a technical validation call and a scoping with the sponsor. The independent baseline then takes typically about 30 days from data readiness and ends in a management review with you.

How are IT security and co-determination handled?

Access is read-only and limited to metadata; nothing is attributed to individuals, which is the basis for works-council agreements. Documentation for IT security questionnaires and review processes is part of the engagement.