School data security: shared rules for student data, devices, and parent messages

Learning & Education

School data security: shared rules for student data, devices, and parent messages

Intermediate | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)

Intermediate: Method names appear, but the whiteboard explains the key points. Use the examples as a guide and fill it in, thinking it through for your own situation.

This school data security template helps teachers and staff at schools, tutoring centers, and lesson studios follow one set of rules for student records, shared devices, and parent messaging. The hard moments are finishing grades at home, handing a shared tablet to the next person, replying to one family in a parent group, and posting event photos. You list each kind of data with where it is kept, who sees it, and when it is deleted, then write what happens, how to check, and how to prevent it for each pitfall. Draft rules are sorted with MoSCoW (Must, Should, Could, Won't), and the Musts are ranked by impact and likelihood. To start, open the sharing settings of your grades file and look at who can open it, which starts the first row of the table. It also covers briefing newcomers, checks around events, graduation and withdrawal, and incident contacts. The whiteboard has 4 pages, and the task board has 5 columns with 4 parent tasks of 3 subtasks each.

0 Likes 0 Copies Author: WeProcess
information security school student data shared devices parent communication
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Read the whiteboard text as plain text

School Data Security

How to use (4 pages): ① Write the purpose and a table of location, viewers, and deletion timing (frames①–⑤) → ② List risky moments, pitfalls, and the photo rule (frames⑥–⑩) → ③ Pick draft rules with MoSCoW, then set the order and how to brief people (frames⑪–⑮) → ④ Write event checks, exit steps, and contacts (frames⑯–⑱)

1/4 List the data

① Why we set rules (start here)

  • Why we decide e.g. Each teacher handles grades and messages differently, and nobody knows whom to ask
  • Scope e.g. Our staff room and two classrooms. 8 teachers, 2 office staff, 3 volunteers
  • Who decides and by when e.g. The vice principal and the IT lead draft it, and the next staff meeting decides

② Data table (location, viewers, deletion timing)

Location Viewers Deletion timing Taking out
Grades and evaluations e.g. Shared staff folder e.g. Homeroom teacher and academic affairs staff e.g. When the retention period set by the school ends (for records the law requires you to keep, check the latest guidance) e.g. No. Open only on school PCs
Contacts and addresses e.g. Roster in the messaging tool e.g. Homeroom teacher and office staff e.g. End of the month the student leaves e.g. Paper rosters never leave the staff room
Photos and videos e.g. Event folder in the school cloud e.g. The teacher who took them and the PR lead e.g. Choose and keep at the end of the year e.g. Never kept on personal phones
Health and special needs e.g. Locked cabinet and a folder with limited viewers e.g. Homeroom teacher and school nurse e.g. When the set retention period ends (for items with a legal retention period, such as health checkup records, check the latest guidance) e.g. No

③ Student data

  • e.g. Grades, attendance, test papers
  • e.g. Special needs such as allergies
  • If data is missing from table ②, add it there too

④ Parent data

  • e.g. Phone numbers, email addresses, home addresses
  • e.g. Meeting records and family circumstances
  • If data is missing from table ②, add it there too

⑤ Staff data

  • e.g. Contact details of teachers, office staff, and volunteers
  • e.g. Accounts for shared devices and the messaging tool
  • If data is missing from table ②, add it there too

2/4 List the risky moments

⑥ Moments when the data in ② could be at risk

  • Student and parent data reaches other people
    • Taking data out e.g. Finishing grades at home
    • Shared devices e.g. Handing one to the next person after class
    • Parent messages e.g. Replying to one family
    • Photos and videos e.g. Posting event photos
    • Shared accounts e.g. 3 teachers use a single ID
    • Graduation and withdrawal e.g. Rosters and photos are left behind

⑦ Pitfall: taking grade files home on a personal USB drive

  • What happens: e.g. A USB drive is dropped on the train home, and the grades of the whole class may end up with a stranger
  • How to check: e.g. Ask the device manager whether personal USB drives are blocked by a setting, and look at the take-home log
  • Current state: e.g. At the end of term, 2 people did grading at home
  • How to prevent it: e.g. Work at home only by a method the school approves, and never use a personal USB drive

⑧ Pitfall: forgetting to log out on a shared device

  • What happens: e.g. The next student to sit down can open the messaging tool or grade screen of the teacher before
  • How to check: e.g. After class, look at whose name is still logged in on the browser and the messaging tool
  • Current state: e.g. 1 of the 3 classroom PCs was still logged in under a teacher name
  • How to prevent it: e.g. Log out when you finish, and shorten the time before the screen locks automatically in the device management console

⑨ Pitfall: sending a personal message to the parent group

  • What happens: e.g. News about one family, such as an absence or grades, becomes visible to every parent in the class
  • How to check: e.g. Check the recipient name and head count before sending, and review the messaging tool send log once a week
  • Current state: e.g. A personal reply was posted to the group once this year
  • How to prevent it: e.g. Send personal matters as individual messages, and use the group only for notices to everyone

⑩ Pitfall: how far event photos are shown (write the photo rule)

  • What happens e.g. The face of a student whose family declined appears on a page anyone can see
  • How to check e.g. Compare the consent list with the visibility setting of the place where photos are posted
  • How to prevent it (the photo rule) e.g. Check the consent list before posting. Show photos to parents only, and never post photos where a name tag is visible

3/4 Choose the rules

⑪ MoSCoW (sort draft rules from the preventions in ⑦ to ⑩)

Must Required
  • e.g. Grade files are never taken out on personal USB drives
Should Should do
  • e.g. Give out a list of the methods the school approves for working at home
Could If possible
  • e.g. Have a second person check the recipients before parent messages go out
Won't Not this time
  • e.g. Replace every classroom device this school year

⑫ Rank the Musts from ⑪ (impact × likelihood)

Vertical axis: Impact (bigger toward the top) / Horizontal axis: Likelihood (more likely toward the right)

  • Be prepared High impact but unlikely. e.g. A photo of a student whose family declined appears on a public page. Set a step to check the consent list before posting
  • Decide first High impact and likely. e.g. Taking grades home on personal USB drives. Decide at the next staff meeting
  • Decide later Low impact and unlikely. e.g. Names left on wall displays. Decide during the year
  • Make it a routine Low impact but likely. e.g. Forgetting to log out. Add it to the end-of-class routine

⑬ Briefing a new teacher

  • e.g. On the first day, explain table ② and the Musts from ⑪ in 10 minutes
  • e.g. Log out of a shared device together
  • e.g. At the end of week 1, ask if anything was difficult

⑭ Briefing a part-time teacher

  • e.g. Before the day they handle grades, explain the rule against taking them out
  • e.g. Give them their own account instead of a shared ID
  • e.g. Decide in advance the day their account is stopped when they leave

⑮ Briefing a volunteer

  • e.g. Give a role that does not involve student rosters or grades
  • e.g. No photos. If photos are needed, take them on a school device
  • e.g. On day 1, hand over the photo rule from ⑩ on one sheet of paper

4/4 Run it through the year

⑯ Check the rules in the order decided in ⑫ at each school event

What to check Where to look Owner
Start of the year e.g. Create accounts for new people and stop those of people who left e.g. Member list in the messaging tool console e.g. Vice principal and classroom manager
Around events e.g. Whether consent covers the newly enrolled students e.g. Consent list and the photo visibility setting e.g. PR lead
End of term e.g. Whether grade files exist only in the decided location e.g. Sharing settings screen of the shared folder e.g. Academic affairs teacher
End of the year e.g. Whether device updates have stopped, and data whose deletion time in ② has come e.g. Device update log and a check with the vendor e.g. IT lead

⑰ Handling data at graduation or withdrawal

  1. List it out From table ②, write down every place that holds that student's data e.g. Grade files, the messaging tool roster, the photo folder
  2. Hand over or keep Separate what goes to the student from what the school keeps e.g. Return their work to them. Check the school rules or the latest guidance for what to keep and for how long
  3. Delete Delete what has reached its deletion time e.g. Remove the parents from the messaging tool roster and from the group
  4. Record Write who deleted what and when e.g. In the withdrawal log, write what was deleted and the owner name

⑱ Contacts after an incident

  • Who to tell first e.g. If you notice a loss or a wrong send, phone the vice principal (classroom manager) on the spot
  • Outside contacts e.g. The help desk of the device or cloud vendor, and the contact at headquarters or the school operator. Check the latest guidance for who must be told
  • What to record e.g. When, what, whose data, and what you did on the spot. Write in the order you noticed

Task board contents

Not started 16 items

List the data

On page 1, write why you are making rules, then turn the student, parent, and staff data you handle into a table of location, viewers, and deletion timing. This table feeds every later page. Press Ctrl+F (⌘F on Mac) and enter 3/4 to jump to page 3.

Locate grade files

A job for a free slot after school. Open the sharing settings of the file that holds grades (a shared folder or the school system), look at who can open it, and write the location and viewers in the Grades and evaluations row of frame ②. When these two cells are filled, you are done.

Fill in the table

In frame ① write why you are deciding, the scope, and who decides by when, then fill the rest of the Grades and evaluations row of frame ② and the other 3 rows. Write "to check" in any cell you do not know and add an owner name to finish.

Sort into 3 groups

In frames ③ to ⑤, sort the data from table ② into students, parents, and staff. If you find data that is missing from ②, add it to the table too.

List risky moments

On page 2, list the moments when the data in ② could be at risk, and for each pitfall write what happens, how to check, and how to prevent it (also the current state for ⑦ to ⑨). The preventions written here become the draft rules on page 3.

Branch out risks

In the 6 branches of frame ⑥, have teachers and staff add one thing that happened or could happen in each situation.

Check 3 pitfalls

Rewrite the sticky notes in frames ⑦ to ⑨ while looking at the registers, the settings screens, and the send log of the messaging tool. When the current state of all 3 frames shows what really happens, you are done.

Write photo rules

In frame ⑩, write what you found by comparing the consent list with the visibility setting, and a draft photo rule.

Choose the rules

On page 3, choose draft rules from the preventions on page 2, then decide what to settle first and how to brief people who are new. This parent task is for starting with the Musts instead of deciding everything at once.

Sort with MoSCoW

In frame ⑪, sort the preventions from ⑦ to ⑩ into Must, Should, Could, and Won't. Narrow the Musts to 4 or fewer to finish.

Set the order

In frame ⑫, rank the Musts from ⑪ by impact and likelihood, and take the ones in the top right to the next staff meeting.

Brief newcomers

In frames ⑬ to ⑮, write when, what, and how you will check and explain things to new teachers, part-time teachers, and volunteers.

Run it each year

On page 4, build a table for checking the rules at each school event, the steps for data at graduation or withdrawal, and incident contacts. Track the checks you decided in the Check each year column.

Build event checks

In the table of frame ⑯, write what to check and who owns it at the start of the year, around events, at the end of term, and at the end of the year. When all 4 rows have an owner name, you are done.

Set exit steps

In the 4 steps of frame ⑰, write what to list out, hand over or keep, delete, and record. Check the school rules or the latest guidance before writing how long to keep things.

Write contact list

In frame ⑱, write who to tell first, who to contact outside, and what to record, then post it where everyone can see it. When phone numbers are in, you are done.

Writing it out 0 items

Discussing with staff 0 items

Made a rule 0 items

Check each year 0 items

← Back to templates

Preview mode School data security: shared rules for student data, devices, and parent messages

Whiteboard preview

① Why we set rules (start here) ② Data table (location, viewers, dele... ③ Student data ④ Parent data ⑤ Staff data ⑦ Pitfall: taking grade files home on... ⑧ Pitfall: forgetting to log out on a... ⑨ Pitfall: sending a personal message... ⑩ Pitfall: how far event photos are s... ⑫ Rank the Musts from ⑪ (impact × lik... Be prepared Decide first Decide later Make it a routine ⑬ Briefing a new teacher ⑭ Briefing a part-time teacher ⑮ Briefing a volunteer ⑯ Check the rules in the order decide... ⑰ Handling data at graduation or with... ⑱ Contacts after an incident School Data Security How to use (4 pag... Data to protect a... Rules and checks Pitfalls and risk... Briefing and keep... 1/4 List the data Ctrl+F / ⌘F : 2/4... → 2/4 2/4 List the risky mo... ↙ 3/4 Why we decidee.g. Each teacher handles grades and messages differently, and nobody knows whom to ask Scopee.g. Our staff room and two classrooms. 8 teachers, 2 office staff, 3 volunteers Who decides and by whene.g. The vice principal and the IT lead draft it, and the next staff meeting decides Location Viewers Deletion timing Taking out Grades and evalua... e.g. Shared staff folder e.g. Homeroom teacher and academic affairs staff e.g. When the retention period set by the school ends (for records the law requires you to keep, check the latest guidance) e.g. No. Open only on school PCs Contacts and addr... e.g. Roster in the messaging tool e.g. Homeroom teacher and office staff e.g. End of the month the student leaves e.g. Paper rosters never leave the staff room Photos and videos e.g. Event folder in the school cloud e.g. The teacher who took them and the PR lead e.g. Choose and keep at the end of the year e.g. Never kept on personal phones Health and specia... e.g. Locked cabinet and a folder with limited viewers e.g. Homeroom teacher and school nurse e.g. When the set retention period ends (for items with a legal retention period, such as health checkup records, check the latest guidance) e.g. No e.g. Grades, attendance, test papers e.g. Special needs such as allergies If data is missing from table ②, add it there too e.g. Phone numbers, email addresses, home addresses e.g. Meeting records and family circumstances If data is missing from table ②, add it there too e.g. Contact details of teachers, office staff, and volunteers e.g. Accounts for shared devices and the messaging tool If data is missing from table ②, add it there too ⑥ Moments when th... Student and parent data reaches other people Taking data out e.g. Finishing grades at home Parent messages e.g. Replying to one family Shared accounts e.g. 3 teachers use a single ID Shared devices e.g. Handing one to the next person after class Photos and videos e.g. Posting event photos Graduation and withdrawal e.g. Rosters and photos are left behind What happens: e.g. A USB drive is dropped on the train home, and the grades of the whole class may end up with a stranger How to check: e.g. Ask the device manager whether personal USB drives are blocked by a setting, and look at the take-home log Current state: e.g. At the end of term, 2 people did grading at home How to prevent it: e.g. Work at home only by a method the school approves, and never use a personal USB drive What happens: e.g. The next student to sit down can open the messaging tool or grade screen of the teacher before How to check: e.g. After class, look at whose name is still logged in on the browser and the messaging tool Current state: e.g. 1 of the 3 classroom PCs was still logged in under a teacher name How to prevent it: e.g. Log out when you finish, and shorten the time before the screen locks automatically in the device management console What happens: e.g. News about one family, such as an absence or grades, becomes visible to every parent in the class How to check: e.g. Check the recipient name and head count before sending, and review the messaging tool send log once a week Current state: e.g. A personal reply was posted to the group once this year How to prevent it: e.g. Send personal matters as individual messages, and use the group only for notices to everyone What happense.g. The face of a student whose family declined appears on a page anyone can see How to checke.g. Compare the consent list with the visibility setting of the place where photos are posted How to prevent it (the photo rule)e.g. Check the consent list before posting. Show photos to parents only, and never post photos where a name tag is visible 3/4 Choose the rules → 4/4 4/4 Run it through th... ⑪ MoSCoW (sort dr... MustRequired e.g. Grade files are never taken out on personal USB drives ShouldShould do e.g. Give out a list of the methods the school approves for working at home CouldIf possible e.g. Have a second person check the recipients before parent messages go out Won'tNot this time e.g. Replace every classroom device this school year Vertical axis: Im... High impact but unlikely. e.g. A photo of a student whose family declined appears on a public page. Set a step to check the consent list before posting High impact and likely. e.g. Taking grades home on personal USB drives. Decide at the next staff meeting Low impact and unlikely. e.g. Names left on wall displays. Decide during the year Low impact but likely. e.g. Forgetting to log out. Add it to the end-of-class routine e.g. On the first day, explain table ② and the Musts from ⑪ in 10 minutes e.g. Log out of a shared device together e.g. At the end of week 1, ask if anything was difficult e.g. Before the day they handle grades, explain the rule against taking them out e.g. Give them their own account instead of a shared ID e.g. Decide in advance the day their account is stopped when they leave e.g. Give a role that does not involve student rosters or grades e.g. No photos. If photos are needed, take them on a school device e.g. On day 1, hand over the photo rule from ⑩ on one sheet of paper What to check Where to look Owner Start of the year e.g. Create accounts for new people and stop those of people who left e.g. Member list in the messaging tool console e.g. Vice principal and classroom manager Around events e.g. Whether consent covers the newly enrolled students e.g. Consent list and the photo visibility setting e.g. PR lead End of term e.g. Whether grade files exist only in the decided location e.g. Sharing settings screen of the shared folder e.g. Academic affairs teacher End of the year e.g. Whether device updates have stopped, and data whose deletion time in ② has come e.g. Device update log and a check with the vendor e.g. IT lead List it outFrom table ②, write down every place that holds that student's datae.g. Grade files, the messaging tool roster, the photo folder Hand over or keepSeparate what goes to the student from what the school keepse.g. Return their work to them. Check the school rules or the latest guidance for what to keep and for how long DeleteDelete what has reached its deletion timee.g. Remove the parents from the messaging tool roster and from the group RecordWrite who deleted what and whene.g. In the withdrawal log, write what was deleted and the owner name Who to tell firste.g. If you notice a loss or a wrong send, phone the vice principal (classroom manager) on the spot Outside contactse.g. The help desk of the device or cloud vendor, and the contact at headquarters or the school operator. Check the latest guidance for who must be told What to recorde.g. When, what, whose data, and what you did on the spot. Write in the order you noticed → 2/4 List the risky mo... ↙ 3/4 Choose the rules → 4/4 Run it through th...
100%

Drag to move, scroll to zoom