Today — 15 to 30 minutes of typing
Paper first, then forms — per class, per day, after teaching has finished. It does not happen, and no amount of training makes it happen.
The problem
A parent has almost no idea what happened in their child's school day.
They find out at the end of term
A report card arrives three months after the term began. By then a child who stopped attending in week three, or stopped understanding in week five, is already far behind.
The school office absorbs the questions
Parents who want to know call, or walk in. The bursar and the head teacher answer the same questions all day instead of doing their work.
The portals that exist are quiet
School software in this market ships a parent portal. Most go silent within weeks of term starting — because nothing flows into them.
Why this is unsolved
The portal is not the hard part. Filling it is.
What a teacher would have to do, every single day, for a parent portal to have anything in it:
Attendance
Per class, per period — then transcribe it from paper into a system
Behaviour and incidents
Written in a notebook, if at all; almost never reaches a parent
Marks for daily work
Marked on paper, entered again later — or never entered
Homework set and returned
Told to the class out loud; the parent never hears it
A note the parent should see
The thing that actually matters, and the first thing dropped
This is unpaid administrative work on top of teaching, and teachers do not do it. Every parent portal in this market is downstream of that one fact — which is why buying more software has never fixed it.
Our approach
Make the daily entry take seconds, and the portal fills itself.
With EduCloud — about 20 seconds, spoken
The teacher says it in Kinyarwanda, or photographs the register they already marked on paper. EduCloud structures it; the teacher confirms with one tap.
“S2A — Keza, Mutoni na Ishimwe ntibaje. Uwase yakoze neza mu mibare.”→ Three absences recorded against the right children, and a positive note filed for a fourth — each one reaching that child's parent the same afternoon.
Nothing is typed. Nothing new is added to a teacher's day. That is the whole design constraint.
How it works
From a lesson ending to a parent knowing.
Capture
A voice note in Kinyarwanda, or a photograph of the register the teacher already marked on paper. Nothing is typed.
- Speak for about twenty seconds at the end of a lesson
- Or photograph the paper register you already filled in
- Works with no network — it syncs when the signal returns
Capture works offline and syncs when the network returns. Rwandan school connectivity is a design input, not an excuse.
For parents
A short message, every afternoon, in the language they think in.
EduCloud · Today
Keza M. — S2A
- Attendance
- Present, all periods
- Mathematics
- Did well in today's exercise
- Homework
- English reading, due Thursday
- Fees
- Term balance settled
Sent in Kinyarwanda by default. English or French on request.
A digest, not a firehose
One short message a day. Parents ignore notification streams; they read a daily summary about their own child.
Ask a question back
Typed or as a voice note, in Kinyarwanda. Answers are read from real school records — never invented.
Built for the phone they own
Low-end Android and thin bandwidth, and it works when the network does not. Reachable by USSD for guardians without a smartphone.
A behaviour note is a teacher's words, structured — never a model's judgement of a child. Nothing reaches a parent that a teacher has not confirmed.
Fees
We handle fees. We are not fighting for the payment rail.
What we do
A payment arrives with whatever reference a parent typed on a feature phone — a first name only, two siblings at once, or nothing at all. We match it to the right child, and the balance appears in that afternoon's digest.
What we do not do
We do not hold parent money, and we do not try to replace the fee-collection rail your school already uses. Our own subscription settles through a licensed payment service provider.
A school can adopt EduCloud without changing how it collects fees. We sit beside the rail, not across it.
Built here
Built for Rwanda — not localised into it.
Dormitories with patron and matron. O-level S1–S3, A-level S4–S6, and TVET tracks. Kinyarwanda as the working language rather than a translated label. These are the structures every Rwandan school actually runs on — and the ones imported systems do not model, so schools end up bending around the software instead.
Built and in place
The multi-tenant school system: registers, classes and streams, dormitories, fee records and reconciliation, and the screens a bursar and a director use every day.
In development
Kinyarwanda voice capture and the photographed-register path — the part that makes daily entry take twenty seconds. Designed and being built; not yet shipped to a classroom.
Partner schools
We are choosing our first schools now.
If you run a school and the description above sounds like your term, we would like to talk. The first schools we work with shape what EduCloud becomes — and they get it first.