How it runs when the products are in place.
Fictional sample. A fictional regional health network on Microsoft 365. Nothing here describes a real patient, provider or customer.
-
1
A data class, a rule, and a person who must sign
Halden's privacy office writes one rule in Simple Council: any agent that reaches a data class marked protected needs a named approver. Council applies it, routes the request, and records the approval with the agent, the version and the date, in a ledger that cannot be quietly edited.
-
2
The IT help desk that runs on the identity you already have
The service desk runs in SimpleOS Desk on the network's own Microsoft identity, with SLA targets per priority and a Teams surface where a ticket is raised, assigned and approved without leaving the chat. Resolution proposals are guarded: a person confirms before a change is made.
-
3
The rollout is a project with a signed scope
The Copilot rollout itself runs in SimpleOS Delivery from the signed statement of work, with milestones and acceptance criteria on the plan and a red-amber-green view the steering group reads each week.
Every sentence above describes what the named products do today, in the words of each product's own "what works today" list. What a product does not do yet is on that product's page, with the date it was checked.