Scope
Define covered persons, locations, and activities so the code’s reach is clear and disputes about applicability are minimized.
A written code clarifies expectations, reduces compliance gaps, and documents the employer’s preventive measures. Under ESIGN (15 U.S.C. ch. 96) and state electronic transaction laws, an electronically signed code can be enforceable when it meets e-signature legal tests.
The template supports onboarding, annual acknowledgements, investigations, and contract attachments across public and private organizations.
The HR Director is usually responsible for tailoring the template, coordinating reviews with legal counsel, scheduling distribution, and maintaining the acknowledgement log for audits and regulatory inquiries.
Employees and contractors review the code, confirm acknowledgement by signature or e-consent, and follow the reporting and investigative procedures described in the template when incidents arise.
Define covered persons, locations, and activities so the code’s reach is clear and disputes about applicability are minimized.
List prohibited behaviors and required conduct with concrete examples to reduce ambiguity and guide enforcement decisions.
Describe multiple reporting channels, protections against retaliation, and confidentiality expectations for complainants and witnesses.
Provide a clear investigation process, timelines, decision makers, and how conflicts of interest are managed to ensure impartiality.
Outline possible sanctions and decision criteria while preserving the organization’s discretion and due-process protections.
Include a signature block or e-consent mechanism and date fields for each recipient to document receipt and acceptance.
| Field | Configuration |
|---|---|
| Signature Type | Electronic signature with audit trail |
| Authentication | Email link or SMS code per sensitivity |
| Access Control | Role-based access for admin vs viewer |
| Retention | Set automatic archival and export schedules |
Ensure the chosen solution meets required security standards and preserves a tamper-evident record for audits and disputes.
Date entered in the Effective Date field
Set a firm deadline (e.g., 30 days from distribution)
Tie to policy date and require completion within set days
Document review at least annually
Retention begins on the acknowledgement date
Create initial text and exhibits for stakeholder review.
Legal and executive approval prior to publication.
Send to signers and capture acknowledgements.
Store signed records according to retention schedule.