Skip to content

Operating cycle

Match the decision and evidence to the live service rhythm.

Service work overlaps, but each operating area needs a visible question, owner, evidence, and review date. Use this map as an educational aid, not managed services, an audit, or certification.

Service areaControl questionEvidenceWatch for
Own

Which mission work, users, records, boundaries, and accountable roles define the service?

Service charter, role map, critical periods, support boundary, and review rhythm.

A live platform has administrators but no accountable service owner.

Support

How do people get help and how is work routed by impact and urgency?

Visible intake, request classes, severity rules, owners, response targets, and updates.

Requests disappear across email, chat, meetings, and personal relationships.

Sustain

Can the nonprofit maintain access, integrations, records, recovery, and administrator continuity?

Access review, runbook, backup administrator, monitoring, reconciliation, and recovery test.

The service depends on one person or fails quietly between systems.

Change

How will configuration, releases, and urgent restoration remain reviewable?

Change class, owner, safe test, communication, rollback, acceptance signal, and close record.

Undocumented production changes become permanent operating knowledge gaps.

Review

What do support, reliability, access, data quality, effort, cost, and risk say now?

Monthly signals, quarterly decisions, owned backlog, accepted risk, and updated charter.

Dashboards accumulate while recurring service problems remain ownerless.

Renew or exit

Should the nonprofit renew, right-size, improve, replace, or retire the service?

Value review, contract dates, commitments, license fit, export path, continuity, and decision owner.

An invoice becomes the default decision because alternatives were never prepared.

Before the next service review closes

  • Which nonprofit owner can approve the decision?
  • What evidence is complete, incomplete, or contradicted?
  • Which operating signal changed value, cost, risk, access, or mission effect?
  • Which repeat request or workaround needs a service-level response?
  • What must remain recoverable and under nonprofit control?