<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by MySchool on Medium]]></title>
        <description><![CDATA[Stories by MySchool on Medium]]></description>
        <link>https://medium.com/@MySchool?source=rss-ccebd1ef16c5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*I2LrYft5-KtUUiS3YiAZ0A.png</url>
            <title>Stories by MySchool on Medium</title>
            <link>https://medium.com/@MySchool?source=rss-ccebd1ef16c5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:11:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@MySchool/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why Schools Stay With School Management Systems They’ve Outgrown]]></title>
            <link>https://medium.com/@MySchool/why-schools-stay-with-school-management-systems-theyve-outgrown-b7809e4b3941?source=rss-ccebd1ef16c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7809e4b3941</guid>
            <category><![CDATA[edtech]]></category>
            <category><![CDATA[school-management]]></category>
            <category><![CDATA[canadian-education]]></category>
            <category><![CDATA[independent-schools]]></category>
            <category><![CDATA[school-management-system]]></category>
            <dc:creator><![CDATA[MySchool]]></dc:creator>
            <pubDate>Thu, 08 Oct 2026 14:31:52 GMT</pubDate>
            <atom:updated>2026-10-08T14:31:52.911Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0BzWSxDh2EXTWLEL5Vyiqg.png" /></figure><p><strong>A school can recognise that its management system is creating extra work and still decide to keep it.</strong></p><p>Knowing where the problems lie doesn’t automatically make replacing it feel like a good idea.</p><p>Your team has learned to use it. Someone knows how to get the reports right. A migration sounds expensive, disruptive, and difficult to fit into an already busy year. And who can guarantee that the next system will be better?</p><p>Those concerns deserve proper answers. But they also deserve proper examination.</p><p>What keeps schools attached to systems they’ve outgrown-and do those reasons always hold up when you consider the cost of staying?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ny7xUemvngNjxYei.png" /></figure><h3>Reason #1: “We’ve already put so much into this”</h3><p>Your current system represents more than a subscription fee.</p><p>Someone configured the records, built the templates, and worked out how to produce the reports your school needs. Staff attended training, learned through experience, and eventually became comfortable. Some of that work may have taken years.</p><p>So when someone suggests replacing the system, the obvious question is: <em>Are we really going to do all of that again?</em></p><p>Replacing it can feel like admitting that effort was wasted. <strong>But the time already spent cannot be recovered by keeping the system longer. </strong>What matters now is how much work each option will require in the years ahead.</p><p>If staying means repeating the same manual tasks every term, that earlier investment may be drawing your school into further expense.</p><p>Ask:</p><ul><li>How much staff time goes into maintaining and working around the current system each term-and what does that time cost?</li><li>What would a switch require, including staff time?</li><li>Which existing processes and decisions could carry over?</li></ul><p>A system should earn its place through what it enables today. But any proposal to replace it needs to account honestly for the work of getting there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xg5JJvriKs0IEcU6.png" /></figure><h3>Reason #2: “Our team already knows how to make it work”</h3><p>Most schools have someone who understands the system better than anyone else.</p><p>They know which export to use, which fields need checking, and why a report only works with a particular filter. Colleagues turn to them when something goes wrong. Their expertise keeps important work moving.</p><p>That person may be cautious about a replacement. They may defend a process that looks unnecessarily complicated to everyone else.</p><p>There are understandable reasons for that. They know what can go wrong. They have spent years solving problems that others barely see. And a change may unsettle a role in which they have become trusted and capable.</p><p>The workaround may be inefficient, but the knowledge behind it is valuable.</p><p>But how much of it is being used to compensate for the system?</p><p><strong>If routine work depends on their intervention, the school has a bottleneck.</strong> That person also carries a burden: every question, exception, and deadline finds its way back to them. Taking leave becomes harder when nobody else can confidently cover the work.</p><p>Bring that person into the assessment early. Ask them to show where the system needs help, what each workaround achieves, and what a replacement must handle reliably. Give them a meaningful role in shaping the change and time to learn the new system.</p><p>Their experience can help the school make a better choice. And a better system should give them more room to use that experience beyond keeping routine tasks on track.</p><h3>Reason #3: “What if the migration goes wrong?”</h3><p>Keeping the current system has a familiar cost. Replacing it creates a visible decision with someone’s name attached.</p><p>What happens if records don’t transfer correctly? If staff cannot complete an essential task? If the change disrupts reporting or leaves families confused? The person recommending a switch may worry that every problem will come back to them.</p><p><strong>Meanwhile, the extra work caused by staying is spread across the school and absorbed into ordinary routines: delays, corrections, dependence on individual staff, and time taken away from other work.</strong></p><p>It helps to examine both sets of risks. What could go wrong during a switch? What already goes wrong-or requires constant attention-under the current arrangement?</p><p>A credible proposal needs clear agreement on the problems the change should solve, named owners across the affected teams, and staff time allocated to preparation, testing, and training.</p><p>Then ask how the migration risks would be managed:</p><ul><li>Who will check transferred data and test essential workflows?</li><li>Which school deadlines must the implementation plan accommodate?</li><li>What support will be available when problems arise?</li></ul><p>Clear answers won’t remove every difficulty. But a practical plan, backed by the people who control the budget and workload, can make the change far more manageable than the vague prospect of “moving everything to a new system.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*T1np31rdIZI_ewIR.png" /></figure><h3>Reason #4: “How do we know the next system will be better?”</h3><p>Perhaps your school has heard ambitious promises before. Perhaps the current system also looked straightforward in a demonstration.</p><p>Now your team knows how much complexity can sit behind a polished interface. They are right to ask whether a replacement will solve the problem or simply introduce different limitations.</p><p>That scepticism can protect your school from another disappointing purchase-provided it leads to closer examination.</p><p>Start with the tasks that currently cause trouble. Ask a prospective provider to demonstrate those specific workflows using realistic school scenarios:</p><ul><li>Can staff produce the report they actually need?</li><li>What happens when information changes halfway through a process?</li><li>Where will staff still need to export, re-enter, or check data?</li><li>What support will be available during implementation and afterwards?</li></ul><p>Ask about limitations as directly as capabilities. Where possible, speak with a school with similar requirements about implementation, everyday use, and support.</p><p>You don’t need certainty that every task will be effortless. <strong>You need credible evidence that the replacement will address the problems driving your search.</strong></p><h3>Give staying the same scrutiny as switching</h3><p>Competing priorities, staffing, or a difficult implementation window may affect when your school can switch. But <a href="https://www.trymyschool.com/blog/the-hidden-costs-of-fragmented-systems">postponing the change still has a cost</a>.</p><p>If you decide to wait, give that decision a clear basis and a review date.</p><p>Record the current costs, the concerns about changing, and the evidence still needed. Agree on what would prompt another look: a recurring reporting problem, growing staff workload, or a requirement the system can no longer meet.</p><p>The question is whether your school has enough evidence to judge the cost of staying.</p><p>Count the recurring work. Involve the people who understand it. Turn migration worries into planning questions, and doubts about replacements into requirements that providers must demonstrate.</p><p>Your concerns may identify something that needs careful preparation. They may also rest on assumptions that no longer hold up.</p><p><strong>Before committing another year to your current system, ask yourself: what will that year cost?</strong> And what evidence do you need to make a better decision?</p><p><em>Originally published at </em><a href="https://www.trymyschool.com/blog/why-schools-stay-with-school-management-systems-theyve-outgrown"><em>https://www.trymyschool.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7809e4b3941" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fix the Process or Replace the School Management System? How to Tell Which Problem You Have]]></title>
            <link>https://medium.com/@MySchool/fix-the-process-or-replace-the-school-management-system-how-to-tell-which-problem-you-have-f8c816906e98?source=rss-ccebd1ef16c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8c816906e98</guid>
            <category><![CDATA[school-software]]></category>
            <category><![CDATA[canadian-education]]></category>
            <category><![CDATA[school-management-system]]></category>
            <category><![CDATA[edtech]]></category>
            <dc:creator><![CDATA[MySchool]]></dc:creator>
            <pubDate>Thu, 08 Oct 2026 14:28:38 GMT</pubDate>
            <atom:updated>2026-10-08T14:28:38.307Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ECOoea40m3JspVVFO3Z2cA.png" /></figure><p>When something keeps going wrong in school operations, there are two easy explanations.</p><p>The process is broken. Or the system is broken.</p><p>Both can be true. But they require very different fixes.</p><p>If the real problem is unclear ownership, inconsistent training, or a process nobody follows, replacing the software will simply move the same problem somewhere new. On the other hand, if the platform itself forces staff into duplicate entry, disconnected workflows, or manual workarounds, another procedure document will not solve much either.</p><p>Before changing either one, you need to know where the constraint actually sits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vI1IWykybGJMNj_a.png" /></figure><h3>Could this process work well in the system you already have?</h3><p>Pick one recurring piece of work that causes frustration. It could be updating <a href="https://www.trymyschool.com/what-we-do-sis">student information</a>, <a href="https://www.trymyschool.com/what-we-do-provincial-reporting">preparing reports</a>, <a href="https://www.trymyschool.com/what-we-do-admissions-and-enrollment">processing enrolment changes</a>, or <a href="https://www.trymyschool.com/what-we-do-communication">communicating</a> with families.</p><p>Then strip away the history around it and ask:</p><p><strong>If everybody followed the agreed process perfectly, could the work be completed efficiently using the tools you already have?</strong></p><p>That question separates a surprising number of process problems from system problems.</p><p>If the answer is yes, the issue may be training, ownership or process design.</p><p>If the answer is no — because somebody would still need to re-enter information, move data manually, maintain a separate spreadsheet or jump between systems — then the constraint is probably deeper.</p><p>Good process can make difficult work easier. What it cannot do is remove a limitation built into the technology.</p><h3>Signs that the process may be the problem</h3><p>Sometimes the software is capable of supporting the work, but the way it is being used has drifted over time.</p><p>One person does the task one way. Someone else has their own shortcut. Nobody is quite sure who owns a particular step. A new employee learns by watching whoever happens to be available. Features that would simplify the work exist but are not being used. Before long, the process exists mostly in people’s heads.</p><p>In those situations, replacing the platform can be nothing more than an expensive distraction.</p><p>Look for patterns such as:</p><ul><li>Different people using different methods for the same task</li><li>Steps being completed in the wrong order</li><li>Staff not knowing which information or system is authoritative</li><li>A process working well for experienced employees but poorly for newer staff</li><li>Problems disappearing once ownership and expectations are made clear</li></ul><p><strong>Those are clues that the process deserves attention first.</strong></p><p>Documenting the workflow, clarifying responsibility, and providing focused training may solve considerably more than a new platform would.</p><h3>Signs that the system may be the constraint</h3><p>But what if the process is already clear?</p><p>What if everyone knows what to do, follows the same steps, and still ends up doing extra work simply to get the job finished?</p><p>That is a different problem.</p><p>Perhaps information has to be entered in more than one place. A report can only be produced after somebody exports and reorganises the data. Two departments need the same information but cannot work from the same record. A workflow stops at a certain point because the system simply does not support the next step.</p><p>These are not necessarily failures of discipline.</p><p>They are signs worth investigating when:</p><ul><li>The same information has to be entered or checked repeatedly</li><li>Staff depend on spreadsheets because the system cannot hold or present what they need</li><li>Information has to be exported before it becomes useful</li><li>Teams maintain separate versions of the same information</li><li>Routine work requires moving manually between disconnected systems</li><li>A well-understood process still relies on workarounds to get finished</li></ul><p><strong>The important distinction is that these problems remain even when people follow the process correctly.</strong></p><p>You can document the workaround. You can train people to perform it consistently. You can even make it relatively efficient.</p><p>But it is still a workaround.</p><h3>Does the problem follow the person or the workflow?</h3><p>There is another useful way to diagnose the issue: look at where the problem appears.</p><p>Suppose one staff member consistently struggles with a task while everybody else completes it without much difficulty. <strong>That points towards training, role clarity or an individual process issue.</strong></p><p>Now suppose every person who takes responsibility for that workflow eventually creates the same spreadsheet, manual check or extra step.</p><p>That tells you something different.</p><p><strong>The workaround is not following the person. It is following the work.</strong></p><p>This is especially useful in schools where experienced staff have spent years making imperfect systems function remarkably well. Their knowledge can make structural limitations difficult to see.</p><p>When someone leaves, changes role or takes time away, what looked like a functioning process can suddenly become much more fragile.</p><h3>What would happen if you fixed the process perfectly?</h3><p>Before considering a system change, imagine that you solved every process problem you could.</p><p>Everyone receives proper training.</p><p>Every step has an owner.</p><p>The workflow is documented.</p><p>Everyone follows it consistently.</p><p><strong>Now ask: what work would still remain?</strong></p><p>If the recurring problem disappears, you probably had a process problem.</p><p>If staff would still be copying information, reconciling records, exporting data or maintaining parallel tools, you have identified something process improvement cannot remove.</p><p>That does not automatically mean replacing the entire system. The answer could be a configuration change, an integration, a different module or a smaller change to the technology you already use.</p><h3>Do not confuse a better workaround with a solved problem</h3><p>Schools are very good at making imperfect processes function.</p><p>Often, almost too good.</p><p>A spreadsheet becomes neatly organised. A manual check gets added to the monthly routine. Someone documents the export-and-import process carefully enough that another employee can follow it.</p><p>Those improvements matter. They reduce risk and make the day-to-day work easier.</p><p>But they can also make a structural problem easier to live with without actually removing it.</p><p><strong>The question is not simply, “Can we make this process work?”</strong></p><p>Most capable teams can.</p><p><strong>The better question is: “Should this work require these extra steps in the first place?”</strong></p><p>That is where the difference between process improvement and system change becomes much clearer.</p><h3>Fix the constraint, not the symptom</h3><p>Replacing technology every time a workflow becomes frustrating would be expensive, disruptive, and unnecessary.</p><p>But so is asking staff to keep refining a process that is fundamentally constrained by the tools underneath it.</p><p>The goal is not to prove that the process is broken. Nor is it to prove that the system is broken.</p><p>It is to identify the point where the unnecessary work begins.</p><p>If clearer ownership, better training, and a consistent workflow remove the problem, fix the process.</p><p>If the unnecessary work remains even after those things are in place, look at the system.</p><p>Sometimes the answer really is a better process.</p><p>And sometimes the process has already been doing everything it can. If the same limitations are still there, it may be time to look at the system underneath it.</p><p>MySchool is a unified school management system built for independent schools in Canada that want to bring student information, admissions, tuition, communications, reporting, donations, and day-to-day administration into one connected platform.</p><p><strong>If your current school management system is creating more work than it removes, see how MySchool could work as an alternative.</strong></p><p><em>Originally published at </em><a href="https://www.trymyschool.com/blog/fix-the-process-or-replace-school-management-system"><em>https://www.trymyschool.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8c816906e98" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The First 30 Days Back: Where School Operations Start to Crack]]></title>
            <link>https://medium.com/@MySchool/the-first-30-days-back-where-school-operations-start-to-crack-3e1d2bf2f28a?source=rss-ccebd1ef16c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e1d2bf2f28a</guid>
            <category><![CDATA[school-management-system]]></category>
            <category><![CDATA[schools]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[school-leadership]]></category>
            <category><![CDATA[school-principals]]></category>
            <dc:creator><![CDATA[MySchool]]></dc:creator>
            <pubDate>Fri, 25 Sep 2026 06:37:37 GMT</pubDate>
            <atom:updated>2026-09-25T06:37:37.352Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ld1SDfgBCmwp7gLHijyllA.png" /></figure><p>The first month of the new school year is a stress test for your school’s systems.</p><p>It is when things are gaining momentum again, information is moving between teams, and routines are being re-established.</p><p>At this stage, it is normal for some things not to be running at full efficiency yet. The start of a new year takes time. Responsibilities become clearer, processes find their rhythm, and teams adjust as the first few weeks unfold.</p><p>Some of the friction you are observing during this time may already feel familiar.</p><p>But that is the distinction worth making: <strong>what is simply part of the early weeks of a new school year, and what operational inefficiencies followed you from the last one?</strong></p><h3>Start with the workarounds</h3><p>Every school has some everyday operational friction: a process takes a little longer than expected, a new staff member needs help, or a message goes out twice because the first version had the wrong date on it.</p><p>A workaround is different.</p><p><strong>It is an extra step people introduce because the normal process does not get them where they need to go.</strong></p><p>It might mean:</p><ul><li>copying information from one system into another,</li><li>keeping a separate spreadsheet because the main record does not contain what is needed,</li><li>checking the same data in two places,</li><li>relying on one person who knows how to get around a limitation.</li></ul><p>The key difference is that everyday friction tends to reduce as routines become established. A workaround stays because people still need it to complete the task.</p><p>And if the same workaround has already returned this year, that is worth looking at more closely.</p><h3>Where the workarounds tend to appear in the first month</h3><p>The early weeks put pressure on a fairly predictable set of areas. These are the places to look while the detail is still fresh:</p><ul><li><strong>Student and family records. </strong>If the office spent the first week correcting information families had already provided, that information did not move on its own.</li><li><strong>Access for new staff. </strong>Waiting a few days for logins is an ordinary start-of-year delay. It becomes a workaround when a colleague quietly does the work on their behalf for a week.</li><li><strong>The first billing cycle. </strong>Amounts checked by hand before invoices go out, or payment plan changes from July reapplied manually.</li><li>And whether the numbers came out of the system, or someone had to export them and rebuild the report in a spreadsheet. This is also usually the earliest signal of how <strong>The first reports requested. </strong>provincial reporting season will go.</li><li><strong>Questions from families. </strong>The same question arriving fifty times normally means the answer sits somewhere families cannot reach, so it lands on the office instead.</li><li><strong>The desk everything routes through. </strong>In the first weeks, watch where requests concentrate. That tells you where knowledge is held by a person rather than a record.</li></ul><h3>Why workarounds harden into structure</h3><p>When systems are fragmented, they demand human bridges to connect them. Your team is resilient, so they build those bridges. They put in the hours, cross-check the data by hand, remember the exceptions, and the school runs smoothly for the families who rely on it.</p><p><strong>Because they succeed, it is very easy for school leadership to mistake a workaround for a working process.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ogvxcm2XMpI3ZDJH.png" /></figure><h3>Three signs your friction is structural, not seasonal</h3><p>To figure out what kind of problem you have, look at how the work is actually getting done this week. Structural friction leaves distinct footprints.</p><h4>1. The bottlenecks have the exact same names.</h4><p>Look at who is feeling the most pressure right now. Are they the same individuals who were overwhelmed during last year’s critical periods? If the start of term, report card season, fee collection, and re-enrolment always break the same way for the same people, the constraint is not the calendar. It is something in how the work is set up, and it did not arrive with this year’s students.</p><h4>2. The “temporary” fix is now documented.</h4><p>If you look closely at how your administrative office operates, you might find that the workaround has been quietly formalised. It is written on sticky notes, saved in a shared drive, or passed down verbally to new hires. Maybe everyone simply knows that there is one extra step you “always have to do.” When a workaround becomes part of a staff member’s onboarding, the school has accepted it as a permanent condition.</p><h4>3. The gaps have already reached families.</h4><p>Structural cracks rarely stay internal. If a family has already been asked to supply a medical form they submitted during admissions, or if a teacher is working from a different class roster than the front desk, your data is sitting in separate places. Families are generous about the occasional September slip. A pattern of misaligned information, though, quietly erodes their confidence that the school has its house in order.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jcb7qI-vTNXwIpby.png" /></figure><h3>What to do with this in September</h3><p>Write the workarounds down while they are still easy to see, with a note on what the normal process could not do, who stepped in, and roughly how long it took.</p><p>That list raises one question, and it is the one worth carrying into October: is each item a process problem or a system one?</p><p>Some workarounds exist because a process was never clearly defined, or because nobody was trained on the part of the system that would have handled it. And some are there because the technology that would do the job does not exist at the school.</p><p>There is an honest way to tell those apart from the rest, and we will go through it shortly in our next article.</p><p><em>Originally published at </em><a href="https://www.trymyschool.com/blog/first-30-days-back-where-school-operations-start-to-crack"><em>https://www.trymyschool.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e1d2bf2f28a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Seven Things To Handle In September: A Head of School Checklist]]></title>
            <link>https://medium.com/@MySchool/seven-things-to-handle-in-september-a-head-of-school-checklist-643cdd50d0a7?source=rss-ccebd1ef16c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/643cdd50d0a7</guid>
            <category><![CDATA[school-management-system]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[canada]]></category>
            <category><![CDATA[school-leadership]]></category>
            <category><![CDATA[schools]]></category>
            <dc:creator><![CDATA[MySchool]]></dc:creator>
            <pubDate>Fri, 25 Sep 2026 06:37:24 GMT</pubDate>
            <atom:updated>2026-09-25T06:37:24.442Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Pwj1d7yC2WGgBDpWnm2Gg.png" /></figure><p>The start of a school year is busy, and there is no version of it that isn’t. You already know that.</p><p>What is easy to miss is that it is also one of the better moments in the year to sit down and look at what is coming. The term hasn’t taken on its own momentum yet, decisions are still relatively open, and there is usually a little more room to move things than there will be in a month.</p><p>An hour spent this way tends to save considerably more later, because a good deal of what turns into stress in October and November is simply work that needed to begin in September and didn’t.</p><p>Here are seven things worth going through before the term gathers pace.</p><h3>1. Put the next six weeks on one calendar</h3><p>Not just events. Put everything with a date attached to it in one view.</p><p>Board meetings. Reporting deadlines. Parent evenings. Tuition dates. Admissions activity. Professional development. Trips. Major communications. Anything leadership will need to prepare, approve or contribute to.</p><p>Then scan the whole period (rather than looking at one week at a time) to have a bigger picture and better perspective of what’s to come.</p><h3>2. Work backwards from the dates that matter</h3><p>Once the dates are visible, identify the things that cannot simply be dealt with when they arrive. Some dates have two or three weeks of work behind them.</p><p>If a board meeting is in four weeks, when does the information for the report need to be ready?</p><p>If families need something by the end of the month, when does the team need to start preparing it?</p><p>If an event requires several departments, when does coordination need to happen?</p><p>For the biggest items, write down the next action, the date it needs to happen, and who is doing it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7DH3W2Io_NVbhhxd.png" /></figure><h3>3. Ask your leadership team what they need from you</h3><p>A quick conversation can surface things that will never appear on your own checklist.</p><p>Ask each person responsible for a major area of the school:</p><p>What will you need from me before the end of September?</p><p>It might be an approval, decision, introduction, budget sign-off, piece of information or simply time to talk something through.</p><p>Finding that out now gives everyone more room to work. The aim is to catch the things that are easy to postpone until they suddenly become urgent.</p><h3>4. Check that responsibilities are clear</h3><p>September is full of recurring jobs that everyone knows need to happen. Sometimes, however, nobody has explicitly confirmed who is doing them.</p><p>For the important work coming up, make sure you can answer:</p><p>Who owns it? When does it need to happen? Who else needs to be involved?</p><p>You do not need a new project plan for every task. “Sarah’s doing the report, Marcus sends her the enrolment numbers by Friday” is usually enough.</p><h3>5. Look at September from the family’s perspective</h3><p>Families are managing new schedules, activities, forms, payments, events and school information too.</p><p>Take a quick look at what they will need over the coming weeks.</p><ul><li>Have important dates been communicated?</li><li>Are instructions clear? Does a new parent know who to email when they are stuck?</li><li>Is there one message you could send this week that would stop the same question arriving fifty times?</li><li>Are there forms, permissions or reminders that would be better sent before everyone becomes busier?</li></ul><p>A little anticipation here can make September easier for both families and the school office. Every question you answer in advance is one your office does not have to answer on the phone.</p><h3>6. Check the everyday essentials one more time</h3><p>You have probably done this already, but September always shifts a few things.</p><p>Look at the student and family records, the timetable, the contact lists, and whether your new staff can actually get into the systems they need.</p><p>This does not need to become an audit.</p><p>Think of it as a final operational sweep before things start being used constantly.</p><h3>7. Keep some space in your own calendar</h3><p>Finally, look at your own calendar.</p><p>September will find ways to fill every empty space if you let it.</p><p>Reserve a few short blocks now for the work that is easy to postpone when the school gets busy: checking progress on upcoming deadlines, speaking with your leadership team, reviewing what is coming next and making decisions that require more time.</p><h3>Final thoughts</h3><p>Almost everything that feels urgent in October is work that needed to start in September and didn’t. To avoid emergencies in the upcoming months, it’s worth taking even a little bit of time now to be better prepared for the demanding time ahead.</p><p>It’s also worth checking whether you’ve had <a href="https://www.trymyschool.com/blog/three-conversations-head-of-school-before-new-school-year">the three conversations</a> that belong at the start of a year: with your team, with your board, and with yourself. Look at what broke last year, what it cost, and whether you’re prepared to go through it again this year.</p><p><em>Originally published at </em><a href="https://www.trymyschool.com/blog/7-things-to-handle-in-september-head-of-school-checklist"><em>https://www.trymyschool.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=643cdd50d0a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Three Conversations Every Head of School Should Have Before the New School Year]]></title>
            <link>https://medium.com/@MySchool/three-conversations-every-head-of-school-should-have-before-the-new-school-year-42fb4255f322?source=rss-ccebd1ef16c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/42fb4255f322</guid>
            <category><![CDATA[education]]></category>
            <category><![CDATA[schools]]></category>
            <category><![CDATA[school-leadership]]></category>
            <category><![CDATA[school-management-system]]></category>
            <category><![CDATA[head-of-school]]></category>
            <dc:creator><![CDATA[MySchool]]></dc:creator>
            <pubDate>Wed, 16 Sep 2026 09:28:05 GMT</pubDate>
            <atom:updated>2026-09-16T09:28:05.715Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nNqQbFyn0OQwmc0DtpZnqw.png" /></figure><p>There is a short window in late August when the previous school year already feels distant, but <strong>you can still remember what it took.</strong></p><p>You can still remember the report that took half a day to assemble, the admissions information that had to be checked across three places, the spreadsheet someone rebuilt because the numbers did not match, the process that stopped because the one person who knew how it worked was away.</p><p>By the end of September, that memory is gone. A new school year takes over, and it needs your attention. The pace picks up, immediate priorities move to the top of the list, and the <strong>same workarounds quietly return</strong> because there is no longer much time to question them.</p><p><strong>Whatever you leave unexamined now, you will work around until next June.</strong> Three conversations are enough to start changing that. Each is short, and each ends with something you can act on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vCJLAthYeQujKgry.png" /></figure><h3>1. With your team</h3><p><strong>The question: What broke under load last year?</strong></p><p>Start with the people who ran last year’s operations:</p><ul><li>your office manager,</li><li>your registrar,</li><li>whoever handles admissions,</li><li>someone from the business office,</li><li>a teacher involved in timetabling or reporting.</li></ul><p>The goal is not a general conversation about what was difficult. Schools are complex organisations, and every year contains busy periods, unusual requests, and problems nobody could have prevented.</p><p>You are looking for the places where <strong>your processes stopped holding when demand increased.</strong></p><p>Ask your team to think about the periods when the school was under the most operational pressure:</p><p><strong>What happened when the volume increased?</strong></p><ul><li>Which reports suddenly required manual work?</li><li>Where did people copy information from one system into another?</li><li>Which spreadsheets became essential?</li><li>Where were staff waiting for someone else before they could continue?</li><li>Which processes depended on one person knowing what to do?</li><li>Where did families have to supply information the school already held?</li></ul><p><strong>Separate the inconvenience from the pattern.</strong> A one-off error may simply be a mistake. A process that repeatedly requires staff to export data, reconcile conflicting records or maintain an unofficial spreadsheet is something else. So is a task that works well for most of the year but becomes unmanageable every time the school reaches a predictable busy period.</p><p>Those are the issues to capture.</p><p>Do not finish the conversation with “we should improve that next year.” <strong>Write the problems down while people still remember what happened. </strong>For each one, record:</p><ul><li>what staff were trying to do,</li><li>what made the normal process difficult,</li><li>what workaround they used,</li><li>who was affected.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hhkWlJlS9rlkx0yS.png" /></figure><h3>2. With your board</h3><p><strong>The question: What did it cost?</strong></p><p>The list from your team tells you where the school struggled. Your board needs the same information in a form it can act on, which means <strong>putting a number against it.</strong></p><p>Some costs are easy to find:</p><ul><li>overlapping subscriptions,</li><li>overtime,</li><li>temporary support,</li><li>additional tools brought in to keep a process moving.</li></ul><p><strong>Others are absorbed quietly through staff time:</strong></p><ul><li>hours spent re-entering information,</li><li>reconciling records,</li><li>rebuilding reports,</li><li>chasing missing data,</li><li>maintaining workarounds around systems that do not connect.</li></ul><p>If you have not put a figure on those costs yet, we walked through a simple method to do it in <a href="https://www.trymyschool.com/blog/the-hidden-costs-of-fragmented-systems">The Hidden Costs of Fragmented Systems: What Your Workarounds Are Really Costing You</a>. Start with a few recurring problems, estimate the staff hours they consume across the year, and apply a reasonable hourly cost. The result will not capture everything, but it will give you something concrete to discuss.</p><p><strong>Once the cost is visible, the conversation changes.</strong> “This process is frustrating” is easy to defer. A <strong>recurring cost in staff time, software, and lost capacity</strong> is something the board can weigh against the cost of fixing it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hDJ4Vr03avK8OY5e.png" /></figure><h3>3. With yourself</h3><p><strong>The question: Am I prepared to repeat the last school year?</strong></p><p>The third conversation is the shortest, but it is the one that determines whether anything happens next.</p><p>Look at the list, look at the cost, then ask yourself:<strong> if nothing changes, am I comfortable running another school year this way?</strong></p><p>There may be good reasons to answer yes. Some problems are temporary. Some can be solved through clearer processes, better training or a small internal change. Other priorities may matter more this year, and a major system change may not be realistic yet.</p><p><strong>But make that a conscious decision rather than letting September make it for you.</strong></p><p>Because there is another possible answer. Perhaps the same issues appeared in 2024/25 and again in 2025/26. Perhaps your team has already refined the workaround as far as it will go. Perhaps the school has grown, but the processes supporting it have not. Perhaps something that once felt mildly inefficient now consumes enough staff time to become a genuine operational constraint.</p><p>If that is what your evidence shows, the question changes. It is no longer “Could this be better?” It becomes,<strong> “Is this the year we finally do something about it?”</strong></p><p>That does not mean selecting new software tomorrow. It means <strong>giving the issue a real place on the school’s agenda this year: </strong>investigating the problem, understanding the options, and working out what change would require.</p><p>Without that decision, it is very easy to spend another year <strong>managing what you already know is not working.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iezKapRoH6boDorh.png" /></figure><h3>Three things to take into September</h3><p>You do not need a completed transformation plan before the school year begins. You need enough clarity to stop last year’s evidence disappearing beneath this year’s workload:</p><ol><li>Talk to your team and leave with a <strong>written record of what broke.</strong></li><li>Talk to your board and leave with an <strong>estimate of what that friction cost.</strong></li><li>Decide whether those are <strong>problems you are willing to absorb for another year.</strong></li></ol><p>September will bring plenty of new things to solve. The problems you already understand do not have to be among them.</p><p><em>Originally published at </em><a href="https://www.trymyschool.com/blog/three-conversations-head-of-school-before-new-school-year"><em>https://www.trymyschool.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42fb4255f322" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Choose a Student Information System for a Canadian Independent School]]></title>
            <link>https://medium.com/@MySchool/how-to-choose-a-student-information-system-for-a-canadian-independent-school-3284633353df?source=rss-ccebd1ef16c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3284633353df</guid>
            <category><![CDATA[independent-schools]]></category>
            <category><![CDATA[si]]></category>
            <category><![CDATA[k-12-education]]></category>
            <category><![CDATA[canadian-education]]></category>
            <category><![CDATA[k-12-school]]></category>
            <dc:creator><![CDATA[MySchool]]></dc:creator>
            <pubDate>Wed, 16 Sep 2026 09:24:18 GMT</pubDate>
            <atom:updated>2026-09-16T09:24:18.958Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UVkYu-oHNPrbHZwAcM5TzQ.png" /></figure><p>For a Canadian independent school, evaluate an SIS in this order: how well it fits your existing workflows, whether it supports your province’s reporting requirements, which country hosts your student data, how it connects to your other systems, how it performs for teachers and families, what implementation and migration involve, and the full multi-year cost.</p><p>Once your school has decided that its current systems are no longer working well enough, that list is the work ahead.</p><p>If you are still getting familiar with the role of an SIS, start with our <a href="https://www.trymyschool.com/blog/student-information-system-a-short-guide-for-k-12-independent-schools">Student Information System: A Short Guide for K-12 Independent Schools</a>. If you are already evaluating SIS software, here is what to look at before making a decision.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fN_SZ22OLW5hKSGg.png" /></figure><h3>1. How do you check if the SIS fits the way your school works?</h3><p>Feature lists can make very different student information systems look similar.</p><p>Most platforms will cover the basics: student records, attendance, grades, schedules and reporting. The more useful question is how well those functions support the work your staff complete every day.</p><p>Before comparing vendors, look at how information currently moves through your school. Follow a student record from application and enrolment through attendance, academics, tuition and graduation.</p><p>Look closely at the points where staff:</p><p>Independent schools also tend to have workflows that do not fit neatly into a standard template. Timetables, tuition structures, admissions processes, assessment models, bursaries and learning support can vary considerably between schools.</p><p>When vendors demonstrate their SIS, give them real scenarios from your school and ask them to show exactly how those processes would work.</p><h3>2. How should provincial reporting shape your SIS decision?</h3><p>For Canadian schools, provincial reporting deserves its own place in the evaluation, and the requirements differ in every province.</p><p>In Ontario, private schools submit information to the Ministry of Education through OnSIS and complete requirements such as the annual Notice of Intention to Operate a Private School. Schools may also work with OUAC and OCAS depending on the programmes and pathways they support.</p><p>British Columbia has its own reporting environment, including the 1701 Student Data Collection and the province’s Education Data Exchange.</p><p>A system that stores student information but cannot support the reporting processes your province requires will leave staff exporting records, reformatting files, rebuilding reports by hand and checking the results twice.</p><p><strong>Ask vendors:</strong></p><p>A demonstration of the reporting workflow itself is far more useful than a general statement that the system “supports Canadian schools.”</p><h3>3. Where will your student data be stored?</h3><p>An SIS contains some of the most sensitive information a school manages: student and family details, academic records, attendance information and, in some cases, financial, health or learning-support data.</p><p>Data residency and security should therefore be discussed early in the selection process.</p><p><strong>Ask prospective providers:</strong></p><p>Canadian hosting may also matter to your leadership team or board from a privacy, governance or data-residency perspective. Under PIPEDA and provincial privacy legislation, your school remains accountable for student information even when a vendor holds it.</p><p>The provider should be able to explain its security and privacy approach clearly, without relying on vague statements about being “secure” or “compliant.”</p><h3>4. How should the SIS connect with your other school systems?</h3><p>The SIS is the central student database. It is still only part of the technology environment of an independent school.</p><p>Admissions, tuition, parent communication, learning management, IEPs, donations and provincial reporting may all depend on the same student information. That makes the relationship between systems as important as the systems themselves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0xkFZnfIbyS3rpI-.png" /></figure><p>If these functions sit in separate products, find out how data moves between them. What happens when an applicant becomes an enrolled student? Does their information transfer automatically? If a parent changes an address, which systems are updated? Can finance, admissions and academic teams work from the same underlying record?</p><p>When evaluating an SIS, consider the wider environment it will sit within, not only the functions inside the student record.</p><h3>5. How do you test usability with the people doing the work?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qNXMWwomrf793VA5.png" /></figure><p>Teachers may need to take attendance quickly before class. Administrators may spend much of the day working on student records. Finance and admissions teams need different information again. Parents and students may interact with the platform through a portal or mobile app.</p><p>Include representatives from those groups when you evaluate shortlisted systems.</p><p>Ask vendors to demonstrate the common tasks your staff complete. See how many steps they take, whether information is easy to find and how clearly access can be controlled for different roles.</p><p>Look closely at the family experience too. If parents struggle to find grades, forms, messages or payment information, those problems come back to the administrative team as emails and support requests.</p><h3>6. What should you establish about implementation, migration, and support before signing?</h3><p>Choosing the software is only part of an SIS transition. Your existing records need to be moved, the platform needs to be configured, and staff need enough training to use it confidently.</p><p><strong>Before signing, establish:</strong></p><p>Support performance is worth examining in the same detail. Ask providers for median first response time, ticket resolution rate and client satisfaction figures. Where possible, speak directly with schools that have already completed an implementation with them.</p><h3>7. What does the SIS really cost?</h3><p>The subscription price rarely tells the whole story.</p><p>Find out whether implementation, training, support, integrations, payment processing and important modules are included. Check whether pricing changes as enrolment grows or as functionality is added.</p><p>For Canadian schools buying from international providers, currency matters too. A contract priced in another currency introduces exchange-rate movement into future budgeting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*N49uaLyJmFiX6Iop.png" /></figure><p>There is also an internal cost to consider. Staff time spent reconciling data, rebuilding reports, maintaining duplicate records or navigating disconnected systems belongs in the calculation.</p><h3>What does a good SIS decision look like in practice?</h3><p>Two Canadian independent schools provide useful examples.</p><p><a href="https://www.trymyschool.com/case-studies/okanagan-christian-school">Okanagan Christian School</a> in Kelowna, British Columbia, moved from Blackbaud after dealing with disconnected modules, rising costs and difficult workflows. After switching to MySchool, government reports and audit preparation that had taken multiple days could be completed in minutes. Report cards went from roughly a full day of work to about an hour, parent communication engagement increased from below 50% to above 60%, and the school reported approximately $10,000 in annual software savings.</p><p><a href="https://www.trymyschool.com/case-studies/the-study-academy">The Study Academy</a> in Toronto approached the decision from a different position. Its previous SIS was used mainly for provincial reporting, while much of the school’s other work lived in spreadsheets, folders and Google Drive. After moving to MySchool, attendance follow-up dropped from 90–120 minutes each morning to a few minutes, school-wide communication saved more than four hours per week, and a full-year timetable could be created in about an hour.</p><p>Both schools measured the outcome in the same place, which was the daily work of their staff. The value of a student information system shows up in how a school operates once the system is in use.</p><h3>Questions to ask before choosing a student information system</h3><p><strong>1. Does the system support the way our school operates?<br></strong>Map your current processes before you compare vendors, then ask each one to demonstrate those processes rather than their standard demo script. Pay particular attention to timetabling, tuition structures, bursaries and assessment models, since these vary most between independent schools.</p><p><strong>2. Which provincial reporting processes does it support?<br></strong>Ask which specific submissions the system generates for your province, whether that is OnSIS in Ontario, the 1701 collection in British Columbia, PASI submissions in Alberta or Charlemagne reporting in Quebec. Establish what the system produces automatically and what your staff still prepare by hand.</p><p><strong>3. Where will our student data be stored?<br></strong>Ask for the hosting location, the encryption approach and the backup schedule in writing. Canadian hosting matters to many boards for privacy and governance reasons, and your school stays accountable for student information under PIPEDA regardless of where the vendor holds it.</p><p><strong>4. How are permissions and access controlled?<br></strong>Teachers, administrators, finance staff and families all need different levels of access to the same records. Ask the vendor to show how roles are configured and how quickly access can be changed when someone joins or leaves.</p><p><strong>5. How will the SIS connect with our other systems?<br></strong>Identify every system that depends on student data, then ask how information moves between them. The specific test is what happens when an applicant becomes an enrolled student and whether that transfer requires manual work.</p><p><strong>6. What will teachers, administrators, families and students experience day to day?<br></strong>Involve people from each group in the evaluation and ask them to complete real tasks in the system. Count the steps involved in routine work such as taking attendance or finding a payment record.</p><p><strong>7. How will our existing data be migrated?<br></strong>Establish who is responsible for the migration, what happens to legacy SIS data and spreadsheets, and how records are validated once they have moved. Ask whether migration is included in the price or quoted separately.</p><p><strong>8. What training and ongoing support are included?<br></strong>Ask whether training is role-specific and whether it continues past launch, since a system that only the original project team understands becomes fragile within two years. Confirm who your school contacts when something goes wrong and what response time you can expect.</p><p><strong>9. What will the system cost over several years?<br></strong>Build a three to five year view that includes implementation, training, integrations, payment processing and any modules quoted as extras. Add the currency the contract is priced in and the staff time your current process consumes.</p><p><strong>10. Can the vendor show results from comparable Canadian independent schools?</strong><br>Ask for references from schools of similar size, province and structure to yours. A vendor who can point to schools running the same provincial reporting as you has already solved the problems you are about to encounter.</p><h3>Choosing the right SIS for your Canadian independent school</h3><p>No single student information system will suit every school.</p><p>Your province, enrolment, internal resources, existing technology and the way your teams work should all shape the decision. For Canadian independent schools and private schools, provincial reporting, data residency, implementation support and predictable pricing deserve particular attention alongside standard SIS functionality.</p><p>MySchool is a unified school management platform for Canadian independent K-12 schools. Its SIS connects student records with admissions, tuition, communication, LMS, IEPs, donations and reporting within one ecosystem, with Canadian data hosting and CAD invoicing on per-student pricing.</p><p>The platform provides dedicated provincial reporting functionality for Canadian schools, including OnSIS reporting in Ontario and 1701-related workflows in British Columbia, using the student, enrolment, attendance and assessment information already held in the system.</p><p>MySchool also supports migration from legacy systems and spreadsheets, provides role-specific training and assigns each school a dedicated Customer Success Manager through implementation and ongoing use. MySchool reports a 37-minute median first response time, 99.6% of tickets solved and 98.9% client satisfaction.</p><p>If your school is evaluating its options, explore <a href="https://www.trymyschool.com/what-we-do-sis">MySchool’s Student Information System</a> or <a href="https://www.trymyschool.com/request-a-demo-new">talk to our team</a> about what your school needs from its SIS.</p><p><em>Originally published at </em><a href="https://www.trymyschool.com/blog/how-to-choose-a-student-information-system-for-a-canadian-independent-school"><em>https://www.trymyschool.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3284633353df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hidden Costs of Fragmented Systems: What Your Workarounds Are Really Costing You]]></title>
            <link>https://medium.com/@MySchool/the-hidden-costs-of-fragmented-systems-what-your-workarounds-are-really-costing-you-072ec139c5e2?source=rss-ccebd1ef16c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/072ec139c5e2</guid>
            <category><![CDATA[k-12-education]]></category>
            <category><![CDATA[school-management]]></category>
            <category><![CDATA[independent-schools]]></category>
            <category><![CDATA[edtech]]></category>
            <category><![CDATA[school-leadership]]></category>
            <dc:creator><![CDATA[MySchool]]></dc:creator>
            <pubDate>Mon, 17 Aug 2026 07:31:00 GMT</pubDate>
            <atom:updated>2026-08-17T07:31:00.850Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jx_v3cM4xXg9znAm84epgA.png" /></figure><p>Earlier this summer we suggested a small exercise. Sit down with the people who run admissions, enrolment, billing and reporting, and <a href="https://medium.com/@MySchool/survive-or-thrive-how-did-your-school-really-do-this-year-quiz-39a5a323c245">ask each of them what took far more effort this year than it had any right to,</a> and who ended up holding it together.</p><p>Some schools did that on paper, most carry the answers around in their heads. Either way, you have a list.</p><p>This list is your effort documented.</p><p>Schools are very good at praising effort but much less practised at pricing it. Nobody approved this spending in a meeting, and most of it never reached a budget line. It builds up quietly and accumulates at schools that are otherwise run beautifully.</p><p>This article gives you a way to put a figure on the cost your team already absorbed this year, before another one starts adding to it.</p><p><strong>Here are the costs that show up again and again in schools running on fragmented systems. A few of them you can already see. The rest are hidden, which makes them even worse.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HeRWB7wNOpcCczMM.png" /></figure><h3>The Costs You Can See</h3><p>Some of this is already in your budget, and you could point to it today. Subscription fees for two tools that overlap. The support contract for the system nobody likes using. Overtime in the last week of June. The temporary help you brought in to survive <a href="https://www.trymyschool.com/what-we-do-provincial-reporting">report</a> card season. Add those lines up, and you get a real figure.</p><p>It will look manageable. Which is exactly the problem, because this is the smaller half of what you are paying.</p><h3>The Costs You Cannot See</h3><p>The rest never reaches a budget line at all. It gets absorbed by staff, by families, and by the calendar. Most schools make the decision to keep their current setup based only on the visible half, which is why the decision so often comes out wrong.</p><h4>Hidden Cost #1: The Hours Nobody Counts</h4><p>Start with the obvious one. Someone at your school spends part of every week doing work that exists only because two systems will not talk to each other. Re-keying a student’s details into a second database, or chasing a figure through email because no report will produce it.</p><p>Each task is small enough to feel unremarkable. Put a rate against it, and it stops being small. Say two people lose five hours each to that work in a normal week. Across a forty-week school year, that is four hundred hours. A school administrative salary of around $50,000 works out to roughly $30 an hour once benefits and payroll costs are counted, so those hours cost you in the region of $12,000 a year.</p><p>That is ten weeks of full-time work, and none of it produced anything new.</p><h4>Hidden Cost #2: The Families Who Left Through the Blurry Middle</h4><p>Scattered <a href="https://www.trymyschool.com/what-we-do-admissions-and-enrollment">admissions</a> data hides the middle of your funnel. You know how many families enquired and how many eventually enrolled. What happened in between stays vague.</p><p>So a family that went quiet after a tour looks exactly like a family that was never serious, and nobody follows up because nobody can see the difference.</p><p>One family lost that way costs far more than a single year of tuition. Count every year they would have stayed, and the siblings who would have followed them in.</p><h4>Hidden Cost #3: Tuition That Lands Later Than It Should</h4><p>When payment reminders depend on someone remembering to send them, they go out late during the weeks the office is busiest. Those are the same weeks the school needs the money to arrive.</p><p>Late <a href="https://www.trymyschool.com/what-we-do-tuition-management">tuition</a> puts pressure on cash flow, and it comes with a second charge attached. The uncomfortable follow-up conversations land on staff who did nothing to cause the delay.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7mnkIEDpuZSCRaAR.png" /></figure><h4>Hidden Cost #4: The Errors That Reached a Family</h4><p>Every school has a version of this story. An invoice with the wrong amount on it, a message about a child sent to a parent who should not have received it, because the family update went into one system and never reached the other.</p><p>Your team catches most of these. Your team catches most of these. One that gets through is forgivable, and families are generous about the occasional slip. What they respond to is the pattern, because the third time in a year stops looking like bad luck and starts looking like how the school is run.</p><p>That costs you something harder to price, which is a family’s confidence that the school has its house in order. Re-enrolment runs on that confidence, and families who lose it rarely announce it. They simply do not come back.</p><p>Put a figure on one of those departures. A student who leaves after Grade 6 instead of staying through Grade 12 takes six years of tuition with them. At $10,000, which sits near the bottom of the range for Canadian independent day schools, that single family is $60,000.</p><h4>Hidden Cost #5: The Departure Your School Cannot Absorb</h4><p>Ask what happens if your registrar or business officer resigns in March. Fragmented systems concentrate knowledge in people, because someone has to hold the map of where everything actually lives.</p><p>Losing that person means recruitment costs and months of reduced capacity, with a handover that cannot be complete because most of what they knew was never written down anywhere.</p><p>The same arrangement wears people down long before they hand in a letter. Staff who spend their year fighting the tools rarely say that on the way out, and they still go.</p><h3>Doing the Math Yourself</h3><p>You do not need a consultant for this. Take three items <a href="https://medium.com/@MySchool/dont-waste-a-hard-year-what-2025-26-can-teach-you-about-your-school-s-operations-3259b5f7ab25">from your July list</a>, estimate the hours each one swallows in a normal week, multiply by forty, and apply an hourly rate for the people doing the work.</p><p>Then add one family. Not a hypothetical family. The one you can already name, who left for reasons your team half suspects but nobody recorded.</p><p>The total will be conservative, because it leaves out everything you have no way to measure yet. It will still be larger than anyone at the table expects, and it will be something your board can respond to. A feeling about workload is easy to defer. A number is much harder to put off.</p><h3>What To Do Next</h3><p>Whatever total you land on, notice one thing about it. That amount is annual. Your school paid it last year, and it is already booked in for years to come unless something changes.</p><p>Which brings you to the question the rest of the summer is for. Some of what you are paying for is process, and better habits will clear it without spending a dollar. Some of it is structural, and no amount of discipline gets around it.</p><p>Telling those two apart is the next piece of work, and it is a great deal easier in August than it will be in October.</p><p><em>Originally published at </em><a href="https://www.trymyschool.com/blog/the-hidden-costs-of-fragmented-systems"><em>https://www.trymyschool.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=072ec139c5e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Signs Your School Ran on Heroics (Not Systems) This Year]]></title>
            <link>https://medium.com/@MySchool/5-signs-your-school-ran-on-heroics-not-systems-this-year-2992c8f3a03c?source=rss-ccebd1ef16c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/2992c8f3a03c</guid>
            <category><![CDATA[edtech]]></category>
            <category><![CDATA[school-management]]></category>
            <category><![CDATA[independent-schools]]></category>
            <category><![CDATA[school-management-system]]></category>
            <category><![CDATA[canadian-education]]></category>
            <dc:creator><![CDATA[MySchool]]></dc:creator>
            <pubDate>Fri, 24 Jul 2026 09:16:30 GMT</pubDate>
            <atom:updated>2026-07-24T09:16:30.440Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FmI0QV9rVTCpJA9rhxZYNA.png" /></figure><p>Most Heads of School already know the answer in their gut. The problem is that a gut feeling does not hold up in a budget meeting. It also does not tell you what to fix before September. So before the year fades into summer memory, it is worth naming the signs plainly.</p><p><strong>Here are five that show up again and again in schools that leaned on heroics this year.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*miP8BEOs0N4vYdy1.png" /></figure><h4>Sign #1: One Person Was the Actual System</h4><p>Ask yourself who would have to answer a question at 11pm on a Sunday for the school to function on Monday. If a name comes to mind fast, that deserves a closer look. One person often ends up holding the billing quirks, the family history, and the logic that only they know. When that knowledge lives in one head, <strong>the school depends on their memory for daily operations </strong>, not on a system. <strong>But that memory does not come with a backup.</strong></p><h4>Sign #2: Board Reports Took Days To Assemble Instead of Minutes</h4><p>Pulling together enrolment numbers, tuition status, or attendance trends should not require stitching together several spreadsheets and a few emails to confirm the figures. If it does, that points to a gap in your data setup, not a busy season. A well-built system produces a clean answer on demand. When every report needs a manual reconciliation first, <strong>the document your board reads is not a report. It is a reconstruction, built under deadline pressure.</strong></p><h4>Sign #3: Decisions Got Made From Memory Rather Than From Records</h4><p>Think back to admissions calls, re-enrolment conversations, or a tricky parent situation. Did the answer come from a system, or from someone recalling what happened last time? Institutional memory is valuable. But it works best as a backup to good records, not as a stand-in for them. When staff routinely say “I think we did this before, let me check with so-and-so,”<strong> the school is relying on memory instead of a system that should already have the answer.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wqyKB73wgAN3nMRs.png" /></figure><h4>Sign #4: Something Almost Slipped Through, and It Only Didn’t Because Someone Caught It</h4><p>Every school has a story from this year. Maybe a re-enrolment deadline nearly got missed. Maybe a family almost did not get a reminder they needed. These near misses feel like good catches in the moment. Looked at together, they form a pattern. A school that depends on someone noticing in time<strong> is one busy week away from the miss that does not get caught.</strong></p><h4>Sign #5: “We Will Fix That Someday” Became a Running Line</h4><p>If your team said this more than once this year, pay attention to it. It usually means the fix requires touching a system, a process, or a habit that nobody had the bandwidth to change mid-year. That is understandable in the moment. But if the same workaround shows up again next year with the same promise attached, <strong>it was never a “someday” project. It quietly became a permanent patch.</strong></p><h3>What To Do Next</h3><p>None of this means your team failed. It means they got the school through the year despite the systems they were working with, which is a much harder and far less sustainable way to operate. And it does not last.</p><p>This is exactly the gap MySchool is built to close. MySchool helps independent K-12 schools in Canada unify and streamline their operations by integrating <a href="https://www.trymyschool.com/what-we-do-sis">SIS</a>, <a href="https://www.trymyschool.com/what-we-do-admissions-and-enrollment">admissions</a>, <a href="https://www.trymyschool.com/what-we-do-tuition-management">tuition</a>, <a href="https://www.trymyschool.com/what-we-do-communication">communication</a>, <a href="https://www.trymyschool.com/what-we-do-provincial-reporting">reporting</a>, and <a href="https://www.trymyschool.com/what-we-do-lms-and-iep">LMS</a> in one intuitive, cloud-based platform.</p><p>Even if only one of these signs showed up in your school this year, we’d be happy to talk through tightening the operations behind it.</p><p><em>Originally published at </em><a href="https://www.trymyschool.com/blog/5-signs-your-school-ran-on-heroics-this-year"><em>https://www.trymyschool.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2992c8f3a03c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t Waste a Hard Year: What 2025/26 Can Teach You About Your School’s Operations]]></title>
            <link>https://medium.com/@MySchool/dont-waste-a-hard-year-what-2025-26-can-teach-you-about-your-school-s-operations-3259b5f7ab25?source=rss-ccebd1ef16c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3259b5f7ab25</guid>
            <category><![CDATA[canadian-education]]></category>
            <category><![CDATA[independent-schools]]></category>
            <category><![CDATA[edtech]]></category>
            <category><![CDATA[school-management-system]]></category>
            <category><![CDATA[school-management]]></category>
            <dc:creator><![CDATA[MySchool]]></dc:creator>
            <pubDate>Thu, 23 Jul 2026 08:12:31 GMT</pubDate>
            <atom:updated>2026-07-24T07:28:28.259Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZcZ4sod3hMDjBqCdBFyFvg.png" /></figure><p>Now that the year is finally over, and the reports have gone out and the invoices have been sent and the ministry submissions have made it in one way or another, most school leaders are thinking about exactly one thing, which is: rest. And that’s completely fair.</p><p>But whether you’ve sat down with some kind of year-end diagnostic and seen the results in black and white, or you simply know in your bones that this year ran on more effort than it should have, there’s a case to be made for doing one small thing before the summer closes over everything.</p><p>We want to make that case here, because the window for it is shorter than it looks.</p><h3>The Frustration Is the Data</h3><p>The whole argument comes down to this: the frustration of 2025/26 is the most accurate operational data your school will ever collect, and right now you’re holding all of it.</p><p>That might sound like an odd way to describe a difficult year, so let us explain what we mean. When a consultant comes in to assess a school’s operations, they spend a few days interviewing people and mapping processes, and then they hand over a report full of educated guesses.</p><p>What your team just went through is the opposite of a guess. Ten months of real load showed you precisely where your systems hold and where they give way.</p><p>You already know which report quietly ate a whole weekend, because someone on your team lived that weekend, and you probably know whose inbox the admissions follow-ups depended on, because everyone noticed the week that person was away.</p><p>In other words, the year was a stress test, one you never asked for and couldn’t have designed better if you’d tried, and the results are sitting in your team’s memory right now.</p><p>The trouble is that memory is exactly where they’re sitting, and memory has a shelf life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UVF7QcYHLUhqYs4ttKp50g.png" /></figure><h3>Summer Is an Eraser</h3><p>Here’s what happens next if nothing gets written down: by the middle of August, the sharp edges of June will have gone soft.</p><p>The registrar who spent three evenings untangling enrolment data will remember it, honestly and without any intention to mislead, as a busy patch. The bursar who chased a single tuition question through eleven email threads will have filed it under the usual.</p><p>This is simply how human memory works, and in most ways it’s a mercy, because nobody wants to carry June around all year. The problem is that it’s also how the same friction gets carried from one year into the next.</p><p>The pain fades before anyone acts on it, and then November comes, the same thing breaks in the same place, and the office fills with the familiar chorus of “we really need to fix this someday.”</p><p>And someday, as you may have noticed, never books itself in. By the time there’s finally room in the calendar to think about operations, nobody can point to what exactly needs fixing anymore.</p><p>What’s left is a vague sense that things are harder than they should be, which is a real feeling but a useless planning document. You can’t take a vague sense to your board and come back with a budget.</p><h3>Write It Down While It’s Still True</h3><p>Which brings us to the actual suggestion, and the good news is that it’s small: you don’t need to fix anything in July, or even decide anything. You just need to get the evidence on paper before it evaporates.</p><p>In practice, that means sitting down with the people who run the school’s engine room, or sending them one short email. <a href="https://www.trymyschool.com/what-we-do-admissions-and-enrollment">Admissions</a>, <a href="https://www.trymyschool.com/what-we-do-tuition-management">tuition</a>, <a href="https://www.trymyschool.com/what-we-do-donations">donations</a>, <a href="https://www.trymyschool.com/what-we-do-provincial-reporting">reporting</a>, <a href="https://www.trymyschool.com/what-we-do-communication">communications</a>.</p><p>Ask each of them what took far more effort this year than it had any right to, and then ask the follow-up that really matters, which is: what the workaround was and who was holding it up.</p><p>As the answers come in, push gently for specifics, because there’s a world of difference between “reporting was stressful,” which is a mood, and “the OnSIS submission meant cross-checking two systems by hand and swallowed four days,” which is a fact you can still act on months from now.</p><p>Give this an hour sometime in the next few weeks and you’ll end up with something most schools never have: a written record of where your operation actually cracked under load, gathered while everyone still remembers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xl53rYk-Pye09ikRyxuSAw.png" /></figure><h3>What That Record Buys You</h3><p>The reason we keep calling this evidence is that evidence changes conversations. A school that walks into September holding that record is in a different position on almost every front.</p><p>When the board asks why the office needs a new system or another pair of hands, there’s an answer with names and numbers in it rather than a plea. When the leadership team argues over priorities, the argument can start from what actually happened instead of from whoever remembers it loudest.</p><p>And if the school does eventually decide that 2026/27 is the year to sort out its systems, it can measure every option against its own documented failure points rather than against a feature checklist written by someone who has never set foot in a school office.</p><p>That last part matters more than it sounds, because most school system decisions go wrong right at the beginning, at the requirements stage, for the simple reason that nobody can say out loud what the current setup actually fails at.</p><p>There’s a quieter reason to do this too. Underneath every workaround in that record, there’s a person who absorbed it.</p><p>The report that ate a weekend was someone’s weekend, and the enrolment data scattered across four spreadsheets was reconciled by someone at nine on a Tuesday night, probably at their kitchen table.</p><p>Schools run on this kind of quiet heroism, and every year it goes unrecorded, it gets quietly rebooked for the next one.</p><p>Writing down where the systems failed is, in a very practical sense, how you stop asking the same people to keep covering for them.</p><h3>A Word About Timing</h3><p>If your notes do end up pointing at the systems themselves, be realistic about when that work starts.</p><p>A school that wants a genuinely better operational footing for September 2027 needs to open the conversation this autumn, while the memory of this year is still fresh and the details still have their edges.</p><p>Schools that wait until they feel ready tend to start from zero in the middle of a busy term, with nothing on paper and the evidence long gone, and the whole process takes twice as long for it.</p><h3>Next Steps</h3><p>MySchool is a K-12 school management ecosystem that helps independent K-12 schools in Canada swap fragmented systems and manual effort for one connected operational foundation.</p><p>So if your summer notes end up pointing at the systems themselves, we’d happy to talk about what a different September could look like for you.</p><p>Don’t waste a hard year. Write down what it taught you before the summer takes it back.</p><p><em>Originally published at </em><a href="https://www.trymyschool.com/blog/dont-waste-a-hard-year"><em>https://www.trymyschool.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3259b5f7ab25" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Survive or Thrive: How Did Your School Really Do This Year? (Quiz)]]></title>
            <link>https://medium.com/@MySchool/survive-or-thrive-how-did-your-school-really-do-this-year-quiz-39a5a323c245?source=rss-ccebd1ef16c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/39a5a323c245</guid>
            <category><![CDATA[edtech]]></category>
            <category><![CDATA[school-management]]></category>
            <category><![CDATA[canadian-education]]></category>
            <category><![CDATA[school-management-system]]></category>
            <category><![CDATA[independent-schools]]></category>
            <dc:creator><![CDATA[MySchool]]></dc:creator>
            <pubDate>Thu, 23 Jul 2026 07:54:53 GMT</pubDate>
            <atom:updated>2026-07-24T07:29:33.722Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gmMdE3aLaf56VfgS8rje4A.png" /></figure><p>Somewhere in the last week of June, every school goes quiet in the same way. The final bus pulls out. The photocopier cools down for the first time since September. And a Head of School sits at a desk stacked with end-of-year paperwork and thinks the thought every school leader thinks at this exact point in the calendar: we made it.</p><p>You did. Report cards went out. Concerts happened. Families were invoiced, mostly on time, and the ministry got its numbers. From the outside, another successful year. In the ways that matter most, it was.</p><p>But before the summer smooths the memory over, one question deserves an honest answer. How did you make it? Did the year run on systems, or did it run on Linda?</p><p>Every school has a Linda. Yours might be a registrar or a business officer, and she may well be the finest professional in the building. She knows which version of the spreadsheet is the real one. She knows the workaround for the workaround. When she takes a week off, small fires start. When she mentions retirement, the leadership team goes pale. Linda is what an engineer would call a load-bearing employee, and a school held up by load-bearing people is a school that has quietly swapped structure for effort. That swap is what this quiz is built to catch.</p><p><strong>The question is simple: did your school thrive last year, or did it survive on effort?</strong></p><h3>Why It Matters</h3><p>A school that thrives runs on systems, so a hard week stays a hard week. It gets absorbed, and the building moves on. A school that survives runs on people soaking up friction, and that arrangement holds beautifully right up until it doesn’t. A resignation letter or an early audit is all it takes, and the timing is never polite.</p><p>Here’s the trouble: from the outside, the two schools look identical. Both hit their deadlines. Both filed their reports. The difference lives underneath, in what those results cost, and cost is very good at staying off the report card. It hides in unlogged overtime and in the slow wearing down of your best people.</p><h3>How the Quiz Works</h3><p>Fifteen questions. Answer each with the first honest response that comes to mind:</p><p><strong>Yes (2 points).</strong> You can answer confidently and could prove it today.</p><p><strong>Partially (1 point).</strong> Something exists, but it’s incomplete, outdated, or depends on one person remembering.</p><p><strong>No or not sure (0 points).</strong> Not sure counts as no. If you can’t answer a question about your own school, that’s useful information on its own.</p><p>One rule matters more than the rest: these questions test whether you can reach the answer, as much as what the answer is. If getting the number would take three days and four emails, that’s a Partially at best. The distance is part of the diagnosis.</p><h3>The Quiz</h3><ol><li>Could you state your school’s current cash position on the same business day?</li><li>Do you know what percentage of tuition was collected on time this year?</li><li>Are payment reminders automated, or did someone spend the year writing individual emails to families in arrears?</li><li>Do you know your conversion rate from inquiry to enrolment, and can you name the stage where you lose the most families?</li><li>Did every inquiry receive a response within one business day, all year?</li><li>Could you name the grade or transition point that costs your school the most families, backed by records?</li><li>When a family withdrew this year, was the reason recorded somewhere you can learn from later?</li><li>If your registrar resigned tomorrow, could someone else run re-enrolment within a week?</li><li>Are your five most critical administrative processes documented somewhere other than one person’s head?</li><li>How many separate systems hold information about a single student? Could you name them all without checking?</li><li>When a family updates their phone number, does it change everywhere at once?</li><li>Can you trust that two systems will give you the same answer to the same question?</li><li>Could a parent complete a routine task this year, a form, a payment, an absence report, entirely online, without calling the front office?</li><li>Could you produce your provincial enrolment report this week if it were suddenly due?</li><li>Do you know what share of your week went to administration versus the mission, people, and strategy work you came to do?</li></ol><h3>Your Score</h3><p>Give yourself 2 points for every Yes, 1 for every Partially, 0 for every No or Not sure. Add it up. There are thirty points on the table.</p><p><strong>24 to 30: You thrived. </strong>Your school runs on systems, and that is genuinely uncommon. Your operations are visible and your team’s knowledge is transferable, which means a bad month stays a bad month instead of becoming a bad year. Look at where you dropped points anyway. Even disciplined schools carry one blind spot, and yours now has a name.</p><p><strong>14 to 23: You survived, at a cost. </strong>This is where most Canadian independent schools land, including plenty with excellent reputations. Things worked because good people worked hard. More than is comfortable depends on the memory and effort of specific individuals, and that setup holds until something tests it. Something always does, eventually.</p><p><strong>0 to 14: You ran on heroics. </strong>Your school operated because dedicated people made it operate by hand, and too much of their effort went to friction instead of mission. Here’s the genuinely good news: schools in this band have the most to gain and usually gain it fastest, because the problems behind a low score are common and well understood, which means they’re fixable.</p><p>Whatever your total, go back and count your Not sure answers. Each one is a question about your own school you currently can’t answer. A high count means information isn’t reaching you, and improving that visibility is job one, whatever else you decide.</p><h3>What To Do With Your Result</h3><p>However your school scored this year, the point of an exercise like this was never to make you feel behind. It’s to replace a feeling with a fact, so that whatever you decide to change next year, you’re deciding it on purpose.</p><p>So try this before the new school year gathers pace. Pick one section of the quiz and have your leadership team answer it independently, no comparing notes. Then put the answers side by side. The disagreements are the interesting part, because every one marks a spot where someone is working with information the others can’t see.</p><p>And if the same pattern shows up across several areas, the problem is probably not one weak process. It’s the foundation underneath the processes: student information scattered across places that don’t talk to each other, so every task starts with a search and every report starts from scratch.</p><p>That’s where MySchool can help. MySchool gives independent K-12 schools in Canada one connected school management platform for <a href="https://www.trymyschool.com/what-we-do-sis">student information</a>, <a href="https://www.trymyschool.com/what-we-do-admissions-and-enrollment">admissions</a>, <a href="https://www.trymyschool.com/what-we-do-tuition-management">tuition management</a>, <a href="https://www.trymyschool.com/what-we-do-communication">communication</a>, <a href="https://www.trymyschool.com/what-we-do-lms-and-iep">learning</a>, and <a href="https://www.trymyschool.com/what-we-do-provincial-reporting">reporting</a>. Your teams can spend less time holding disconnected systems together and more time actually running the school.</p><p>You got through 2025/26, and that’s worth a proper rest. The decision waiting on the other side of it is whether 2026/27 should run the same way. The best time to fix operational friction is before it becomes another year of workarounds.</p><p><em>Originally published at </em><a href="https://www.trymyschool.com/blog/survive-or-thrive-how-did-your-school-really-do-this-year-quiz"><em>https://www.trymyschool.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39a5a323c245" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>