A running academic record for each student, built from the homework they've actually submitted and the feedback a teacher's given on it — a record of work, not a stream of moments or a points system.
Planned Not yet started — this page describes the intended design and build plan.
Overview
Several closed-source classroom apps build a "portfolio" out of photos, videos, and reward points shared
to parents. Notipa's version is deliberately narrower: the homework a student has actually submitted, in
one place per student, with whatever feedback a teacher attaches — a term-over-term academic trail, not
a curated highlight reel.
No behaviour-gamification, full stop. No points, no stars, no badges, no leaderboard, no streaks — not now, and not as a future add-on. This constraint is part of the feature, not a footnote to it, and it's what keeps faith with Notipa's existing position as a genuine communication and admin tool rather than a behaviour-gamification app wearing a communication feature.
How it will work
A per-student timeline. Guardians and teachers see every homework submission for a student in order, alongside the teacher's feedback or mark, if one was given.
Built from what's already there. No separate content to create — it's a view over homework submissions that already exist, not a new thing for a teacher to keep updated.
No separate photo/video feed. Nothing beyond the file attachment a submission already carries — no "moments" stream, no curated highlights.
Feeds report cards, doesn't duplicate them. Once report cards ships, a teacher drafting one can pull directly from a student's portfolio instead of hunting back through individual homework posts.
Development plan
1Data model
Primarily a view over existing homework submission records, grouped per student and ordered by date.
An optional teacher feedback/mark field on a submission, if not already present.
2Guardian & teacher UI
A per-student timeline view, filterable by term or class, scoped strictly to a guardian's own linked student(s).
3Report card linkage
Surface relevant portfolio entries in the report card drafting flow, once report cards exist, as reference material rather than a duplicate data-entry step.
4Testing & guardrail review
Permission tests confirming strict guardian scoping to their own child.
An explicit design review confirming the feature has no path toward points, badges, or any reward mechanic — a product guardrail as much as a technical one.
Technical considerations
This is presentation and light data-modeling on top of homework submission — not a new subsystem, and not new data a teacher has to create.
Sits deliberately apart from the file attachment already supported on homework — that's one file per assignment, not a curated stream to browse.
The no-gamification constraint applies to this feature and to anything built on top of it later.