Calculate the percentage of infrastructure tasks covered by Ansible automation.
Automation coverage = automated_task_types / total_operational_task_types × 100. This measures breadth of automation across distinct recurring workflows (not run frequency) — a task type counts as 'automated' if a maintained playbook/role exists for it, regardless of how often it runs. Tracking this over time highlights where manual toil is concentrated and whether an automation investment program is making measurable progress.
coverage_percent = (automated_tasks / total_operational_tasks) × 100
This calculator counts distinct task types, treating each as binary (automated or not) regardless of frequency — a rarely-run but automated disaster-recovery task counts the same as a frequently-run automated deployment. Weighting by frequency or risk is a reasonable variation if manual toil hours matter more than breadth.
Most teams still count a task as automated if a human clicks 'run' or approves a pipeline stage — the distinction that matters here is whether the actual execution steps are codified versus done by hand via SSH/console.
There's no universal number, but teams operating at scale typically aim for 80%+ coverage of routine operational tasks, while accepting that some rare, high-risk, or highly variable tasks may remain intentionally manual.
Audit runbooks, on-call tickets, and change requests over a recent period (e.g. a quarter) to enumerate distinct recurring task types, then cross-reference against your Ansible role/playbook inventory to count how many are covered.