Clear announcements
Place current school information and next actions behind one branded entry point.
Schools & Education
One trusted front door for school and family communication.
City of Hats can bring announcements, forms, requests, documents, and appropriate secure communication into a branded school experience. The deployment must still respect safeguarding, student-record, consent, accessibility, and age-appropriate design requirements.
Best fitSchools reducing fragmented family communication
Typical accessBranded browser portal with staff workflow
Important boundaryNot an SIS, LMS, or safeguarding system
What this solution does
Make the next school action easier to find
Families should not need to search across paper notices, personal email threads, social posts, and several apps to understand what to do next. A configured portal can organize communication around the school journey while Operations gives authorized staff a place to handle responses.
Digital forms and requests
Guide families through configured permissions, acknowledgements, or administrative requests.
More inclusive access
Support localized interface content while preserving human review for high-stakes or safeguarding communication.
Core workflows
Useful from enrollment through everyday school life
Each school chooses which modules are appropriate and which records must remain in its student information, learning, safeguarding, or document systems.
School announcements
Publish timely information and make the requested family action clear.
Forms and acknowledgements
Collect configured responses while preserving the school’s consent and records requirements.
Events and schedules
Present relevant dates, instructions, and links without replacing the authoritative calendar unless configured.
Family communication
Offer approved communication paths and move sensitive exchanges into an appropriate protected workflow.
Document delivery
Provide a defined route for supported reports or documents, subject to identity and authorization controls.
Administrative follow-up
Use Operations to assign and resolve configured family or student-service requests.
How it works
Start with safeguarding and audience design
A school portal may serve adults, teenagers, or younger children. The interface, identity, consent, and support model should reflect the actual audience.
Define audiences and authority
Identify students, parents, guardians, staff, and administrators, including who may view or approve each type of information.
Map records and escalation
Decide what remains in the SIS, LMS, safeguarding, attendance, or document system and how urgent concerns leave the portal.
Pilot for inclusion
Test accessibility, language, low-connectivity behavior, shared devices, support, consent, and staff training with a limited community.
Security and privacy
Protect students through governance as well as technology
Encryption does not replace safeguarding practice, parental authority checks, age-appropriate notices, restricted staff access, records management, or the school’s legal obligations.
Audience-aware identity
The school must define how students, parents, guardians, and staff are recognized and what each is permitted to see or do.
Restricted staff access
Roles should follow responsibility and be reviewed as staff, classes, and safeguarding duties change.
Translation with review
Machine translation can improve access but high-stakes instructions, consent, and safeguarding content need qualified review.
Student-record boundary
The school must decide what enters City of Hats and what stays only in the authoritative student or safeguarding record.
Scope clarity
Important boundary
A strong fit when
Your school needs a clearer family communication layer and can define audiences, authority, safeguarding escalation, records, accessibility, and support.
What it does not replace
It is not automatically an SIS, LMS, gradebook, attendance system, emergency alert network, identity provider, or safeguarding case-management platform.
Confirm before deployment
Review student privacy, parental consent, age-appropriate design, accessibility, records, safeguarding, translations, shared devices, staff permissions, emergency communication, and jurisdiction-specific education law.
Straight answers
Questions teams ask before a demo
Product scope reviewed: 10 August 2026
Does City of Hats replace our SIS or LMS?
No. It can provide a branded communication and workflow layer while the school’s SIS, LMS, safeguarding, or records platform remains authoritative.
Can families use the portal in several languages?
Localized interface content can be configured. High-stakes instructions, consent, special-education, and safeguarding content require human review rather than blind reliance on machine translation.
Can younger students use the portal?
That depends on the configured workflow, jurisdiction, school policy, age-appropriate design, consent, and whether a parent or guardian should act instead. It must be assessed before deployment.
Is this an emergency notification system?
Not by default. Schools need an independently reviewed emergency-notification and safeguarding process, including alternative channels when internet or provider services are unavailable.
How should sensitive student information be handled?
Collect the minimum needed, restrict access, define the authoritative record, use an appropriate protected workflow, train staff, and apply the school’s retention and incident procedures.
Explore the platform
Build the complete workflow
Design for families, records, and safeguarding together.
Tell us who will use the portal, which systems remain authoritative, and which accessibility, language, consent, and safeguarding rules apply.