<?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 Juho Isola on Medium]]></title>
        <description><![CDATA[Stories by Juho Isola on Medium]]></description>
        <link>https://medium.com/@juhoisol?source=rss-391a97f81ffb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*pydinlgOH4-TgOmE.png</url>
            <title>Stories by Juho Isola on Medium</title>
            <link>https://medium.com/@juhoisol?source=rss-391a97f81ffb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:03:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@juhoisol/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[Make your school year plans solid before timetable generation]]></title>
            <link>https://medium.com/@juhoisol/make-your-school-year-plans-solid-before-timetable-generation-738c442acce8?source=rss-391a97f81ffb------2</link>
            <guid isPermaLink="false">https://medium.com/p/738c442acce8</guid>
            <category><![CDATA[timetable]]></category>
            <category><![CDATA[schools]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Juho Isola]]></dc:creator>
            <pubDate>Tue, 11 Aug 2026 13:33:51 GMT</pubDate>
            <atom:updated>2026-08-11T13:33:51.889Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OCZcA7w9cZY2nLgl" /></figure><p>A timetable usually fails before anyone presses the generate button in your timetable optimization tool.</p><p>The visible failure might come later: a teacher double-booked in September, a workshop group with no suitable room, a part-time teacher placed on a non-working day, or an option block that just cannot be build.</p><p>But the cause often sits earlier in the school year plan.</p><p>Timetable generation places agreed lessons into periods. It should not invent the curriculum structure, repair staffing assumptions, or guess which room can support a workshop. If those decisions are still unclear, the timetable solver inherits the uncertainty.</p><p>That is why the planning stage matters.</p><p>Before generation, the school needs a staffed and feasible curriculum structure. The best way to do this is to map it in a visual editor that spans across multiple academic years. That includes:</p><ul><li>term dates, holiday weeks, exam windows, and day profiles</li><li>courses, subjects, modules, groups, and pathways</li><li>teacher contracts, availability, skills, and target loads</li><li>rooms, labs, workshops, equipment, and campus rules</li><li>option blocks, bands, sets, and fixed points where the school uses them</li><li>policy constraints such as lunch, breaks, gaps, and pinned commitments</li></ul><p>In many schools, those decisions live across multiple spreadsheet files, emails, previous-year files, and some in the timetable tool. That split creates the familiar planning season problem: the timetabler is expected to produce a clean grid from inputs that were never pulled together.</p><p>A planning-first workflow to your timetabling problem changes the order, and solves both: the planning problem and the timetabling problem.</p><p>The school builds the year model first. Then it proves the model is ready for timetable placement. After this, you don’t even need hundreds of timetable optimization settings and preferences anymore, just a click of a “generate timetable” button should be enough.</p><p>A typed plan is not the same as a feasible plan.</p><p>In real timetable work, planners use checks such as block build, combing chart, clash table, conflict matrix, and trial timetable runs.</p><p>Each check answers a different question:</p><ul><li>Block build: can this block work internally without a teacher or room being needed twice?</li><li>Combing chart: can blocks fit together without double-booking a teacher?</li><li>Clash table or conflict matrix: which blocks across year groups are compatible?</li><li>Trial timetable: does the proposed structure work with next year’s real staff?</li></ul><p>They protect the timetable from carrying structural errors into placement.</p><p>Automatic timetable generation is really useful and saves a lot of time when it works from a clear model. The planner still decides what is fixed, what can move, and which commitments matter most. A sports afternoon may be locked. A workshop may need a specialist room. A part-time teacher may only be available on certain days. A course may need double periods rather than single periods.</p><p>Those decisions should be explicit before the solve.</p><p>If they sit in an Excel file on someone’s desktop computer or in one planner’s memory, the timetable tool has to rediscover them through failed runs and manual cleanup.</p><p>Smootables treats school year planning and automatic timetabling as one data model. Most timetabling tools handle the school-year planning phase poorly or even ignore it completely expecting the school to suddenly appear with complete and polished spreadsheets.</p><p>In Smootables, the same visual and easy to use workspace holds your academic years, terms, courses, groups, teachers, rooms, equipment, workloads, constraints, and pathway assignments across multiple campuses. Pre-generation validation can then flag gaps before the timetable solver runs.</p><p>That matters because the best time to find a missing teacher, impossible workload, or unavailable workshop is before the school waits for a solve.</p><p>All timetables in Smootables are of course still editable after the automatic optimization. If planners need to move lessons, pin commitments, resolve waiting-area lessons, and compare alternatives, all of that is still doable. But those edits are just final polishing instead of trying to make the impossible timetable possible, when the underlying plan stays connected to the timetable.</p><p>Check out how Smootables handles the school year planning at <a href="https://smootables.com/en/school-year-planning">https://smootables.com/en/school-year-planning</a></p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/make-your-school-year-plans-solid-before-timetable-generation-isola-uhnqf/?trackingId=8SORZ3u4Rv2SDe5MrfRH1A%3D%3D"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=738c442acce8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A simple live Week A/B indicator for school websites]]></title>
            <link>https://medium.com/@juhoisol/a-simple-live-week-a-b-indicator-for-school-websites-1f6406da461a?source=rss-391a97f81ffb------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f6406da461a</guid>
            <category><![CDATA[schools]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[timetable]]></category>
            <dc:creator><![CDATA[Juho Isola]]></dc:creator>
            <pubDate>Mon, 10 Aug 2026 15:43:01 GMT</pubDate>
            <atom:updated>2026-08-10T15:43:01.057Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CUbpdkScf9bkXXIx" /></figure><p>Many schools run a two-week timetable, the A/B week rotation system. Families and students then ask the same question all year each monday: Is this Week A or Week B?</p><p>The usual answer is a static PDF, a calendar image, or a line on the school website that someone has to update. That works until a holiday pauses the cycle, the term restarts on the wrong label, or the website says Week A while the timetable office is working from Week B.</p><p>We built a free school week rotation calculator for that small but recurring problem.</p><p>It lets a school set:</p><ul><li>cycle length, such as Week A / Week B or a longer rotation</li><li>the anchor date that proves which week the cycle starts on</li><li>whether holidays pause the rotation or still advance it</li><li>the weekday that starts the school week</li><li>custom labels and a simple site-friendly theme</li></ul><p>The output is a live indicator schools can paste into a website, parent portal, or intranet. The widget reads the settings from the URL. There is no login, no backend, and no timetable data to upload. It only answers the rotation-week question so that everyone is on the same week.</p><p>The calculator starts with one date you trust.</p><p>Example:</p><ul><li>Cycle: two weeks</li><li>Labels: Week A and Week B</li><li>School week starts: Monday</li><li>Anchor date: 1 September 2026</li><li>Anchor label: Week A</li><li>Holiday pause: 26 to 30 October</li></ul><p>The tool finds the week that contains the anchor date, then counts full school weeks from that point to the target date.</p><p>If holidays pause the timetable, holiday weeks do not advance the count. If the school chooses advance mode, every week increments the cycle, even across breaks.</p><p>That distinction matters. Some schools keep the A/B sequence moving through holidays. Others pause during half-term so the next teaching week resumes where the timetable left off. The calculator supports both because schools use both patterns.</p><p>A static Week A/B page is easy to publish and easy to forget.</p><p>A live website embed gives families the answer on the page they already check. It can sit on:</p><ul><li>the school homepage</li><li>a parent information page</li><li>the timetable page</li><li>an intranet dashboard</li><li>a student portal page</li></ul><p>The school can also test dates before copying the embed. That matters at term boundaries, after holiday weeks, and around special weeks where the normal rotation changes.</p><p>The widget shows the rotation label only. It does not publish lesson times, room changes, cover, or staff calendars.</p><p>For a full school timetable, this kind of a simple rotation label is only one part of the solution. A full school-year planning system still needs terms, groups, teachers, rooms, lesson rules, constraints, and published timetable views.</p><p>If you only need a live Week A/B indicator, this very simple and free embedding tool is enough.</p><p>Try it here: <a href="https://smootables.com/en/tools/school-week-rotation-calculator">https://smootables.com/en/tools/school-week-rotation-calculator</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f6406da461a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to create a school timetable: The handoff check before you should open the timetable grid]]></title>
            <link>https://medium.com/@juhoisol/how-to-create-a-school-timetable-the-handoff-check-before-you-should-open-the-timetable-grid-78399d92e0cc?source=rss-391a97f81ffb------2</link>
            <guid isPermaLink="false">https://medium.com/p/78399d92e0cc</guid>
            <category><![CDATA[education]]></category>
            <category><![CDATA[edtech]]></category>
            <category><![CDATA[teaching]]></category>
            <category><![CDATA[timetable]]></category>
            <dc:creator><![CDATA[Juho Isola]]></dc:creator>
            <pubDate>Mon, 13 Jul 2026 09:53:31 GMT</pubDate>
            <atom:updated>2026-07-13T09:53:31.366Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ovNpMHvkooLvwtoK" /></figure><p>Someone on the leadership team asks whether the timetable is “ready to build.” The usual answer sounds reasonable: the option blocks are typed in, staffing looks roughly right, and the period count matches last year. So the coordinator opens the scheduling tool and starts timetable placement.</p><p>That is often where the rework begins.</p><p>Creating a school timetable is planning work. You take a staffed curriculum structure that has already been checked for feasibility and put agreed classes into periods without clashes. It is a different job from designing option patterns, contact ratios, or staffing models. If those pieces do not fit, fixing them during placement costs more time than fixing them during year planning. Most timetable problems are already solved in the school-year planning stage.</p><p>The mistake is treating “complete on paper” as the same thing as “ready for the grid.”</p><p>Experienced planners do not start timetabling with a typed list of classes. They start with a plan structure that has already survived a few named checks:</p><p>Block build tests a single block internally. Can every lesson inside the block be staffed and roomed without double-booking a teacher or a room within that block? If the block will not build, it cannot be scheduled as proposed.</p><p>Combing chart tests whether blocks fit together. Can you combine blocks without putting the same teacher in two places at once across blocks?</p><p>Clash table or conflict matrix tests compatibility between blocks in different year groups. It also helps you decide scheduling order later, because some combinations are tight long before you touch the solver.</p><p>Teacher workload checks make sure all teacher work contracts and part-time availabilities are respected correctly.</p><p>These routines answer different questions. Skipping them and hoping the generator will “sort it out” usually means the timetable generator surfaces problems you should have caught weeks earlier, often as cryptic validation errors or kickouts that look like tool bugs instead of planning mistakes.</p><p>Timetable generation places agreed classes into periods. That is just mathematical constraint-optimization. It does not invent the curriculum or repair an unstaffable option pattern. That sentence is worth repeating to anyone who treats the timetable solver as a magic fix for a weak school-year plan.</p><p>You can often spot a weak handoff before the first full generate run:</p><ul><li>Too many course placements marked “to be decided later” still sitting in the period plan</li><li>Teachers over their weekly/yearly limit on the workload view, treated as a problem for timetabling to solve</li><li>Option blocks that look fine in a spreadsheet but have never been combed against each other</li><li>Part-time availability recorded vaguely (“works Mon-Wed”) instead of as concrete windows</li></ul><p>Each of these is a year-planning issue wearing a timetabling costume. Coordinators then spend June and July resolving clashes that were predictable in April.</p><p>Before placement starts, the handoff record should show why construction can begin:</p><ul><li>Calendar and period counts are signed off</li><li>Option pattern, bands, sets, and blocks are agreed</li><li>Curriculum audit and staff loading chart still match</li><li>Block build, combing chart, and clash checks have been run on the proposed structure</li><li>Trial timetable work is done where the structure was still uncertain</li></ul><p>If any of those lines is missing, the right next step is usually a conversation with the academic planning owner, not another timetable optimization run with different constraints settings.</p><p>Once the structure is feasible, the creation cycle has a sensible order:</p><ol><li>Clean teacher, room, class, and subject data (duplicates and missing availability cause late clashes)</li><li>Lock day and week structure (period counts, school day profiles for each period, cycle length, breaks)</li><li>Set constraints and fixed points (hard rules vs soft preferences)</li><li>Choose manual, automatic, or mixed generation, and place the tightest lessons first</li><li>Run validation before and after placement (static data checks, does plan lesson count and timetable grid lesson count match, then constraint checks)</li><li>Resolve kickouts with targeted swaps, especially around part-time staff</li><li>Review with departments and publish one authoritative version</li></ol><p>That sequence is obvious on paper and easy to scramble under timetabling deadline pressure. Electives before singletons, validation skipped because “we need a grid to show SLT,” publication before department review: each shortcut creates expensive rework later.</p><p>We published a planner guide that maps these seven stages from handoff through publication, including workflow notes for each step. It stays on process and decisions rather than timetabling tool comparison.</p><p>Read the full guide: <a href="https://smootables.com/en/resources/learn/school-timetabling/creating-school-timetable">https://smootables.com/en/resources/learn/school-timetabling/creating-school-timetable</a></p><p>What check does your school treat as the real “go” signal to determine when the school-year plan is ready and actual timetabling can start?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78399d92e0cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>