SkieHow should a school run a pilot of Skie?
Pick one or two classes, a small team and a clear period, usually a term. Include one IT person, one teacher and someone who approves rules. Set the structure, provision the tablets, watch compliance and online status, collect plain feedback, and decide on expansion at the end. Pricing is on request.
A pilot answers a short list of questions. Do the tablets stay protected? Can your people set them up? Do teachers find the controls useful? Do parents accept it? Choosing a small, real group beats a big demo because it exposes the actual friction.
Build the team first. You need an IT person who will provision tablets and read the dashboard, a teacher who will use the lock and the lecture list in real classes, and someone with authority to approve rules and talk to parents. Without the third person, small decisions pile up.
Scope it tightly. One or two groups, one baseline policy, one app list per grade, a timetable with three or four windows, and a Wi-Fi network you have already tested with the network check. Make sure each group has a policy and an app list before you provision, as the readiness gate requires.
During the pilot, look at the same few numbers each week: compliance score, online and silent share, tablets on the latest policy, low battery and open events. Keep a log of problems and who solved them. Note which requests teachers make, because that tells you which roles and lists you need at full scale.
At the end, decide using written criteria you set at the start, such as zero lost tablets without a response, teachers using the lock weekly and no parent complaints that remain open. Not available yet: attendance from the tablet and school ERP integration, so do not judge it against those.
A practical tip: tell the pilot families it is a pilot and that rules may change. People are generous about a pilot that is described as one.