It’s 4:40 on a Thursday. A newer educator finds you in the office: a toddler in her room has a rash that wasn’t there at lunch. Does she call the parent? Does she write it down somewhere? Which app(s) does she use to document? You answer, the same way you answered that other educator in March, and for the educator before her.
Nothing went wrong. It’s just that your center’s procedure for a sick child exists in one place, and that place is your head. And a process that lives in someone’s head is only as reliable as whoever is on shift that day and remembers it.
A one-page standard operating procedure (SOP) fixes that. It’s not a binder. It’s one page per process, which a staff member can read in under a minute and follow without coming to find you.
Your Policy Manual Isn’t Doing This
Most licensed centers already have written policies. They’re expected to, at least in Alberta. The province’s licensing handbook lists an orientation process for staff with respect to the policies and procedures as part of the program plan. But a policy usually says what has to happen. It rarely says how it happens in your building, in what order, and by whom.
Take illness, for example. Alberta’s Early Learning and Child Care Regulation lists the signs of a sick child. They include vomiting, fever, diarrhea, or a new or unexplained rash or cough, needing more care than staff can give without compromising the other children, or any other symptom a staff member believes may mean the child poses a health risk to others on the premises. The parent must be contacted, and the child doesn’t return until the licence holder is satisfied they no longer pose a health risk.
What the Regulation doesn’t tell your educator at 4:40 is whether to call or message first, where to record what she saw, who decides when the child comes back, what proof you’ll ask for, and a multitude of other details.
Every center answers those questions a little differently. The SOP is where you write your answer down, so it’s the same answer every time.
What Fits on One Page
You don’t want anyone to be bogged down by a lot of text and detailed steps. So, aim for a one-page limit. If a procedure won’t fit, it’s safe to assume that it’s two procedures pretending to be one or a procedure with a bigger policy embedded in it.
| Section | What It Answers | Example: A Sick Child |
| Purpose | Why this process exists, in a sentence or two | Children showing signs of illness are identified, monitored, and communicated about with parents |
| Trigger | The specific event that starts it, and who notices | An educator observes symptoms during care hours |
| Finish line | What “done” looks like | Parents informed in writing, child sent home if needed, symptoms recorded |
| Frequency | How often it happens: daily, weekly, or whenever something occurs | Unpredictable (happens at random) |
| Steps | Four to eight steps, each starting with a verb and carrying a one-line reason | Observe, decide, message, call if worse… |
| Review record | Date, version, who reviewed it, what changed (for this particular SOP) | Version 1.0, initial creation |
Two sections matter more than they look:
- The trigger has to be an observable event, not a category. “When a child is sick” invites debate, while “when an educator observes symptoms” doesn’t.
- The finish line is the most-skipped line in any procedure. Without one, staff stop when they feel That’s how a phone call gets made and nothing gets written down.
Frequency deserves a thought as well. Daily processes train themselves through repetition. The ones that only come up now and then, like illness or license renewals are the ones people forget between occurrences. The SOP is particularly important for random events like illnesses.
What This Looks Like in Practice
The examples in that table come from a sickness-management process we documented with a previous client. It runs six steps:
- Observe the symptoms.
- Decide how to respond, using the symptom list.
- Send a written message through the center’s childcare management platform.
- Call the parents if the child gets worse.
- Receive a doctor’s note before the child returns.
- Upload the note to the child’s file.
Three things about it are worth copying, whatever process you’re documenting.
It makes decisions the Regulation leaves open. Message first, then call, and require a doctor’s note before return. Those are the center’s choices, not provincial requirements. The symptom list, by contrast, comes straight from the Regulation. Knowing which lines are which matters the day you revise the page.
Every step comes with a reason. The messaging step doesn’t just say “send a message.” It explains concisely that there must always be written proof the child was unwell, in case a parent later raises a complaint or licensing asks why the parents were contacted. A step with a reason attached is much harder to skip on a busy afternoon than a bare instruction.
It covers the grey areas. For an illness that isn’t on the list, the SOP sends staff to Health Link (811) with three specific questions to ask, instead of leaving it to guesswork.
We also pair our SOPs with color-coded flowcharts for staff who’d rather glance at a picture than read a paragraph. The chart and the page say the same thing, but the chart adds a nice visual layer.
How to Write Your First One
- Pick the question you keep answering. Your first candidates should be processes that caused the most “what do I do” moments last month.
- Write it by watching, not remembering. Ask whoever does the task best to walk you through it, and write down what they actually do. Your memory of a process is usually a tidier version than the reality.
- Draft the trigger and finish line before the steps. If you and your lead educator can’t agree where the process starts and ends, you’ve probably found the reason it goes wrong.
- Separate the rules from your choices. Mark which lines come from the Regulation or Alberta Health Services guidance and which are your center’s own decisions. The first kind can’t change without a source. The second kind you can change at a staff meeting.
- Test it on your newest staff member. Hand it over with no commentary and ask them to talk through what they’d do. Every question they ask points to a missing line.
- Put it where the work happens. A procedure sitting in a shared drive nobody opens isn’t documented. Put it somewhere people can easily access.
Keep it alive
A procedure that’s written once and never touched eventually becomes worse than no procedure at all, because it’s confidently wrong. Give every SOP a named owner and a review date. And review it early whenever one of these happens:
- The regulation or public health guidance changes.
- An incident shows the procedure didn’t hold up.
- You switch the software or system a step refers to.
- Staff tell you “we don’t actually do it that way anymore.”
That last one is useful information, not a complaint. Update the page, bump the version number, and log the change in the review record so everyone knows which version is current.
If you’re an owner: every process your director documents is one less thing that stalls when they’re away, and one less question that only you can answer. If you’ve ever wondered whether your center could run without you for a few weeks, this is where the answer starts.
Start with One
You don’t need a full procedures manual by Friday. You need one page for the question you answered three times this month. Write it, test it on someone new, and put it where the work happens. Then do the next one.
If you’d rather work through your first few with someone who has done it before, you can book a free call and we’ll be happy to talk it through.
