A permission slip response that holds up as a real consent record — name, timestamp, and a signature — not just a yes/no click nobody can point back to.
Planned Not yet started — this page describes the intended design and build plan.
Overview
Extends the shipped permission slip roster — currently yes, no, or no-answer per student — into an
attributable consent record: a name, a timestamp, and a signature behind each response, not just a tap.
It fits Notipa's self-hosting position well: the school keeps this record on its own instance, without
needing a third-party e-signature vendor in the middle.
How it will work
Signature on response. When a guardian answers a permission slip, they confirm it with a typed name by default, matched against their account, or a drawn signature for slips where that matters more.
Timestamp and device metadata. Each response records when it was given and basic device/IP metadata, building a lightweight audit trail alongside the signature itself.
Detail view on the existing roster. The response roster teachers and admins already see — who's said yes, who's said no, who hasn't answered — gains a "view signature" detail per response, rather than becoming a separate feature.
Optional per slip. A school can require a full signature only on slips where it matters (field trips, medical consent) and keep the simpler click-based response for lower-stakes notices.
Development plan
1Data model
Extend the existing permission slip response model with a signature field (typed name or a drawn-signature image), timestamp, and device metadata.
2Signature UI
A typed-name confirmation step as the default response flow.
A draw-to-sign canvas as an option for slips flagged as needing it.
3Per-slip requirement toggle
A setting on each permission slip letting a teacher or admin decide whether it needs a full signature or the existing plain click.
4Testing & export
Tests confirming signature data is stored correctly against the right student and guardian, and can't be edited after the fact.
Signature detail included in data export tools once that ships, so a school can produce a compliance record on request.
Technical considerations
Typed-name signature keeps the low-friction default response flow intact; drawn signature is opt-in, not a new requirement for every slip.
Device/IP metadata strengthens the record without requiring a third-party identity verification service, which would work against the self-hosting, no-vendor-in-the-middle positioning.
Feeds directly into data export tools once that ships, rather than needing its own separate export path.