Research prototypeFictional data · runs in your browser
Know what you approved, why, and who owned it.
For CIOs and change leaders: boardlevel builds an evidenced decision record for each major change. AI assembles it alongside your CAB; a named executive decides.
Open the demoWalk one fictional decision through all seven stages.
Decision record · CDR-DEMO-0001
Fictional
Deploy Microsoft 365 Copilot enterprise-wide
ScopeRequested 12,400 users in one wave. Recommended ~4.8% of seats; HR, legal and M&A excluded.
Evidence7 items. Output-quality testing doesn't exist yet; permissions scan covered 1.3% of sites.
DissentCISO, CFO, Legal/Privacy and Red Team, preserved verbatim.
Conditions6, each with an owner. None verified.
AI authorityRecommend only
Decision ownerAwaiting approver · Proposal v1
Human authority
People, not software, approve change and accept risk.
Gaps stay visible
Missing, stale or conflicting evidence is shown, not smoothed over.
01The executive problem
The biggest changes. The most fragmented assessment.
01
Changes cross every boundary.Strategy, processes and people connect to applications, data, infrastructure, security, suppliers and sites.
02
Each forum sees its slice; no one sees the whole.CAB, architecture, security, risk, legal and procurement keep separate records. The links sit in stale diagrams, tickets and people's heads.
03
Separate approvals are not one decision.Accountability diffuses. After a failure, what was known, and who accepted the remaining risk, is hard to establish.
02boardlevel and the CAB
Your CAB approves the change. boardlevel prepares the decision.
It doesn't replace your CAB. It reads from the systems you already run and gives the accountable executive one evidenced view of impact, unknowns and dissent.
Designed to read from10 source types
CMDBArchitecture repositoryCloud inventoryIdentity and securityNetworkHR and organisationFacilities and sitesRisk and legalProcurement and suppliersProject and change
03How it works
From proposal to record, in seven stages.
The record in the hero is what stage seven produces.
No.StageOutcome
01ProposalThe sponsor states the change, scope and intended benefit.
02Impact mapEvery function, system and site touched, with gaps marked.
03Evidence trailEach claim linked to its source, or flagged as missing.
04Specialist panelSecurity, finance, legal and risk challenge the proposal independently.
05Open challengesUnresolved dissent is kept verbatim, not smoothed over.
06Executive reviewThe accountable executive sees one view, not six reports.
07Decision recordA named decision, its conditions and its owner, in one record.
See the 10 impact layers+
Strategy and capabilitiesProcessesPeople and roles● UnknownApplicationsIntegrations and dataCloud and on-prem infrastructureNetworks● UnknownSecurity controls and trust boundariesSuppliersSites and buildings● Unknown
04Human control
People decide. AI recommends.
Policy sets the ceiling per class of change. For major change, AI stops at Recommend, and no single person holds two roles.
A1Assist
A2 · CeilingRecommend
A3Execute after approval
A4Bounded delegation
A5Adaptive under policy
A2: AI proposes a course of action with rationale. A human decides and acts.A3–A5 not in pilot scope
RoleDoesCannot
ProposerSubmits the change and its intended benefit. Cannot assess or approve it.Assess or approve it
ChallengerRed Team and domain roles contest assumptions. Dissent is preserved, not merged.Edit the proposal
Risk ReviewClassifies impact and checks what the goal, scope and policy actually permit.Approve the change
ApproverA named human approves the reviewed version or returns it for correction.Propose or execute it
ExecutorActs only within current authority and verified pre-start controls. A2 cannot execute.Change scope
AuditorSeparately records verifier, source and result. A condition owner cannot verify their own control.Alter the record
05Security and data
What runs where, and who decides.
This prototypeThe demo runs in your browser. Fonts load from an external font service.
Who decidesAI is capped at Recommend for major change. A named human approves; each approval is tied to a proposal version.
Pilot dataDocuments and context you choose to share for the selected decision; no production-system connections required.
06Design partners
Bring one major decision to a pilot.
For design partners with a live decision and the appetite to document how it was made. Draft a brief to share with your sponsor.
Stays on your device
Pilot termsDesign partners
Length6 weeks
Your effortSponsor ~2 hours a week; 3–5 specialists, about 1 hour each.
CostFree for selected design partners
You getA decision record for one live, major decision (dependencies, risks, perspectives, recommended actions), then a debrief.
Built bySecurity Sages, led by Evan Phair, a cybersecurity and technology governance leader with 15+ years' enterprise experience. hello@securitysages.com