Operating charter worksheet

Otomat editorial · Reviewed 23 October 2026 · Ungated working template

Define one operating goal, baseline, owner, data and action boundary, acceptance gate and handover before a build.

Use blank fields to prepare a decision. Inputs stay in this page’s memory and are never submitted or saved by this app. Reset or reload to clear them. Downloads include your entries and are created on your device. Keep sensitive data out of this worksheet. A download records only the fixed worksheet identifier in analytics.

Operating goal and workflowWhat constraint matters? Describe the start/end of one task and the non-AI alternative.Owners and committed capacityBusiness owner, technical maintainer, finance reviewer, risk approver and backup. Use roles rather than personal details.Baseline and task populationWindow, eligible tasks, accepted completion, cycle time, exceptions, review/correction effort and source references.Data and source rightsSources, authorized uses, destinations, retention/deletion and the person who can approve each. Unknown rights block the build.Permitted and prohibited actionsSeparate read, draft, approve and execute. Define independent approval, scoped credentials and external caps.Acceptance test and stop ruleIndependent normal/exception/denied cases; agreed thresholds; reviewer; evidence version. What would make us stop?Dependencies and decision gatesSource access, integrations, staff availability, cost/capacity limits and gate dates. Dates are hypotheses.Ownership and handoverAssets, licenses, export/restore, model replacement, primary/backup competence and residual limitations.

Blank fields do not mean zero. Record unknowns and assign an evidence request. This template is a proposed method, not evidence of a completed deployment or financial return.

Read the guide and illustrative example