I asked Tiiny what a Year 3 parent needs to do this week

Simulated parent scenario using public school newsletters. Results from an actual TiinyOS test.

I wanted one list I could check before the school week: what to book, what to pay for, and when pickup changes.

For this test, I gave Tiiny text extracted from two public school newsletters. I set the date to 15 October 2026 and asked it to read them for a Year 3 parent. That kept older notices from turning into new reminders.

The request included:

Please turn these two real school newsletters into a short action list: what to book, pay, bring or attend. Merge repeated items, exclude events already past and items only for other year groups.

Tiiny pulled out the £3 disco ticket, the recommendation to bring no more than £5 for spending, parent consultations, and early pickup at 13:00 on 21 October. It left the individual consultation times open.

I still had to check the disco poster. The answer listed all three sessions instead of picking the Year 3/4 slot. It also split parent consultations into two entries, which could look like two appointments.

I'd check those details before copying anything into a calendar. This run produced a draft list; it didn't create events or read a parent group.

Model: Qwen3.6-35B-A3B-Turbo. Input was mechanically extracted newsletter text; poster layout was a limitation.