KBT/Acceptable Use Policy

From AptivateOER

< KBT
Jump to: navigation, search
Contents
Contents
BMO Training KENET
Timetable
Training Objectives
Documentation
Appendix
Participants

View contents and print

[Edit contents] [Edit template]

A good Acceptable Use Policy should:

  • be short, clear, to the point
  • have good structure
  • have clearly defined terms
  • explain the consequences of not following the policy (the disciplinary process)
  • be created by an all-inclusive process
  • be well publicised and visible to users
  • be both accessible and visible
  • allow for exemptions, subject to approval in cases where the policy might not apply
  • be fair and not discriminate
  • be incorporated into other university documents eg employment contracts
  • be well researched (eg through a survey) and based on facts (eg bandwidth statistics)
  • be enforceable - have authority from on high
    • enforcement could be technical (eg blocking certain websites) or human (chat to user about it)
  • be updated regularly
  • have clear goals
  • be linked to a wider objective eg furthering education
  • be there for a good reason and the reasons should be explained to the users
Create a book