# The Automation Owner
Source: https://humanspark.ai/frameworks/the-automation-owner/

*You can own an automation without writing its code. The owner knows what it is for, what it may change, where judgement comes in, how it is checked and who is called when it fails.*

**When to use:** When deciding who is in charge of an automation, or answering the question "who do I put in charge of this?"

> An automation owner understands the purpose, the trigger, the inputs, the rules, where AI judgement is involved, what the system is allowed to change, where a person must approve, how the result is checked and who is responsible when it fails.

> The owner may build it, use a no-code platform, work with an AI coding agent, or hand a specification to IT or a developer. All four keep the business logic with the person who knows the work. The owner is usually the person who does the work today.

> When the automation moves money, changes legal records, touches sensitive data or becomes business-critical, the owner brings in specialist help.

> **Links:** The Pilot Charter, the Three Implementation Tiers.