According to Department for Education data, more than one million children in UK state schools speak a first language other than English at home. In Manchester, where Molo was built, that proportion is particularly high. Many city primary schools serve communities where Urdu, Punjabi, Bengali, Somali, Polish, or Arabic is the primary household language.
For working parents in those families, school communication creates a compounding problem. The notices, letters, and newsletters arrive in English. Understanding them requires either a strong English reading level, a willing bilingual family member, or a translation tool. But even families who can read the English content face the same problem every other family faces: the schedulable information is buried in prose, in PDFs, in tables. The translation barrier sits on top of the standard extraction problem, not instead of it.
Where the scheduling gap appears
Consider a family whose parent with the school-registered email address is more confident in Urdu than in written English. A newsletter arrives. It is a three-page PDF, mostly English, with some headers and a date table on page two. The parent can identify that there is a document. They may be able to extract the main headline. But reading through the narrative sections to find all the schedulable events, understanding the context (is this a mandatory trip or optional?), and then manually entering the correct dates in a digital calendar is a significant ask.
The consequence is not usually a complete failure to process the newsletter. It is a partial one: the obvious dates get entered, the nuanced ones do not. Parents evening gets added to the calendar because it is in the subject line. The trip consent deadline buried on page three, described in a paragraph with conditional language, does not.
The families most affected by this gap tend to be those where the scheduling burden falls on one parent who faces additional language processing overhead. The result is a family calendar that is less complete, and a higher rate of missed deadlines for activities that require advance action.
What automatic extraction does in this context
When a newsletter is forwarded to Molo and processed, the extraction layer reads the full document content, not just the portions that are easy to locate. It identifies date expressions, event names, and action items across the entire text. For a parent who would otherwise process the first page and skim the rest, this matters: the events from page three are extracted the same way as the ones from page one.
The calendar events that appear after extraction are short, structured, and in a standard format. An event with the title "Year 5 Residential trip consent deadline" and the date "14 April" is comprehensible even with limited English reading confidence. The narrative context that made it hard to extract is stripped away; what remains is the information needed to act.
We are not claiming Molo provides full translation. The event names and notes fields are extracted from the English source, and they will reflect the English terminology used in the newsletter. A parent who cannot read English will still need some level of support to understand event names. But the reduction in reading load is meaningful: instead of a three-page document requiring careful reading in a second language, what needs to be reviewed is a short list of dated events in plain terms.
The case for multilingual date resolution
Some schools in areas with large bilingual communities do provide translated communications, either informally (a bilingual staff member adds a note) or through formal translation services. In these cases, the same notice may arrive partly in English and partly in another language, or the dates may be written in the second language's conventions.
Date conventions vary meaningfully across languages. In some languages, the ordinal format differs. In others, months are abbreviated differently or not abbreviated at all. A date written as "14 avril" in a French portion of a document is the same date as "14 April," but our extraction layer needs to resolve both reliably. We are actively building out multilingual date normalisation for the languages most represented in UK school communities.
The current position is that English-language date expressions in any document, regardless of the surrounding language, are reliably extracted. Documents where the date itself is written in another language script may have lower extraction confidence for that specific date, and we surface those for manual review rather than risk a wrong entry.
What we are working toward
The fuller version of multilingual support we are building toward involves three things: reliable date extraction across the main date-format conventions used in languages common in UK schools; a notification interface that can surface events in a format a parent can share with a bilingual family member for quick review; and improved extraction confidence for documents that mix languages within the same notice.
We are a small team working on a focused problem. Multilingual support is on our roadmap because it is a meaningful access gap, not because it is the path of least resistance. The families who most need the scheduling help are sometimes those for whom the current tool works less reliably. That is worth fixing.
The broader point about equitable scheduling
Shared family calendars that stay updated are typically a feature of households where someone has the time, language confidence, and digital literacy to maintain them. Those prerequisites are unevenly distributed. Tools that reduce the maintenance burden help more where the burden would otherwise be highest.
We are not saying Molo solves the underlying inequity in school communication design. Schools do vary significantly in how accessible their communications are, and that variation reflects resource constraints as much as intent. What we are saying is that a tool which closes the gap between "email arrives in inbox" and "event appears in calendar" is more valuable for the families where that gap currently costs the most.