1. Dave Mercer Monkeytree Creative Inc. November 19, 2011 Building a Policy Framework

2. What is Policy? A means of:  Defining intent  Ensuring consistency  Enhancing transparency  Clarifying/defining mandates  Limiting/resolving conflict  Facilitating continuity  Establishing/maintaining legitimacy

3. What it is NOT  Static – evolving through experience and necessity; policy needs to be amendable through clear mechanisms  Omnipotent – it is impossible to prepare for every conceivable eventuality – The “alien” model; –Creating non-specific policies where appropriate can provide legitimate flexibility if consistency is maintained

4. High-Level Policy – N.S. DGA  Amendments and regulations to the Degree Granting Act (1989)  Created before private universities were a reality in Canada  Changes required to plug gaping loopholes and define roles, responsibilities, requirements, procedures and penalties  Designed to protect students from unscrupulous private higher education providers  Modeled on Private Career Colleges Act and regs

5. N.S. DGA (cont.)  Need was perceived and addressed  Mechanisms created were based on the need and the intent (form follows function)  Other sources were utilized where possible – not necessary to reinvent the wheel  Clear mechanisms for administration of the Act and regs are contained within  Amendment more difficult than anticipated due to objection by Opposition critic

6. Website Policy  Definitions  Purpose  Roles, responsibilities  Regulatory (behavioral) sections – rules, privacy, copyright (policies subject to laws)  Dispute resolution (incl. penalties for misuse)  Technical sections (IT, support)  Maintenance (regular review, amendment procedures, by whom)

7. Next Steps  Timelines  Different types of functionality… Different policy requirements; multiple ‘models’?  What can we define/describe/establish now?  What can we prepare in advance?  What ‘templates’ can we use?  Input from stakeholders?  Who approves the final product?