Session Identity
Title, course/program code, instructor name, department, and facility or virtual link with expected start and end times.
A concise CORE form reduces ambiguity about roles, timing, and participant consent while creating a durable record for compliance and reporting. When executed correctly, it documents intent and consent, supports FERPA- or HIPAA-related requirements where applicable, and provides an auditable chain of custody for instructor and participant agreements under federal e-signature law (15 U.S.C. §7001) and state UETA statutes.
The Education Workshop CORE is completed and used by distinct campus roles and external partners depending on the workshop type.
Accurate completion ensures each stakeholder can meet institutional, legal, and operational responsibilities without delay.
Title, course/program code, instructor name, department, and facility or virtual link with expected start and end times.
Concise measurable outcomes or competencies that participants are expected to achieve during or after the workshop.
Roster entries including full legal names, role (student/staff/guest), contact details, and emergency contact information.
Signed acknowledgments for activity risks, media release, FERPA-consent notes, or HIPAA-authorized disclosures when health data is collected.
Required items, digital resources, and accommodations requested to meet accessibility laws and institutional policy.
Assessment metrics, certificate issuance, data retention instructions, and follow-up communications or surveys.
| Field | Configuration |
|---|---|
| Routing Order | Sequential or parallel signer routing depending on approvals required |
| Authentication | Email link (default) or SMS code; use stronger methods if FERPA/HIPAA applies |
| Required Fields | Mark participant name, consent, and emergency contact as mandatory |
| Retention Policy | Set auto-archive and retention tags per institutional policy |
Confirm platform compatibility, supported file types, and integration needs before issuing the CORE electronically.
Date by which participants must enroll
Date when permissions automatically lapse
Scheduled start and end dates
Date to issue participant assessments
Date record moves to long-term storage
Define objectives and materials before enrollment opens.
Obtain participant and guardian signatures ahead of sessions.
Execute the session and record attendance.
Store signed CORE and related documents per retention policy.
| 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 free trial | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes (Business Premium) | Yes (limits may apply) | Yes | Yes | Varies |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
A school district standardized a CORE to collect field-trip permissions and emergency contacts from parents
A university program used the CORE to enroll attendees and collect pre-workshop acknowledgements