SkieWhat does the Skie compliance score measure?
The compliance score reflects how many of the protections a device should have are confirmed in place when Skie reads them back from Android after a policy is applied. It is calculated per device, then averaged for groups, branches, schools and the organisation. A compliance run can be started on demand.
A policy says what should be true of a device: factory reset blocked, unknown sources blocked, the filtering DNS locked, and so on. The compliance score says how much of that is confirmed true. The measurement is not what the server sent. It is what the device read back from Android afterwards.
At device level you see the individual protections and which ones are in place. Higher up, Insights summarises average compliance, the number of fully compliant devices and the share of devices on the latest policy and latest app. Daily snapshots per group let you see change over time.
Why the number can be lower than expected: a device that has not synced since the policy changed has not read anything back yet. Optional switches that you have left off are not counted against the device. A device on an unreviewed model may leave built-in apps alone by design. Check the device page before concluding there is a fault.
You can run a compliance check on demand when you want a fresh reading, for example before an exam day or after a large policy change. The impact preview shows what a change will touch before you publish it, which makes a drop in score easier to predict.
Skie does not claim that a high score means a device is beyond tampering. It is a measure of state, and breach alerts, the audit log and the self-heal are part of the same picture.
Practical tip: report on the average, but act on the lowest ten devices.