Define a software service charter

Control principle

Treat important software as an owned service, not an orphaned project deliverable.

A system is live, but ownership, service boundaries, decision rights, and review dates are still implied rather than documented.

Use it in the active service

Start with these controls

1. Name the service owner, administrator, data owner, vendor owner, and business decision authority.
2. Describe the users, mission work, records, integrations, and operating hours the service supports.
3. Set support boundaries, escalation paths, maintenance windows, continuity expectations, and excluded work.
4. Record measures, known constraints, review dates, and events that trigger a new service decision.

Pause point

Do not let operating pressure erase nonprofit ownership

A charter does not replace contracts, security plans, privacy duties, continuity plans, or regulated operating procedures.