I think a checklist is a great idea. Our culture and structure are not conducive to "thou shall" or "thou shall not", hence we've been developing checklists for different stages & activities of IT procurement.
Two areas that are particularly worrying about click agreements;
1. University data protection
2. IT Accessibility (if the app is intended for student, instructional, workgroup, public, etc., use)
Anyone here who executes a contract is required to obtain prior General Counsel Office approval (institution-wide, not just IT). However, in practical terms, GC wouldn't be able to handle all the approval requests for click-agreements. Hence, GC asks folks to consider the risks associated with click-agreements, and approach GC for review if warranted, before clicking.
Director, Architecture/Service Management
University of Maine System
[log in to unmask]
How do you handle click-agreement for software? Volume and cost are two considerations (e.g., one user installs a freeware application vs Blackboard student agreement). We looking at developing a short checklist (3-5 items) for the user to review before clicking/accepting. If the agreement meets the checklist requirements, it’s OK. If not, the agreement may need additional review.
David M. Antonacci, PhD
Associate Vice Chancellor, Chief Information Officer
University of Kansas Medical Center
Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss.