School social media has a constraint almost no other account has: most of the best content contains children. That single fact changes the workflow more than anything about platforms or posting times, so this guide starts there rather than with content ideas.
Nothing here is legal advice. Consent rules differ by country and by district, and your own safeguarding policy overrides anything below.
How should photo consent work in practice?
The policy is usually already written. The problem is that it lives in a filing cabinet and the person posting is a teacher with ten minutes.
What makes it workable:
- A current list, not a form from September. Whoever posts needs to know today which children cannot be photographed. A list that lives in an office is a list that gets guessed at.
- Consent recorded per child, checked before publishing, not after. Removing a photo after a parent complains is not the same as never posting it, and everyone involved knows that.
- Different levels for different uses. Many families are comfortable with a class photo on the school website and not with a named child on a public platform. Treat those as separate permissions, because they are.
- A default of no faces when in doubt. Hands, work, the back of a room, the finished project. A surprising share of good school posts contain no identifiable child at all.
The practical rule that saves the most trouble: never name a child in a caption on a public platform, even where a photo is permitted. A name plus a face plus a location is a different thing from a photograph.
Who should be allowed to post?
Fewer people than want to, and more than one.
A single administrator holding all the accounts means nothing gets posted during their leave and the school loses access if they leave the job. Every teacher having the password means an account nobody controls.
The workable arrangement is a small group who can draft and a smaller group who can publish. Departments, sports teams and trips send in photos and a sentence. One or two people check the consent list and publish. That is one gate, staffed, rather than twenty people each making a judgement call under time pressure.
Access should be delegated rather than shared. Roles on the Page and on the Google account, not a shared password in a staff document, and access removed the week a person leaves rather than the term after.
What should a school actually post?
The audience is mostly current parents, with prospective parents and alumni behind them. That means the useful posts are less exciting than the ones people want to make.
| Post type | What it does | How often |
|---|---|---|
| Practical notices: closures, timings, deadlines | The most read posts you will publish, by a distance | As needed, and repeated |
| Student work and projects | Shows the school working, often without faces | Weekly |
| Events and trips | Reaches families who were not there | After each one |
| Staff introductions | Builds the relationship parents actually want | Monthly |
| Achievements | Genuine pride, but do not let it become the whole feed | As they happen |
| Admissions and open days | The one properly promotional thing | Seasonal, planned early |
A note on the first row: do not treat a snow closure or a changed pickup time as beneath the account. Those posts get read by everyone and they are why parents follow the page at all.
How do you plan around the academic year?
A school year is the most predictable calendar in social media, which is an advantage almost nobody uses.
The dates you already know a year ahead: term starts and ends, open days, exam periods, sports days, concerts and productions, holidays, results days, and admissions deadlines. That is a substantial part of a year’s posts, and it can all be drafted in the quiet weeks rather than the busy ones.
A workable rhythm:
- Batch the predictable during the summer. Term dates, open day reminders, welcome-back posts, the admissions sequence.
- Leave two slots a week open for whatever actually happened that week.
- Front-load September and the admissions window, which are the two periods with no spare capacity at all.
The holiday calendar tool covers the general dates, and how to plan a month of content is the general version of the batching approach.
What about a bad day?
Every school has one eventually: an incident, a rumour, a local news story, an angry thread in the comments.
Decide in advance, while nothing is wrong:
- Who speaks. One named person, usually the head, and nobody else.
- What pauses. Scheduled posts should stop the moment something happens. A cheerful sports photo publishing itself an hour after an incident is the most avoidable communications failure there is, and it happens because nobody remembered the queue.
- Where the answer lives. Usually the school website or a direct message to parents, with social pointing to it rather than hosting the discussion.
- Comment policy. Published in advance, applied consistently, and never invented mid-argument.
The pause point is worth repeating because it is specific to scheduling. If you queue posts in advance, and you should, you need to know how to empty that queue in two minutes.
The short version
- Consent first, checked before publishing, with a current list the poster can actually see.
- Never name a child alongside a photograph on a public account.
- Several people draft, one or two publish, access delegated and revoked properly.
- Practical notices outperform everything else. Post them without embarrassment.
- Batch the academic year in the summer, and know how to pause the queue on a bad day.
Scheduling a school year in advance
The two things a school needs from a scheduler are unusual: a way to hold a post until somebody has checked it, and a way to stop everything at once.
BulkPublish covers both. A post can be held for approval so a draft from a department cannot publish until whoever holds the consent list has said yes, and scheduled posts sit in a queue that can be paused or cleared rather than firing regardless. Recurring posts handle the reminders that repeat every term, and the photographs are uploaded once and checked against each network’s size and format rules before anything is queued.
The pricing page lists what each plan connects, and most schools need three or four accounts rather than thirty.