Oversight Settings
How this console behaves: who can see what, when an escalation raises itself, and how penalties are computed. Escalation thresholds in particular are worth arguing about — set too tight, the queue becomes noise; set too loose, it becomes a record of things that were already too late.
Oversight organisation
Entities are onboarded from the directory. Removing one archives its record rather than deleting it — the seven-year retention obligation survives the engagement.Entity directory
Escalation thresholds
When the console raises something on its own initiative.
Readiness belowRaises a readiness escalation to the nodal officer.
Critical gaps at or aboveEscalates directly to the Head of Department.
Overdue rights requests at or aboveSection 13 exposure — escalates within one working day.
Incidents open beyondPost-incident review overdue.
SLA breaches in a quarter at or aboveTriggers a penalty statement for departmental confirmation.
Automation
Raise escalations automaticallyWhen a threshold is crossed, open an escalation with the nodal officer rather than waiting for someone to notice.
Weekly digest to the steering committeeEvery open escalation, ranked by severity, sent Monday morning.
Apply penalties without confirmationOff by default. A computed penalty applied without a departmental conversation tends to produce a dispute rather than a payment.
Roles
Access in this console is portfolio-wide by design. An oversight role that can only see some entities cannot do oversight.
Oversight administratorEverything, including onboarding entities and editing the rate card.2 people
Portfolio analystRead every entity, compose reports, raise escalations. Cannot close them.6 people
Engagement managerManage work orders and milestones for assigned entities.4 people
Steering committee memberRead-only across the portfolio, plus escalation decisions at the final rung.7 people
AuditorRead-only, including audit trails. No mutations of any kind.3 people
Demo data
Reset the demonstration data
Restores every record across Venture AI — consents, incidents, requests, enrolments and the portfolio — to the seeded state. Anything changed in this session is discarded.
Phase 2 note
These settings are held in the client for the demonstration. In Phase 2 they become tenant configuration on the oversight organisation, and the escalation thresholds become the input to a server-side rules engine that evaluates on a schedule rather than on page load.