What is stored when you sign a form

No authorization form can exist today

Nothing in PTRS can create a form for a guardian to sign: no screen, no service, no way for a club to add one. Nothing on this page has ever actually run in an installed copy of PTRS.

It is written down anyway, because an e-signature is a legal record, and whoever eventually builds the missing half needs to know exactly what the existing half already keeps, and does not.

The record

Signing a form saves one signature record with the fields below.

Field	Value	Note
Form	The form being signed	Not applicable
Guardian	Already proven to belong to whoever is signing	Not applicable
Member	The child from the request	Not applicable
Signed at	The exact moment PTRS wrote the record	PTRS's own clock, not the moment the guardian actually read the form
IP address	The address the request came from, or the word "unknown"	Behind the usual server setup this is the address of that server, not necessarily the guardian's own device, unless specifically configured otherwise
Device information	Whatever the browser sent	Not applicable
Answers to the form's own questions	Whatever the screen sent	Never checked for anything at all
The signature itself	Whatever the screen sent	A very large text field, meant for an image, and never checked for anything at all

PTRS refuses a second signature for the same form, guardian and child combination, with a message saying the form was already signed for that child.

What is not stored

There is no digest of the form's own wording at the moment it was signed, no version number on the form itself, and no snapshot of the form's title, description or questions copied into the signature. So if a form is edited after being signed, the signature still points at it, and nothing records what was actually agreed to at the time. There is also no way to withdraw a signature once made, and no field marking one as withdrawn or replaced. And there is no field at all for the signer's own typed name; see below for where that value actually ends up instead.

The act of signing is still covered by PTRS's own tamper-evident audit trail, which permanently records that a signature happened, naming the form, the guardian and the child. So that a signature happened is durable, even though exactly what was agreed to is not.

What the screen actually sends

The Forms screen collects a typed name and sends it as the signature image itself. So the field meant to hold an image ends up holding a plain name such as "Denise Thompson", and the field meant to hold the answers to the form's own questions is never sent at all, so those answers are always blank.

Two more things about that screen are worth knowing. The I agree to the terms above checkbox has no effect whatsoever: it is not connected to anything, so the sign button works whether it is ticked or not. And signing always signs for the first child shown on the card, even when more than one child's name is listed on it, with nothing on screen saying which child was actually covered.

What the document actually contains

The Download PDF action is named for a document and does not actually produce one: it returns plain data instead, with no document formatting and no file at all.

Of the signature itself, that reply carries exactly one thing: the time it was signed. The signature does not appear. Not the typed name, not the address it came from, not the device information, not the answers to the form's questions. A downloaded record would show the form, the child's name, the guardian's name and a timestamp, and nothing else that actually distinguishes a signed form from an unsigned one beyond that timestamp being present at all.

Nothing on screen even reaches this action in the first place: the button behind Download PDF does nothing when tapped, and the one piece of code that could build its own web address has nothing calling it either. Even if something did call it, the address it would build carries nothing proving who is asking, so opening it directly would be refused anyway.

Which children a completed form claims

The list of forms still needing a signature is correct: it only ever lists a child who has genuinely not signed yet.

The list of completed forms is not. For every signed form, it lists every child linked to the guardian as though each one had signed, without checking which child the signature actually covers.

So a guardian of two children who signed a photo release for one of them would see that form listed under Completed, naming both children, and at the same time, correctly, under Pending, naming only the one who still needs to sign. The same form appears on both tabs, and the completed tab states a consent that was never actually given for one of the two children.