Trace · URN 110793

How we read Steeple Morden CofE VC Primary School

last read 14 Aug 2026, 16:09 UTC · took 28.2s · 20 dates across 1 school years

Nobody types these dates in. A program finds whatever the school publishes its term dates on and reads it. This page is the working out: the files we downloaded, and every date we got out of them. Open the same file and you can check us.

Find the page

saved for next time

We start at the school's website and follow it to whatever it publishes term dates on, in this case a file on steeplemorden.cambs.sch.uk. That address is saved, so every later check goes straight there.

Download it

sha-256

3 files came back. We fingerprint the contents (96977b2ce4…8091b04a97). If the fingerprint matches last time's, the school hasn't changed anything and we stop here.

Read it

28.2s

This school publishes its year as a colour-coded chart rather than a list of dates, so a model reads it the way you would — square by square, working out from the key what each colour means. 2 other files were read and produced nothing useful.

Work out the dates

plain code

Ordinary code takes it from here, pairing those sentences into terms and filling in the holidays between them. It also checks the year adds up: if the dates leave too few school days, we throw the whole read away rather than publish it.

Save it

one copy

The dates get written down once. The school's page, your calendar feed and this trace all read that same copy, so they can't disagree with each other.

Where it came from

what we downloaded, and what we actually used

steeplemorden.cambs.sch.uk/term-dates-and-calendar
We read this one and found no term dates in it.
not used · 0 dates
static.wixstatic.com/media/b84bb4_9eebed1a2ce24864881cc0e7e0744a0a~mv2.jpg/v1/fill/w_1280,h_720,al_c,q_85,usm_0.66_1.00_0.01,enc_avif,quality_auto/b84bb4_9eebed1a2ce24864881cc0e7e0744a0a~mv2.jpg
We read this one and found no term dates in it.
not used · 0 dates
static.wixstatic.com/media/3b5061_53bfa3b24e2346609ced17086e254c00~mv2.jpg/v1/fill/w_558,h_770,al_c,lg_1,q_85,enc_avif,quality_auto/Screenshot%202026-07-14%20111731.jpg
We read 20 dates out of this one.
used · 20 dates

Every date we read off the chart

the file itself is linked above

2026/2720 dates

INSET Day1 Sept
INSET Day2 Sept
Autumn Term3 Sept – 23 Oct
October Half Term26 Oct – 30 Oct
Autumn Term2 Nov – 27 Nov
INSET Day30 Nov
Autumn Term1 Dec – 18 Dec
Christmas Holiday21 Dec – 1 Jan
INSET Day4 Jan
Spring Term5 Jan – 12 Feb
February Half Term15 Feb – 19 Feb
Spring Term22 Feb – 25 Mar
Easter Holiday26 Mar – 9 Apr
Summer Term12 Apr – 30 Apr
Bank Holiday3 May
Summer Term4 May – 28 May
May Half Term31 May – 4 Jun
INSET Day7 Jun
Summer Term8 Jun – 21 Jul
Summer Holiday22 Jul – 31 Aug

A chart states its dates in colour, not in words, so there is nothing to quote back at you. What we can show is every date we took off it — open the file above and the two should agree square for square.

What we saved

the single copy the school page and your calendar both read

This run

fingerprint: 9ad891d462…aec401a032
saved at: 25 Aug 2026, 20:43 UTC
run signature: e38c4c4966…3fd06d0eee
dates published: 35
last confirmed: 14 August 2026

Why your calendar doesn't fill up with duplicates

Each event gets an ID built from who said it, what kind of day it is, and when it starts. Read the school again tomorrow and the same day comes out with the same ID, so your calendar updates the entry it already has rather than adding a second one.

# same inputs, same ID, every time
sha256(owner | kind | start)[:24]
  → a4384bdd…f1763a2c@termsync.co.uk