# HumanProof · Procurement and operations checklist

Version: 2026-09-28 · For the responsible department, IT and procurement

Organisation / case: ____________________
Business owner: ____________________
Technical owner: ____________________
Intended users and scope: ____________________
Target date / your decision status: ____________________

## Make requirements specific

Enter a verifiable requirement in each row. A requirement is not a promise that the product provides it.

| Topic | Your requirement | Evidence / open question | Owner |
| --- | --- | --- | --- |
| Documents and processes | ____________________ | ____________________ | ____________________ |
| Devices, operating system and version (macOS or Windows), writing apps | ____________________ | ____________________ | ____________________ |
| Browsers and offline process | ____________________ | ____________________ | ____________________ |
| Assistive technology and alternatives | ____________________ | ____________________ | ____________________ |
| User numbers and licence scope | ____________________ | ____________________ | ____________________ |
| Submission, DMS / LMS / API | ____________________ | ____________________ | ____________________ |
| Identity association and key trust | ____________________ | ____________________ | ____________________ |
| Access and retention | ____________________ | ____________________ | ____________________ |
| Hosting / self-hosting / network boundaries | ____________________ | ____________________ | ____________________ |
| Updates, recovery and support | ____________________ | ____________________ | ____________________ |
| Contractual / legal assessment | ____________________ | ____________________ | ____________________ |
| Required external evidence | ____________________ | ____________________ | ____________________ |

## Define the technical acceptance trial

- [ ] Trial Writer on the actual macOS or Windows devices with the intended writing apps. Check the system requirements of the chosen installer.
- [ ] Check permissions and visibly unavailable signals.
- [ ] Verify PDF evidence and the JSON alternative with an unchanged test file.
- [ ] Try file mismatch, missing binding and unconfirmed key as separate cases.
- [ ] Record the PDF scope: the browser checks the embedded record, not visible PDF content or the PDF/CMS signature.
- [ ] Respect limits: HumanProof PDF 32 MiB, JSON record 16 MiB, comparison file 64 MiB.
- [ ] Actually test the offline process with the prepared environment.
- [ ] Document the data flow from device to recipient and their storage.

Acceptance criterion / result / evidence: ____________________
Open issue / owner / decision: ____________________

## Before an agreement

- [ ] Specify the licence, services, onboarding and support in the offer.
- [ ] Establish the evidenced scope of integrations, hosting and identity services.
- [ ] Assign the necessary legal and organisational assessment.
- [ ] Assess external certifications or guarantees only against available evidence.
- [ ] Name the person responsible for subsequent substantive assessment.

Next step and contact: ____________________

This template is not an offer or evidence of certification. It does not set contractual terms or operating commitments. Product contact: kontakt@extraara.de. Do not include confidential manuscripts, credentials or private keys in an initial enquiry.