SFS Essential Competencies/ Skills

ESSENTIAL COMPETENCIES

Please click the link to view resources developed to develop an understanding of the Essential Competencies and how they can be used to enhance learning. Resources include: 

• Competencies / skills definitions, standards and links to IB Learner Profile
• A student friendly version
• Posters
• Articles and videos to promote the importance of developing these skills in 21st Century learners
• Examples per subject
• Assessment rubrics

Thinking Technology? Think SAMR!

School Posting Policy

If content can potentially be shared with the world

• teachers have a responsibility to check that what is being posted by their students follows these guidelines.
• there should not be enough information to contact a student.

School accounts are for school material. Students should know that teachers and administrators have the ability to change passwords and access school accounts.

Students should:

• not share personal information.

Ask yourself: Could someone contact me based on this information?

• know who they’re communicating with.

Ask yourself: Who is going to look at this, how are they going to interpret it, and how am I representing myself and my school?

• treat other people the way they want to be treated.

Ask yourself: Is this inappropriate, immature or bullying?

• use appropriate language and proper grammar and spelling.

Ask yourself: Would I want this to be graded for proper grammar and spelling?

• properly cite the creator of an original work.

Ask yourself: Who is the original creator of this work?

• know how to give constructive feedback.

Ask yourself: Is it True, Helpful, Inspiring, Necessary, Kind? (THINK)

These guidelines are based on International School of Bangkok Blogging Guidelines.

adoption date: November 2012

review date: November 2013

Policy Writing Policy

• Final policy should be 1 side of A4.

• Tech sub-committee (2 or 3 people) writes draft policy.

• Whole Tech team edits.

• Send to all relevant staff for feedback - tell staff feedback will be considered.

• Tech sub-committee considers feedback.

• Whole Tech team edits.

• Consider giving a specific opportunity to admin team to edit.

• Adopt - include adoption date and review date.

• Plan to review on review date.

adoption date: January 2012

review date: January 2014

NOTES FOR REVIEW

Google Chrome notes

New Core Tool policy