Scope of Work
Describe specific tasks, systems, hours, and supervisor names. Limit access by role and avoid open-ended language that could expand duties beyond training objectives.
A Student Technician Agreement protects the institution, the student, and third parties by defining expectations, limiting liability, documenting consent to access systems and data, and establishing IP and confidentiality rules. For e-signature and electronic records, ensure the process meets binding-signature standards under the federal ESIGN Act (15 U.S.C. ch. 96) and applicable state UETA rules; some transactions still fall under statutory exceptions. Including data-handling clauses helps meet FERPA or HIPAA obligations where the work involves education records or protected health information.
Educational institutions, campus IT departments, healthcare training programs, and small employers use Student Technician Agreements to manage student workers who perform technical tasks.
The agreement is suitable for paid and unpaid positions, short-term projects, practicum placements, and remote technical support roles where access, supervision, or privacy obligations exist.
Describe specific tasks, systems, hours, and supervisor names. Limit access by role and avoid open-ended language that could expand duties beyond training objectives.
Specify required orientation, ongoing supervision, the responsible faculty or manager, and processes for reporting incidents or escalating technical problems.
Define confidential information, handling requirements, permitted disclosures, duration of confidentiality, and data return or deletion procedures.
State applicable laws (FERPA, HIPAA where relevant), any Business Associate Agreement (BAA) requirements, and restrictions on accessing or downloading protected records.
Address ownership of work product, inventions, or code; include assignment, licensing, or permitted student use for academic purposes.
List devices issued, responsibilities for care and return, liability limits, insurance expectations, termination notice, and grounds for immediate dismissal.
| Field | Configuration |
|---|---|
| Signer Order | Student first, then supervisor, then authorized institutional signatory |
| Authentication | Email verification or SMS code; use stronger methods if PHI access is needed |
| Conditional Fields | Show HIPAA addendum only when clinical systems access is granted |
| Storage | Save signed PDF with audit trail in a secure records system |
Choose a platform that supports secure eSigning, audit trails, conditional fields, and secure storage to meet legal and privacy obligations.
Access typically granted within 1–5 business days after signed agreement
Required training usually within 7–14 days of start
Payroll or stipend setup can take one full pay cycle
Devices due within 7 days of termination unless otherwise agreed
Retain signed agreement per institutional retention schedule (see retention section)
Signed and stored; triggers account provisioning and equipment issuance
Completion required before unsupervised system access
Supervisor evaluates performance and compliance with rules
Return equipment, revoke access, or extend agreement as approved
A university hires students for after-hours helpdesk support and limits access to non-production systems
A teaching hospital places a student in a medical records support role with restricted EMR views
| 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 | Yes, 7-day trial | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |