What is average compliance and how is it worked out?
Average compliance is the mean of the compliance scores of the devices in view. Each device's score comes from reading its protections back from Android after a policy apply, so the average reflects what devices report, not what was intended. It is a smoother view than the fully compliant count.
Every device carries a compliance score. When a policy is applied, the device reads each protection back from Android and reports how many are in place. Average compliance takes those scores for the devices in the group, branch, school or organisation you are looking at, and shows the mean.
Because it is an average, one device with a very low score is softened by many that are fine. That is both its strength and its weakness. It is a good steady indicator of overall health and a good trend line, but it can hide a single troubled device. That is why Insights also shows fully compliant devices, which is stricter, and the breach centre lists the troubled ones by name.
Read it over time. A flat, high line is a calm fleet. A dip after a policy change usually means devices have not all picked up the new rules yet. A slow slide often means devices are drifting out of contact. Daily snapshots per group make that history available. See daily snapshots.
Skie does not claim a particular range as good or bad, because that depends on what your policy enforces and how many optional protections you switched on. Compare your own groups with each other and with their own past rather than with an outside number.
Practical tip: when the average moves, check on latest policy and on latest app before looking for anything exotic. They explain most movement.