Identification
Visitor full legal name, organization, and a government ID type or badge number where required.
A well-crafted Employee Visitor Declaration creates an auditable record of who entered the workplace, why they were there, and any conditions tied to access. It reduces liability, supports security and safety programs, and helps meet industry- or location-specific recordkeeping obligations.
Retain signed declarations according to your organization’s retention policy and applicable federal or state rules to support audits and incident response.
The internal employee who invited or is responsible for the visitor. They confirm the visitor’s reason for access, verify identity where required, and may sign or initial the declaration to accept responsibility for the visitor while on premises.
The external individual entering the site. The visitor provides identifying information, health or safety attestations if required, signs and dates the form, and must receive any site-specific instructions or restrictions documented on the declaration.
Visitor full legal name, organization, and a government ID type or badge number where required.
Name, department, contact phone or extension, and reason for hosting the visitor.
Arrival and expected departure times; actual check-out time if tracked.
Concise description of the visitor’s business or meeting purpose.
Health, vaccination, NDA, or safety acknowledgements the visitor must affirm.
Signed name, printed name, role, and date/time with a field for electronic signature metadata.
| Field | Configuration |
|---|---|
| Visitor Name | Required text field, auto-capitalize |
| Host Employee | Dropdown linked to employee directory |
| Arrival Time | Auto-populate timestamp on submit |
| Signature | eSignature field with audit trail |
Configure signer authentication and audit trails to meet organizational security requirements and to support later verification.
Store signed declaration at time of exit.
Make records available within 24–72 hours for investigations.
Review access logs monthly or per security policy.
Notify affected parties within 48 hours if required.
Produce records on request per retention rules.
| Criteria | Employee Visitor Declaration | Health Screening Form |
|---|---|---|
| Primary Purpose | access log | medical screening |
| Typical Fields | name, host, times | symptoms, exposures |
| Notarization | not typical | not typical |
| eSign Friendly |
A clinic required visitors to attest no recent infectious symptoms before entry
A general contractor captured visitor PPE confirmation and host assignments at sign-in
The receptionist often facilitates completion and may countersign to confirm ID verification. Their role is administrative: ensuring the record is complete and routed to security or HR as required, not to validate legal assertions about the visitor.
A manager or host employee can sign to accept responsibility for the visitor while on site. This signature ties the visitor’s access to an internal supervisor and supports accountability for conduct and safety during the visit.
Confirm whether the form requires notarization under policy or law.
Choose in-person notary or RON if allowed by state law.
Perform ID checks, KBA, or credential analysis as required.
For RON, retain A/V session when state rules demand it.
Have the notary make required journal entries.
Collect witness names and signatures if state or policy requires.
Include the notary block or RON certificate with the file.
Preserve audio, journal, and signed records per retention rules.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day trial | Varies | Varies | Varies | Varies |
| Bulk Send | Yes | Yes | Yes | Yes | Varies |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | Varies | Varies |
| Envelope Cap | No envelope cap | 100 envelopes/user/year | Varies | Varies | Varies |
Save signed declarations as PDF/A for long-term archiving; also keep a searchable PDF or DOCX copy for records management and redaction when needed.
Attach host approval emails, access badges issued, visitor photo ID copies, or safety briefings as exhibits to provide context for the declaration.
Store records in secure cloud repositories or on-premises DMS with role-based access and encryption at rest.
Embed metadata fields such as visit date, host, and project code to simplify search and retention lifecycle automation.