// IAS Office · Chief Delivery Officer

The CDO's operating week, on one screen.

An opportunities register and a support mechanism — the cadence, escalation, discovery, data-asset intake and RAID that carry a Chief Delivery Officer's day-to-day execution. Seeded from the ICS Review & HR TAG Setup meeting. Everything below is editable and stored on this device only.

Source: Meeting Notes — ICS Review & HR TAG Setup · 17 July 2026, 04:55 PM.
Only what was stated in the meeting is pre-filled. No metrics, names or dates have been invented — blanks are left blank for you to complete.

Help & Docs

Everything about this cockpit in one place — an overview deck, the user manual, and the operator guide for rolling it out to a team.

IAS Office — Overview DeckUse the arrows or your keyboard's left/right keys to move between slides.

GVS IAS Office

The CDO Operations Cockpit

One screen for the operating rhythm of a delivery role — cadence, opportunities, intake, RAID and escalation. Runs in your browser; nothing leaves your device.

4Role templates

0Servers holding your data

1Click to a review deck

The problem

The operating rhythm lives in five places at once

Cadence in a calendar. RAID in a spreadsheet. Actions in a notebook. Intake in an email thread. Escalation in someone's head. Nothing reconciles, so the weekly review starts by rebuilding the picture instead of acting on it.

Role templates

Pick the role you actually run

Each role carries its own daily loop, review cadence, intake list and the KPIs it is measured on.

Fault Manager — release-wise fault resolution, correction against SLA, verification, closure
Delivery Manager — commitment to acceptance, baseline, change control
Test Lead — ATDLC qualification, coverage, load model, Q-Gate
Delivery Executive / CDO — discovery, cadence, opportunities, portfolio RAID

Support mechanism

The cadence that carries the week

Daily standup, weekly operational review, bi-weekly business review, RAID review — each with a purpose and a named owner. Every field is editable, because no two organisations run the same rhythm.

Escalation paths are captured as primary and secondary. If they are unassigned, the cockpit says so rather than leaving the gap silent.

Opportunities

Improvements that do not get lost

A register of what could be simplified, de-risked, built or grown — each with an owner, a due date and a status you move on cadence. Typed, so a conversation about "improvements" becomes a list with names against it.

Intake

Know what you are still missing

The data assets a role needs to operate — org chart, employee data, MIS, T&M, plans and records — tracked with a live completion bar. You can see at a glance whether you are running the unit on complete information or on fragments.

RAID & CAPA

Risks that are owned, dated and moving

Risks, assumptions, issues, dependencies and corrective actions in one log. The test is not whether a risk is listed — it is whether it has an owner, a date, and evidence of movement since last review.

Deck generator

One click to a review deck

Type the agenda, requirements and scope. The generator builds a presentable deck that also pulls in your live cadence, opportunities, intake position and open RAID — then opens it for presenting or printing to PDF.

Empty sections are skipped. Unassigned owners are shown as unassigned rather than quietly omitted.

Architecture

Your data never leaves this device

Everything is stored by your browser, on the machine you are using. GVS operates no server that holds it, so there is no upload, no account, and no copy anyone else can be compelled to produce.

The consequence is real: GVS cannot recover your data either. Export is your only backup.

Getting started

Four steps

1 — Choose your role and load its template
2 — Fill the blanks: escalation names, RAID owners, dates
3 — Work it on your cadence: move statuses, tick intake
4 — Export a backup, and again after every session that mattered

User ManualHow to run the cockpit day to day.

Getting started

Choose your role at the top, then press Load this role's template. This seeds the cadence, intake list and RAID for that role.
Fill the blanks. Escalation names, RAID owners and dates are deliberately empty — they were never decided, so the cockpit does not invent them.
Work it on cadence. Move statuses at standup, tick intake at the weekly review, add items as they arise.
Export a backup. This is the step people skip and the only one that cannot be undone by skipping.

What saves, and when

Everything saves automatically as you type, to this browser on this device. There is no Save button because nothing is being sent anywhere. Closing the tab loses nothing; clearing your browser data loses everything.

The controls

Control	What it does
Export	Downloads a .json file with the entire cockpit state. Your backup and your transfer format.
Import	Loads a previously exported file. Replaces current contents — export first if they matter.
Print	Clean one-page snapshot for a review meeting. Controls and help are hidden automatically.
Generate deck	Builds a review deck from your typed inputs plus the cockpit's live state.
Ops briefing	Optional. Needs your own Anthropic API key. Counts are computed here; the model only words them.

Moving between devices

There is no sync. Export on the first device, transfer the file however you trust, then Import on the second. Note that import overwrites rather than merges — pick one device as primary rather than editing on both.

If something looks wrong

Check you are at the same URL, in the same browser, on the same device, and not in a private window. Those four account for nearly every case of "my data disappeared". The full Troubleshooting Manual covers the rest.

Operator & Admin GuideFor rolling this out to a team or an organisation.

What you are deploying

A single HTML file that runs entirely in the browser. No server, no database, no accounts, no admin console. That removes most of the usual operator workload and moves one responsibility onto you: because data lives on endpoints, your device policy is the data-protection control.

Deployment options

Option	Notes
Public hosted URL	Fastest. Page fetched from the web; data still stays local.
Internal hosting	Serve the file from your own intranet. Static hosting is sufficient.
Local file	Distribute the file directly. Works fully offline.

Changing the address strands existing data. Browser storage is bound to the exact origin. Moving users from one URL to another means their data will not follow — build an Export/Import step into any migration plan.

Governance answers

Question	Answer
Where is data stored?	The user's browser, on their device
Can GVS access it?	No — there is no channel and no store
Can GVS recover it?	No. User export is the only recovery path
Central revocation?	No — no accounts exist to disable
Server-side audit trail?	No

Those last three are structural, not gaps awaiting a roadmap item. If central revocation, central retention control or a central audit trail are hard requirements, this model is the wrong fit for that use case.

What you must own

Backup — mandate an export cadence; there is no central copy to restore
Data classification — write down what may and may not be entered
Access removal — offboarding is device management, not an admin console
AI key policy — decide whether API keys are permitted and what may be sent
First-line support — name an internal owner; GVS is not a support desk

Seeding for your organisation

Configure one cockpit with your cadence, escalation structure and intake list, then Export and distribute that JSON. Your people Import it and start from your model rather than a generic template.

The full Operator Manual covers security posture, rollout phases and what to state — and not state — to an auditor.

Your role

Pick the role you actually run. Each one has its own daily loop, review cadence and intake list — drawn from how the work is really done, not a generic template.

Replaces the cadence, intake and RAID below with this role's defaults. Your opportunities are kept. Export first if you want a backup.

Support mechanism

The governance rhythm that carries the week — the cadence that keeps deliverables and revenue visible, and the escalation path for when they don't.

Escalation protocol

Primary and secondary paths. Names were not set in the meeting — assign them here.

Requested at review: primary & secondary escalation protocols.

Generate slide deck ONE CLICK

Type the requirements, agenda and scope. One click builds a review deck that also pulls in your live cadence, opportunities, intake and RAID. Opens in a new tab — present it, or print to PDF.

Project / deck title

Date / meeting

Agenda one item per line

Project requirements one per line

Scope of work one per line

Builds offline from what you typed plus the cockpit's current state. No key needed.

Opportunities register

Ways to simplify, de-risk and grow the delivery. Each opportunity carries a type, an owner and a status you can move.

Opportunity	Type	Owner	Due	Status

Discovery conversations

The two intake discussions that set the baseline. Same four probes for each: priorities, commitments, backlog, stakeholder friction.

Data-asset intake

Everything to be collected to run the unit. Tick items as they land. Source shown where the meeting named who provides it.

	Item	Source

RAID & corrective actions

Risks, assumptions, issues, dependencies and CAPA carried out of the review.

Type	Item	Owner	Due	Status

Next steps (from the meeting): to be finalised during the HR team and Sreeni discussions. The ramp-up plan for MN BRs is on hold — to be discussed with Satya before it moves.

Ops briefing GLASS-BOX · OPTIONAL

Numbers are computed here in the page, deterministically. The model only puts them into plain words — it can't change a count or invent a fact.

Paste your own Anthropic API key to generate a one-paragraph stand-up brief from the current state. The key stays in this browser and is sent only to Anthropic. Leave it blank and the cockpit still works fully offline.

No briefing generated yet. The deterministic snapshot below is what would be sent: