A library IT group pilots security automation on a single branch before enterprise rollout. What selection practice is that?

A library IT group that pilots security automation on a single branch before enterprise rollout is using pilot selection criteria to prove automation safely. One branch limits blast radius, produces real operational lessons with local staff, and builds evidence for directors before district-wide enablement. Civic automation failures are public and visible; staged pilots are how libraries learn without swapping a proving-ground pilot for a prioritization list of pilot automation candidates ranked by scored risk reduction measured for enterprise rollout. Why the other options fail by concept: Prioritizing pilot automation candidates by scored risk reduction measured for enterprise rollout is a prioritization exercise, not a pilot; it does not prove automation on one branch before district-wide rollout. Evaluating pilot vendor platforms with scored feature checklists before enterprise rollout decision is a procurement exercise, not a pilot; it does not select a branch or prove automation in operations. Selecting enterprise rollout automation targets with broad criteria before pilot branch validation puts enterprise selection before pilot validation; it does not prove automation on one branch before district-wide rollout. Exam caveat: A pilot must be representative enough to matter—choose a typical branch with normal ticket mix, not only the quietest site that cannot reveal failure modes. Operational check: define success metrics for the branch pilot (false isolation rate, enrichment dwell time, staff feedback), run for an agreed period, and require a go/no-go review before expanding playbooks to the rest of the library system.