The completed form, as it WILL look, before anything is recorded.

A guardian signing on a phone sees a scrolling web form: labels, radio buttons and a signature box. What they are actually agreeing to is a document -- and until now the first time anyone saw the two joined together was after the consent had already been stored. Showing the finished page first is the difference between signing a form and signing a screenshot of one.

Writes NOTHING. It takes the same payload as the submit below, renders it onto the school's own PDF and hands it back. A guardian who does not recognise what they see goes back and edits, and no record was created in the meantime.

Unauthenticated, like the rest of the guardian flow: the token IS the authorisation. It is deliberately tolerant about missing fields -- a preview of a half-filled form is useful, and the submit endpoint is what enforces completeness.