TEMPLATE · Operations
Visitor sign-in
A visitor's name, organization, who they are seeing, arrival time, vehicle and agreement to the site rules.
Welcome. Please sign in. Keep your visitor badge visible and sign out when you leave.
About you
- Full nametext
- Emailemail
- Organizationtext, optional
- Phonephone, optional
Your visit
- Person you are visitingtextWe will let them know you have arrived.
- ReasonchoiceMeeting · Delivery · Contractor or maintenance · Interview · Event · Other
- Datetext
- Arrival timetext
- Vehicletext, optionalOnly if you parked on site.
- Badge numbertext, optionalWritten on your visitor badge, if you were given one.
Site rules
- I will follow the site's safety and security rules, stay with my host where asked, and sign out when I leave.tick box
- In an emergency I will follow staff instructions and go to the assembly point.tick box
Signature
- Visitor signaturesignature
- Visitor date signeddate signed
What people see
The template, the way the person you send it to fills it in.
In this template
What is on the page.
- About you: 4 fields
- Your visit: 6 fields
- Site rules: 2 fields
- Signature: 2 fields
It is your own copy in your workspace. Change any of it before you send.
Send it from code
Send the visitor sign-in template from your own code.
Make your own copy once, then send it to the person you name. A test key sends only to you.
npx docustay templates customize visitor-sign-in --name "Visitor sign-in"
# prints the new template's id; then send it as a test:
npx docustay send --test $DOCUSTAY_TEMPLATE_ID --party 'signer=Name <email>'curl -X POST "$DOCUSTAY_URL/api/v1/documents/send" \
-H "Authorization: Bearer $DOCUSTAY_API_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"templateId":"$DOCUSTAY_TEMPLATE_ID","parties":[{"seat":"signer","name":"Name","email":"name@example.com"}]}'What you keep
A sealed copy and its record.
Each person who signs gets the sealed PDF with a certificate of completion, and so do you. Search them in your workspace and read each one by its own record.
Questions
Quick answers.
Who fills it in?
The person you send it to. They are the visitor in this template: they type their own name and email, fill in each box and sign.
Can I send it to many people at once?
Yes. Send to a list sends your own copy to each person on it, and each person signs their own copy.
Can I change the questions?
Yes. In your workspace it is your own copy: add, remove or reword any field, then send it. The original is never changed.
Can people attach files?
14 fields make up the visitor sign-in template. Where it has a file box, people may attach a PDF or a picture, and it is stored exactly as they upload it and never converted.
Is this legal advice?
No. The visitor sign-in template is a starting point in plain words. Change what does not fit before you send it.
More like this
More operations templates.
Vehicle inspection checklist
A pre- or post-use check of a vehicle: mileage, fuel, lights, tires, fluids, damage, with photos and a supervisor's sign-off.
See every field →OperationsIncident report
What happened, when and where, who was involved, any injury or damage, what was done straight away, with witnesses and photos, reviewed by a supervisor.
See every field →OperationsService request or work order
Request work: what needs doing, where, how urgent, access arrangements, photos, and the technician's sign-off on completion.
See every field →