There are three formats of school notice that consistently cause problems, not because they are poorly written, but because of where they arrive in the communication stream and how they are formatted. Understanding them helps explain why even organised parents miss things, and why Molo's extraction is specifically designed to handle all three.
Type 1: The action-required notice buried in a newsletter
UK primary school newsletters are structured around informing, not acting. They cover what has been happening in class, what is coming up, and reminders from the office. In a four-page newsletter, the most urgent piece of information (a consent deadline for a trip leaving on Monday) might appear on page three, in a paragraph between a book fair update and a reminder about PE kit.
The format problem is that newsletters communicate everything with the same visual weight. A lovely note about Year 2's castle project and a hard deadline for paying for the school pantomime appear in the same typeface, same column width, same visual priority. For a parent scanning a newsletter at speed, the decorative content and the action-required content look identical until you have read every word of every paragraph.
What makes this type particularly difficult is the delivery timing. School newsletters frequently arrive on Friday afternoons. Friday afternoons are, for working parents, a moment of transition: leaving work, collecting children, managing the end-of-week domestic rush. A newsletter that arrives at 3:30pm on Friday needs to compete with school bag sorting, the question of what is for dinner, and the general cognitive load of the weekly handover. The page-three deadline does not get found until Sunday, if at all.
When Molo processes a forwarded newsletter, it reads the full document. A consent deadline in paragraph seven of page three gets extracted with the same priority as one in the subject line. The resulting calendar event includes a note flagging that action is required, so the parent sees "Year 5 trip consent deadline" with an action marker rather than an undifferentiated date.
Type 2: The PDF permission slip attached to an otherwise routine email
Some schools send permission slips as separate PDF attachments to emails. The email body might say "Please find attached the permission slip for the Year 3 Planetarium visit on 14 November. Please return by 28 October." The date is in the body. The form is in the attachment. For the parent to complete the action, both pieces need to be registered: the email received, the attachment opened, the form printed or completed digitally, and the deadline noted.
The point where this fails most often is the attachment-to-action gap. Many parents read the email on their phone. Opening a PDF on a phone to see whether it needs printing, signing, or digital submission is friction. The email gets flagged for later. Later arrives in the form of an inbox full-read on Thursday evening, when the parent discovers the attachment they meant to deal with has a deadline of Friday morning.
Molo extracts dates from both the email body and PDF attachments in the same extraction pass. The deadline date from the email body and any additional context from the attachment are combined into a single calendar event. The event note records that a form return is required. The parent still needs to complete the form. What they do not also need to do is remember that the attachment existed.
Type 3: The very early or late notification that arrives out of sequence
Schools send emergency notifications, sudden changes, and urgent reminders at times that do not fit normal communication patterns. A closure due to flooding, a change to the starting time on a specific morning, a last-minute reminder that tomorrow is non-uniform day: these often arrive as a brief email or text at times when parents are not actively monitoring communications.
Before 7am is a common window for school urgent notifications. Schools use the early window so parents receive the information before leaving for work. But before 7am is also a time when most parents are either asleep, managing morning routines with young children, or both. A 6:45am email notifying a 9am non-uniform day lands in a window when the parent is unlikely to be checking email with focused attention.
This is not a failure of school communication practice. The timing is chosen to give maximum notice. The problem is the human attention window. A notification that arrives when attention is available (mid-morning, after school drop-off) would be better, but the school cannot control when you check your phone.
Automatic forwarding means that an early-morning notification, once the forwarding rule is in place, is processed and appears in the calendar regardless of whether the parent opened the email at 6:45am. When they do check their calendar later that morning, the non-uniform day is already there. They did not need to be alert to the notification at the moment it arrived.
What these three types have in common
The common thread is delivery timing and format: all three exploit a gap between when information arrives and when a parent has the time and attention to process it. They are not the result of poor organisation on anyone's part. They are structural features of how school communication currently works.
The types that do not feature here, the clear, prominent emails with a single event and a clear subject line, do not need special handling. Those are easy to process manually. The three types described above are the ones that require either very consistent attention habits or a system that processes them regardless of when your attention is available. That is the specific gap Molo is designed to close.