A week, summarized from what actually happened, not a template
Assignments due and missing come from Bloomz's own native assignment records; when a district connects Google Classroom, grade movement and newly-missing work ride in too. Portfolio highlights and the week's attendance round it out. Every section is ids-and-counts under the hood and a plain-language sentence in the family's language on the surface, composed once, not once per recipient.
Teacher review before it sends, or fully automatic, a district's call
Some districts want a human glance before a hundred family digests go out; others want it fully automatic every Friday at 1pm local. Both are one config switch. In teacherReview mode, drafts queue for approval; in auto mode, a draft approves and sends itself the moment it's composed, and either way delivery only happens once, through the standard bell-and-push pipeline every other Bloomz alert already uses.
teacherReview mode leaves every draft queued until a staff member approves; auto mode sends the moment it's composed. Either way, translation happens once per family language, not once per family.
Translated once per language, not once per family, and scheduled the way your district wants
A district sets the day and time, which languages to cover (or leave it to auto-detect every distinct guardian language on file), and which sections run, then Weekly Learning Summary composes and translates once per DISTINCT language across the whole school, never once per recipient. The same discipline the rest of Bloomz's translation pipeline already follows.
Friday 1pm local by default, every section on, every distinct guardian language covered — a district tunes any of it.
How this reinforces the Bloomz pillars
Connected across Bloomz
20 minutes with Bloomz
answers more than 20 pages ever could.
Bring your hardest scenario, a multilingual community, a PBIS rollout, a vendor consolidation, and we'll walk through the actual product.