Controls
The Controls view shows the unified framework from the inside out — each control with its mapped expectations, coverage state, and associated mechanisms.
The Controls view switches perspective from artefact-first to framework-first. Instead of navigating a regulatory document and looking outward to the controls it maps to, you navigate the unified control framework and look inward at what each control covers and how well it is supported.
Switch to this view from the board header using the Controls option.
What the table shows
The Controls table lists every control in the unified framework that is relevant to your board's scope. For each control, you can see:
- Which artefact nodes map to it — the expectation nodes from all loaded artefacts that have been mapped to this control.
- Coverage state — whether the control is a Gap, Covered, or Implemented, based on what exists in Mechanic behind it.
- Domain and topic — where the control sits in the governance hierarchy.
Filtering controls
The Controls view supports several filters to narrow the table:
- By domain — show only controls from a specific governance domain.
- By expectation type — filter to controls that carry obligations, requirements, practices, or commitments from your loaded artefacts.
- By coverage state — focus on Gaps to find where mechanism work is still needed, or on Implemented to audit what has been confirmed.
Control sets
A board can be associated with a control set — a curated subset of the unified framework relevant to a specific programme, organisation, or system type. When a control set is applied, the Controls view shows only the controls within that set, simplifying the table for focused work.
Control sets are configured via the shield icon in the board header. Options include:
- All controls — no filter applied, the full framework is visible.
- Workspace sets — sets created by your team within the workspace.
- Shared sets — sets published by Balcony for common use cases (e.g., an EU AI Act focused set).
What next?
- Crosswalk — see the artefact-first view with coverage states.
- Domains & Topics — understand the control hierarchy.
- Building a mechanism — start mechanism work for a Gap control.