You teach a great workshop.
The parent has no idea what happened.
You spend two hours teaching a child how to calibrate a 3D printer. They practice, they fail, they learn, they get it right. It’s a great session. Then the child goes home and the parent asks “what did you do today?”
The answer: “nothing.”
That’s not a reflection of your work. It’s just how children communicate. But for the parent, “nothing” means they have no visibility into what they’re paying for. They don’t know if the child is learning, progressing, or just sitting there. And eventually, that uncertainty becomes a problem for you.
Parents who can’t see the value of your workshop will eventually stop paying for it.
So you end up writing progress reports, scheduling parent calls, answering “how’s my kid doing?” messages. That’s administrative work that takes time away from teaching. And the irony: no report you write will be as convincing as the actual work the child did.
Don’t report to parents. Include them.
Parent Access connects the parent directly to their child’s project inside your workshop. They see the real work — not a summary you had to write.
Same workshop. Two different parent relationships.
The parent creates the account. You teach. They see.
$ workshop --students "3D Printing Basics"
Student Progress Parent sees
──────────────────────────────────────────
giorgos_m 72% ✓ full project view
elena_k 45% ✓ full project view
dimitris_p 95% ✓ full project view
PARENT VIEW (what giorgos_m’s parent sees)
$ parent --view giorgos_m
Today’s session:
✓ First Layer Calibration
✓ Temperature Tower Print
○ Material Comparison Notes in progress
Upcoming:
□ Retraction Settings Test
□ Final Project: Design & Print
Your workshop speaks for itself.
Every time a parent asks “how’s my child doing?”, you stop being an educator and start being a reporter. You write a message, choose your words carefully, try to be encouraging but honest. That’s 15 minutes per parent, per week. With 10 students, that’s two and a half hours of reporting — time you could have spent preparing your next session.
And here’s the bigger problem: no message you write is as powerful as the project itself. You can say “Giorgos is doing great, he calibrated the printer today.” Or the parent can open the project and see the completed task, the temperature tower the child printed, and the notes the child wrote about what worked and what didn’t.
Which one builds more trust?
Parent Access removes the reporting layer entirely. You teach. The project records everything. The parent sees it directly. You don’t do anything extra — the transparency is built into the system.
The result: parents who understand what their children are learning, trust your process, and stay enrolled longer. Not because you convinced them with words — but because they saw the work with their own eyes.
Parents see their child’s project. Nothing else.
Better retention. Less admin. More teaching.
Stop writing progress reports.
Let the project speak for itself.
Parent Access is built into the Edu server. Build your workshop, enrol your students, and parents see the value automatically.