CTE Clinical Site Affiliation Agreement

This template includes the core fields needed to set up a student clinical placement at a healthcare facility: participating organizations, placement dates, student level, allowed and restricted activities, supervision, required training, liability, confidentiality, and signatures. It is designed to document who is responsible for what before the placement begins. The structure also helps you capture contact details for follow-up and incident reporting. It is a starting point for a site-specific agreement, not a generic policy form.

The agreement is typically completed by the school or CTE program, the healthcare facility, and the program coordinator. The authorized signers should be the people who can approve placement terms and commit their organization to the agreement. If your district or facility requires legal review, route it before signatures are collected. The form works best when one person owns coordination and confirms all required approvals are in place.

Use it before a student begins any clinical rotation, practicum, or work-based learning placement in a healthcare setting. It is especially useful when the placement involves direct patient contact, facility orientation, or role-specific supervision requirements. Do not wait until the first day of the rotation, because missing signatures or unclear scope can delay placement. If the site changes, the agreement should be updated before students move to the new setting.

The template separates allowed student activities from restricted activities so the placement scope is clear. It also includes fields for the supervision model, whether a preceptor is required, and any mandatory training or orientation. That makes it easier to use progressive disclosure instead of listing every possible task for every student. If a student level changes, update the scope rather than reusing an older version with outdated permissions.

This agreement helps document confidentiality expectations, incident reporting, liability acknowledgment, and required training for a healthcare placement. It also supports minimum-necessary handling of student and placement information by collecting only the fields needed to approve and manage the site relationship. If your program handles any PII, include a clear privacy acknowledgment and limit access to authorized staff. For healthcare settings, align the template with facility safety rules and any local education or clinical placement requirements.

Common mistakes include leaving the allowed and restricted activities too vague, skipping the emergency procedure summary, and using free-text fields where dates or contact emails should be structured fields. Another issue is marking every field required even when the information is not needed for approval. Teams also sometimes forget to confirm whether the facility orientation is required before the first student shift. A final pitfall is collecting more personal data than necessary, which creates avoidable privacy risk.

Yes. You can tailor the clinical setting, training requirements, supervision model, and restricted activities to match a nursing assistant, allied health, or health sciences program. If the facility has its own onboarding checklist or incident process, add those as conditional fields or linked instructions. You can also adapt the signature block to match district, hospital, or program approval workflows. Keep the core agreement consistent so each site is reviewed against the same baseline terms.

This agreement often works alongside student placement rosters, training completion records, and facility orientation checklists. If your workflow uses document storage or approval tools, keep the signed agreement linked to the placement record and the student cohort. The incident reporting contact can also be reused in your emergency and escalation workflows. Avoid duplicating the same data in multiple places unless you need it for audit trail or approval tracking.

An ad-hoc email can confirm a placement, but it usually leaves gaps around supervision, liability, and confidentiality. This template creates a consistent record with clear fields, signatures, and a defined scope for each site. That makes it easier to review, compare, and update agreements across multiple facilities. It also reduces the chance that a student starts with unclear expectations or missing approvals.