Start with one frequent task—growth sharing, campus notices, or family activities. ANCDA helps the kindergarten establish a publish–review–confirm–follow-up loop, with professional review by teachers and visibility controlled by the kindergarten.
Three director priorities
Most kindergartens do not need another chat tool. They need each family task to have a clear purpose, visible status, and accountable follow-up.
Visible growth
BEFORE
The group has many class photos, yet families still do not know what happened for their child.
AFTER
Reviewed growth content is shared by family relationship so families understand the process and teacher support.
Confirmed communication
BEFORE
After an important message is posted, teachers repeatedly ask who has read or responded.
AFTER
Formal notices retain read, signature, or receipt status so teachers know whom to follow up with.
Family participation
BEFORE
Family activities are scattered across chat, images, and temporary spreadsheets.
AFTER
Publishing, family submissions, and completion progress form one follow-up record.
Three frequent scenarios
Growth updates, important notices, and family tasks each solve a different communication problem.
Scenario 1 · Growth sharing
Teachers turn class updates or growth records into family-friendly content, review it, and share by family relationship. Families see a concrete process, not a professional score.
Help families understand what happened, how the teacher supported it, and what they can notice at home.
Explore portfolios and class updatesGrowth record
Today, a new idea made the tower stand
Scenario 2 · Important notices
Administrators or teachers choose the audience; families read, sign, or submit a receipt. Teachers see pending recipients instead of relying on “received” replies in chat.
Make delivery, reading, and confirmation status visible.
Explore campus notice capabilitiesCampus notice
Autumn family event confirmation
Scenario 3 · Family participation
Teachers publish a shared family task, families submit evidence, and teachers review completed and pending participation without piecing together chat messages and images.
Give families a clear entry point and teachers a follow-up record.
Explore family task capabilitiesFamily task
Find the colors of autumn
Complete engagement loop
Keep AI, human review, family permissions, and follow-up in one workflow so every role knows its responsibility.
AI does not replace teacher judgment. Child media and growth content remain subject to consent, review, and family-relationship permissions.
Growth material, a formal notice, or a family task enters the appropriate product.
Only relevant scenarios use AI to organize signals, structure, or suggestions.
Teachers or administrators review the content, recipients, and visibility.
Families view, confirm, or participate, leaving a visible follow-up state.
Teachers use receipts and feedback to continue communication or support.
Current product evidence
These are capabilities in the current family-school product. We show confirmed workflows, not unverified business-result figures.
Audience scope, read status, signatures or receipts, and review queues keep formal notices separate from everyday sharing.
Class updates can be added to growth portfolios, with teacher records, family participation, previews, sharing, and export.
Teachers publish a task, families submit evidence, and teachers see completed and pending participation.
HOING Education Group · Kindergarten Director Liu
Customer voice
“With one phone, parents can understand their child's day anytime and anywhere. It brought families and the kindergarten much closer.”
A buying decision should not be based on feature count alone. Families need a clear entry point, teachers need visible confirmation status, and the kindergarten must retain review and permission controls.
View more customer practicesWho it fits
The same family-engagement loop creates different buying value for different organizations. Start with the most important task, then validate the right product mix through a pilot.
Start with a formal notice or growth update and establish a clear review, viewing, and follow-up process.
Help families understand real learning and the kindergarten's approach without promising fixed enrollment or renewal outcomes.
Prove the process in representative sites and classes before defining shared group standards with room for local differences.
Light pilot
Each stage validates only its own goal: experience the product, prove the workflow, then use real adoption to decide whether to expand or stop.
Select the scenario and confirm roles, permissions, entry points, and consent.
Complete one publish, view, confirmation, and follow-up cycle.
Review delivery, receipts, participation, and follow-up before deciding what is next.
Growth observations, educational suggestions, and AI-assisted content are reviewed before publishing.
Visibility follows class, child, family relationship, and role; child media requires appropriate consent.
Notices, updates, immediate communication, and tasks each use the appropriate entry point and record.
FAQ
Clarify scope, prerequisites, and result boundaries before choosing a demo or pilot.
No. AI only assists with organizing growth signals or drafts where appropriate. Teachers or the kindergarten review family-facing content, and the kindergarten configures visibility by role and relationship.
Formal notices handle delivery and receipts, class updates handle growth sharing, chat handles immediate communication, and family tasks handle participation. Each job uses the right channel.
Choose 2–3 classes and one frequent task. Use 3 days to experience the product, 7 days to prove publishing, viewing, confirmation, and follow-up, then review the agreed scope at 30 days.
Prove one thing first
Tell us your organization type, the family task you want to improve first, and the participating classes. We will help confirm the product, roles, and 3 / 7 / 30-day plan.
