Customer portal · one decision per page

Sign-off without a PDF.

Each approval is one page: three facts, a three-sentence summary, one statement and one button. Dr. Katrin Vogel decides CR-011 there by 6 Oct, without a document attached to an email.

Electronic signature

A one-time code, then a receipt.

Approve opens a sheet that asks for the code from her authenticator app. The signature records the user, the time, the artifact version and an optional comment, and locks that baseline.

Publishing

Hartwell reads what you publish.

Publishing takes a snapshot. Edits your team makes afterwards stay internal until someone publishes again, so the customer never reads a working draft and never signs one.

Shared and internal threads

Some comments stay inside.

Every comment thread is shared with the customer or internal to your team. Internal threads are never shown to Hartwell, so Tomás can raise a check beside the question Jonas Becker asked.

For occasional use

Made for the occasional approver.

Approvers open the portal a few times per phase. It signs them in with an emailed link, works on a tablet, meets WCAG 2.1 AA with 44px targets, and signs off by keyboard alone.

Interface in English and German

German for Hartwell, English for you.

The interface ships in English and German, and each customer user picks a language. Labels are written to fit German, which runs about 30% longer. Records keep the language they were written in, and IDs are never translated.

Customer users

No charge for customer users, ever.

Invite everyone at Hartwell who needs to read, comment, raise issues, run test scripts or sign. Customer users are unlimited on every tier, so access never becomes a budget line.