# HumanProof · Submission checklist

Version: 2026-09-28 · Worksheet

- Assignment / case: ____________________
- Writer / agreed identifier: ____________________
- Recipient / responsible team: ____________________
- Applicable brief or policy and version: ____________________
- Submission channel and deadline: ____________________

## Before writing

- [ ] Agree on permitted tools and required disclosures about their use.
- [ ] Agree on recorded stages and an alternative for technical difficulties.
- [ ] Test permissions, sensor status and the writing app.
- [ ] Deliberately start the session before the work to be documented.

## Before submitting

- [ ] Save or export the final file in the writing app.
- [ ] Bind that exact file to the record when finishing, if required.
- [ ] Export the signed PDF evidence document; include JSON only as an agreed technical alternative.
- [ ] Verify the evidence and bound file yourself.
- [ ] Review metadata such as filename, session times and app identifiers before sharing.
- [ ] Include required source and tool disclosures, and explanations of interruptions.
- [ ] Keep the bound file version unchanged.

Document file: ____________________
PDF evidence document / JSON record: ____________________
Session identifier: ____________________
Interruption or later revision requiring explanation: ____________________

## On receipt and verification

- [ ] Associate the case, filenames and agreed version.
- [ ] Read record integrity and file comparison as separate findings.
- [ ] Record key trust separately; do not use a fingerprint from the same record as independent confirmation.

Date of this check and verifier version: ____________________
Record integrity: ____________________
File: matched / mismatched / not checked / no binding
Key: independently confirmed / not independently confirmed
Independent fingerprint source, if available: ____________________
Warnings / questions / responsible person: ____________________

## Record the scope of the check

For a HumanProof PDF, the browser checks the embedded record, not the visible PDF presentation or PDF/CMS signature. The native app handles the PDF signature separately. A file match confirms identical bytes, not that the session produced them. A capture gap is initially a finding to clarify. This checklist and saved local verification reports are unsigned working documents; they do not replace the signed evidence.