Signing example
Policy acknowledgement e-signature
A policy acknowledgement e-signature turns a compliance chore into a per person record: one employee, one envelope, one certificate naming the version acknowledged. This page shows the information security policy from the documents examples acknowledged by one employee through three required statement marks, and then what running the same envelope across a team of forty actually looks like.
The document itself is written out in full on its own page:read the wording there. This page is only about signing it.
Who signs what
- Ha-eun Park, the employee
- Three statement boxes, all required · Name, signature and stamped date · Version 3.1 named on the acknowledgement page · Email link
The signing journey
Step 1
The summary rides with the acknowledgement
The envelope carries the two page staff summary of the policy, quoting clause numbers from the full fifteen page document that lives on the intranet and on its own documents example page, with the acknowledgement page naming version 3.1.
Step 2
Six fields for one employee
Three required checkboxes sit over the printed statements, that the policy summary was read, that incidents will be reported within thirty minutes, and that the consequences are understood, joined by name, date and signature.
Step 3
Marks, then a signature
Ha-eun types a mark into each box, and the portal refuses to finish while any required box is empty. Her name arrived prefilled from the invitation, her signature is drawn once, and the date stamps itself.
Step 4
The record files itself
The certified acknowledgement goes to the employee and the sender by email, and the certificate records the consent gate's timestamp and version alongside the seven event log. The version acknowledged is fixed inside the document and covered by its hash.
Running it for a team of forty
Each envelope is one signing event, so forty employees means forty envelopes sent from the same saved PDF, about a morning's setup the first time and minutes on renewal. The envelope list then becomes the compliance dashboard: one row per person with a badge, a search box and status filters. There is no export button, so the list itself is where you read completion, and a row still on Waiting after a week gets a resend, which rotates that person's link and logs the resent event.
What the signed page and certificate show
The acknowledgement page shows three X marks against the printed statements, the employee's name, signature and the stamped date, with the version number printed beside the fields. The certificate lists one signer verified by email link, the consent timestamp and version, both document hashes, and seven chained events from Envelope created to Signed.
How to adapt this envelope
Annual renewal is the same envelope against the updated summary, and the new certificates sit beside the old ones per person. A code of conduct or WHS policy swaps the document and the statement wording. For contractors, the same flow works with their external addresses; nothing about the envelope cares who employs the signer.
What makes this signing flow work
The version acknowledged is the version attached
The acknowledgement page names version 3.1 and the document hash in the certificate covers the exact pages sent. When the policy moves to 3.2, the old records still prove precisely which text each person acknowledged, which is the question an incident review actually asks.
Three marks beat one buried signature
Reading, reporting and consequences each carry their own required X on the signed page. An employee cannot acknowledge the policy without individually marking the thirty minute reporting rule, which is the one the organisation most needs remembered.
Consent is recorded twice
The portal's consent gate logs its timestamp and version before any field can be touched, and the three marked statements sit on the page itself. The certificate carries both, so the record is not a single checkbox anywhere.
Questions people ask
Can one envelope go to forty employees?
No. An envelope is one document with one set of signers, and an acknowledgement is personal, so it is one envelope per employee. That is what makes each certificate a clean individual record naming who acknowledged which version and when.
Do employees tick the boxes?
They type a mark into each box and the stamped PDF prints an X wherever a box holds any value. All three are required, and the portal blocks submission while any sits empty, naming the missing one beside the Finish signing button.
Where is the policy version recorded?
In the document itself, on the acknowledgement page and in the summary header, both covered by the document hash printed in the certificate. Separately, the signing consent gate records its own version and timestamp. Nothing depends on anyone remembering which PDF went out.
Can I export a list of who has signed?
No export exists. The envelope list is the record: search, status filters and a badge per envelope. For reporting beyond that, the certificates themselves are the per person evidence, one PDF each, retrievable from each envelope's status page.
What happens to stragglers?
Their envelopes expire thirty days after creation, and an expired link answers plainly that the request has expired. Before that, a resend rotates the link and often shakes an acknowledgement loose; after expiry, send a fresh envelope rather than resurrecting the old one.
Does the employee get to keep a copy?
Yes. The completion email delivers the certified acknowledgement to the employee as well as the sender, so the person bound by the policy holds the same record the organisation files, marks, signature, version and all.
Build your own in about a minute
The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.
Make my policy acknowledgement e-signatureOther signing examples
Employee handbook acknowledgement e-signature
An acknowledgement only proves something if the whole handbook was in front of the person who signed it. This envelope sends the complete Northcote Health Collective handbook, version 3.1, with every field on the last page and none on the four pages before it, so the signer scrolls the document they are acknowledging rather than a one page summary of it.
Consent form e-signature
A consent form e-signature needs two things an ordinary signature does not: proof of who consented and a record of exactly what they agreed to. This two page participant consent for the fictional Marlowe Sleep Study captures both, with six required statement boxes, a six digit emailed code, and an audit trail this page walks through event by event.
Photo release form signature
A photo release form signature for a minor needs three people on one document: the model, a parent or guardian, and the photographer. This release for a fictional dance studio's promotional shoot shows all three signing one envelope in parallel, with the shoot date and the permitted use typed into the photographer's own fields so every signature is given against a written scope.
Want the steps in the builder? Read Send a PDF for e-signature, then Send a document for signature. For everything this generator can do, see the signing flow maker.
Sources
Written and checked by the OneCraft team. Last checked .